What we store,
and what we do not

Who is responsible for your data

The data controller is Michał Zaborowski, a sole trader registered in Poland under the business name whitecode Michał Zaborowski, ul. Kazimierza Morawskiego 5/14, 30-102 Kraków, Poland, NIP 6612315577. For anything in this document, write to the contact form — a person reads it.

The short version

• Your images never leave your computer unless you attach a screenshot to a bug report yourself. The application does all of its work locally. It does not upload photographs, scans, previews, file names or folder paths, and it has no analytics about how you use it — with one exception tied to the licence: once a licence or trial has been activated on your computer, its licence check counts how many times a day the application starts and notes whether a debugger was attached, so a tampered licence can be noticed; section 1 says exactly what. Two exceptions, both yours to make: crash reporting, which is switched off until you turn it on and carries no image data, and a bug report, which is sent only when you press SEND and carries a screenshot only if you tick the box — section 1 says exactly what each one sends.
• The application does not need an account. A trial needs no email address and no card.
• There are no accounts here at all. The forum is a read-only archive, and the conversation has moved to Discord, which is a separate service — section 4.
• One thing you send us is stored: a bug report you send from the application — section 1 says exactly what, and it is deleted whenever you ask. The early-access requests we kept until 9 October 2026 are covered in section 3.
• No cookies of our own. No advertising, no analytics, no tracking, and therefore no cookie banner.

1. The application and your licence

To check that a licence or trial is valid, the application talks to api.trichromalab.com. This is what it sends, and nothing else:

Machine identifier

A SHA-256 hash derived from your operating system's own installation identifier (the IOPlatformUUID on macOS, MachineGuid on Windows, /etc/machine-id on Linux) — or, if the system will not answer, a random value generated once and stored on your machine. We store the hash, never the underlying value. It lets one licence run on a fixed number of machines and stops one trial being taken repeatedly. It is not a hardware fingerprint and does not identify you by name. Purpose: performing the contract (Art. 6(1)(b) GDPR) and preventing abuse of the free trial (Art. 6(1)(f)).

Number of rolls processed

A single counter, so a trial can end after fifteen rolls. It carries nothing about the rolls themselves. Purpose: Art. 6(1)(b).

Colour-engine version

A short code naming the version of the colour engine this build of the application uses, so the licence check returns the key that unlocks it. It is the same for everyone on a given version and says nothing about you or your work. Purpose: Art. 6(1)(b).

Starts, and whether a debugger was attached

Once a licence or trial has been activated on your computer — and after it expires, for as long as the application keeps checking it — each licence check also says whether it happened as the application started, and whether a debugger was attached to the application at that moment. We keep, per machine identifier and day, how many times the application started and how many checks found a debugger — together with the licence identifier the check already carries, and nothing about what you did in the application. It is how we notice a licence being tampered with or passed around: a person looks at it, and nothing is blocked automatically. The counts are deleted after 90 days. A trial that was never activated sends nothing. Purpose: Art. 6(1)(f), our interest in preventing abuse of the licence.

Your IP address, hashed

When a new trial is registered we count registrations per network to stop automated farming. The address is hashed with SHA-256 before it is stored, and the raw address is never written down. Counters older than the current window are deleted. Purpose: Art. 6(1)(f), our interest in not giving the product away to a script.

Licence details, if you have bought one

Licence key and identifier, tier, status, expiry, and the email address and name given at purchase. Purpose: Art. 6(1)(b), and Art. 6(1)(c) for the retention that tax law requires.

The application sends no image data of any kind — not a photograph, not a thumbnail, not a histogram, not a file name — except a screenshot you attach to a bug report yourself, described below.

Crash and fault reporting — off unless you turn it on

The application can report a crash, or a licence check that stopped granting, so it can be fixed. It is switched off by default and sends nothing at all until you turn it on in Settings; turning it off again stops it immediately. Reports are handled by Sentry on their European servers.

A report carries the fault and where it happened, the application version, and an anonymous identifier for the machine. It does not carry your pictures, file names, folder paths, licence key or email address. Screenshots and view hierarchies are disabled, performance tracing is off, and every message passes a redaction step before it leaves. Your IP address is not attached — the reporter's personal-data option is disabled, as is the machine name the library would otherwise fill in by itself. Purpose: your consent (Art. 6(1)(a) GDPR), which you may withdraw at any time by switching the setting off.

Reporting a bug from the application

The application has a button for reporting a bug or sending us feedback. Nothing is sent until you press SEND; then it goes to trichromalab.com/report, our own site. The form shows you what will go:

What you write, and whether it is a bug or feedback

Kept exactly as you typed it.

An address to reply to, if you leave one in the form

Used only to answer you.

About the application and your computer

The application's version and build, your operating system and its version, the amount of memory, the number of processor cores, whether it is a release or a development build, the first 16 characters of the machine identifier described above, and your licence status (trial, licensed and so on).

Where you were in the application

The module you had open, and the rig, camera, film and light it was set to — never a file name or a folder path.

A screenshot of the application's window — only if you tick the box

Off unless you tick it, for each report. It shows whatever was on the window at that moment, your photograph included if one was open.

Your IP address, hashed

To limit how many reports one network can send in a day. Hashed with SHA-256, never stored raw, and the counters are deleted after two days. Purpose: Art. 6(1)(f), keeping the inbox usable when a script finds it.

A report is kept as one row in a database on Cloudflare, and a copy is emailed to us — with the screenshot attached, if there was one. It stays until you ask us to delete it: write to the contact form. Purpose: fixing what you reported, on your consent (Art. 6(1)(a) GDPR) — you decide whether a report is sent at all, and what goes with it.

2. Buying a licence

Purchases are handled by Lemon Squeezy, which is the merchant of record: they are the seller, they take the payment and they handle VAT. We never see or store your card details. Lemon Squeezy passes us your email address, your name and an order reference so that we can issue and support your licence, and we keep with the licence which plan you bought, what each payment came to, and the discount code you used, if any — the last so that a partner who handed out a code can be paid their share. Their own privacy policy governs what they do with the payment data, and it is worth reading: lemonsqueezy.com/privacy.

3. Early access (closed)

Until 9 October 2026 an early-access signup form stood at trichromalab.com/early-access. It is closed, and nothing new is collected. The rows it stored — your email address, your name if you gave one, your rig, what you shoot, and the tag of the link you came through if it had one — are kept only to finish what you asked for: the invite and the early-access licence that runs to 31 December 2026. Purpose: taking the steps you asked for before a contract (Art. 6(1)(b) GDPR). It was never a mailing list: no newsletter, nothing sent to anybody else, no profile.

Ask us at any time and your row goes — write to the contact form. Otherwise every row is deleted by 31 January 2027.

4. The forum archive, and Discord

The forum at forum.trichromalab.com is a read-only archive. Nobody can sign in or write there any more, and the accounts it had no longer hold an email address, a profile or a picture. What stays is what was published: the posts, the images in them, and the username each was written under — public, and indexed by search engines, so a question answered once can still be found. Images are stored as they were uploaded, including any EXIF metadata they carried. If you wrote there and want a post, an image or your username removed, write to the contact form and we will remove it.

The community now meets on Discord, which is a separate service run by Discord Inc. under its own privacy policy; you join it with a Discord account, not one of ours. As the people who run the Trichroma Lab server we see what you post there and your Discord username, as every member does, and nothing more. Nothing from the application, your licence or your trial is sent to Discord, and nothing from Discord is joined to them.

5. Cookies

The marketing site you are reading sets no cookies at all and loads nothing from a third party. There is no banner because there is nothing to consent to.

The forum archive sets none either.

Cloudflare Turnstile tells a person from a script without the puzzles and without profiling you across sites. It loads on the one form on this site — the contact form — and it may also be shown by the application when a free trial is registered, if a network starts registering trials in bulk. It may set its own short-lived cookie to remember that you passed.

The video on the quick start is a still picture served from this site until you press play. Pressing it loads YouTube's player from youtube-nocookie.com, run by Google under its own privacy policy, which may store data in your browser once the video plays. Nothing else on either site loads third-party code.

6. Who else touches this data

• Cloudflare — hosting, the database, image storage and the sign-in emails. Everything described above runs on their infrastructure.
• Lemon Squeezy — payments, as described in section 2.
• Sentry (Functional Software, Inc.) — crash and fault reports only, on their European servers, and only while you leave the setting on. Their policy: sentry.io/privacy.

They operate internationally, so data may be processed outside the European Economic Area under the European Commission's standard contractual clauses. We do not sell data, we do not share it for advertising, and we make no automated decisions about you.

7. How long we keep it

Rate-limit counters

2 days.

Trial records

Kept while the anti-abuse purpose lasts. A trial deleted on request could simply be taken again, which is the one thing the record exists to prevent.

Licences

For the life of the licence, and afterwards for as long as tax and accounting law requires.

Forum archive posts

As published, until you ask us to remove yours.

An early-access signup

Until 31 January 2027, or until you ask — whichever comes first. Unlike a trial record, nothing about it is worth keeping afterwards.

A bug report

Until you ask us to delete it, screenshot included. The counters that limit how many reports a network or a machine can send in a day: 2 days.

8. What you can ask for

Under the GDPR you may ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or hand it to you in a portable format. Write to the contact form and we will answer within one month.

One honest limit: a trial record is kept as described above.

If you think we have handled your data badly you can complain to your national data protection authority. In Poland that is the Urząd Ochrony Danych Osobowych.

9. Children

This is a tool for photographers and is not directed at children under 16. We do not knowingly collect their data.

10. Changes

If this document changes we update the date at the top. If a change matters — a new recipient, a new purpose — we will say so on this site and on our Discord rather than hope you re-read the page.

See also the terms of use.