kopi cam

Privacy Policy

kopicam · Mirical LLC · last updated 2026-11-07

Mirical LLC runs kopicam. This describes exactly what leaves your phone and why.

Photographs you use to build a camera

They are sent to our server and on to Google's Gemini API, which reads them to work out the colour and tone settings that recreate their look. They are downscaled first and sent for that build (a build makes a few passes, and each pass sends them again); when you later refine that camera, small copies are sent once more so the colorist can see the look you started from. We do not store them, and under Google's paid API terms they are not used to train models. This applies only to the reference photos you deliberately pick, never to the photos you take.

Words you type to build or refine a camera

A description you type, or a change you ask a camera for, is sent to our server and on to Google's Gemini API in the same way, so it can read what you asked for. A description can also be researched first: Gemini looks the look up with Google Search. We do not store what you typed.

Photographs you take

They stay on your device unless you choose to share them. Developing happens on the phone, and shots are saved to your own photo library. The one way kopicam itself sends one anywhere is if you attach it as a sample to a camera you publish, which puts it on that camera's public page.

Accounts

kopicam has no account until you publish a camera or unlock someone else's. Sign in with Apple then gives us an identifier from Apple and, if you allow it, your name. Your name is never shown publicly: a camera you publish is credited to a creator name you choose yourself, and you need one to publish. You may hide your email from us and everything still works. You can delete your account from inside the app, which erases it, unpublishes your cameras and deletes their photos. Purchase records stay with Apple and RevenueCat, who keep them for their own accounting.

What else we store

How we measure the app

The app records a short, fixed list of events so we can see where people get stuck. That list is the whole of it:

Every one is a count with a few fixed values, sent with a random id for this install and session, your device model, iOS version, language, time zone and the app's version. Our analytics provider also sees the IP address the request came from. No photograph, no camera name, no instruction you typed and no text you wrote is ever part of it. Our analytics provider is told not to build profiles, and we never send it your account, your creator name or the identifier Apple gives us. There is no advertising, no advertising identifier and no tracking across other companies' apps, which is why iOS never asks you for tracking permission.

When the app crashes, or one of its screens fails to draw, it sends an error report so we can fix what broke: the kind of error, its message, and the list of places in our own code it passed through on the way. No photograph and nothing about you is part of it, and it goes to the same provider on the same terms as the events above. Only released versions of the app send them, not the development builds we test with.

Who we share it with

Google (Gemini, for the analysis above), Apple and RevenueCat (payments and entitlements), Cloudflare (hosting and storage), and PostHog (the events listed above, and error reports). kopicam.com itself counts page views with Cloudflare Web Analytics, which sets no cookies. We do not sell personal data and there is no advertising in kopicam.

Your choices

Delete your account in the app to remove your account data and unpublish your shared cameras. Delete a camera to remove it from your device. Contact us for anything else, including requests under GDPR or CCPA.

Children

kopicam is not directed to children under 13 and we do not knowingly collect their data.

Contact: andrew@mirical.co