Privacy Policy

Overview

VeriOrigin checks text for likely AI generation only when the user starts a check.

Data collected

VeriOrigin may process:

• Selected text that the user chooses to check
• Text pasted into the extension popup
• Readable page text when the user chooses the full-page check
• Nearby visible text context for selected-text checks when needed for a more reliable review
• Technical metadata such as request time, text length, result percentages, confidence, and model routing

The extension may store a local daily usage counter and local usage mode in Chrome storage. These local values are used to operate the daily check limit.

VeriOrigin does not intentionally collect browser history, page URLs, passwords, payment information, form contents, screenshots, or files.

How data is used

The submitted text is used only to provide the AI-detection result requested by the user.

The backend sends submitted text to the configured AI provider to generate a probabilistic result. Diagnostic logs are used to monitor reliability and do not store the checked text.

Data sharing

VeriOrigin shares submitted text with the AI API provider used to generate the requested result. Hosting and network infrastructure providers may process request traffic only to operate and secure the service.

VeriOrigin does not sell user data, use it for advertising, or share it with data brokers.

Limited Use

VeriOrigin uses submitted text only to provide, maintain, secure, and improve the AI-checking feature requested by the user.

VeriOrigin does not use submitted text for personalized advertising, retargeting, creditworthiness, resale, unrelated profiling, or generalized market research.

Humans do not read submitted text unless the user asks for support involving specific submitted content, or access is necessary for security, abuse prevention, or legal compliance.

Data retention

The backend does not intentionally store checked text. Temporary in-memory jobs may exist while a stricter review is running.

Diagnostic logs may store metadata such as result percentages, request mode, text length, and timestamps, but not the checked text.

Security

Production deployments transmit extension requests over HTTPS. API keys are kept server-side and are not included in the Chrome extension package.

Contact

For privacy questions, contact [email protected].