Privacy Policy

1. Overview

Erasio ("we", "our", or "Erasio") is committed to protecting your privacy. This policy applies to all of Erasio: the website at erasio.io, the in-browser online tool, and the Erasio Chrome extension. We designed Erasio with a privacy-first architecture: every watermark-removal computation — for both images and videos — happens 100% on your device, in your browser. Your images and videos are never uploaded to our servers or any third party — not for processing, not for analysis, not for storage. The only information our backend ever receives is the small amount of account and metering data described below, and only if you choose to create an account. Separately, the erasio.io website is supported in part by third-party advertising served by Google AdSense, and uses Google Analytics to measure aggregate traffic. Both set their own cookies and are described in Sections 2, 8 and 9. Advertising and analytics run on erasio.io web pages only — the Erasio Chrome extension contains no ads, no ad SDKs, and no analytics of any kind, and no advertiser or analytics provider ever receives your images, videos, or prompts.

2. Information We Collect

The data we handle depends on how you use Erasio. Most users — including everyone who only uses the extension or online tool as a guest to remove watermarks from images or videos — never send us anything beyond standard web request metadata.

• Data We Do NOT Collect

  We never collect, store, or transmit your images or videos, the pixel or frame content of media you process, the prompts or conversations from the AI sites you visit, your browsing history, your contacts, your location, or any other data that leaves your device beyond what is explicitly listed below.

• Account Information (Only If You Sign Up)

  If you create an Erasio account, we store your email address, a securely hashed password (we never see your plaintext password), your display name if you provide one, your email-verification status, account creation and last-login timestamps, and your selected plan. If you sign in with Google, we receive your Google email, name, profile picture URL, and Google account ID from Google — we do not request or receive your Google contacts, drive, or any other Google data.

• Usage Metering (Credits)

  To enforce daily caps and subscription credit balances, our backend records when a credit is charged: a timestamp, the user or guest identifier the charge applies to, and a count. We do not record what was processed, what file was used, what prompt produced the image or video, or any media content. For guest users (no account), the daily cap is keyed to a salted hash of your IP address — not the IP itself — and that hash is rotated regularly.

• Payment Information

  Payments are processed by Stripe. Your card details are entered into secure fields hosted by Stripe and are sent straight to Stripe — your card number, CVC and billing address never pass through our servers and are never stored by us. From Stripe we receive and store only what we need to run your subscription: identifiers (Stripe customer, subscription, invoice and transaction IDs), the plan you bought, the amount, currency and status of each invoice, the billing period dates, and the link to the invoice Stripe hosts for you. Stripe handles your payment details under its own privacy policy.

• Local Browser Storage

  The extension stores the following data locally in your browser using chrome.storage.local: your UI preferences (dark mode, default model, default mode, language, and other settings), a counter of how many images and videos you have processed (no media data), a processing history log containing only file names, timestamps, media type (image or video), and the model used (never image or video content unless you opt in to "Save media to history", in which case the file is stored only in your own browser and never uploaded), and a short-lived access token used to talk to your Erasio account when you are signed in. All of this stays on your device and is removed when you uninstall the extension or clear browser storage.

• Cookies (Website Only)

  Erasio uses two categories of cookies on erasio.io, and none in the Chrome extension. First, a first-party session cookie: when you sign in, we set a single httpOnly, SameSite refresh-token cookie scoped to /api/auth on our domain, used solely to keep you signed in and to mint short-lived access tokens. Second, third-party advertising and analytics cookies: erasio.io displays ads served by Google AdSense and measures traffic with Google Analytics, both of which may set their own cookies and read device identifiers to measure traffic, cap how often you see the same ad, and — where you have consented — personalize advertising. We do not set fingerprinting cookies and we do not sell cookie data. See Section 9 for how to give, refuse, or withdraw advertising consent.

• Analytics (Website Only)

  We use Google Analytics 4 on erasio.io to understand aggregate traffic: which pages are visited, roughly which country visitors come from, and which features are used. Google Analytics receives your IP address — which Google uses for coarse geolocation and does not retain in Analytics reporting — along with your user agent and page-view events. We use it to measure the site in aggregate, not to build profiles of individual users, and we never send your email address or Erasio account identifier to Google Analytics. The Chrome extension sends no analytics events.

• Standard Server Logs

  Like any web service, our hosting provider and CDN process standard request metadata (IP address, user agent, request path, timestamp) to keep the service running, prevent abuse, and respond to security incidents. These logs are retained for a short, rolling window and are not used to build user profiles.

3. Image and Video Processing

All watermark-removal math is computed entirely within your browser — both in the Chrome extension and on the online tool at erasio.io. Images are processed with the HTML5 Canvas API; videos are processed frame-by-frame in-browser using the HTML5 <video>, Canvas, and MediaRecorder / WebCodecs APIs, and then re-encoded locally back into a downloadable video file. In both cases the algorithm uses pre-computed alpha maps (small PNG calibration files bundled with the extension and the website) plus standard reverse alpha blending: a purely mathematical, local operation. Your images and videos are never sent to our servers or to any third-party service. When you are signed in, the only network call associated with processing a file is a credit-charge request, which carries only your authentication token — no image or video data, no frames, no file name, no thumbnail.

4. How the Extension Talks to Your Account

When you sign in on erasio.io, the website sets the refresh-token cookie described above on its own domain. The Erasio extension reads that cookie only by running a small content script on the erasio.io tab itself, exchanges it for a short-lived access token, and stores that token in chrome.storage.local so the popup stays signed in across re-opens.

• No Second Login

  You do not enter your password into the extension. The extension never sees your refresh token from any other origin — only from erasio.io, where it would already be sent on a normal page load.

• What Crosses the Network

  When signed in, the extension makes the following backend calls and nothing else: refresh the access token, fetch your account profile (/me), fetch your remaining credit balance, charge one credit immediately before processing, and sign out. None of these calls carry image or video data, frames, or file names.

• Signing Out

  Signing out from either the website or the extension revokes the refresh token and clears the access token from chrome.storage.local. The extension immediately reverts to the guest tier with no further server contact (other than the guest daily-cap check at processing time).

5. Chrome Extension Permissions

Erasio requests the following Chrome permissions and uses them only as described:

• storage

  Used to save your preferences, processing counter, history, and short-lived access token locally in your browser. Nothing here is synced to external servers.

• declarativeNetRequest

  Used to filter and re-route image and video download requests on the supported AI sites so watermarks can be removed before the file is saved. The rules are static, ship with the extension, and are not generated from anything you do.

• tabs

  Used so the extension can open the Erasio dashboard, sign-in, or pricing pages in a new tab when you click the corresponding popup button. We do not read the URLs, titles, or contents of your other tabs.

• host_permissions: gemini.google.com, aistudio.google.com

  Required to inject the content script that detects watermarked image and video downloads on Google Gemini and Google AI Studio (including Gemini-generated videos). The extension only activates on these AI sites and does not monitor any other websites you visit.

• host_permissions: labs.google (Google Flow)

  Required to inject the content script that detects watermarked video downloads on Google Flow (labs.google/flow), Google's AI video generation tool. The content script only runs on Google Flow pages and is limited to identifying generated-video downloads so the watermark can be removed locally in your browser before the file is saved. It does not read your prompts, project content, or any other data on the page.

• host_permissions: erasio.io

  Required for the auth-bridge content script that runs only on erasio.io tabs. It exchanges your existing erasio.io session for a short-lived access token so the popup can show your account and remaining credits without asking you to log in again.

6. Authentication and Sign-In

Erasio supports two ways to sign in: email and password (with email verification via a one-time code), and Google OAuth. Email verification codes are delivered through a transactional email provider; the only data shared with that provider is your email address and the one-time code. If you choose Google sign-in, we receive your basic Google profile (email, name, profile picture URL, Google account ID) and store it as part of your Erasio account; we do not request access to any other Google service. You can unlink Google or delete your Erasio account at any time from your account settings.

7. Payments

Paid access to Erasio is sold as a recurring subscription, billed automatically each period until you cancel. Payments are processed by Stripe. Card details are collected in secure fields hosted by Stripe and go directly to Stripe — your card number, CVC and full billing address never reach our servers and are never stored by us, which keeps card data outside our systems entirely. Stripe processes that information under its own privacy policy. What our backend stores is limited to the records needed to run and support your subscription: your Stripe customer ID, subscription ID and plan/price identifiers; for each invoice, its ID and number, the transaction (payment intent) ID, the amount due and paid, the currency, the status, the payment date and the links Stripe provides to view or download that invoice; and the start and end dates of each billing period. We use these to activate your credits, show your billing history, and answer support questions about a specific charge. You can cancel at any time from your account settings.

8. Third-Party Services

We share data with third parties only to the minimum extent needed to operate the service:

• Google (OAuth, optional)

  Only invoked if you choose to sign in with Google. We receive basic profile information from Google as described above; we share nothing back beyond what OAuth requires to complete the sign-in.

• Stripe (payments)

  Receives your card details directly from your browser, plus your email address, when you subscribe, and processes the payment and any recurring renewals. We receive back only transaction identifiers, amounts, currency, status and invoice links — never your card number.

• Transactional email provider

  Receives your email address and the verification code or notification content when we need to email you (account verification, password reset, payment receipts).

• Hosting and CDN

  Standard web request metadata (IP, user agent) is processed by our hosting provider and CDN to deliver and secure the site, per their own policies.

• Google AdSense (website only)

  erasio.io displays advertising served by Google and its partners. Google uses cookies and similar identifiers to serve and measure ads and — subject to your consent where required — to personalize them based on your prior visits to this and other sites. Google never receives your images, videos, prompts, processing history, or account email; an ad request carries only the standard information a browser sends when loading an ad (page URL, IP address, user agent, and ad cookies). You can review how Google uses this data at policies.google.com/technologies/partner-sites and opt out of personalized advertising at any time at adssettings.google.com. The Chrome extension shows no ads and loads no ad code.

• Google Analytics (website only)

  Receives aggregate page-view and traffic data as described in Section 2, for measurement purposes only.

9. Advertising and Cookie Consent

erasio.io is supported in part by advertising. This section explains what that means for your data and how you control it. Advertising is limited to the erasio.io website — the Erasio Chrome extension contains no advertising code.

• What Ads Can and Cannot See

  Ads are served by Google AdSense inside an isolated frame. Ad code has no access to the images or videos you process, the media in your local history, the prompts on the AI sites you visit, your account email, or anything stored by the extension. Watermark removal continues to run entirely on your device; whether you accept or block ads does not change how it works and never causes your media to be sent anywhere.

• EEA, UK and Switzerland

  If you visit from the European Economic Area, the United Kingdom, or Switzerland, you are shown a consent message before any advertising cookies are set, delivered through Google's certified Consent Management Platform. You may consent, refuse, or choose "Manage options" to make per-purpose and per-vendor choices. Refusing is exactly as easy as consenting. If you refuse, you will still see ads, but they will be non-personalized — chosen from the content of the page rather than from your browsing history.

• Changing or Withdrawing Consent

  You can reopen the consent message and change or withdraw your choices at any time using the "Privacy & cookie settings" link in the site footer. You can also opt out of personalized advertising globally, in any region, at adssettings.google.com, and block or clear third-party cookies through your browser settings.

• Other Regions

  Outside the EEA, UK and Switzerland, ads may be personalized by default where local law permits. Residents of California and other US states with applicable privacy laws may opt out of the "sale" or "sharing" of personal information for cross-context behavioural advertising by contacting us at the address in Section 13.

10. Data Retention and Your Rights

Local extension data (preferences, history, counters, access token) lives only on your device and is removed when you uninstall the extension or clear browser storage. Account data (email, hashed password, plan, credit-usage records) is retained for as long as your account exists. You may request access to, correction of, or deletion of your account data at any time by emailing the address below — for most users, deletion is also available directly from your account settings page. After account deletion we keep only the minimum records we are legally required to keep (for example, payment and invoice records we are required to keep for tax and accounting purposes, which are also retained by Stripe). Guest IP-hashes used for daily-cap enforcement are rotated and pruned on a short rolling window. Your advertising consent choices are stored in your own browser by Google's Consent Management Platform and are cleared if you clear site data. Depending on where you live, you may also have additional rights under laws such as the GDPR or CCPA — including the right to object, restrict, or port your data — and you can exercise these by contacting us.

11. Children's Privacy

Erasio is not directed to children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it promptly.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date at the top of this page and, for material changes, publish a note in the Changelog. Continued use of the extension or website after changes take effect constitutes your acceptance of the updated policy.

13. Contact

If you have any questions about this Privacy Policy, want to exercise a data right, or want to delete your account, please contact us at: