Privacy policy

1. Website and APK downloads

The website is hosted on Cloudflare Pages. APK files are served through Cloudflare R2 at downloads.scamhawk.in. Cloudflare processes ordinary connection and security information needed to deliver and protect these services, such as IP addresses, requested URLs, access times and browser/network information. Provider-side logs or security cookies are separate from the text you enter into the checker. See Cloudflare’s privacy policy.

Our website code has no advertising, analytics tracker, account registration, message-history database or local-storage history. Text entered into the checker stays in page memory and is discarded when cleared or the page is closed. The website does not submit it to the Android analysis server or an AI provider. Links to other services have their own privacy practices. Downloading an APK does not create an account or enable a cloud feature.

2. Android text and image checks

Pasted or shared message text is checked locally by default. Opening shared text can trigger an on-device check; it does not automatically submit text to a server. The app does not maintain a scan-history database. Avoid including OTPs, PINs, passwords, full bank details or unrelated private information.

You can choose a screenshot or use your camera app to photograph a message. Google ML Kit performs the selected text/QR recognition on the phone after you accept the image-reading disclosure. Google documents separate SDK collection of installation identifiers, device/app information and performance/usage diagnostics, as well as service contacts. Its published disclosure describes current SDK versions; runtime behaviour of the exact bundled dependencies remains under review. Declining skips recognition for that image; it does not guarantee removal of previously queued SDK work. See ML Kit privacy information and SDK data disclosures.

Recognized text can be wrong. You review and edit it before scanning. The app’s optional server scan sends the reviewed text, not the selected photo. Camera capture uses a temporary private cache copy. Deletion is attempted after review/cancellation; interrupted captures older than 24 hours are cleaned on the next camera attempt. The camera app or your gallery may retain its own copies.

Permissions and other apps

The current manifest permits internet access and optional phone calling/call-ending actions requested by you. Phone permissions are requested in context and can be denied. The current build does not request SMS-inbox, contact-list, microphone, notification-monitoring, location or broad-photo-library access. Camera capture is delegated to your camera app. Text/image sharing is limited to the content you choose.

SMS and WhatsApp help messages use the selected messaging app’s user-controlled flow. Numbers and prepared message text are handed to that app when you choose the action. Calls pass the chosen number to Android telephony. Those providers, recipients and any copies they retain are outside ScamHawk’s deletion controls. Call checklists use your answers and do not analyse or record live calls or video.

3. Optional server analysis and AI assistant

Server analysis sends your current reviewed text to the displayed HTTPS destination only after you select server mode, consent and scan. The development build can use a configured development tunnel; the server operator, tunnel and hosting provider can process traffic or logs. An endpoint is not an independent safety guarantee. Ask the operator about its current handling before submitting private text. Use on-device mode if that handling is unclear.

The optional OpenAI assistant requires a separately configured relay and per-question consent. If enabled, your question is sent through that relay to OpenAI to generate safety guidance. The current relay requests non-storage of response application state, but this is not a promise of zero provider retention; provider security/abuse handling may still apply. The relay access token stays in the assistant screen’s memory. There is no cloud-AI connection in the website checker. See OpenAI’s API data controls. Optional services are pilots, not continuously monitored emergency services.

Optional paired-family pilot

Ordinary offline scanning and local trusted contacts do not require a family account. If you separately join the paired-family pilot, the chosen operator stores account/device references, aliases, credential hashes, recovery/setup metadata, relationships and fixed help/acknowledgement status. These server records are operator-readable and are not end-to-end encrypted. Device/recovery credentials are encrypted locally with Android Keystore protection; the server stores capability hashes. Pairing does not verify a person’s legal identity. Foreground refresh is not guaranteed push delivery.

The family pilot is not activated merely by visiting this website or downloading the APK. Its server, backups and logs require separate operator review before production use. No universal server/proxy backup or security-log retention period has been established for production. This website must not be interpreted as promising immediate erasure from those systems.

4. Storage and retention in the current app

Messages sent to someone else, camera/gallery originals, exported notes and SDK/provider records cannot be erased by clearing ScamHawk. Android and its storage system also affect how deleted data is physically removed.

5. Your choices

• Use on-device checks without enrolling in a family account or using cloud AI.
• Decline a server submission, image-reading consent or optional phone permission; the corresponding feature may be unavailable.
• Remove a trusted contact, delete a saved incident note or clear Android app data. See instructions and their limits.
• If enrolled in a family pilot, use the account-deletion action where available. Removing a device or clearing local credentials is different from deleting a server account.

External privacy/deletion request intake is not yet active. The planned address is listed on the support page with its availability status. Do not email recovery codes, bearer tokens, identity documents or bank credentials. A production rollout remains subject to a working contact process, SDK/data review and device validation.

6. Changes and audience

ScamHawk is a development safety tool, not an emergency service or a guarantee that a message/person is safe. No age or identity verification is currently implemented; age-related safeguards and the intended production audience remain part of launch review. Do not submit children’s private messages or unrelated personal data. Material changes to how the product handles data will be reflected here and, where appropriate, in the app’s disclosures before the relevant feature is used.