SharedShotsSharedShots Privacy Policy
Last updated: 2026-08-18
This Privacy Policy describes how SharedShots collects, uses, and shares information. It covers the SharedShots mobile application (the "App") and the sharedshots.site website, including the web album viewer. In this Policy, "the user" means the person using SharedShots, and "the developer" means the operator and provider of SharedShots. By using SharedShots the user agrees to the practices described here.
Questions can be emailed to sharedshots.support@gmail.com.
1. What is collected
The developer collects the minimum information needed to make shared-event photo albums work.
| Category | Examples | Why it is needed |
|---|---|---|
| Account info | Email address, display name, hashed password | To let the user sign in and identify them to other event members. |
| Event data | Event name, date, description, 6-character join code, member list, join requests | To run the shared album feature, including host approval of new members. |
| Photos | The image files the user captures or imports, plus metadata (filter applied, upload time, uploader id, dimensions, file type) | To display photos in the album to other event members. |
| Videos, including their sound | The video files the user records or imports, and the audio recorded as part of them, plus metadata (duration, upload time, uploader id, poster image) | To play videos back to other event members. Audio is only ever captured as part of a video the user is recording. |
| Comments & reactions | Text comments and "likes" the user adds to photos, with their display name | To show them to other members of that event. |
| Purchase status | Whether a subscription is active or an Event Pass was bought (received from the app store via the billing provider) | To unlock what the user bought. Card details are never received or stored. |
| Device & app diagnostics | Crash logs, app version, OS version, anonymized error messages | To fix bugs. No third-party analytics SDKs are used. |
The App does not collect: precise location, contacts, advertising IDs, browsing history, or biometric data. Photos are captured without location EXIF data, because the camera is built without the location module at all rather than merely not reading it.
The microphone is used only while the user is actively recording a video, to capture that video's sound. The App never records audio at any other time, has no voice-note or standalone audio feature, and does not listen in the background.
Opening an album in a web browser. The website can show an album without the App and without signing up, but the browser is signed in anonymously so the photos can be loaded and added to. That anonymous account holds no email address and no password. The name typed before joining is kept in the browser's own storage on that device so it does not have to be typed again, and is attached to anything uploaded from the browser, the same way it is in the App.
The developer does not sell, rent, or trade personal information to anyone.
2. How data is handled
Account info, event data, and photos are processed in the SharedShots backend (currently Supabase, hosted on AWS). Photos are served over HTTPS via long, randomly generated (UUID) addresses that cannot be guessed and are only ever shown to members of the relevant album (see section 4).
Albums are deleted automatically, on a timer, whether or not the account still exists. Every album has a limited lifetime, and when it ends the album and every photo and video in it are permanently deleted: currently 3 months for a free album or one with a base Event Pass, 6 or 9 months where the pass buyer paid for the lifetime extension, and 12 months for an album hosted by a Premium subscriber. Members are reminded at 30, 14, 7, 3 and 1 days beforehand and the album shows its exact deletion date. Deletion cannot be undone. An album expiring does not affect the user's account or profile.
Account data is otherwise retained for as long as the account exists. When the user deletes their account in-app (Profile, then Delete account), their profile, the events they own, their event memberships, and the photos they uploaded are all removed within minutes, and disappear from every album at that moment. Where the user had added photos to an album someone else owns, the stored image files behind them are erased by a clean-up job that runs daily, which can take up to 72 hours; until then they are reachable only by someone who already saved that photo's direct address. Cached copies at CDN edges may persist briefly before they expire.
SharedShots is a sharing service, not a storage or backup service. No guarantee is made that content will be retained or remain retrievable, and the user should keep their own original copies of any photos that matter to them.
3. Who else processes this data
Nobody is given personal information to use for their own purposes. These services process it only in order to run SharedShots:
| Service | What it receives |
|---|---|
| Supabase (hosted on AWS) | Account info, event data, photos and videos. This is where SharedShots stores everything. |
| Expo | Push notification tokens, and the text of each notification, which can include a display name and an album name. Also contacted to deliver app updates. |
| RevenueCat | Whether a subscription is active or an Event Pass was bought. Never card details. |
| Apple, Google | Only when the user chooses Sign in with Apple or Sign in with Google, to confirm who they are. |
4. Who can see the user's photos
Photos in an event are visible to every member of that event. Members are people who joined using the event's 6-character code (which is only ever shared by the user or another member). The host can require approval before someone joins, and can remove a member at any time. The developer never publishes photos, and they are not listed, indexed, or searchable anywhere.
Each photo does have its own long, randomly generated web address, which cannot be guessed and is only ever shown to members of that album, in the App or in the web viewer. That address is itself the key, though: anyone who was given it, or saved it while they were a member, can open that photo directly afterwards.
Because the App lets members save photos to their own device, any member of an event can download and keep a copy of the photos shared in it. Copies that a member has saved to their own device are outside the developer's control and remain with that member even if the original is later deleted. Users should only share content they are comfortable with the other members of their event keeping.
5. Permissions the App requests
- Camera: to take photos and record video in the App.
- Microphone: only while recording a video, to capture its sound. Not used at any other time.
- Photo library: only when the user taps "From library" to import an existing photo or video, or "Save to library" on something they want to keep locally.
- Notifications: optional. Used to say when photos are added to an album the user is in, when someone asks to join an album they host, and before an album is deleted. Declining them limits nothing else in the App.
These are requested via the standard system prompts and can be revoked at any time: on iOS in Settings, then SharedShots, and on Android in Settings, then Apps, then SharedShots, then Permissions. The App does not ask for tracking permission, and contains no advertising and no third-party analytics SDKs.
6. The user's choices
The user can:
- Edit their display name in the App: Profile, then tap the name. Photos already shared keep the name they were posted under.
- Turn join approval on or off for an album they host (Edit event).
- Remove a member from an album they host (Members list).
- Delete an event they own: removes that event's data for everyone in it.
- Delete an individual photo they uploaded: from the photo detail screen.
- Block a user on their device: that person's photos disappear from the user's gallery (PhotoDetail, More, then Block).
- Report a photo: emails the support address with the photo identifiers (PhotoDetail, More, then Report photo).
- Delete their entire account: Profile, then Delete account. Irreversible.
7. The user's rights
Wherever the user lives, they can ask for a copy of their data, ask for it to be corrected, or ask for it to be deleted, by emailing sharedshots.support@gmail.com. Most of it can also be done in the App without asking anyone (section 6).
In the EU, the UK and the EEA, the user has the right of access, rectification, erasure, restriction of processing, data portability, and objection to processing. The developer processes this data in order to provide the service the user asked for, and relies on its legitimate interest in keeping that service working and secure for the rest. A user who is unhappy with how a request was handled has the right to complain to their local data protection authority.
In California, the user has the right to know what is collected, to have it deleted, to have it corrected, and not to be treated differently for exercising any of those rights. SharedShots does not sell or share personal information, and never has.
8. Children
SharedShots is not directed to children under 13. Anyone who believes a child has provided personal information can contact sharedshots.support@gmail.com and it will be deleted.
9. International transfers
SharedShots can be used worldwide. Data is processed in the European Union (Frankfurt, Germany). By using SharedShots the user consents to their data being transferred to and processed there. If that region ever changes, this Policy will be updated to say so.
10. Security
Data in transit is protected with TLS, and the storage provider applies at-rest encryption. No system is perfectly secure, and no guarantee of security is made; if a breach affecting the user's account is detected, the developer will notify the user by email without undue delay, and will notify the relevant supervisory authority within 72 hours where the law requires it.
11. Changes
This Policy may be updated. Material changes will be announced in the App or by email. Continued use after a change indicates acceptance.
12. Contact
Privacy questions: sharedshots.support@gmail.com