Color is personal.
Your data is, too.
This policy explains what Arctic Code Labs Inc., operating QRCO, processes when you use qrco.ca, the Studio, and QRCO’s MCP connections.
Information we handle
Studio and public MCP requests
QRCO processes the colors, palette settings, names, image pixel arrays, and other tool inputs you or your AI client send so it can return the requested result. The public MCP endpoint does not require a QRCO account. QRCO does not ask your AI provider for your full chat transcript. Your AI provider handles its copy of your conversation under its own terms.
Accounts and saved work
If you sign in with Google, QRCO receives a Google account identifier, display name, and email address to identify your QRCO account. QRCO stores palettes and related names, roles, versions, and publication settings that you save. Account MCP connections also record the authorized client, approved scopes, grant and token state needed to manage access. QRCO stores token hashes rather than plaintext access or refresh tokens in its account database.
Browser and operational information
The Studio uses browser storage for guest palettes, theme preferences, and limited sync state. Signed-in sessions use secure, HttpOnly cookies. QRCO records anonymous daily counts and response times for known MCP tools and tagged Studio arrivals; these aggregates do not contain tool arguments, palette contents, IP addresses, or account identifiers. When private operational analytics is enabled, QRCO also records daily tool activity linked to the authenticated QRCO account ID, public/account request counts, outcome categories, latency buckets, and request-origin country when supplied by a trusted hosting source. Country may describe an AI provider’s server rather than the person using it. The private owner dashboard can resolve account IDs to the name and email already stored in the account; it does not copy those details into activity files. These records exclude raw IP addresses, prompts, tool arguments, palette contents and credentials. Separate authentication diagnostics record time, route, status, and bounded reason codes without tokens or account identities. Hosting infrastructure may also create security and access logs, such as request time, path, and IP address.
Return-visit measurement
On the Studio homepage and connection page, QRCO uses a random first-party browser cookie to estimate return visits. It lasts up to 90 days, is separate from account login, and is not linked to account identities. Private analytics stores a keyed digest rather than the cookie value. For public MCP tool calls, QRCO may calculate a keyed digest from the request IP resolved by its trusted-proxy rules and a coarse client family. No raw IP or user-agent string is saved in these recurrence records. These are pseudonymous connection estimates, not unique people: an AI provider may share an address across users or change addresses. Recurrence records are retained for up to 90 days; clearing cookies or rotating the private key resets recognition. Do Not Track and Global Privacy Control disable this recurrence measurement when supplied with the request.
You can change return-visit measurement for this browser below. This preference is separate from account authentication and Google Analytics or advertising settings. Disabling it clears the return-visit cookie; a first-party opt-out cookie remembers that choice for up to one year.
Analytics and advertising
The Studio homepage loads Google Analytics and Google AdSense. Those services may collect device, browser, and interaction data and use cookies or similar identifiers under Google’s policies and your browser or Google settings. The public MCP tool responses themselves do not contain ads.
Why we use it
We use this information to answer color requests, provide account features you choose, authenticate and secure sessions, honor permissions and publishing choices, prevent abuse, troubleshoot failures, and understand aggregate service reliability. We do not need your Google password or one-time sign-in code, and you should not send either to QRCO support or an AI agent.
How long it remains
- Public MCP request content is processed to answer the request and is not saved in QRCO’s daily usage aggregate. A connected AI provider may separately retain the request under its own policy.
- Anonymous QRCO tool and tagged Studio usage aggregates are retained for up to 90 days. Account-linked operational activity is also retained for up to 90 days. QRCO’s account-authentication diagnostics are retained for up to 7 days.
- Login challenges expire after 5 minutes. Browser account sessions expire after at most 7 days and become invalid after 1 day of inactivity. OAuth account grants last up to 30 days unless you disconnect sooner; access tokens expire after 15 minutes.
- Saved account palettes, version history, and account profile information remain while the account is active or until you delete applicable palettes or request account-data removal. A published page remains available until it is unpublished or removed. Copies made by others are outside QRCO’s control.
- Guest palettes and preferences stored in your browser remain until you clear them or the browser removes them. Hosting logs, backups, and Google-managed analytics or advertising data follow those providers’ retention settings; contact us for information about QRCO’s current host configuration.
Your choices
You can use the public color tools without signing in, delete browser-stored guest palettes, remove individual saved palettes in the Studio, unpublish a public palette, and disconnect an AI agent from Agent access. Browser and Google settings offer controls over cookies, analytics, and personalized ads. To request access to, correction of, or deletion of account information, contact us; we may need to verify account ownership first.
Questions or requests
Contact Arctic Code Labs Inc. at girmayf@gmail.com or see Support. We may update this policy as QRCO changes; the date above shows the latest version.