Privacy Policy
What happens to your photos and information when you use DumpRoll.
Who we are and what this covers
This policy explains how DumpRoll (“DumpRoll”, “we”, “us”) handles information when you use the DumpRoll mobile app for iPhone and Android and the website at dumproll.app.
Contact: support@dumproll.app.
You use DumpRoll with a DumpRoll account that you sign in to with the account your phone already has: Sign in with Apple on iPhone, Sign in with Google on Android. There is no DumpRoll email address, password or profile. Earlier versions of the app had no sign-in and used anonymous IDs instead. Some features described below are not available in every version of the app. Where a section applies only to a feature, it says so.
Your photos
Rolls you shoot on your own
The exposures you shoot and the frames DumpRoll develops from them are stored in the app’s private storage on your phone. Development runs on your phone. We do not upload these photos to our servers, and we cannot see them. The exposures themselves never leave your phone.
The details of each roll (which film it uses, the order of exposures, when it was shot and developed, and how you arranged your dump) are kept in a database on your phone.
Your developed dumps in your own cloud storage
So that your developed dumps come back when you reinstall DumpRoll or use another phone of the same kind, DumpRoll keeps a private copy in your own cloud storage, automatically:
- iPhone: the private iCloud database Apple provides to DumpRoll in your iCloud account (CloudKit). It does not appear in iCloud Drive or Photos.
- Android: DumpRoll’s hidden app data folder in your Google Drive. It does not appear in My Drive, and DumpRoll can only reach this folder, not your other Drive files.
What is kept there: each completed dump (its developed frames, the order you arranged, its title, the film it was shot on and when, and for each exposure when it was taken and, if location was saved for it, where; see Location and capture details), the films you downloaded or have seen, and a small set of app preferences. Rolls you are still shooting, the original exposures, and frames you saved to Photos are not copied. This storage belongs to your Apple or Google account, counts toward its storage, and is protected by Apple or Google; we never receive these copies and cannot see them. If your iCloud or Google Drive is full, unavailable or signed out, DumpRoll keeps working and says that your dumps are waiting to sync.
Saving and sharing
DumpRoll asks only for permission to add photos to your Photos library, and only adds developed frames when you choose to save them. It does not ask for permission to read your library and cannot import photos from it. When you share, the frames you selected are passed to the app or service you choose in your phone’s share sheet; that destination’s own terms and privacy policy apply from then on.
Shared Roll (where available)
A Shared Roll is one roll that several people shoot together. It is not available in every version of the app. If you join or host one, the exposures you shoot into it are uploaded from your phone to private cloud storage operated for us by Cloudflare (R2). Each upload uses a short-lived link that our server issues only for your own exposure. The exposures cannot be viewed by anyone, including other members, while the roll is being shot.
When the roll ends, each member’s app downloads the roll’s exposures through short-lived links and develops them on that member’s phone. From then on, every member has their own copy of the developed roll, including your exposures, and can save or share it. We cannot delete copies on other members’ phones.
Our server also records the Shared Roll itself: its film and format, who is a member and whether they are the host, and for each exposure its position in the roll, which member shot it, its upload status, file size, timestamps, when it was taken and where (see Location and capture details). It does not record the content of the photos.
Location and capture details
When DumpRoll uses location
DumpRoll asks for location only while you are using the app (“While Using the App” on iPhone, foreground location on Android). It never asks for or uses location in the background, and it reads your position only while the camera is open on a roll that saves location. If you allow only an approximate location, DumpRoll uses the approximate position your phone gives it.
Rolls you shoot on your own: optional
Save location is a choice you make for each roll when you load it, and it stays with that roll. It starts on only if you have already allowed DumpRoll to use location; otherwise it starts off.
- Off: DumpRoll does not read your location for that roll, and no location is saved with its exposures.
- On: for each exposure, DumpRoll saves where it was taken: latitude and longitude, the accuracy your phone reported, and when that position was taken. It uses only a position from the last two minutes; if there is none, the exposure is saved without a location.
These details are stored with the roll on your phone. When the roll is developed, they become part of the completed dump, so they are included in its private copy in your own iCloud (CloudKit) or Google Drive app data described above. We never receive that copy.
Shared Rolls (where available): required
A Shared Roll always records where each exposure was taken. To host, join or shoot a Shared Roll, DumpRoll needs location permission, and the camera takes an exposure only when your phone has a position from the last two minutes. If it does not, no exposure is taken and the app asks you to try again.
With each exposure, your phone sends our server its capture time and location (latitude, longitude, the accuracy your phone reported, and when that position was taken). Our server does not accept an exposure into a Shared Roll without a recent, valid position.
Other members do not receive your coordinates. When the roll is handed over for developing, every member receives the capture time of every exposure, but the location of an exposure goes only to the member who shot it. Your developed copy of the roll, and its private copy in your iCloud or Google Drive, therefore contain the locations of your own exposures only.
On our server, an exposure’s location is erased when its photo is deleted from our storage, 30 days after the roll ends. Its capture time stays with the roll’s records. If you delete your account, the exposures you shot stay part of the roll for its other members, no longer linked to you, and their locations are erased at the same point.
Capture time
Every exposure records when it was taken and your phone’s time zone offset at that moment, whether or not location is saved. If you turn on the date stamp for a roll, that date and time are printed onto its developed frames.
The photo files
DumpRoll keeps the location and capture time described above as separate details. It does not write location (GPS), device make or model, capture time or other camera metadata into the image files: it keeps only the image’s orientation, and on Android it removes those fields from the camera’s output. Developed frames are new images rendered by DumpRoll’s development engine and carry no camera metadata. This applies to exposures uploaded to a Shared Roll as well.
What location is used for
Only to provide the feature itself: recording where your photos were taken, in your own dumps and in Shared Rolls. DumpRoll does not use location for advertising, marketing, analytics or personalization, does not sell it or give it to data brokers, does not use it to track you, and never includes it in crash reports. You can change DumpRoll’s location permission at any time in your phone’s settings.
Separately, our servers and service providers can see the IP address your phone connects from, as any internet service can (see Your account and our servers).
Camera
DumpRoll uses the camera only to shoot your roll while the camera screen is open. It shoots still photos only. It does not record video and does not use the microphone.
Your account and our servers
Your DumpRoll account lives on our backend, which runs on Supabase. When you sign in, Apple or Google confirms who you are to our backend, which then gives your account a random user ID and session tokens kept in the app’s private storage on your phone.
- Sign in with Apple: DumpRoll asks Apple for no email address and no name. Our backend receives only Apple’s identifier for you in DumpRoll.
- Sign in with Google: Google tells our backend your Google account identifier, email address, name and profile picture link, and our backend stores them with your account to recognise you. We do not use them to contact you or for marketing. The app also keeps your Google account address on your phone so it connects to the right Google Drive.
Accounts are separate on each platform: an iPhone account and an Android account are never combined, even if they share an email address, and your dumps do not move between iPhone and Android. Shared Rolls work between iPhone and Android.
In earlier versions without sign-in, the app used an anonymous user ID. When you sign in on a phone that used one, it becomes your account, so your existing Shared Rolls stay yours.
We use your account to:
- keep your library to yourself on your phone and in your own cloud storage,
- confirm what your purchases include (see below),
- record your membership of a Shared Roll and the exposures you shoot into it.
Like any internet service, our backend and its providers receive technical information with each request, such as your IP address, the time of the request and basic app and device information sent by the network library. They keep it in service logs for a limited time to run and secure the service. We do not use it to build a profile of you.
Rolls you shoot on your own never use our servers: after you have signed in once, shooting, developing and your dumps work without a connection, and their photos and details are never sent to us. When new DumpRoll films are published, the app downloads them from our film catalog (hosted by Vercel); those downloads contain no information about you.
Purchases and subscriptions
Purchases are made through the Apple App Store or Google Play. Apple or Google processes your payment; we never receive your card or bank details, your name, or your store account’s email address.
We use RevenueCat to manage purchases. The app identifies you to RevenueCat with your DumpRoll user ID, and RevenueCat receives your purchase and subscription transactions from the app and from Apple or Google, together with technical information it needs, such as app version, platform and store country.
Our server asks RevenueCat what your purchases are and records, for your account: the products purchased, which store, purchase, renewal, expiry, grace-period, billing-issue and refund dates, and whether the purchase was a test purchase. It uses this only to decide what your purchases unlock. When RevenueCat notifies our server of a change, we keep only the notification’s ID, type and processing result, not its contents.
Purchases belong to the DumpRoll account that made them. Restoring purchases while signed in to another DumpRoll account on the same platform moves them to that account; they are never active on two accounts at once.
Rewarded ads
Without DumpRoll Creator, some actions offer a rewarded ad: you choose to watch a short ad, for example to load another roll or to make a roll ready sooner. These are the only ads in DumpRoll. There are no banners, no interstitial or app-open ads, and no ads on the camera or while you shoot. Creator shows no ads.
The ads come from Google AdMob. DumpRoll sets up Google’s ad software to limit what it uses:
- Google’s limited ads mode is switched on, so ads are not personalized and features that rely on an identifier stored on your phone are off. Every ad request also asks for non-personalized ads.
- DumpRoll does not ask for permission to track you (App Tracking Transparency), so your iPhone’s advertising identifier is not available to the app. On Android, the app does not have the permission needed to read your advertising ID.
- Google’s publisher first-party ID, an identifier it can keep in the app, is switched off.
- DumpRoll does not give Google your photos, your location from the camera, your email address or your name.
When it shows an ad, Google’s ad software still processes information as Google describes for it: your IP address, which may indicate your general location; which ads you saw and how you interacted with them; technical and performance information about the app and the ad software; and identifiers limited to this app or to its developer. Google uses this to deliver and measure ads and to detect fraud and abuse. If Google’s limited ads are served with programmatic demand, Google may store data on your phone only to detect invalid traffic. On Android, Google’s ad software may also send its own crash reports to Google; on iPhone, DumpRoll switches those off.
To confirm that you watched an ad before giving you its reward, DumpRoll gives Google your DumpRoll user ID and a one-time reward ID with the ad. Google sends them back to our server with a signed confirmation. Our server records, for your account: which reward it was for, its status and times, how it was confirmed, and Google’s transaction ID, so that one ad is never rewarded twice.
Where the law requires consent for ads, Google’s consent form is shown before any ad is loaded, and no ad is loaded if consent is required and not given.
Crash reports
If the app crashes or records an error, it sends a crash report to Firebase Crashlytics, a service provided by Google, so we can find and fix the problem. A report contains:
- the technical stack trace and error type,
- device model, operating system version, app version and build, and when it happened,
- short technical log lines that DumpRoll writes about what the app was doing,
- a random installation identifier created by Crashlytics and a Firebase installation ID.
DumpRoll does not attach a user ID to crash reports. The app removes file paths, web links, tokens and identifiers from the error messages and log lines it records before sending them. Crash reports never include your photos.
From Firebase, the app uses only Crashlytics. It does not include Google Analytics or any other analytics software. The ad software used for rewarded ads is described in Rewarded ads.
What we don’t do
- We don’t show ads other than the rewarded ads you choose to watch, and we don’t personalize them.
- We don’t track you across other companies’ apps or websites, and the app doesn’t use your phone’s advertising identifier.
- We don’t sell your information, and we don’t use your photos, location, email address or name for advertising.
- We don’t ask for your contacts, microphone or access to your Photos library, and we never use your location in the background.
This website
dumproll.app is hosted by Vercel. It has no analytics, no advertising and no tracking, and it does not set cookies. Vercel processes the technical information your browser sends with each request, such as your IP address and browser type, to deliver the site and protect it from abuse.
Device backups
Separately from DumpRoll’s own private copy of your dumps, your phone’s backup service (for example iCloud Backup or Android backup) may include DumpRoll’s app data, including your rolls, depending on your settings. Those backups are managed by Apple or Google under their terms, not by us.
Service providers
We share information only with these providers, and only to run DumpRoll:
| Provider | What it does for DumpRoll | Information involved |
|---|---|---|
| Supabase | Backend database, accounts and sign-in, server functions. Hosted in the EU (Frankfurt, Germany). | Account (user ID and the Apple or Google identity described above), purchase records, Shared Roll records (including the capture time and location of Shared Roll exposures), request logs |
| Cloudflare (R2) | Private storage for Shared Roll exposures | Exposures you shoot into a Shared Roll |
| RevenueCat | Purchase and subscription management | Your DumpRoll user ID, purchase transactions |
| Apple | Sign in with Apple; iCloud (CloudKit) storage for your dumps; App Store distribution and payments | Your sign-in; your private dump copies in your iCloud account (including any locations saved with them); purchases — under Apple’s privacy policy |
| Sign in with Google; Google Drive app data storage for your dumps; Google Play distribution and payments | Your sign-in; your private dump copies in your Google Drive (including any locations saved with them); purchases — under Google’s privacy policy | |
| Google (AdMob) | Rewarded ads and confirming their rewards | The information described in Rewarded ads, including your DumpRoll user ID and the reward ID for each rewarded ad |
| Google (Firebase Crashlytics) | Crash reporting | Crash reports as described above |
| Vercel | Website hosting; the public film catalog the app downloads films from | Website and film download request data |
Some of these providers process information in the United States and other countries where they operate. We may also disclose information if the law requires it.
Why we use information
We use the information above only to:
- provide the app and the features you use, including purchases and Shared Rolls,
- show the rewarded ads you choose to watch and confirm their rewards,
- keep the app working and fix crashes,
- keep the service secure and prevent abuse,
- meet legal obligations.
Where laws such as the EU or UK GDPR apply, we rely on performance of our contract with you (providing the app, purchases and Shared Rolls), our legitimate interest in keeping the app stable and secure (crash reports and service logs), and compliance with legal obligations. For rewarded ads, Google’s consent form asks for your choices where the law requires consent.
How long we keep it
| Information | Kept |
|---|---|
| Rolls, photos and roll details on your phone | Until you uninstall the app (and in any device backups you keep) |
| Locations saved with your exposures, on your phone | Until you delete your account in the app or uninstall the app (and in any device backups you keep) |
| Locations in your dumps’ private copies in iCloud or Google Drive | Until you delete your account in the app, or remove DumpRoll’s data in your iCloud or Google Drive settings |
| Locations of Shared Roll exposures on our server | Erased when the exposure’s photo is deleted, 30 days after the roll ends, including after you delete your account |
| Shared Roll exposures in cloud storage | Deleted automatically 30 days after the roll ends. Uploads that never became part of a roll are deleted sooner. |
| Shared Roll records (membership, exposure positions, timestamps) | Kept after the roll ends; they contain no photos. Deleted on request (see below). |
| Your account (and an earlier anonymous ID) | Until you delete your account in the app, or on request |
| Your dumps’ private copies in iCloud or Google Drive | Until you delete your account in the app, or remove DumpRoll’s data in your iCloud or Google Drive settings |
| Purchase records | While you use DumpRoll; deleted on request |
| Purchase notification IDs | Kept to avoid processing the same notification twice |
| Rewarded ad records on our server | Until you delete your account in the app, or on request |
| Information Google processes for ads | As set out in Google’s privacy policy |
| Crash reports | For the retention period set by Firebase Crashlytics |
| Service and website request logs | For the limited log retention period of each provider |
Your choices and rights
- Delete your account: in the app, open About → Account → Delete account. This deletes your account on our server, your dumps’ copies in your iCloud or Google Drive, and the rolls and dumps on that phone. Frames you saved to Photos or shared elsewhere are not affected. See Delete your data.
- Sign out: your rolls stay on the phone and come back when you sign in with the same account.
- Ask us to delete or access server data: follow the steps on Delete your data or contact us at support@dumproll.app.
- Camera, Photos and location permissions: you can change them at any time in your phone’s settings.
Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal information, to object to or restrict some uses of it, and to complain to your local data protection authority. We will not ask for more than we need to find what belongs to you.
Security
Information travels between the app and our services over encrypted connections. Shared Roll storage is private and reachable only through short-lived links our server issues after checking that the request is allowed. The app contains no secret keys for our services, and our database checks every request against the identity making it. No system is perfectly secure, but we work to protect your information and limit what we hold in the first place.
Children
DumpRoll is not directed at children, and we do not knowingly collect personal information from children. If you believe a child has given us personal information, contact us and we will delete it.
Changes to this policy
If we change how DumpRoll handles information, we will update this policy and its effective date before the change takes effect. If a change is significant, we will also say so in the app or on this website.
Contact
Questions or requests about privacy: support@dumproll.app.