Privacy Policy

Last updated: 21 September 2026

This Privacy Policy explains how AllShots collects, uses, and protects your information when you use the AllShots mobile application and the guest web app (together, the “App”).

1. Who is responsible

The controller for the processing described here is Boz Apps, proprietor Berk Özdoruk, Halilim Street No 5, Bodrum, Türkiye. Contact: allshots.app@gmail.com. Full contact details are on our imprint page.

2. Roles

Each event has a host who creates it, invites guests and decides why photos are collected at that event.

Where an individual organises a private event — a wedding, a birthday, a family celebration — we operate the service and are responsible for the processing described in this policy.
Where an organisation uses AllShots in a professional or business context, that organisation determines the purpose of the collection and we process the content on its behalf. In that case a separate data processing agreement applies; hosts can request one from us.
For the operation of the App itself — accounts, fault diagnosis, measuring our advertising — we are always responsible in our own right.

3. Information we collect

Account data. When you join or host, we create an account identifier. You may continue anonymously (an automatically generated guest account) or sign in with your email address, Apple ID or Google account. If you sign in, we store that email address.
Content you create. Photos, videos, voice recordings and notes you capture or upload, along with the optional nickname you choose and the time the content was created.
Event data. Event names, dates, type, settings, join codes, and which events you joined.
Technical data. Basic device and diagnostic information needed to run the service reliably, and a push notification token if you allow notifications.
Purchase data. If you buy an event plan in the App, our payment infrastructure provider processes the Apple purchase receipt and product identifier. If you buy on the web, Paddle (our reseller and merchant of record) collects your email address, billing country and payment details to complete the order and sends us the order number, product, amount and your email address so we can apply the plan to your event and answer refund requests. We never see or store your payment card details — payment is handled entirely by Apple or Paddle.
Advertising identifiers. Only if you explicitly allow tracking via the iOS App Tracking Transparency prompt, we collect your device advertising identifier (IDFA) to measure the performance of our ads. If you decline, we do not collect it.

4. Why we process it, and on what basis

Running the service — joining events, storing and showing content, enforcing event limits and settings: performance of the contract with you.
Keeping the service safe and working — reviewing reported content, diagnosing faults, preventing abuse: our legitimate interest in a service that works and is not misused.
Purchases — verifying entitlements and keeping records: performance of the contract, and our legal obligations.
Responding to your support requests: performance of the contract, and our legitimate interest in supporting our users.
Measuring our advertising — only where you have agreed: your consent, which you can withdraw at any time.

We do not sell your personal data, and we do not use your photos for advertising.

5. Device permissions

Camera. Used only to let you take photos and record videos inside an event. We do not access your camera in the background.
Microphone. Used when you record a video, so your clip has sound, and when you record a voice memory for an event.
Photo Library (read). Used only when you choose to pick an existing photo to add to an event (when the host enables gallery uploads).
Photo Library (add/save). Used only when you choose to save an event photo or QR code to your device.
Notifications. Used to tell you about your events — for example when an event is about to expire.

Permissions are requested at the moment a feature needs them and can be revoked any time in your device Settings.

6. Who can see your content

Content you upload to an event is visible to the event host and, depending on the gallery mode the host has chosen, to other guests of that same event. In open mode guests see each other’s content; in private mode each guest sees only their own uploads while the host sees all of it.

The gallery mode is a visibility setting within the service; it is not a form of encryption. Content is not published, is not indexed by search engines, and is not searchable outside the event.

7. Our access to your content

AllShots is a hosted service. Content is stored on managed cloud infrastructure and is encrypted in transit and while stored. It is not end-to-end encrypted.

As the operator of that infrastructure we hold administrative credentials and are therefore technically able to access stored files. We do not access event content routinely, and the App gives us no feature for browsing user galleries. We access content only where it is necessary:

at the host’s explicit support request;
to review content reported through the in-app report function;
to diagnose a specific technical fault;
where we are required to do so by law.

Any other use is excluded. We do not use content for advertising, analytics, profiling or machine-learning training.

8. What we do not do

We do not perform facial recognition, face matching or any other biometric analysis of the photos.
We do not use your content to train machine-learning models.
We do not sell personal data, and we never share photos, videos, voice recordings or notes with advertising partners.
Photos are re-encoded on your device before upload, which removes EXIF metadata including any GPS coordinates. Videos are not yet processed this way; we are working on it.
Crash and error diagnostics are processed in the EU, on servers in Germany, with screen contents fully masked and without IP addresses.

9. Service providers

We use the following providers to operate the App. Each processes data on our behalf under its own security and privacy commitments:

Google Ireland Ltd. / Google LLC (Firebase: Authentication, Cloud Firestore, Cloud Storage, server-side functions) — stores your content and account data.
Sentry — receives crash and error diagnostics so we can fix problems. Processed in the EU, on servers in Germany.
RevenueCat, Inc. — manages in-app purchases and subscriptions on our behalf.
Expo / 650 Industries, Inc. — delivers push notifications.
Apple Distribution International Ltd. — purchase and payment processing through the App Store, and Sign in with Apple.
Paddle.com Market Ltd. (UK) and Paddle.com Inc. (US) — reseller and merchant of record for purchases made on the web: checkout, invoicing, taxes, fraud prevention and refunds. Paddle acts as an independent controller for the payment itself; see Paddle's privacy policy.
Meta Platforms Ireland Ltd. — receives app events (such as install, event creation, and purchase confirmations) so we can measure whether our advertising works. See “Advertising & measurement” below.

We will update this list before adding a new provider.

10. Advertising & measurement

We advertise AllShots on platforms like Facebook and Instagram. To understand whether those ads work, we share limited app events (for example: app installed, event created, purchase completed) with Meta, together with device information. Your photos, videos, voice recordings, notes and event content are never shared with advertising partners.

On iOS, sharing that can be used to identify your device across other companies’ apps only happens if you tap Allow on the App Tracking Transparency prompt. If you decline, we only receive aggregated, privacy-preserving measurement (such as Apple’s SKAdNetwork), and your advertising identifier is not collected.

11. Where your data is processed

Content and account data are stored with Google Firebase, across more than one region:

The database — accounts, event records, nicknames and notes — is held in the eur3 multi-region, in the European Union.
Media files — photos, videos and voice recordings — are held in the us-east1 region, in the United States.
Server-side functions run in the us-central1 region, in the United States.

Transfers to the United States are covered by Google’s Cloud Data Processing Addendum, including the EU Standard Contractual Clauses it contains, and by Google LLC’s certification under the EU–US Data Privacy Framework.

Crash and error diagnostics are processed by Sentry in the European Union, on servers in Germany.

Web purchase and invoice data are processed by Paddle in the United Kingdom and the United States under Paddle's own safeguards, including the UK International Data Transfer Addendum and the EU Standard Contractual Clauses.

We are based in Türkiye and access the infrastructure administratively from there, within the limits described in section 7.

12. Data retention

Content in a free event is deleted automatically seven days after the first upload. The host is notified 24 hours beforehand.
Content in a paid event is currently kept until the host deletes the event. Deleting an event removes its files from our storage.
Removing an individual item hides it from the galleries in the App.
Diagnostic error records are kept for 30 days.
Support correspondence is kept for as long as we need it to handle your request and to document how it was resolved.

We may introduce a maximum retention period for paid events. If we do, we will give hosts at least 30 days’ notice and the opportunity to download their album beforehand.

13. Deleting your account and data

You can delete your account and associated data at any time from Settings → Delete account & data inside the App. For hosts, this deletes your events and their content. For guests, this removes your uploaded content and your account identifier. You can also email us to request deletion.

14. If you appear in a photo taken at an event

Guests at an event take photos and upload them to a private gallery held by the organiser of that event. If you appear in one of these photos, the organiser of the event decides why the photos are collected; we provide the technical service.

The photos are not public, are not indexed by search engines, and are visible only within that event. We do not run facial recognition and do not identify anyone in them.

You can object to a photo being kept and ask for it to be removed, without having an account. Write to allshots.app@gmail.com with the event code if you have it, or a description of the event and roughly when it took place. You can also contact the organiser of the event directly. We aim to respond within seven days.

15. Security

Content is transmitted over TLS and stored encrypted at rest by our infrastructure provider.
Access to event data is enforced on our servers by security rules. Joining an event requires its event code or QR code.
Each event is stored separately; a host has no access to another host’s events.
Administrative access is limited to us, on the terms set out in section 7.
Unlawful or objectionable content can be reported in the App; reported content is hidden immediately and reviewed.

16. Children

The App is not directed to children under 16, or under the higher minimum age required in your country. We do not knowingly collect data from children under that age. This concerns the age required to use our service; whether children may be photographed at an event is a matter for the host and the parents or guardians concerned.

17. Your rights

Depending on where you live, you may have the right to access your personal data, to have it corrected or deleted, to receive a copy of it, to restrict or object to certain processing, and to withdraw a consent you have given. To exercise any of these, write to allshots.app@gmail.com.

If you are in the European Union, the United Kingdom or Switzerland, you also have the right to lodge a complaint with your national data protection supervisory authority.

We do not make automated decisions that produce legal effects for you, and we do not profile you.

18. Requests from authorities

We disclose content or account data to an authority only where we receive a legally valid, written request from a body competent to make it, and only to the extent that request requires. We keep a record of such requests and, where we are legally permitted to do so, we inform the affected host.

19. Data breaches

If a security incident affects your personal data, we will assess it without delay, notify the competent supervisory authority where we are required to, and inform affected users where the incident is likely to result in a high risk to them.

20. Changes

We may update this policy from time to time. Material changes will be reflected by updating the “Last updated” date above, and, where a change materially affects your rights, by notice in the App.

21. Contact

Questions about privacy? Email us at allshots.app@gmail.com.