ContentLoop
← Back to home

Privacy policy.

Last updated: May 27, 2026

The short version

ContentLoop is a BYOK (Bring Your Own Key) tool. We don't charge you for AI usage, we don't mark up Anthropic, and we don't make money by selling, training on, or analyzing your content. We collect the bare minimum to make the product work and try to make most data live in your browser instead of our servers.

What we collect

Your Anthropic API key (BYOK).Stored in your browser's localStorage only. It is sent with each generation request from your browser to our /api/generate endpoint, which uses it solely to call Anthropic on your behalf. We never log it, persist it on our servers, or transmit it anywhere except Anthropic.

Source content you paste. The text you submit for generation passes through our server in-memory only. We do not store it after the response is returned. We never train on it. We never share it.

Voice profile and custom formats. Stored locally in your browser by default. If you sign in (via Clerk), they sync to our Postgres database (Neon) bound to your Clerk user ID, so you can access them across devices.

Generation history. Last 30 runs are stored in your browser. If you sign in, history can sync to our DB bound to your Clerk user ID.

Auth (when used). If you sign in, we use Clerk for identity. Clerk stores your email, name, and avatar if you provide them. We only see your Clerk user ID server-side; we never see your password.

Payments (when used). If you upgrade to Pro, NOWPayments handles the crypto transaction. We receive a webhook with the order ID and payment status, and persist a row in our pro_subscriptions table tying your Clerk user ID to a 30-day validity window. We never see your wallet address, your card, or your personal billing info.

Analytics. We use Vercel Analytics, which records anonymized page views, country, and browser type. No personal data, no cookies, no cross-site tracking.

What we do not collect

  • We do not sell, rent, or share your data with third parties.
  • We do not train AI models on your input or output.
  • We do not run third-party advertising or tracking pixels.
  • We do not log your Anthropic API key.
  • We do not log the content you generate.

The Chrome extension

The ContentLoop Chrome extension uses the following permissions:

  • activeTab + scripting— when you click the extension icon, we read the visible page's text (article body, headings) so we can pass it to the generator. We never read pages you didn't open the popup on.
  • storage— your Anthropic key is stored in Chrome's extension storage (which is local to your browser). Same security model as localStorage.
  • contextMenus— adds a right-click menu “Send to ContentLoop”. No data leaves your machine until you actually click Generate.
  • host_permissions: <all_urls> — required so the popup can scrape the article on whichever site you open. Scraping only happens after you explicitly open the popup; we never proactively access any URL.

The extension sends scraped page text + your Anthropic key directly to https://contentloop-puce.vercel.app/api/generate, which forwards it to Anthropic and returns the result. No analytics, no telemetry, no third-party calls.

Data storage and retention

Browser-local data (voice profile, history, BYOK key, custom formats) lives in your browser. Clearing your browser clears it. We have no copy.

Server-side data (Clerk user, Pro subscription records, optionally synced voice/format/history when signed in) lives in our Neon Postgres database, hosted in AWS us-east-1. We retain it as long as your account is active.

How to delete your data

  • Local data:clear your browser's storage for contentloop-puce.vercel.app, or use the “Clear all” buttons in the workspace.
  • Account data: email ernest2011kostevich@gmail.com with the subject “Delete my data” and the email you signed in with. We delete your Clerk user + all linked DB rows within 7 days.

Subprocessors

Contact

Questions? Email ernest2011kostevich@gmail.com.

Changes to this policy

If we change anything material, we'll update the date at the top and (where possible) note the change in the product release notes.