ProofShot — Privacy Policy
Last updated: October 4, 2026. Applies to ProofShot 26.10.1.
All languages · Terms of Use · Support
This policy explains how ProofShot handles information. “We” means the application provider identified on ProofShot’s App Store listing. The documentation and support repository is maintained under the GitHub account napp-dev.
1. Information kept on your device
ProofShot stores photos, videos and any recorded sound, optional check names, the date and time a check was saved, its deletion date, and your app preferences on your device. These records let you review what you photographed before leaving.
The app does not upload this content to us or Firebase, and does not add it to your photo library. We cannot view or recover your saved checks. The app has no account system or its own cloud synchronization. iOS device backups may include app data, depending on your settings; those backups are managed by you and Apple, not by ProofShot.
2. Permissions
- Camera: to take photos and record videos in the app.
- Microphone: optional, to include sound in a video when permission is granted.
- Notifications: optional local reminders before a check’s scheduled deletion.
You can change these permissions in iOS Settings. The app does not request access to contacts or precise GPS location. The current version has no advertising, subscriptions or in-app purchases. We do not use advertising identifiers or collect a log of your checks and viewing actions for behavioural analytics. Firebase’s technical processing is described separately below.
3. Firebase Remote Config
At launch, ProofShot requests remote configuration from Google’s Firebase Remote Config to check the minimum supported app version. Firebase Installations supplies an installation identifier and authentication token. The SDK sends technical information, including app and Firebase identifiers, app version and build, SDK and iOS versions, device region/country code, language and time zone. Network requests also expose your IP address to Google. Firebase may process operational diagnostic data and aggregate version information.
This is technical service data, not your photos, videos, recorded sound or check names. The app does not include Firebase Analytics or Crashlytics, and does not use Remote Config personalization. Configuration requests start automatically; there is no separate in-app switch to disable them. Removing the app stops future requests from that installation. Device permissions do not control this network processing.
4. Purpose, providers and processing locations
Local data supports the features you choose to use. Technical configuration supports version compatibility and reliable operation; support messages are used to answer your request. Where a legal basis is required, we rely on our legitimate interests in those operational and support purposes, subject to your rights under applicable law.
Google processes Firebase service data on its infrastructure, which may be outside your country. Details: Firebase privacy information and Google Privacy Policy. We do not sell personal information or share your check content for advertising.
This documentation site is hosted on GitHub Pages. We add no analytics scripts, external advertising or tracking cookies. GitHub processes hosting requests under its Privacy Statement.
5. Retention and deletion
Choose 1, 3 or 7 days, or a custom deletion date for a check. Expired checks are removed when the app next opens or becomes active; deletion does not necessarily occur while it is closed. You can delete a check or all records in the app. Deleting the app removes its local app data from the device; offloading it may keep that data. Copies in device backups follow your backup settings and may be restored.
Deleting checks does not delete Firebase technical records. Firebase installation identifiers are retained under Google’s documented service rules until deletion is requested; other technical data follows the provider’s retention rules. Uninstalling the app is not a request to immediately erase Google’s existing records. We keep support emails and related information only as needed to handle the request and applicable obligations.
6. Your choices and requests
You can manage permissions, deletion dates, local records and device backups. Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to processing, and complain to a competent data protection authority. If processing depends on consent, you may withdraw it without affecting earlier lawful processing. Installing the app does not waive these rights.
Contact us by email at napp.dev.support@gmail.com. Do not send passwords, sign-in details or installation tokens; attach photos or videos only if they are needed to resolve your request. Since we have no account system, we may be unable to link technical data to you using only a name or email address; any information needed to handle a request must be limited to what is necessary.
When you email us, we receive your email address, message and any attachments. We use that information only to respond.
7. Security, children and changes
The app uses local iOS storage, and Firebase connections use HTTPS. ProofShot does not provide an in-app PIN or biometric lock; protect your device with its security settings. No storage or network service can be guaranteed completely secure.
ProofShot is a household utility, not a service specifically directed at children. Where local law requires it, a parent or guardian should supervise use and recording permissions. If a child has sent personal information to support, contact us by email without repeating that information.
Updates to this policy are published here with a revised date. Any additional notice or consent required by applicable law will be handled as required. Questions about this policy: napp.dev.support@gmail.com.