Privacy Policy

Last updated: 2026-09-16

What you create in the App — photos, captions, folder and group names — is stored on your device, not sent to the developer or analytics services. PDF sharing and photo exports that you initiate are separate. The App sends limited usage and diagnostic data to Google's Firebase to improve the App and fix defects. The Android version and iOS version 1.1.0 and later show ads before purchase. iOS version 1.0.0 has no ads or tracking permission request. See section 5 for these version differences.

1. What is not sent to the developer or analytics services

The App does not send the following to the developer or analytics services:

Photos you take, screenshots you import, or their image data
Titles, descriptions, folder names, group names, or any text you enter
Name, email address, phone number or other contact details
Precise location from GPS or similar sources (see section 4 for approximate region inferred from an IP address)

The App requires no account, and the developer has no server that stores your photos or text. We do not add the contents of photos, captions or other user-created text to analytics events or crash reports. When you share a PDF, its contents are passed to the app or recipient you choose in the operating system's share sheet. That service's policies apply to the shared copy.

2. What is stored on your device

The following is kept inside the App's own storage:

The images you captured or imported, and their thumbnails
Titles, descriptions, folder and group names, ordering and display settings
Whether you have made the in-app purchase

Uninstalling the App removes this data from the App's storage. Individual items can be deleted inside the App. Exported photos and shared PDFs are separate copies and must be deleted at their destinations. Operating-system backups and photo syncing follow the settings and policies of those services.

3. Device permissions

Camera

Used to take photos. Captured images are stored in the App's own storage.

Photo library (read)

Used to bring existing photos and screenshots into the App. Normally, you select the images to import. On iOS, if you enable screenshot waiting, the App checks for new screenshots taken after waiting began. It automatically imports a single new screenshot or asks you to choose if there are several. Screenshots from before waiting began are not automatically imported. The App does not send photo-library contents to the developer or analytics or advertising services.

Photo library (add)

Used to save photos from the App back to your camera roll. This feature asks for add-only access: saving does not require reading, and we ask for no more permission than a feature needs.

4. Usage and crash data

To improve the App and fix defects, it uses Google Analytics for Firebase and Firebase Crashlytics, provided by Google LLC. The following is sent:

App launches, screen views, usage time, and which features were used and how often (captures, imports, groups created)
Numbers such as a photo count or the current column count
App version, OS version and device model
App-installation and diagnostic identifiers used to count usage and investigate defects
Approximate location, such as country or region, inferred from an IP address (the App does not use the device's location services)
Events indicating that the purchase screen was opened or an in-app purchase completed
Error details and the sequence of events when the App stopped
Diagnostic information about App and SDK operation and stability

Custom analytics events are limited to predefined event names and numbers, such as counts. Firebase also automatically collects information such as device and session data. Photo and caption contents are not sent to analytics services.

Usage and crash reporting are enabled by default. You can stop them at any time from the App's menu. "Send usage data" and "Send crash reports" are separate switches, and your choice is remembered. Turning them off does not delete data that was already sent.

See Privacy and Security in Firebase for Google's handling of this data.

5. Advertising and tracking

The Android version and iOS version 1.1.0 and later show one Google AdMob banner ad below the photo list before purchase. iOS version 1.0.0 displays no ads and does not contain an advertising SDK. After purchase, ads are no longer displayed and no new ads are loaded. This does not delete information already sent.

To deliver, measure and analyse ads and prevent fraud, device identifiers, approximate location inferred from an IP address, ad impressions, interactions and advertising SDK usage, and device and diagnostic information may be sent to Google and its advertising partners. This does not include photo or caption contents. The usage and crash reporting settings in section 4 are separate from advertising.

iOS version (App Store)

iOS version 1.0.0 has no ads and does not request App Tracking Transparency (ATT) permission. The following describes iOS version 1.1.0 and later, which introduce advertising.

The App tracks you (personalises ads using data from other companies' apps or websites) only if you allow it through ATT. It checks ATT when the photo list opens and when the App returns to the foreground. It requests permission only if Premium access is not stored on the device, ATT is not yet determined, the App is active, and no other permission request is pending. It does not request a prompt for Premium users or if ATT has already been answered. iOS settings or device or account restrictions may also prevent the prompt from appearing.

While ATT is not determined, the App does not call the advertising SDK's initialisation API or request ads. If tracking is not authorised, ads are requested as non-personalised and the iOS advertising identifier (IDFA) is not available. If Premium access is stored at launch, the App also does not call that API or request ads. Declining ATT does not prevent you from using basic features such as taking photos and editing.

You can review and change the permission in iOS Settings > Privacy & Security > Tracking. The usage and crash reporting controls in section 4 are separate from ATT.

Android version (Google Play)

Identifiers such as the advertising ID may be sent, and information may be used to personalise ads. You can manage the advertising ID and ad personalisation in Android settings.

See How Google uses information from sites or apps that use our services for Google's handling of advertising data.

6. In-app purchase

The App offers a one-time in-app purchase. The transaction is handled by Apple (App Store) or Google (Google Play), who process your payment details. The developer never receives them.

To confirm or restore a purchase, the App communicates with those stores. That communication never includes photos or text you created in the App. Your purchased state is kept on the device, so paid features work offline. When usage reporting is enabled, purchase events are also sent for analytics as described in section 4. Payment details, such as card numbers, are not sent to Firebase.

See Apple's Privacy Policy and Google's Privacy Policy for how they handle your data.

7. About this website

Everything above concerns the App. This website (easyshot.tsukuruya.me) is separate, and the following applies to it.

This site uses Google Analytics (GA4), provided by Google LLC, to understand how the site is used. It sets cookies and sends the following to Google:

Pages viewed, time spent, and the referring page
Approximate region, browser and device type
An identifier generated by a cookie

This is used to improve the site. It contains nothing that directly identifies you, such as a name or email address. Data you create in the App (photos, captions, folder names) has nothing to do with this and is never transmitted.

To opt out, disable cookies in your browser or install the Google Analytics Opt-out Add-on. See Google's Privacy Policy for how Google handles this data.

8. Sharing with third parties

Usage and diagnostic data is sent to Google as the Firebase provider. Information needed to purchase or restore is sent to Apple or Google as the store provider. Advertising information may be sent to Google and its advertising partners as described in section 5 (except iOS version 1.0.0, which contains no ads). The developer does not sell or provide data to data brokers. These transmissions do not include photo or caption contents. See section 1 for sharing that you initiate.

Website analytics data is sent to Google as described in section 7.

9. Children's privacy

The App is not directed primarily at children. The App does not send photo or caption contents to the developer or analytics services. Usage and diagnostic data and advertising information are handled as described in sections 4 and 5, regardless of the user's age.

10. Changes to this policy

If this policy changes, this page is updated and the date above is revised. Significant changes are also noted in the App's release notes.

11. Contact

Questions about this policy: see the contact page.