Your information deserves clarity.

This is an early, local version of Offtrace. The demo uses fictional data and does not search personal identifiers or send verification emails.

What the live check would use

When live mode is configured, we verify your email through Supabase before checking it. Supabase handles sign-in and stores account data. The breach check sends a truncated SHA-256 hash of your verified email to LeakCheck. A hash is still personal data; it is not a guarantee of anonymity.

What is stored

The application stores your encrypted scan identifier, verification and consent information, breach source metadata, report history, and actions you save. Your email is also held by the authentication provider for sign-in. We do not request raw leaked passwords, mailbox access, or payment details in this alpha. There are no advertising trackers or session recordings.

What a result means

A breach match describes a historical record. It does not establish current account compromise, account ownership at the time of a breach, or another person’s behavior. A check returning no matches cannot establish that you have no exposure. Public-profile searches, phone lookups, automatic monitoring, payments, and automated removal submissions are not active in this version.

Your controls

You can download your reports and saved actions, sign out, or delete your account in Settings. Deletion removes the application’s operational records and requests deletion of the live sign-in account. It does not erase external breach databases, provider request logs, or source websites. Backup retention depends on the configured hosting service and must be disclosed before real-user onboarding.

Before a real-user launch

Operator identity and contact details, hosting locations, international transfer arrangements, backup expiry, and final retention periods must be finalized. This notice describes the implementation; it is not a finished public-launch privacy policy. Armenian interface copy and English guides also need review.