Report an issue.
A bug, or an idea, tell us. Reports arrive here from any platform, and go straight to the people who build Catchlight.
No account, no tracking. We only use what you send to fix the issue or build the feature.
After you press send.
Your report doesn't go into a queue. There's no ticketing system, no outsourced help desk, no bot that answers before a human has read it. It arrives with the same people deciding what gets built next, which is why a good report so often turns into the next fix.
If you left an email address, that's where the reply lands. If you didn't, that's fine too, plenty of useful reports are anonymous, we just can't tell you when it's fixed.
We keep your report only as long as we need it to deal with the issue, plus a brief record that it happened, then we delete it. That's the whole lifecycle. It's in the privacy policy in more words.
The diagnostics file, before you trust it.
The app keeps a small log of technical breadcrumbs, what it was doing and when, never what you wrote.
You don't have to take that on trust either. The export is a plain text file, so open it and read it before you attach it, it's your file. If anything in it looks like your writing rather than plumbing, don't send it, and tell us that instead, because that would be a bug all of its own.
If it's about your personal data.
A complaint about how we've handled your personal data is different from a bug, and the law treats it differently, so we do too. Choose "Data protection complaint" on the form and leave an email, we reply by email for these. We'll acknowledge it within 30 days and give you a full answer within a calendar month, and if we ever need longer, we'll tell you why rather than going quiet.
If our answer doesn't put it right, you can take it to the Information Commissioner's Office at ico.org.uk. That route is always open, it doesn't depend on asking us first, though we'd obviously rather hear about it.
What makes a bug report easy to fix.
The ordinary detail is the valuable part. What you tapped, what you expected, what happened instead. "Sync is broken" is a mystery for both of us. "I ticked a task and the tick came back" is one we can actually chase.
If you're moving to a new phone.
Your Takes are not in your iPhone backup. That's deliberate, and it's worth knowing before you need it rather than after. The database and the key that opens it are both marked as excluded from device backups, so they never leave for anyone else's servers, and the cost of that is a safety net you might reasonably have assumed was there. Restore a new iPhone from a backup and Catchlight opens empty.
What does bring them back is the cloud folder you chose plus your 12-word Privacy phrase. On the new phone, "I already use Catchlight" takes you to the phrase entry, and once you point it at the same folder your Takes arrive as it syncs.
The phrase doesn't travel either, for the same reason the key doesn't. It's stored on the device you set it up on and nowhere else, so the copy you wrote down is the copy that matters. If you never wrote it down and you still have the old phone, it's under Settings → Security → Privacy phrase, and today is the day.