Real Press

Privacy Policy

Last updated: February 14, 2026

What we collect, how we use it, and what we don't touch.

Our Privacy Promise

0third-party trackers
0advertising cookies
0data broker relationships
1session cookie (only when logged in)
  • Your IP is never stored — only a truncated hash for rate limiting
  • No Google Analytics. No tracking pixels. No fingerprinting.
  • Anonymous search: queries are logged with a session hash, never your IP
  • Extension stores all history locally on your device

Open DevTools → Network and see zero requests to third-party analytics domains.

How We Compare

Privacy featureReal PressGoogleBingPerplexity
Third-party trackers020+10+5+
Advertising cookiesNoYesYesYes
Data broker salesNoAd monetizationAd monetizationNo
Search history tied to identityOptionalDefaultDefaultAccount-linked
IP address storedNever (hashed)YesYesYes

Tracker counts are estimates based on EasyList/EasyPrivacy filter lists and public privacy audits.

Overview

Real Press helps you find content written by actual humans. This policy explains what data we collect, how we use it, and your rights regarding that data. It covers the Real Press website (real.press), the Verification API, and the Real Press browser extension for Chrome and Firefox.

Data We Collect

Account Information

When you sign in with Google or GitHub, we receive your name, email address, and profile image from the OAuth provider. We use this to create and maintain your account. We do not access your Google or GitHub passwords.

Submitted Content

When you submit a URL for analysis, we extract the article text and images from that URL to run AI detection. The extracted content, AI scores, and source URL are stored in our database and may appear in public search results.

When you paste text directly, the text is analyzed for AI detection and stored privately. Pasted text is never included in public search results and is only visible to you and site administrators.

Screenshots

When you upload a screenshot (via the website or browser extension), the image is sent to our server for OCR text extraction and AI detection. Screenshots are processed in memory and are not permanently stored on our servers. Extracted text and scores are stored as described above.

API Usage

If you use the Verification API, we log the request type and timestamp for quota tracking. API request content (text, URLs, images) is processed for AI detection and the results are returned in the response. API-submitted content is not added to public search results.

Browser Extension

The Real Press browser extension for Chrome and Firefox provides the following functionality and handles data as described below.

Authentication Tokens

When you sign in through the extension, an authentication token is stored locally on your device using chrome.storage.local (or the Firefox equivalent). This token is never sent to any third party — it is only used to authenticate requests to real.press.

Page URLs

When you use “Check This Page” or the right-click context menu, the URL of the current page is sent to the Real Press API for content extraction and AI detection. We only send the URL when you explicitly request a check — the extension does not automatically track or report your browsing activity.

Screenshots

When you capture a screenshot through the extension, the visible portion of the current tab is captured and sent as a base64-encoded image to the Real Press API for OCR and analysis. The screenshot is transmitted over HTTPS and is not stored locally in the extension or permanently on our servers.

Check History

The extension stores your recent checks (up to 50 entries) locally on your device for convenient access. This history is stored in chrome.storage.local and never leaves your device. You can clear this history at any time.

Permissions

  • activeTab — Read the URL of the current tab when you request a check
  • contextMenus — Add “Check this page” and “Check this link” to the right-click menu
  • storage — Store your authentication token and check history locally
  • scripting — Relay OAuth tokens from the real.press authentication callback page
  • Host permissions (real.press) — All API calls are sent exclusively to real.press

Data Security

All data transmitted between your browser, the Real Press extension, and our servers is sent over HTTPS (TLS 1.2+). Authentication tokens are stored locally on your device using your browser's built-in extension storage API. Our database is hosted with encryption at rest. API keys are stored as irreversible hashes — we cannot recover your key after creation.

Data Sharing

We do not sell your personal data. Content submitted via URL may appear in public search results on Real Press. We use select third-party services for functions such as AI detection, payment processing, database hosting, and web application hosting. These services receive only the limited and necessary information they need to perform their function.

Data Retention

Analyzed content and scores are retained indefinitely to power search results. Account data is retained while your account is active. You may request deletion of your account and associated data by contacting us.

Your Rights

You may request access to, correction of, or deletion of your personal data at any time. To make a request, contact us at the email address below.

Contact

For privacy-related questions or data requests, email privacy@real.press.