Screengram privacy policy

Screengram is a screenshot camera app. This policy describes what data the app handles, where it lives, and what is sent off your device. Plain language, no surprises.

If you have questions, email jfu213@gmail.com.

Short version

• Your photos, screenshots, screengrams, captions, and albums stay on your device. Screengram does not upload them to any server.
• Screengram has no accounts, no login, no feed, no followers, no advertising, and no third-party tracking SDKs.
• Two narrow exceptions: anonymous crash diagnostics (sent automatically when the app crashes) and feedback you explicitly submit through the in-app feedback form. Both are described below.

What stays on your device

All of the following live locally on your iPhone and are never transmitted by Screengram:

• The photos you capture with the in-app camera
• The screenshots Screengram pairs them with
• The composite screengrams Screengram produces
• Captions, overlay text, and album names you create
• Your library, album organization, and viewing history
• The local event log used to debug your own session (see "Diagnostic events" below)

Photos that Screengram saves to your camera roll are stored in your Photos library and are governed by Apple's photo permission system. You control them like any other photo.

What is collected

Crash diagnostics (Sentry). When the app crashes, a diagnostic report is sent to Sentry, a third-party crash reporting service. The report includes the type of crash, the stack trace, the iOS version, the device model, and a random per-install identifier (see "Install ID" below). It does not include the contents of your screengrams, screenshots, photos, captions, album names, or any other content you create in the app. Crash reporting is declared in the app's privacy manifest as NSPrivacyCollectedDataTypeCrashData, linked to the install ID, and used solely for fixing bugs.

Install ID. When Screengram first launches, it generates a random UUID and stores it locally in the app's shared container. This identifier is included in crash reports and in any feedback you explicitly submit, so that multiple reports from the same installation can be correlated for triage. It is a random value, is not derived from any device or user identifier, and cannot be reversed to identify you. It is reset if you uninstall and reinstall the app.

Diagnostic events (local-only by default). Screengram writes a local event log to your device documenting in-app actions like "screengram saved" or "share sheet completed," along with non-identifying metadata. This log lives on your device. It is only sent off-device if you choose to attach it to a feedback submission (see below).

What you can choose to send

Feedback. If you open Settings → Send Feedback and submit a report, the app sends a JSON payload to Screengram's feedback service (a small Cloudflare Worker) which files a ticket in our issue tracker. The payload includes:

• The description you typed
• Your install ID
• Your device model and iOS version
• The recent diagnostic event log (so we can see what you did before the issue)

We use feedback submissions to fix bugs and improve the app. Nothing is sent unless you tap the submit button.

What Screengram does not do

• No advertising SDKs, no advertising identifiers (IDFA), no advertising frameworks.
• No third-party analytics SDKs (e.g., Firebase Analytics, Mixpanel, Amplitude).
• No location collection.
• No contact list or address book access.
• No tracking across other apps or websites.
• No selling or sharing of personal information.
• No accounts, sign-in, or backend service that persists your content.

Permissions Screengram asks for

Screengram requests these iOS permissions. You may decline any of them; the affected features will simply not work.

• Photo Library — to read screenshots from your camera roll (so we can pair them with a fresh photo) and to save finished screengrams back to your library. Required for the core capture flow.
• Camera — to take the paired photo. Required for the core capture flow.

Screengram does not request notifications, location, microphone, contacts, calendars, or any other permission in v1.

Third-party services Screengram uses

• Sentry — receives crash diagnostics described above. Sentry's privacy policy.
• Cloudflare Workers — receives feedback submissions when you submit them, and forwards them to our internal issue tracker. Cloudflare's privacy policy.

Both services are configured to receive only the narrow data described above.

Children

Screengram is not directed to children under 13. We do not knowingly collect data from children under 13.

Changes

If this policy changes, the effective date at the top will be updated and the new version will be posted at this URL. Material changes will also be noted in the app's release notes.

Contact

Questions, concerns, deletion requests, or anything else:

jfu213@gmail.com

Deletion: because Screengram does not maintain a user account or store your content on a server, "deleting your data" simply means uninstalling the app, which removes all locally stored screengrams, screenshots, photos, albums, captions, the install ID, and the local event log. If you have submitted feedback that included your install ID, email the address above and we will remove the matching submissions from our issue tracker.