Privacy Policy

See what data we use, why we use it, how long we keep it, and how to access or delete your data.

Last updated: October 21, 2026

This policy explains how your personal data is collected and processed under the UK GDPR.

1. Data Controller and Scope

This policy explains the personal data processed as Data Controller on the LeakData.io platform operated by CyberVisir Solutions Ltd (the "Company"), registered in the United Kingdom (England and Wales) under company number 17215486 with registered address Suite 10826, 5 Brayford Square, London, United Kingdom, E1 0SG.

2. Data Categories Collected

The following personal data categories are processed:

  • Identity Information: First and last name.
  • Contact Information: Email address and phone number.
  • Digital Identity: Social media account names/usernames.
  • First-party Product Measurement: Successful account, verification, manual security action, monitoring, integration, report and payment lifecycle outcomes are recorded in our own database with opaque internal IDs, server times and reviewed categorical fields. Search inputs, monitoring targets, breach contents and payment details are not copied into this measurement ledger.
  • Optional Product Analytics: After you enable analytics cookies, reviewed product events, coarse categories such as plan tier and locale, a random browser identifier, and—while signed in—an opaque internal account ID. Analytics event and replay payloads do not include names, email addresses, search terms or their hashes, passwords, monitoring targets, breach details, full URLs, query strings, referrers, free-form errors, or user-agent fields.

4. No Data Sale Commitment and Security

Direct breach-search values are not retained in plaintext search history; a one-way hash and limited operational metadata may be retained under the applicable plan and security controls. Monitored assets are retained for the service and account lifecycle. Query and monitoring data are NOT SOLD to third parties for advertising or marketing purposes. Payment-card details are not stored on LeakData servers.

Analytics is off by default: until you consent to analytics, no Amplitude code runs and nothing is stored in your browser or sent. Automatic capture is limited to reviewed session and navigation structure; arbitrary page text, form values, element attributes, and full locations are excluded. Session Replay masks all text and input values and blocks media, code, tables, results, and other sensitive containers. Withdrawing consent stops collection and clears the analytics identity in the browser.

5. Data Retention

Service data is retained according to the applicable service and account lifecycle.

An unused local registration that remains unverified for at least 30 days after creation may be deleted with its linked data, allowing a new registration with the same email address. Resending a verification email does not extend this period. Accounts with payment, subscription, monitoring, family, team, or provisioning records require separate review and are excluded from this automatic cleanup.

The minimized first-party product-event ledger and new consent-decision receipts are retained for up to 400 days or until linked account deletion. New consent receipts do not store request IP addresses, user-agent strings, or caller-provided timestamps. Historical consent audit rows created before this design are access-restricted and are not destructively altered without a separately reviewed retention decision.

If you consent to optional analytics, the minimized analytics data described above is sent directly by your browser to Amplitude's European Union endpoints and processed by Amplitude as our analytics provider. Analytics and sampled replay data follow the retention configured for our EU Amplitude project. This optional processing stops when you withdraw analytics consent.

If the optional face search feature is legally approved and enabled, its processing region and the retention and deletion rules for photos and provider requests are those disclosed in the then-current notice, approved data-processing agreement, and provider terms; LeakData does not promise a fixed region or retention period before that review is complete. Withdrawing face-search consent prevents future optional searches, but does not retroactively undo processing completed for a search you already submitted. Erasure or account-deletion requests are handled under applicable data-subject rights and the approved provider deletion process.

6. Connected AI Assistants

If you connect your LeakData account to an AI assistant such as ChatGPT or Claude, the assistant can receive the following from LeakData when you ask it to: the names, dates and exposed data types of breaches found for your verified email address; your monitored email addresses in masked form (for example m***@example.com), when each was last checked and how many findings each has; and your action-plan steps and whether each is done. At your request, the assistant can mark an action-plan step as done.

LeakData does not send full email addresses, passwords, password hashes or raw breach records to the assistant. From the assistant, LeakData receives your request, its language setting and an anonymous identifier used only to limit request rates.

Looking up public breach information through an assistant without connecting an account involves no account data. You can disconnect an assistant at any time in its connection settings. The assistant provider handles your conversation under its own privacy policy.

7. User Rights

Under the UK GDPR, you have the right to access your personal data and learn to whom it has been disclosed, to have it corrected or erased, and, where the law provides, to restrict or object to its processing and to receive it in a portable format. You can submit these requests through your user panel or our support address. You also have the right to lodge a complaint with the UK Information Commissioner’s Office (ICO). Self-service export includes linked first-party product events and consent receipts; account deletion removes those local rows. A request concerning previously delivered optional analytics should identify the relevant LeakData account and approximate time period; we will verify the requester and, where applicable, use the opaque internal account ID in Amplitude's EU-project deletion process without sending an email address or search data to Amplitude. Withdrawing consent stops future collection but does not itself erase data already delivered.

Send a data rights requestOpen account and data settings
CyberVisir Solutions Ltd · Suite 10826, 5 Brayford Square, London E1 0SG · Company No: 17215486