Privacy
Effective 14 November 2026. This version replaces the earlier False Peak texts and describes each app individually.
Ten Shots is a shared camera for events. This policy explains what the app and the App Clip keep, why, who processes it, and how you delete it. Our general privacy information for all our apps is at limmatstudios.com/privacy; this page is the detailed policy for Ten Shots.
Who's responsible
Limmat Studios GmbH, Zahnradstrasse 22, 8005 Zürich, Switzerland, hello@limmatstudios.com. We are the controller of the data described here. Our apps were previously published under the name False Peak.
We follow the Swiss Federal Act on Data Protection (FADP) and, where it applies to you, the EU and UK General Data Protection Regulation (GDPR).
No sign-up
You never create an account or give us an email address or phone number. The app and the App Clip each get a random, anonymous identifier from Firebase Authentication the first time you open them. When you move from the App Clip to the full app, a one-time code (valid for 30 days) lets the app take over the App Clip's identifier so your events come with you.
Everything below is stored under that identifier. It does not contain your name, but it does connect your events, prints, reports and Pro status to each other.
What we keep
| What | Why | Where it goes | How long |
|---|---|---|---|
| Events you create or join: the event name, film, guest limit, and the name you type to sign your prints | To run the event and show who took which print | Google Firebase | Until deleted (see below) |
| Your prints: each shot, turned into a finished print on your phone and uploaded as an image. The original photo and its metadata (such as location) stay on your phone | To show them to the event when the host develops it | Google Firebase; checked by Google Cloud Vision | Until deleted |
| When you accepted the terms (a timestamp, on joining or creating an event) | To show that you agreed to the content rules | Google Firebase | As long as your participation |
| Reports and blocks: who reported which print, whose print it was, the host, the reason and time; the people you block, including their name; prints you hid | To keep events safe and act on reports | Google Firebase | Until deleted |
| A notification token, if you allow notifications | To tell you when an event is developed | Google Firebase Cloud Messaging, Apple | Until deleted, or until it stops working |
| Whether you have Ten Shots Pro, linked to your anonymous identifier | So you can host events | RevenueCat, Apple, Google Firebase | See below |
| Crash reports and usage statistics (full app only, not the App Clip): what went wrong in a crash, and counts such as events created, events joined, shots taken, events developed, the paywall shown, prints reported and people blocked | To fix bugs and improve the app | Firebase Crashlytics, Google Analytics for Firebase | According to those services' retention settings |
| Server logs with your anonymous identifier for some actions (for example a report, a host block, a held print, a deleted account) | Security, operating the service, following up reports | Google Cloud Logging | According to Google Cloud's log retention |
Crash reports and usage statistics are not tied to your anonymous identifier, carry no photos or names, and Analytics runs without the advertising identifier. Ten Shots doesn't use your location, contacts, microphone or photo library. Your typed name and app settings are also kept on your phone.
Why we may use it
Running events, storing and showing prints, notifications and Pro status are needed to provide the app you asked for (performance of a contract). Screening, reports, blocks and server logs protect the people in events and our service (our legitimate interest). Crash reports and usage statistics are based on our legitimate interest in a working, improving app; you can object at any time by writing to us. Giving a name and taking photos is voluntary, but you can't join an event without a name.
Who sees your prints
Only people in the same event, and only after the host develops the prints. Before that, nobody can see them, the host included. Once developed, everyone in the event sees each print with the name of the person who took it, and can save or share it from their phone. The host can remove any print from the event after it's developed.
Screening, reports and blocks
Each print is checked automatically by Google Cloud Vision (SafeSearch) when it's uploaded. A print that's likely to contain nudity, or very likely to contain graphic violence, is held back: only the host can see it and decide to show it or remove it. No person looks at your prints as part of this check. If the screening service is unavailable, a print may go through without being checked, so reporting still matters.
Anyone in an event can report a print. It's hidden for them right away and held back from the other guests, and the report is stored so we can review it. Anyone can block a person to stop seeing their prints; a host who blocks a guest removes them and their prints from the event, and they can't join that host's events again.
Service providers
- Google Firebase and Google Cloud (Authentication, Firestore, Storage, Cloud Functions, Cloud Messaging, Cloud Vision, Cloud Logging) store events and prints, run the app's servers, send notifications and screen prints. Our server functions run in Google's EU region in Belgium.
- Firebase Crashlytics and Google Analytics for Firebase receive crash reports and usage statistics from the full app.
- RevenueCat keeps track of Ten Shots Pro subscriptions, using your anonymous identifier.
- Apple handles purchases and delivers notifications.
Google, RevenueCat and Apple may process data in the United States and other countries outside Switzerland and the EEA. Where applicable we rely on the Swiss–US and EU–US Data Privacy Framework, otherwise on standard contractual clauses.
We don't sell your data, show ads, or track you across other apps and websites.
How long we keep it
There is no automatic expiry. Events, prints, names, reports and blocks stay until they are deleted: by you with Delete my data, by the host with Delete my data (which removes the whole event), or when a host removes a print or blocks a guest. Notification tokens that stop working are removed automatically.
Delete your data
In the app, open Settings and tap Delete my data. This deletes, straight away:
- the events you host, with every guest's prints, the join code and every guest's link to the event;
- your prints, your name and your participation in events you joined;
- reports you filed and reports about your prints;
- your blocks, hidden prints and notification tokens, any open transfer code, and your anonymous identifier.
It does not cancel a Pro subscription, which Apple bills: cancel it from Settings > Manage subscription in the app, or in your Apple Account settings. RevenueCat's record of your purchases and existing server log entries are not removed by this button; write to us if you want them deleted. Prints other people already saved to their own phones are outside our control.
Children
Ten Shots is for people who host or attend events. It isn't directed at children under 13, and we don't knowingly collect their data. If you think a child has used it, write to us and we'll delete the data.
Your rights
You can ask to access, correct or delete your data, to restrict or object to its use, to receive it in a portable format, and you can withdraw consent at any time. Write to hello@limmatstudios.com and include the event name, since without an account we can't otherwise tell which data is yours.
You can also complain to a supervisory authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the EU or UK the data protection authority where you live or work.
We don't make automated decisions with legal or similarly significant effects. Screening only holds a print back for the host to decide.
California residents
Categories we collect: identifiers (anonymous identifier, notification token), the name you type, photos (your prints), safety records (reports and blocks), purchase status, and usage and crash data. We don't sell personal information or share it for cross-context behavioural advertising.
Changes
When this policy changes, the effective date above changes too.