Policies · source checked 2026-11-12

Privacy and account data

How OpSift handles account records, submissions, verification challenges and service-order information, with user controls and limited analytics.

Research cards, a comparison sheet and a magnifying glass

Data used to provide the service

An account stores your name, email, authentication records and the research you choose to save. Submissions and corrections store the product details and evidence you provide. Claims store a domain-bound challenge and its verification outcome.

Orders retain the service, currency, amount, provider references and status needed to account for the transaction. OpSift does not collect card details through its own forms; enabled purchases use hosted checkout.

Operational providers and messages

When configured, the email provider delivers account verification, recovery and requested service notifications. A payment provider processes the checkout and refund. These providers receive the data necessary for the relevant action.

Notification preferences are available in your account. Marketing consent is not required to save research or submit a tool. Authentication and transaction messages remain necessary to operate the requested service.

Your controls and retention

You can export your own account data and request account deletion from the account page. Deletion requests are reviewed so that financial, dispute and necessary audit records are handled consistently rather than silently erased.

Do not send confidential client files, passwords or payment credentials in a tool submission or correction. Public product evidence is sufficient for the editorial workflow.

Analytics and security boundaries

Only the shared Plausible service is eligible for optional analytics. Tracking is limited to approved public paths and does not include account identifiers, search queries, form values, authentication, payment or administration paths. Browser privacy signals are respected.

Access controls protect private records and administrator operations at the server. A claim verifies domain control for a specific listing; it is not an assertion that the vendor has any independent security certification. Use the account support route for a privacy request.

Sources & editorial notes

Source checked: 2026-11-12. Vendor statements are not hands-on product tests. OpSift editorial method and service policies describe our own process.

Suggest a correction ↗

Continue your research