Privacy

Plain-language privacy policy. Last updated 24 October 2026.

The short version

Collie is local-first. Your documents live on your Mac, and I never see them. The app has no analytics and no tracking. The only personal data I hold is what you need to buy Collie and get your key: your email, billing details and purchase record.

Who is responsible

The data controller is kcygan.dev Kacper Cygan, the seller named in the Terms. Write to kacper@getcollie.cloud about anything on this page.

On your Mac

Your writing (documents, folders, revisions, pictures) is stored in a database in Collie’s folder on your Mac (~/Library/Application Support/app.collie.desktop). It isn’t uploaded anywhere.
Crash, error and feedback reports are saved in that same folder, so problems can be fixed. A report holds the kind of problem, the error name and message, the technical stack trace, the screen it happened on (for example /app?doc=…), the app version, macOS platform and processor type, and, for feedback, the note you wrote. No document text is included on purpose. These reports stay on your Mac. Collie never sends them anywhere by itself.
Your license (the key and the email it was bought with) is saved in that folder too.

What leaves your Mac

License check: when you paste a key, Collie sends that key to getcollie.cloud to check it is valid and hasn’t been refunded. The key contains the email it was bought with.
Updates: Collie asks getcollie.cloud whether a new version exists (shortly after launch, about once an hour while you’re online, or when you check by hand) and downloads it. If you’ve pasted a key, Collie sends it with that question. If the key was refunded, no new update is offered, and the version you have keeps working. Your documents are never part of these requests. The server sees your IP address, like any download.
Pictures from the web: if a document shows a picture that lives on another website (for example one in a pasted or imported note), Collie loads it from that website, which then sees your IP address and when it was loaded. Pictures you add from your Mac stay on your Mac.
Optional report webhook: only if you set one up yourself. Even then, only identifiers are sent (an event name, a report id, a fingerprint, the kind of problem, the screen area, the app version, the platform and the time), never messages, stack traces or notes.
AI features you turn on: if you connect an AI provider or an agent such as Claude Code or Codex, the text you ask it to work on goes to that provider under their terms. Nothing is sent unless you set this up.

When you buy Collie

Stripe handles checkout and payment. Stripe receives your card or other payment details, name, email and billing address. I receive your email, name, billing address, any VAT ID you enter, the amount, tax, currency and any discount code.
Your license record on getcollie.cloud holds your email, your key, the Stripe checkout and payment ids, the amount, currency, discount code, and when the key was created, emailed or refunded.
Resend delivers your license email.
Stripe sends your receipt and invoice. Invoices are kept as Polish tax law requires.
Refunds: I keep the refund record, the reason you pick and anything you write (on the refund page or in “Tell me what’s missing”), to improve Collie. The credit note is kept with the invoice.
If you tick “Email me when Collie gets better” after a refund, I keep your email, your reason and when you said yes, because you asked. I write rarely, and every email has an unsubscribe link.

The website

getcollie.cloud runs on Fly.io, on servers in the EU (the Netherlands). Like any server, it keeps short technical logs, which can include IP addresses.
To stop abuse, the site counts requests per IP address for up to a day. It stores only a hash of the address, not the address itself.
The website uses Cloudflare Web Analytics to count visits. It doesn’t use cookies or store anything on your device, and it doesn’t track you across sites.
If you joined the waitlist while it was open, I keep your email to tell you about Collie, because you said yes. You can ask me to remove it at any time.
A daily encrypted backup of purchase records is kept off the server so a sale is never lost. Only I can decrypt it.

Who processes data for me

Stripe Payments Europe, Ltd. (Ireland): payments, receipts, invoices and tax.
Resend (United States): sending email, under the EU Standard Contractual Clauses.
Fly.io, Inc. (United States, servers in the EU): hosting, under the EU Standard Contractual Clauses.
Cloudflare, Inc. (United States): app downloads and website visit counts, under the EU Standard Contractual Clauses.
Google (Gmail): stores the encrypted backups, which Google cannot read.

I don’t sell your data, and I don’t share it with advertisers.

Why I’m allowed to

To sell you Collie, deliver your key and support you: that’s our contract (GDPR art. 6(1)(b)).
To keep invoices and tax records: that’s a legal obligation (art. 6(1)(c)).
To prevent fraud and abuse, keep the site secure and keep backups: those are legitimate interests (art. 6(1)(f)).
For the closed waitlist: your consent (art. 6(1)(a)), which you can withdraw at any time.

How long

Purchase and invoice records: 5 years from the end of the year of purchase, as Polish tax law requires.
License records: as long as your license exists, so your key can always be sent again.
Backups: up to 90 days.
Rate-limit counters: up to a day.
Waitlist: until you unsubscribe or Collie launches for that list.
Reports on your Mac: until you delete them. The log trims itself past 2 MB.

Your rights

You can ask to see your data, correct it, delete it, restrict or object to its use, or get a copy to take elsewhere. You can withdraw consent at any time. Email kacper@getcollie.cloud and I’ll reply within a month. Some records (like invoices) must be kept by law even if you ask me to delete them. You can also complain to the Polish data protection authority: Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa (uodo.gov.pl), or to the authority where you live.

See also the terms and the refund policy.