Privacy

Your message stays in your browser.

Link checks

Up to three extracted HTTP(S) URLs are sent to our server and Google Web Risk. URLs can contain personal information. Remove sensitive details before checking. We do not intentionally store submitted messages or URLs in our application database; hosting and provider operational logging is separate.

Usage and abuse prevention

We count accepted app-open, check-start, and check-complete events. These are not unique-person counts. Random event identifiers expire after one day. A secret-keyed, time-windowed digest of the request IP is used for request limits and removed after expiry; we do not store the raw IP in these tables.

Optional contributions and feedback

If you opt in, predefined warning labels and a category contribute to pattern counts. No message text or destination is included. Reports do not establish that a site is malicious. Feedback stores your answers, optional tester code and written comments. Do not include private messages or personal information in feedback. Aggregate patterns and voluntary feedback are retained during the beta; there is currently no automatic deletion schedule for them.

Accounts and history

Accounts are not yet enabled. Once connected, Firebase will handle sign-in and session persistence. History is off by default. Explicitly saved checks contain category, warning labels, generic advice and the lookup status, not the original message or URL. Profile preferences and history can be deleted; account deletion requires a recent sign-in. Device resources may be cached for loading speed. A message shared into the installed app is temporarily cached on your device until the app consumes it.

Questions

Use the in-app feedback form for beta questions. A dedicated support mailbox is not yet available. Do not submit passwords or payment information.