Privacy policy

What is never sent anywhere

The images you open are not uploaded. Separation, halftoning and packaging happen in your browser, on your machine. That is not a promise in a policy, it is how the program is built.

The finished films, preview, PSD, PDF and report are produced locally too, and saved wherever your browser saves them. They never reach the server.

What the server stores

• Account. An email address and the identifier from your sign-in provider (Google), if you used one. There is no password, because we do not store one because we never create one.
• Session. A hash of the cookie value, when it was created and when it expires. The value itself is not stored, so a leaked database cannot be used to sign in as you.
• Export ledger. Credits and debits: date, source, amount, plan and a reference to the payment.
• Export records. An identifier, the file name, the formats, a fingerprint of the settings, timestamps and status. The file name does reach the server: it is what labels the rows in your own export history.
• Feedback messages. The text, its kind, your address and the technical context: version, ink count, document size, line count.
• Messages from the form on the site. The email address, the message and the page it was sent from. We do not record an IP address, neither yours nor anyone’s: the spam protection is built so that it does not need one.
• Step counter. To know how many people opened the tool and how many of them got as far as a separation, we record three things: the date, the name of a step from a short list, and a hash. The hash is computed from your address and browser together with a random key that is created for one day and disappears with it, so neither your address nor the hash itself is kept any longer, and neither can tie you to yesterday or to your account. No page name, no text and none of your data goes into it.

The fingerprint is a short number computed from the export settings. An image cannot be reconstructed from it; it exists so that re-exporting the same thing within a day is not charged twice.

Payment

Payments are handled by Creem, a payment provider acting as merchant of record. Card details are entered on their page, never pass through ColorLayers and are not stored here.

From them we receive confirmation of payment with an order or subscription identifier, which is what appears in the ledger. Their handling of your data is governed by their own policy.

Cookies

One cookie is used: the session, so the application knows you are signed in. There are no advertising or analytics cookies.

Page views are counted with Cloudflare Web Analytics. It sets no cookie, gives you no identifier and does not follow you to other sites: it counts requests for pages rather than people. It is not present in the application.

Our own step counter, described above, sets no cookie and gives you no identifier.

Your settings (language, units, shop profile) and, if you were working on artwork, its draft are also kept in your browser. All of that stays on your device and is never sent to the server.

Who has access

The owner of the service has access to the database. Feedback messages and messages from the form on the site are forwarded to a private Telegram chat so they can be answered, together with your address, because the reply goes to your email.

Data is not sold and not passed to third parties, other than the payment provider without which payment cannot be taken.

How long, and how to delete it

The export ledger is kept for as long as the account exists: it is a financial record, and it is what explains where your balance came from.

To delete the account along with its sessions, export records and messages, write to the address below. Deletion is final, and any remaining balance goes with it.

Contact

colorlayers.hello@gmail.com, or the contact form in the application, under the account menu.

Company details will appear here once the legal entity exists. This document describes how the system works as of the date it was last changed, and is not legal advice.