Privacy Policy
Last updated: 26 October 2026
Who this applies to
This policy covers colorise.online, a free set of browser-based colour tools run as an independent project. You can reach us at [email protected]. The site has no accounts, so we hold no name, email address or password for visitors.
The sections below describe what the site's code does today. If that changes, this page changes and the date above is updated.
What stays in your browser
Images you open in Photo mode are processed in your browser. They are not uploaded to our servers and never leave your device. The same goes for the colours you pick, your recent palettes and your history: they are kept in your browser's local storage on your device and are not sent to us. Clearing your site data removes them.
Pages like the converters and the palette scale are computed on our server from the colour in the address you open (for example a HEX code). That value is part of the web address, so it can appear in server logs as described below.
Analytics: Google Analytics 4 with Consent Mode v2
We use Google Analytics 4 to understand which tools and pages are used. It runs in Google Consent Mode v2 (advanced mode). When a page loads, every consent signal (analytics storage, ad storage, ad user data, ad personalization) starts as denied and Google's ads data redaction is switched on.
Until you choose Accept, Google Analytics sends only cookieless, non-identifying pings: no analytics cookies are set and no persistent identifier is stored on your device. Like any request, these pings reach Google's servers from your network; Google states that GA4 does not log or store IP addresses. Choosing Reject keeps it that way.
If you choose Accept, Google Analytics may set cookies (named _ga and _ga_ followed by the property id) to recognise a returning browser and measure visits. The product events we send are: switching mode (pick, photo, read), clicking Fix, copying an export (with its format), dropping an image, using the eyedropper, finishing or skipping the first-run tutorial, and clicking an example scenario. They contain no image or colour data from your files.
Advertising: Google AdSense
The site may show ads to cover hosting costs. The AdSense script is not loaded at all until you choose Accept, and no ad is requested before that. If you choose Reject, no ad script is loaded.
After you accept, Google and its advertising partners may use cookies and similar identifiers to show, limit and measure ads, which can include personalised ads. How Google does this is explained in How Google uses information from sites or apps that use our services. You can review and change personalised advertising in Google's ad settings.
Our own counting (no Google)
We count visits ourselves so we can see which pages work, without sending that data to a third party. This runs on our server and is kept in files on it. It does not use Google.
- Page views. When an HTML page is requested, we record the page path, the country (read from a header added by our CDN, Cloudflare), the referring site, the time, and a visitor identifier. Your IP address is used to make the identifier and to guess whether the visit is automated, but it is not stored.
- The visitor identifier is kept in a first-party cookie named kroma_vid, valid for 400 days, and mirrored in your browser's local storage. Before the cookie exists, the identifier is a hash of the date, your IP address and your browser string. It is not used for advertising and is not shared. You can delete the cookie in your browser settings; email us if you want records tied to an identifier removed.
- Product actions. The same identifier is attached to the product events listed above (mode changes, Fix clicks, exports and so on) in a first-party log. The log keeps the most recent 50,000 records and older ones are dropped.
- Search engines and other crawlers are recognised and counted separately, without a visitor identifier.
Our cookieless heartbeat
A small first-party script (hb.js) measures how many real people use the site and for how long. It sets no cookie and writes nothing to your storage. It does not send anything until you interact with the page (moving the pointer, scrolling, typing or touching) while the tab is visible.
From then on it sends small messages to /api/hb on this site: the page path, the seconds of active time since the last message, whether the device has a touch screen and, on the first page of a visit, the host name of the website that referred you if it is a different site. It stops when you hide or leave the tab, skips automated browsers and is not loaded on admin pages.
The server turns your IP address and browser string into an identifier with a keyed hash. The key is random, kept only for the current UTC day and replaced at 00:00 UTC, so an identifier cannot be linked from one day to the next and cannot be reversed. The raw IP address and browser string are not stored. Only daily totals (visitors, sessions, active time, top pages, referrers, countries and device types) are kept, for 8 days.
Server logs and our CDN
The site is served through Cloudflare and runs on a web server. Like any website, those providers process the technical data a request contains (IP address, time, requested address, browser string) to deliver pages, block abuse and keep a standard access log. We do not use these logs to identify individuals. Their handling is governed by the providers' own policies.
Cookies and local storage on your device
- af_consent (local storage): your cookie choice, Accept or Reject.
- NEXT_LOCALE (cookie, 1 year): the language you last used.
- kroma_vid (cookie, 400 days, plus local storage): the first-party visitor identifier described above.
- _ga and _ga_* (cookies): only after you accept analytics.
- Google advertising cookies: only after you accept, and only when ads are shown.
- Colour history, recent palettes and the tutorial flag (local storage): stay on your device.
Changing or withdrawing consent
The cookie banner appears on your first visit. You can change your choice at any time with the Cookie settings button in the footer of every page, which opens the banner again. Choosing Reject sets all four consent signals back to denied for Google. Withdrawing consent does not delete data Google already collected; use Google's ad settings and the Google Analytics opt-out add-on for that.
Legal bases and your rights
Where UK GDPR or GDPR applies, we rely on your consent for analytics cookies and advertising, and on our legitimate interest in running, securing and understanding use of a free site for the first-party counting described above. You have the right to access, correct, erase, restrict or port personal data we hold, to object to processing based on legitimate interests, to withdraw consent, and to complain to your data protection authority.
If California law applies, you have the right to know, delete and correct personal information and to opt out of its sale or sharing. We do not sell personal information. Advertising cookies set by Google after you accept may count as sharing for cross-context advertising; choosing Reject, or the Cookie settings button, opts you out of that. We do not discriminate against anyone for making these choices.
Most identifiers we hold are hashed and cannot be tied back to you without more information from you. To make a request, email [email protected] and tell us what you need.
International transfers
Google and Cloudflare operate worldwide, so data they process may be handled outside your country. Their own policies and transfer safeguards apply to that processing.
Children
The service is not directed at children under 16, and we do not knowingly collect personal data from them.
Changes
We may update this policy as the site changes. The "Last updated" date at the top will change when we do.