Privacy Policy

Last updated: October 5, 2026

1. What we collect

Nickname: what you type in. It appears as “Shot by …” on your photos and in the list of people in a camera.
Anonymous user ID: created automatically the first time you open the app. We do not collect your email address, phone number, or real name.
Photos: the photos you take with a camera, and when you took them. Photos are shown only to the people in that camera, and only after its developing time.
Camera details: the camera's name, number of shots, developing time, members, film, and invitations (who invited whom).
App language: saved so that invitation notifications reach you in the language you use.

We do not use your location, your contacts, or an advertising identifier. We do not give your data to third parties for their own use and we do not use it for advertising.

2. What we use it for

Only to provide the app's features: sharing a camera, developing and showing photos, and saving them.

3. Storage and deletion

Photos are stored on Google Cloud (Firebase, Tokyo region) and are deleted automatically 30 days after the developing time.
When the person who created a camera deletes it, its photos can no longer be seen by its members.
When you choose “Delete account” in the app's settings, your nickname, user ID, and notification token are deleted. Photos you left in cameras you joined stay there with your name, as part of what the group shares, until they expire. Your nickname in those cameras' member lists also stays until then. Records used to prevent creating or joining cameras in rapid succession (when you last created one, how many you created, the ID of your last camera, when you last joined one, and when invitation notifications were sent) remain under the user ID. Crash and usage records (Crashlytics, Google Analytics) are linked to the user ID and may remain for up to 90 days after you delete your account.

4. Access control

Photos can be retrieved only by the members of that camera, and only after its developing time. Nobody, including the person who took a photo, can get it out before the developing time.

5. Services we use

Firebase (Google LLC): authentication (an anonymous ID and, if you choose, a Sign in with Apple identifier; we do not receive your name or email address), database, storage, push notification tokens, App Check (confirming that requests come from the real app), Google Analytics for Firebase (how screens are used, linked to the anonymous user ID), and Crashlytics (crash information). Cloudflare: serving the web pages. We use all of these only as far as needed to provide and improve the service, never for advertising.

6. If you use NapShot outside Japan

Your data is stored on servers in Japan (Tokyo). Japan is recognized by the EU and the UK as providing an adequate level of protection for personal data. Where Google or Cloudflare process data in other countries, they do so under safeguards such as their standard contractual clauses.
If you live in the EU, the UK, or a similar jurisdiction: our legal bases for processing your personal data are providing the service to you (performance of a contract) and our legitimate interests in preventing abuse and diagnosing problems. We do not use your data for advertising and we do not make automated decisions that single you out.
You can ask to access, correct, delete, or receive a copy of your data, and to restrict or object to its use. Use “Delete account” in the app's settings or contact us. You also have the right to complain to the data protection authority in your country.
NapShot is for people aged 13 and over. If the age at which you can consent to data processing is higher in your country, use the app only if you have reached that age or have your parent's or guardian's consent.

7. Changes

If this policy changes, we will announce it on this page.

8. Who runs NapShot, and contact

NapShot is run by an individual in Japan (named in the Terms of Use). Please contact us.