papershot Privacy Policy
Last updated: 2026-10-13
Applies to: https://papershot.app and the papershot apps for iOS and Android.
1. Who We Are
papershot is operated by Wellbayt LLC-FZ ("papershot", "we", "us", "our"), a free zone limited liability company registered in Dubai, United Arab Emirates. We are the data controller: the company that decides why and how your personal data (any information about you) is used. The exception is a business that uses papershot for its own guests: for that data, we are its processor (we handle the data on the business's instructions) under our Data Processing Addendum.
Contact: support@papershot.app
Postal address: Wellbayt LLC-FZ, Dubai, United Arab Emirates (full registered address on request).
United Arab Emirates Data Office. We are subject to Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the "UAE PDPL"). You can also raise questions about our compliance with the UAE Data Office, the federal data protection authority.
2. What papershot Is
A host makes a moment: a private, time-boxed shared roll. Guests join from an invite card, by scanning its QR code, opening its link, or typing its code, with or without an account, in the iOS or Android app. The web page at /join only shows the invite and the app store links. Photos, videos, and memos are made in the app. There is no web app, no public feed, and no public search. What is in a moment is shown to the people in it; our own administrators can also see it, for example to review a report.
The host decides when the roll develops: as it happens, when the roll closes, or after a delay the host sets. Until then, other guests see only a blurred tile for each item, with who added it and when. The item itself goes only to the host and the person who added it. The host can also hide photos, videos, or memos from the other guests altogether, so that each one stays between the person who added it and the host.
3. Data We Collect
Account and identifiers
- The identifier Apple or Google gives us when you sign in, plus your name and email address if the provider shares them
- If you sign in with a code sent by email instead, the email address you type in. We use it to send you sign-in codes, to recognise your account next time, and to write to you about your account or your moments. We never send marketing email.
- Your display name and, if you set one, your profile photo
- For guests without an account, an install identifier: a signed, device-stable token so your shots stay yours across app launches. If you later sign in, you can claim the media you added as a guest.
- Your device platform and when the app last checked in
Your content
- The photos, videos, and memos you add to a moment, with the film look you chose applied at capture, plus their width, height, and the time they were taken. Before upload, the app keeps only a short allow-list of EXIF fields (exposure settings, lens, camera make and model, and the time taken); location, maker notes, and serial numbers are dropped.
- Moment details: name, dates, film stock, shots per guest, video and memo lengths, guest capacity, and the reveal setting
- Prompts the host writes or records for videos and memos, the Guest Lens shot list, and the moment's cover photo (stored on our server). Which Guest Lens prompts you have answered is stored only on your device.
- Studio drafts (backdrops, photos off the roll, stickers, and text) are stored only on your device, and exports are rendered on your device
- Favourites (the hearts you tap)
Reports and blocks
- Reports you make about a photo, video, memo, or person, with the reason you pick, and the people you block or, as a host, block from posting
Purchases
- Purchase receipts and product identifiers from Apple or Google. We never see your card number.
Notifications
- A push notification token from Google's Firebase Cloud Messaging, which delivers notifications on both iOS and Android (on iOS, through Apple's push service, APNs)
- On iOS, Live Activity tokens so the roll can show on your lock screen while a moment runs
Consent records
- When you confirmed that you meet the minimum age and accepted the Terms
- Each consent you give or withdraw: its kind, whether it was granted or revoked, the time, and the IP address it came from
Security log
- A record of actions on the service, such as sign-ins, moments made and joined, uploads, reports, blocks, purchases, and account deletions, with the time and, for most of them, the IP address and device details (user agent) they came from
Crash and performance data
- Crash reports and performance traces go to Sentry under pseudonymous ids only: a random id for the app on your phone and, when you are signed in, your papershot account id. They name the screen and, where relevant, the moment's random id. The app sends no email address or username and blanks the IP address field, although Sentry, like any server, sees the network address a report arrives from. No screenshots, no view hierarchy, no session replay.
Product analytics
- The apps send usage events to Firebase Analytics (Google Analytics 4): event names such as
moment_create,photo_capture, andupload_complete, with sizes bucketed. The values carry no names, email addresses, or content: moments are referred to by their random ids, and purchases by the app store's transaction id. - User properties such as whether you are signed in, pro mode, app language, theme, and whether you have purchased, under a pseudonymous id: a random id for the app on your device and, when you are signed in, your papershot account id
- Your device model, operating system version, and language, and the version of the app
- A coarse location, down to the city, that Google infers from your IP address
- The apps do not collect the identifier for vendor (IDFV) on iOS, and do not read the advertising identifier on either platform.
- This is on by default. Turn it off in Settings under Help improve papershot or, without an account, in Privacy choices. In the United Kingdom the app asks first, and nothing is collected until you say yes.
The website
- On https://papershot.app, a cookie that remembers the language you pick, browser storage that remembers your theme, and a cookie that remembers your analytics choice
- Website analytics (Google Analytics 4), only if you accept analytics cookies, wherever you are. Until you do, nothing loads from Google and nothing is sent. With your consent: the pages you view, how you arrived (the referring site and any campaign tags on the link), the links and buttons you use, how far you scroll, how fast pages load, your browser, device, and screen size, and a coarse location Google infers from your IP address, under a pseudonymous cookie id. Invite page addresses are recorded without their invite code, nothing you type is recorded, and the admin area carries no analytics.
- When a phone opens /download and is sent straight to its app store, our server records the redirect in Google Analytics (the store, the page language, and any campaign tags on the link) only if you accepted analytics cookies. Otherwise nothing is sent.
- See /cookies for the cookies, how long they last, and your choices.
Camera, microphone, and photo library
- Camera access only while you are taking a photo or video, or scanning an invite's QR code
- Microphone access only while you are filming, leaving a memo, or recording a prompt
- Photo library access only when you are picking a photo or saving one
- Each needs your device-level permission, and none of them is used in the background.
- On Android, the app uses Google's ML Kit, on your phone, to read invite QR codes and, for the depth effect that blurs the background, to find people and faces in the frame. It does not recognise who anyone is, and the images stay on your phone. ML Kit sends Google metrics about how these features perform and are used, never the images.
Age
At sign-up and at your first join as a guest, you confirm that you meet the minimum age for papershot where you live, and accept the Terms. See section 12.
App store privacy labels, in short. Data linked to you: contact info, identifiers, purchases, user content (photos, videos, and audio), usage data, coarse location, and diagnostics. No tracking across other companies' apps or websites, and no third-party advertising.
4. How We Use Data and Our Legal Bases
We use personal data for the purposes below. The legal bases apply to people in the EEA and the UK; equivalent grounds apply under the UAE PDPL and other regional laws.
| Purpose | Data used | Legal basis (GDPR Article 6) |
|---|---|---|
| Run the service (moments, invites, uploads, reveal, viewing) | Account, install identifier, content, moment details | Contract (Art. 6(1)(b)) |
| Process purchases and prevent fraud | Purchase receipts, identifiers, IP address | Contract, legal obligation (Art. 6(1)(b), 6(1)(c)) |
| Send transactional email, push notifications, and Live Activities | Email, push and Live Activity tokens, app language | Contract (Art. 6(1)(b)) |
| Keep moments safe: automated screening, reports, blocks, human review | Thumbnails and poster frames, reports, blocks, account or install identifier | Legitimate interests, legal obligation (Art. 6(1)(f), 6(1)(c)) |
| Fix crashes and keep the app fast | Crash reports and performance traces (pseudonymous) | Legitimate interests (Art. 6(1)(f)) |
| Understand which features get used (app analytics) | Usage events, user properties, device details, and coarse location (pseudonymous) | Legitimate interests (Art. 6(1)(f)), with an opt-out in Settings; in the United Kingdom, consent (Art. 6(1)(a)) |
| Understand how people find and use the website (website analytics) | Pages viewed, referring site and campaign tags, links and buttons used, device and browser details, page speed, coarse location (pseudonymous) | Consent (Art. 6(1)(a)), which you can withdraw at any time with Cookie choices |
| Keep the service secure and look into abuse | Security log, including IP address and user agent | Legitimate interests (Art. 6(1)(f)) |
| Enforce our terms and respond to legal process | Account, identifiers, content as needed | Legal obligation, legitimate interests (Art. 6(1)(c), 6(1)(f)) |
We send no marketing email and there is no product-update mailing. Where we rely on legitimate interests, you can object at any time by writing to support@papershot.app.
5. Automated Screening and Reports
Every finished upload from the current apps is screened automatically by Amazon Rekognition. Only the thumbnail of a photo or the poster frame of a video is sent, never the original file and never audio. Older versions of the apps that upload a photo without a thumbnail are not screened automatically, and what they add can still be reported. A high-confidence match hides the item and files a report, which a person reviews within 24 hours. A lower-confidence match leaves the item visible and files a report, so a person looks at it too. The screening fails open: if it cannot run, the item stays visible. No decision with legal or similarly significant effects is made automatically.
Anyone in a moment can report a photo, video, or memo (nudity or sexual content, violence or graphic content, harassment or hate, spam, or something else) and block another person. Hosts can block a guest from posting. We review reports within 24 hours. If something of yours was hidden or removed, you can appeal by emailing support@papershot.app.
No training on your content
We do not use your photos, videos, memos, or any other personal data to train artificial intelligence or machine-learning models. If we ever want to use content to train a model, we will ask you first, and use only the content of people who say yes.
6. How We Share Data
We do not sell personal information. We do not share personal information for cross-context behavioural advertising. We do not permit cross-app tracking.
Within a moment
Your display name is shown to the other people in the moment. What you add is shown to them according to the moment's reveal setting and the host's choices. Until the roll develops, other guests see only a blurred tile with your name and the time; only the host and you can see the item itself.
Service providers (subprocessors)
- Amazon Web Services: hosting of the website and the service (Amplify), media storage (S3), delivery (CloudFront), the database (RDS Postgres), automated screening (Rekognition), transactional email (SES), scheduled jobs (EventBridge), and server logs (CloudWatch). Region: Ireland (
eu-west-1), with delivery and upload acceleration at AWS locations worldwide. - Apple: in-app purchases and App Store Server Notifications, the Apple Push Notification service, and Sign in with Apple.
- Google: Firebase Cloud Messaging for push notifications on iOS and Android, Google Play Billing, Google Sign-In, Firebase Analytics (Google Analytics 4) in the apps, Google Analytics on the website, Google Cloud BigQuery for a daily copy of the analytics data (section 8), ML Kit on Android (section 3), Google Workspace for our email (what you write to support@papershot.app and our replies), and Google Fonts, which receives the Chinese, Japanese, or Korean characters in a moment's name, with no identifier, when we draw the picture for an invite link's preview.
- Sentry: crash and performance monitoring.
Each provider gets only the data it needs for its service, under a data processing agreement, with the protections the law requires. See /subprocessors for the full list with regions and data categories.
Legal disclosures
We may disclose personal data to comply with a binding legal demand (a subpoena, court order, or regulator request) or to protect our rights, property, or safety, or those of the people who use papershot or the public. We tell the people affected where that is lawful and practicable.
Business transfers
If we go through a merger, acquisition, financing, reorganisation, or sale of assets, personal data may be transferred with the same protections. We will tell you about any change of controller.
7. International Data Transfers
We store and process data in the European Union, in AWS eu-west-1 (Ireland). AWS's delivery network serves media, and speeds up uploads, from locations around the world, usually the one nearest you. Some providers process data in the United States, and we operate from the United Arab Emirates, so personal data may be transferred to those countries.
Where personal data of people in the EEA, the UK, or Switzerland leaves those places, we rely on:
- the European Commission Standard Contractual Clauses (Module Two and Module Three, June 2021) for transfers from the EEA;
- the UK International Data Transfer Addendum to the EU SCCs, or the UK International Data Transfer Agreement, for transfers from the UK;
- the mechanism recognised by the Swiss Federal Data Protection and Information Commissioner for transfers from Switzerland.
For transfers from the United Arab Emirates, we follow Articles 22 and 23 of the UAE PDPL (cross-border transfer) and the UAE Data Office's guidance.
Copies of our transfer agreements are available from support@papershot.app.
8. Data Retention
- Free moments. Media is kept for 48 hours after the roll closes.
- Paid moments. Media is kept for 30 days after the roll closes.
- When a moment expires. A scheduled job, run every hour, deletes the moment's photos, videos, and memos, its cover and recorded prompts, and every other file stored for it, and tells the host. About an hour later it deletes the moment's records: its details, guest list, shot list, favourites, reports, and the rest. If the host has notifications on, the app reminds them before the roll is deleted.
- Deleted moments and items. When a host deletes a moment, its files go at once and its records within about two hours. When a photo, video, or memo is deleted, its files go at once and its record within 48 hours. An item hidden or taken down after a report is kept out of sight, with its files, until its moment is deleted, so that the decision can be reviewed and appealed.
- Guest data. What a guest adds goes with the moment. A guest's name and profile photo stay with the guest profile for that phone until the guest asks us to delete them (see Delete your account), or until the guest signs in, when they move to the account. When we delete a guest's data, everything that phone added to any moment goes with it; reports the guest filed stay, without the phone's id.
- Account data. Kept while your account is active.
- Deleted accounts. Deleting your account deletes the moments you host: their files at once, their records within about two hours. Your profile photo, your push and Live Activity tokens, and any guest profile from your phone go at once too. What you added to other people's moments stays on their rolls until those moments expire. The account itself and its consent records are deleted for good 30 days later; from then on, what you added to other people's moments no longer carries your name or your phone's id. A deleted account cannot be restored: you can sign in again, but to a new, empty account.
- Purchase records. Kept for 7 years after the purchase, for tax and accounting, and then deleted. They stay, for those 7 years, when the account or the moment they paid for is deleted.
- Reports and blocks. A report goes with the moment it is about, or 48 hours after the item it is about is deleted. A record of each moderation decision stays in the security log. A block stays until the person who placed it removes it or their account is deleted for good.
- Security log. Kept to protect the service and to show what happened. IP addresses and user agents are removed from it after 12 months. When an account is deleted for good, its entries no longer name the account; when a moment is deleted, its entries lose its name and the names of the people in it.
- Cached copies. Our delivery network can keep serving a copy of a deleted file from its cache for a while: up to a day for photos, videos, and memos, and longer for some profile photos, covers, and recorded prompts added before 7 October 2026. Copies people saved on their own phones are theirs, and we cannot reach them.
- Crash and analytics data. Crash data is held by Sentry under its retention settings. Google Analytics keeps analytics data from the website and the apps for up to 14 months, and that period does not restart when you come back. Each day, Google Analytics also sends a copy of the previous day's analytics events to Google Cloud BigQuery, in our own project in the European Union, where the copy is deleted after 60 days. If you ask us to delete your data, copies already in BigQuery stay until their 60 days are up. Aggregated data may be kept longer.
9. Security
- Encryption in transit via HTTPS / TLS, including forced TLS to the database
- Media encrypted at rest (AES-256)
- Media goes straight from your phone to storage over short-lived signed URLs. The storage itself is closed to the public
- Media is delivered through CloudFront from addresses that cannot be guessed. Anyone who has an address can open that file until it is deleted, so treat a copied address as you would the photo itself
- Administrator access limited to named people, each with their own account, and a log of every change they make in the admin panel
Limits. No security method is perfect. We cannot promise absolute security.
Security incidents. What we do if a personal data breach happens is set out in section 10.
10. Data Breaches
A personal data breach is a security incident that leads to personal data being lost, destroyed, changed, disclosed, or accessed without authorisation. For example: someone breaking into our database or storage, or a moment's photos being seen by people who were not in it. If we discover a breach, or someone tells us about one, we:
- Contain it. We act at once to stop it: we revoke exposed credentials and keys, close the gap, and take the affected part of the service offline if we need to.
- Assess it. We work out what happened, which data and which people are affected, and the likely risk to them.
- Notify the authorities. Where the law requires it, we notify the competent supervisory authorities (including the UAE Data Office and the relevant EEA and UK authorities) without undue delay and, where feasible, within 72 hours of becoming aware of the breach, or sooner where a law sets a shorter deadline.
- Tell you. If the breach is likely to put your rights and freedoms at high risk, or wherever a law requires it, we tell you directly and without undue delay, by email or in the app. If we cannot reach everyone affected individually, we publish a notice on our website and in the app instead.
- Fix the cause. We correct what allowed the breach, review our safeguards, and keep an internal record of every breach, its effects, and what we did about it, including breaches we did not have to report.
What our notice tells you. In plain language: what happened and when; what kinds of your data are involved; the likely consequences; what we have done and are doing about it; steps you can take to protect yourself, such as watching for messages that pretend to come from papershot; and how to reach us.
Breaches at our service providers. Our subprocessors (section 6) must tell us without undue delay about any breach affecting your data. We then follow the same steps. Business customers whose data is affected are notified as our Data Processing Addendum provides.
Reporting a breach or vulnerability. If you think your papershot data has been exposed, or you have found a security problem, email support@papershot.app with "URGENT: Security" in the subject line, or see our security.txt.
11. Your Choices and Rights
In-app controls
- Delete your account in Settings under Delete account, or without the app as Delete your account explains. The moments you host, and everything in them, go at once. What you added to other people's moments stays on their rolls, without your name once the account itself is deleted for good 30 days later. A deleted account cannot be restored.
- Download a copy of your account data in Settings under Request my data. The app gives you a JSON file with: your profile and notification settings; every moment you host, with what is on its roll and links to its recorded prompts; what you added to other people's moments; the moments you joined; your Guest Lens shot lists; your favourites; your purchases, with their receipts; the people you blocked, and the posting bans you placed or were given; the reports you filed; guest profiles that moved to your account; your Sign in with Apple record; your consents log, with the IP address each consent came from; your devices and Live Activities; your security log (what your account did, when, and from which IP address and app or browser); and your past requests. You can ask three times in a row, then once every 20 minutes; a request that fails does not count.
- Turn app analytics off in Settings under Help improve papershot, or in Privacy choices without an account
- Manage push notifications in your device settings
- Report a photo, video, or memo, or block the person who added it, from the item itself
On the website
- Accept or reject analytics cookies at any time with Cookie choices at the foot of any page. Rejecting deletes the analytics cookies already set.
- A Global Privacy Control signal from your browser counts as rejecting
Data requests
Email support@papershot.app to access, correct, port, or delete personal data, or to appeal a moderation decision. We respond within 30 days (or sooner where the law requires). We may keep limited data where the law requires it, to prevent abuse, or in backups until they roll off.
12. Children
papershot is for people aged 13 or older, or 16 or 18 where the law where they live says so. You confirm that you meet this minimum age, and accept the Terms, at sign-up and at your first join as a guest. We do not knowingly collect personal information from children under 13 in breach of the Children's Online Privacy Protection Act (COPPA), and we do not knowingly collect personal data of children where parental consent would be needed under GDPR Article 8, the UK Age Appropriate Design Code, or the UAE PDPL. If you believe a child has given us personal data, email support@papershot.app and we will delete it.
13. Regional Rights and Addenda
EEA, UK, and Switzerland (GDPR / UK GDPR / FADP)
You have the rights of access, rectification, erasure, restriction of processing, data portability, and objection. Where processing is based on consent, you can withdraw it at any time without affecting what was done before. You can complain to your local supervisory authority. Our EEA and UK representatives (GDPR Article 27) are not yet appointed. We will name them in section 1 once they are.
Automated decision-making. Automated screening can hide an item until a person reviews it (section 5). We make no decision with legal or similarly significant effects by automated means alone.
California (CCPA / CPRA)
California residents have the right to know what personal information we collect; to access, correct, and delete it; to opt out of sale or sharing for cross-context behavioural advertising (we do neither); and to limit the use of sensitive personal information. We do not treat you differently for exercising these rights. To exercise any right, email support@papershot.app or use the in-app controls. We verify your identity through the email address on your account; an authorised agent can act for you with written authorisation. To submit a Do Not Sell or Share My Personal Information request, email the address above with that phrase in the subject line, although we do not sell or share personal information as California law defines those terms.
Shine the Light. California Civil Code section 1798.83 lets California residents ask what personal information we shared with third parties for direct marketing. We shared none in the preceding calendar year.
Sensitive personal information. We use sensitive personal information only for the purposes it was collected for, such as running and securing the service.
Other US state privacy laws
Residents of states with comprehensive consumer privacy laws have rights of access, correction, deletion, and portability, and rights to opt out of targeted advertising, sale, and certain profiling. We do not sell personal data, do not run targeted advertising, and do not profile people for legal or similarly significant decisions. To exercise your rights, email support@papershot.app. Where a law gives you a right of appeal, you can appeal a denied request by replying to our response.
Brazil (LGPD)
If you are in Brazil, you have rights under Law No. 13.709/2018 (LGPD), including confirmation of processing; access; correction; anonymisation, blocking, or deletion of unnecessary or excessive data; portability; deletion of personal data processed with consent; information about the public and private entities we share data with; and information about your right to refuse consent and what follows from that. To exercise these rights or to reach our Encarregado (data protection officer), email support@papershot.app with "LGPD" in the subject line. You can also complain to the Autoridade Nacional de Proteção de Dados (ANPD).
Canada (PIPEDA and provincial laws)
We follow the Personal Information Protection and Electronic Documents Act (PIPEDA) and the substantially similar provincial laws in Quebec (Law 25), Alberta (PIPA), and British Columbia (PIPA). You have the right to access and correct your personal information. Contact support@papershot.app. You can complain to the Office of the Privacy Commissioner of Canada or the relevant provincial commissioner.
Australia (Privacy Act 1988)
We handle personal information under the Australian Privacy Principles. You can ask to access and correct your personal information by emailing support@papershot.app. Raise a complaint with us first; if it stays unresolved, you can take it to the Office of the Australian Information Commissioner (OAIC).
United Arab Emirates (PDPL)
We are established in the United Arab Emirates and subject to the UAE PDPL. If you are in the UAE, you have rights under Articles 13 to 18 of the PDPL, including the right to be told how your personal data is used, to access it, to have it corrected or deleted, to restrict or object to processing, and to data portability. To exercise any right, email support@papershot.app. You can also complain to the UAE Data Office.
Other regions
Where local law gives you more rights, those rights apply. To ask about your jurisdiction, contact support@papershot.app.
14. Cookies and Similar Technologies
See /cookies for what the website stores and the storage the apps use. Wherever you are, the website asks before it loads any analytics, and Cookie choices at the foot of every page changes your choice. Section 3 describes the apps' analytics and how to turn it off. The website runs no advertising.
15. Notifications and Live Activities
Push notifications are rendered on our server in your app language. We send them when a moment starts, ends soon, and has ended, plus a recap two days later and warnings before a roll is deleted. On iOS, a Live Activity can show the running roll on your lock screen. Both are optional: manage them in your device settings.
16. Policy Changes
We post updates to this page. We tell you about material changes in the app or by email. The "Last updated" date at the top shows when the policy last changed. Using papershot after a material change means you accept it, except where the law requires fresh consent.
17. Contact
Controller: Wellbayt LLC-FZ (United Arab Emirates)
Email: support@papershot.app
Response time: 30 days (or sooner where the law requires).
Urgent requests: Put "URGENT: Privacy Request" in the subject line.