Privacy, in plain terms.
Verity processes the content you choose for evidence review. Browser capture, automatic review, local storage, and workspace retention have separate, visible boundaries.
What Verity processes
Data submitted for verification is processed to generate claim outcomes, confidence context, and evidence trails that support team workflows.
- Processing scope is aligned with verification and workspace functionality.
- Operational telemetry is limited to reliability, security, and product-quality needs.
- Teams can enforce internal controls around content and review access.
What the extension can access
The extension sends content only for a requested feature or a separately enabled automatic-review feature.
- Pasted or selected text is sent when you choose Verify. A manual page scan sends the readable article or currently opened email message for backend content analysis.
- Page Watch is off by default. Opened-email review is a second, separate opt-in and excludes inbox lists, hidden content, quoted replies, and compose fields.
- Image analysis is an extraction and OCR precheck, not a verification verdict. Video and audio remain explicit workspace handoffs until a live media-verification contract is available.
Local storage and credentials
The extension separates local product state from short-lived authentication material.
- Preferences, recent review summaries, and page annotations may be stored in Chrome extension storage.
- Verity session tokens and manually entered API keys use browser-session storage and are removed from legacy persistent extension storage.
- Removing the extension or clearing its storage removes extension-local state; it does not by itself delete workspace data already saved to Verity.
Retention and deletion
Saved workspace records follow the account and workspace retention controls that apply to the user. Verity does not publish a universal server-retention duration where production enforcement has not been confirmed.
- A user can start an account and user-owned data deletion request from signed-in Settings or the public account-deletion page.
- A deletion-request receipt confirms that the request was recorded; it is not a claim that every downstream system has already completed deletion.
- Any data retained for a documented legal or security obligation must be separated from active product data. Production completion timing will be published only after operational approval and verification.
Signup campaign attribution
When you arrive through a campaign link, Verity can keep its source, medium, campaign and creative labels and the entry page in your browser tab for up to 24 hours. A new account can retain the first recorded campaign so we can understand where signups come from.
- This record excludes claim text, documents, full referring URLs, email addresses, IP addresses and advertising identifiers. Campaign labels do not determine your price or account access.
- This collection is skipped when the browser signals Global Privacy Control or Do Not Track. Clearing tab storage removes a pending local record; it does not erase an account record already submitted.
- Account attribution follows the account deletion process. A source record is not proof of a payment, a successful verification or newsletter consent.
Questions about your data?
Use our contact page to discuss your team setup and we can help map privacy requirements to your operational use of Verity.