Your media stays on your device during scanning.
This policy applies to the Sensitivity Android beta, package com.sensitivity.android. The Apple-app privacy policy describes iPhone, iPad and Mac versions separately.
Sensitivity for Android
Sensitivity is provided by Dmytro Polianskyi. For privacy questions, contact hello@sensitivityscan.com.
You choose what the app can inspect.
The app uses Android photo and video permissions or the system photo picker to read the media you authorize. Access can be limited to selected items where Android supports it. You can change or revoke access in Android Settings. Revoked or unavailable items cannot be scanned.
If you select an item held by a cloud media provider, Android or that provider may download or stream it to the device. That transfer is governed by the provider's policies. Sensitivity does not upload your media to its developer for analysis.
Models run locally.
Photo classification and video-frame analysis run on your device. Media contents, thumbnails, filenames, media identifiers, detection scores and result lists are not sent to Sensitivity servers. The Android beta has no Sensitivity account, cloud library or advertising SDK. Optional product analytics and crash diagnostics are described below. Detection is imperfect; review every result before taking action.
Off unless you choose to help improve the beta.
Starting with Android beta build 2, you can choose to enable product analytics in the first-run dialog or Settings. It is off by default. If you opt in, the app sends a limited set of interaction events to Amplitude, our analytics service provider, to help us understand reliability and use of the beta. These cover app opening, onboarding, Settings, scan start/completion/pause/resume/stop and background transitions, paywall viewing, and purchase or restore completion.
Events contain a random resettable installation identifier, a random event identifier, event time, Android platform, app version/build, and beta/development and schema labels. They do not contain your photos or videos, filenames, media identifiers or URIs, scan counts, detection findings or scores, purchase receipts or tokens, account details, advertising identifiers, or location. This beta uses our existing Amplitude Development project.
The app sets the analytics IP field to 0.0.0.0 to prevent IP-based location enrichment. Amplitude necessarily receives the connection's IP address to handle the network request; this is not a promise that your IP address is never transmitted. See Amplitude's Privacy Notice.
The app keeps a local queue of at most 100 events when delivery is pending; entries older than seven days are discarded when the queue is next updated. Turning analytics off in Settings clears the local queue and installation identifier and cancels the active analytics connection. It stops future analytics collection, but cannot retract events already received by Amplitude. Re-enabling analytics creates a new installation identifier. You may contact us with privacy or deletion requests; because the identifier is not tied to an account, we may be unable to identify your earlier events from your email alone. We do not claim that server-side events are automatically deleted after seven days.
Scanning remains local whether analytics is on or off. Debug builds do not send these product-analytics events. Google Play's own processing and this website's analytics are separate.
Crash reports are a separate choice.
Starting with Android beta build 4, Firebase Crashlytics is available as a separate optional diagnostics setting, off by default. Only after you enable it does the app initialize Firebase for crash reporting. Google Firebase then receives crash and app-not-responding (ANR) diagnostics, stack traces, technical app/device/operating-system information, and installation and session identifiers. We use these reports to investigate crashes and improve app stability. Reports are transmitted over encrypted HTTPS.
This integration does not add Firebase Analytics or advertising tracking. We do not attach user/account IDs, photos, videos, media filenames, scan results or custom media logs to crash reports. Standard diagnostics can include runtime exception text supplied by the operating system or libraries; we cannot promise that every such message is fully redacted. See Firebase's privacy and data-processing information.
Turning diagnostics off disables automatic report transmission and requests deletion of unsent Crashlytics reports. It does not delete reports already sent to Firebase. There is no in-app remote-deletion control for those reports. You can contact us with privacy questions or requests. Optional Amplitude product analytics has its own setting and is unaffected by your diagnostics choice.
Local results and preferences
The app stores media references and scan checkpoints locally, including selected and completed item references, candidate results, failure state and timestamps. Saved results and scan checkpoints use encrypted app-private storage with keys managed by Android Keystore. Preferences, reminder settings and the locally cached video-unlock state are stored in app-private settings. The app does not create a cloud copy of your library.
Temporary decoding data stays on the device. Android backup is disabled for the app. Local app records remain until cleared through the app where available, through Android's Clear storage control, or by uninstalling the app. Clearing app records does not itself delete the original media from your library.
Review and deletion are your choices.
Sensitivity does not automatically delete media based on a model prediction. When you choose to delete selected media, it uses Android's media-deletion flow, including system confirmation where required. Recovery or cloud synchronization of deleted originals depends on Android and your media provider.
Device authentication can protect access to saved results where available. This does not protect a compromised device or replace Android's device security.
Google Play handles purchases.
Where video scanning is offered as an in-app purchase, checkout, payment and restoration are handled through Google Play Billing. Google processes purchase and payment information under its own policies. Sensitivity receives the purchase status and information required to verify and acknowledge it through Google Play; it stores a local unlock flag and purchase date. The developer does not receive your full payment-card details, and the app does not send purchase tokens to a Sensitivity backend.
See Google's Privacy Policy. Clearing local app storage does not erase Google's purchase records or cancel a transaction.
Local reminders and scan progress
If you permit notifications, the app can show local reminders and foreground scan-progress notifications. These do not use a Sensitivity push-notification server.
Information you send voluntarily
If you contact support by email, we receive your email address and the message and attachments you choose to send. We use them to respond and resolve the issue. Please do not send sensitive photos or videos unless they are necessary and you intentionally choose to share them. You can request deletion of support correspondence by emailing us; retention may be required for legal obligations or resolving a dispute.
The website is separate from the Android app.
Opening the website uses your browser and the website's own analytics controls. The Android beta's local-scanning policy does not mean this website is analytics-free. See website statistics and opt-out information.
Policy updates
We will update this page if the Android app's data practices change. The date above identifies this revision.