What we keep, and what we never see.

Three tools send a file to the server: the image optimizer, the image converter and the image downloader. The file travels over HTTPS, is decoded by the image library in the worker handling your request, and the result is streamed straight back to you. Files are held in memory for the life of that request only — they are not written to disk, not attached to your account, and not queued for later use.

The image downloader is different in one respect: you give it a public page URL, so our server fetches that page and the images it references, and returns them to you. The URL you enter is therefore visible to us in request logs for as long as those logs are retained.

Requests to these endpoints carry your IP address, as any web request does. We use it to rate-limit abuse and nothing else.

Every core tool works without an account. If you create one — to save palettes, saved colours or vault entries — authentication is handled by Clerk, which stores your email address and password hash and sets a session cookie. We receive the account identifier and email address, never your password.

Passwords you choose to keep in the Vault are encrypted on the server with AES-256-GCM using a key derived from a secret held in the deployment environment. The plaintext is never logged, never returned in a list response, and revealed only to your own authenticated session when you ask for it. Deleting an entry deletes the stored ciphertext.

If you sign in, we also store the items you explicitly save — palettes, colours and vault entries — against your account. Nothing is saved implicitly, and signing out does not delete what you chose to keep.

FileDrops exists to store files, so this is the one place where uploads are written to storage. When you create a drop we keep the file itself, its name and size, the expiry you chose (one to seven days), a download counter, and a random owner token that ties the drop to your browser.

A drop link is unlisted: anyone who has the link can download the files until the drop expires, is deleted, or reaches its download limit. Treat a link as public for the duration you set, and do not use FileDrops for permanent backups or for material you are not entitled to share — see the terms for the acceptable-use rules.

Several tools remember state locally, in localStorage, so a refresh does not wipe your work. That data never reaches our servers and can be cleared at any time from your browser settings:

• Saved and favourite palettes in ColorLens and the palette explorer.
• The last two comparisons in the code diff checker, and its view preferences.
• Optimizer settings and the FileDrops owner token for this browser.
• Your theme choice, where the tool offers one.

We measure traffic to know which tools are used and which pages are slow. Two systems do that: Vercel Analytics and Speed Insights, which report aggregated, cookieless usage and performance measurements, and Google Tag Manager, which loads our tag configuration and may set cookies.

Cookies you may receive: an authentication session cookie if you sign in (Clerk), an owner cookie that identifies your own FileDrops in this browser, and analytics cookies set through Tag Manager. We do not run advertising or cross-site tracking pixels.

You can block or delete all of these in your browser; the tools keep working. Blocking cookies does mean saved items and FileDrops ownership will not persist between visits.

These are the only services that can touch data on our behalf, and what each one sees:

• Vercel — hosting and edge delivery; sees request metadata including IP addresses.
• Google Tag Manager — tag delivery and analytics cookies.
• Clerk — account creation, sign-in and session management.
• Sanity — the content API behind the blog and approved testimonials; testimonial forms create a private pending moderation record.
• Email provider — your review and contact details pass through our configured SMTP mailbox to deliver the moderation notification.
• Cloudflare R2 — object storage for FileDrops once enabled on this deployment.

We do not sell data, do not share it with advertisers, and do not use your files to train anything.

• Uploaded files (FileDrops) — until the expiry you chose, or until you delete the drop, whichever comes first. One to seven days.
• Optimizer, converter and downloader files — for the duration of the request only.
• Account data — until you delete your account or ask us to.
• Saved palettes, colours and vault entries — until you delete them.
• Server logs — a short, rolling window for security and abuse prevention.
• Email — for as long as it takes to answer, then archived for reference.
• Testimonial submissions — retained while pending moderation; approved entries remain until permission is withdrawn.

You can use every core tool without giving us anything identifiable. Beyond that, you can clear local tool state from your browser, delete saved items from inside the tools, delete FileDrops from the owner view, and ask us to delete your account data.

If you are in the EU, UK, or another region with data-protection law, you can ask for a copy of what we hold about you, ask for it to be corrected or deleted, object to processing, and complain to your local supervisory authority. Mail info@colormind.space and we will respond within 30 days.

The service is not directed at children under 13, and accounts are not knowingly created for them.

When this policy changes materially, the date at the top changes with it and the diff is described in the release notes where we keep public notes on the site. Continuing to use the tools after a change means you accept the updated version.

Questions, deletion requests, or anything else privacy-related: info@colormind.space.