Privacy policy

Updated November 1, 2026

Your exports stay in your browser, and we only see comment text when you ask for an AI brief, which we pass to a model provider and don't store. This page lists everything we do collect, who processes it for us, how long we keep it and how to delete it.

Who we are

Comment Scraper is a browser extension for Chrome and Edge, the website comment-scraper.com, and comment-scraper-mcp, a small server that lets AI apps such as Claude and Cursor read your exports on your computer. All three are run by CommentScraper, Portland, Oregon, USA ("we", "us"). For anything about privacy, email hello@comment-scraper.com.

The short version

  • Exports are stored only in your browser and expire after 30 days. We never receive them.
  • From version 1.4.0, exports include the username of whoever wrote each post and comment. Like the rest of the export, they stay in your browser. Hosted AI briefs leave out the author field.
  • The plugin for Claude and Cursor reads your exported files on your computer and sends nothing to us.
  • If you save a thread to Karakeep, it goes from your browser straight to your Karakeep server. We never see the thread, the server's address or your API key.
  • When you run a hosted AI brief, the comment text goes through our server's memory to a model provider and the result comes back to you. We don't write it to disk or keep it.
  • We collect your email address, your plan and credit records, usage counts, anonymous failure counts and a small set of product events.
  • We don't collect your browsing history. We don't sell data. We don't use comment text for anything except the brief you asked for.

Where comment text goes

What you do Who handles the comment text What is kept
Export only Only your browser Stored in the extension's local database (IndexedDB) until it expires after 30 days
Hosted AI brief Your browser, then our server (in memory only), then the model provider, then back to your browser We don't write comment text to disk. Our application logs and error reports never contain comment text; they record the request ID, your user ID, token counts, timing and error codes.
Reading exports in an AI app (plugin or MCP server) Your computer, then the AI app you use and its model provider Nothing on our side. The server runs on your computer and sends us nothing.
Save to Karakeep Your browser, then the Karakeep server you set up Nothing on our side. The note is on your Karakeep server, and how long it stays there depends on that server.

Exports stay in your browser

When you export a thread, the extension saves the result in your browser's extension storage (IndexedDB). An export contains the thread title, the post and comment text, the usernames of the people who wrote them, scores, timestamps, reply structure and links.

Each saved export expires 30 days after you made it, and the extension reminds you 3 days before. Expired exports are removed when you next open the side panel (checked at most once a day) or finish an export. An export that belongs to a batch still running or paused stays until the batch ends. The extension also keeps only your most recent exports (10 on Free, 50 on paid plans, 200 MB at most) and removes the oldest when you go over.

We can't see your exports. Files you download or copy are on your computer and outside our control.

To make sure a paused export resumes in the same Reddit session, the extension stores a one-way hash of your Reddit username in its local storage. It is never sent to us.

AI briefs

When you ask for a hosted brief, the extension sends the thread title, the subreddit or source, the post text and the comments being analysed, with each comment's score, which comment it replies to and whether the original poster wrote it. Each comment gets a short local reference such as c12 so the brief can point back to it. A long thread is split into chunks, and the summary of each chunk is sent once more so the model can combine them. It leaves out the author field. Usernames written inside the post or comments are part of the text, so they're sent as written. Before sending, we cut any comment longer than 4,000 characters and put each comment on one line.

The request goes to our server, which holds it in memory only and forwards it to Anthropic's API, our model provider. Anthropic says it doesn't use inputs or outputs from its API to train models unless the customer opts in (we haven't), and that it deletes them within 30 days unless it has to keep them longer to comply with the law or to enforce its Usage Policy, for example when its safety systems flag them (Anthropic: model training, Anthropic: data retention, checked 2026-10-08). The brief comes back to the extension and is stored with its export in your browser.

If Anthropic's API fails on a request, our server sends that request to OpenAI's API instead, so your brief can still finish. We tell OpenAI not to store these requests. OpenAI says data sent to its API is not used to train or improve its models unless the customer opts in (we haven't), and that it keeps API abuse-monitoring logs for up to 30 days unless it has to keep them longer for legal or safety reasons (OpenAI: your data, checked 2026-10-01). If you'd rather not send comments to either, turn hosted briefs off in settings. Exports and copying a thread with a prompt still work without sending comment text to us.

We don't store the comment text, the per-chunk summaries or the finished brief on our servers. We don't sell it, we don't use it to train models and we don't use it for anything other than producing the brief you asked for. Per-chunk summaries are cached in your browser so an interrupted brief can pick up where it left off.

The brief panel says this next to the Generate brief button, and nothing is sent until you press it. You can turn off hosted briefs in settings at any time.

Reading exports in Claude, Cursor and other AI apps

The plugin for Claude and Cursor, and the comment-scraper-mcp server it runs, work on your computer. The server reads the JSON exports in your Downloads folder and the folders directly inside it, or the folders you set in COMMENT_SCRAPER_DIRS. It doesn't write, move or delete files, makes no network requests and sends nothing to us.

When the AI app asks for a thread, the server gives it the comments, with the username of whoever wrote each one, and the app sends that to its model provider like the rest of your conversation. The app's and the provider's own terms and privacy policies apply to that.

npx downloads the comment-scraper-mcp package from the npm registry the first time and keeps it in a local cache. Later starts may still contact npm to check the package. That's npm's traffic, not ours, and it carries none of your exports.

Saving to Karakeep

Karakeep is a bookmark app that you can host yourself or use as Karakeep Cloud. If you set up Save to Karakeep in the extension's settings, you enter your Karakeep server's address and an API key you created in Karakeep. Both are kept in the extension's local storage in your browser. They are never sent to us.

When you press Save to Karakeep, the extension sends the thread's Markdown export to that address, using your API key. The export holds the thread title, the post and comment text, the usernames of the people who wrote them, scores, ages and the link to the thread. It goes from your browser to that server directly, not through ours.

To reach that server, the extension asks your browser for access to that one address when you save the settings. Pressing Remove next to the address deletes the address and the key and gives that access back. Uninstalling the extension removes them too.

What happens to a note after that, including any AI tagging or summaries your Karakeep is set up to run, depends on your Karakeep settings and on whoever hosts that server, which is you or, for Karakeep Cloud, the Karakeep team.

What we collect

Account

Your email address. We use it to send sign-in codes and messages about your account or billing. You only need an account for AI briefs and paid plans. Exports work without one.

If you sign in with Google, Google sends us a signed sign-in token. It contains your email address and whether Google has verified it, and it can also contain your name and profile photo. We use only the email address. The rest is dropped as soon as the token is checked and never stored. We don't get your contacts or anything else from your Google account. Signing in with Google or with a code sent to the same address opens the same account. For addresses outside Gmail and Google Workspace, use an email code: Google can't confirm those are still yours.

Plans, credits and payments

Your plan, its status and dates, and the Stripe subscription or payment ID that goes with it. A ledger of your credits: when they were granted, used and when they expire. For each brief, a record with the request ID, its status, credits reserved and charged, how many chunks were processed, token counts and the time. To stop a request ID being reused for different content, we also store a SHA-256 hash of each chunk. We store no comment content.

Usage counts

How many briefs you've run and how many credits you've used, so we can apply your plan's limits.

Anonymous parse-failure counts

So we notice quickly when Reddit changes its pages, the extension reports whether each export succeeded or failed, and our server adds the reports up by the hour. Each report includes the parse path (Reddit's JSON or the page itself), the selector version and a comment-count range. It includes no URLs, no content and nothing that identifies you. You can turn this off in settings.

Product events

The extension creates a random install ID. It has nothing to do with your Reddit account. When you sign in, we link it to your user ID. We record only these events:

  • install
  • export_completed, with the source site, how the export ended and a comment-count range
  • brief_completed
  • upgrade
  • account_warning_reported, when you click the button saying you got a warning from Reddit

Events don't include thread URLs or content. You can turn off this reporting in settings.

We also count each of these events, except upgrade, in Vercel Analytics. The count has no install ID or user ID, and the comment-count range is left out. Vercel works out the browser and country from the request and doesn't store the IP address. When reporting is off, nothing is counted there either.

Account and billing counts

We count these in Vercel Analytics as totals: new accounts (counted the first time you sign in), checkouts started, purchases, renewals, scheduled cancellations and ended subscriptions (with the plan), and full refunds. The counts have no email address or account ID. They come from the account and billing records described above, so they're counted even when product event reporting is off.

Settings the extension downloads

The extension downloads a signed settings file from our server when you open its side panel, and again before an export if the last download is more than an hour old. It holds the page selectors, rate limits and on/off switches for each source. This request carries no Reddit data.

Sign-in rate limits

When you ask for a sign-in code or sign in with Google, we store a salted hash of your IP address and of your email address, with the time. We use them only to limit how many codes and new accounts one address can request, which stops people from farming free briefs. We delete them after 7 days.

Bot check on the website

When you open the sign-in form on comment-scraper.com, Cloudflare Turnstile checks that a person is there, not a script. It reads signals from your browser and your IP address, and we only learn whether the check passed. We use that result only before we email a sign-in code. Signing in from the extension doesn't involve Cloudflare.

Website

We use Vercel Analytics to count visits to comment-scraper.com and clicks on the Add to Chrome buttons. It doesn't use cookies. If you sign in on the website to manage your account, your browser keeps a sign-in token so you stay signed in.

What we don't collect

  • Your browsing history, or any page other than the thread you choose to export
  • Your Reddit password or Reddit username (only the local hash described above, which never leaves your browser)
  • Your Karakeep address or API key, or anything you save to Karakeep
  • The author field in your exports. Hosted AI briefs leave it out; usernames written in post or comment text are sent as written
  • Your card number, which goes to Stripe and never reaches us

We don't sell personal data. There are no ads on the site or in the extension.

Who processes data for us

Provider What for What they receive
Stripe Payments, invoices, the billing portal and tax Your email and the payment and billing details Stripe needs. Card details go to Stripe, not to us.
Resend Sending email Your email address and the message
Cloudflare Checking that a person, not a script, is using the sign-in form on the website Signals from your browser and your IP address, during the check
Google Sign in with Google, if you choose it Google sends us your email address, and possibly your name and photo, which we drop. Google sees that you signed in to Comment Scraper.
Vercel Hosting the website and our API, including the brief endpoint; website and product analytics Requests to our site and API. During a brief, the comment text passes through in memory. The counts described above, with no install ID, user ID or email.
Anthropic Generating AI briefs The thread title, post and comment text, scores, reply links and chunk summaries for that brief
OpenAI Generating AI briefs when Anthropic fails The thread title, post and comment text, scores, reply links and chunk summaries for that brief

Our database runs on our own server, not a third-party database service. It holds your account, plan, credits, usage, events and failure counts. It holds no comment content.

How long we keep things

  • Exports in your browser: until they expire after 30 days and the next cleanup removes them, or until you delete them.
  • Comment text on our servers: not kept. It exists in memory only while a brief runs.
  • Exports read through the plugin or MCP server: never sent to us, so there's nothing for us to keep.
  • Account, plan, credit and usage records: until you delete your account.
  • Payment records (each payment's Stripe transaction ID, amount, currency, refunded amount and dates): 7 years from the payment, for tax and refunds. If you delete your account sooner, we keep them until then without your email.
  • Product events: 13 months. If you delete your account sooner, they stay until then with their install ID but without your user ID.
  • Sign-in rate-limit hashes: 7 days.
  • Stripe keeps its own payment records under its own privacy policy.

Deleting your data

In the extension's settings, "Delete all local data" removes every export and brief stored in your browser. Remove, next to your Karakeep address, deletes that address and your Karakeep API key. Uninstalling the extension also removes its local storage.

To delete your account, use the delete option in your account settings or email hello@comment-scraper.com from the address on the account. We first cancel your Comment Scraper subscription, if you have one, and then delete your account, plan records, credits and usage records. Payment records, product events and rate-limit hashes stay for the periods listed under How long we keep things, then we delete them.

You can also email us to ask what account data we hold about you, or to correct it.

Changes to this policy

If we change what we collect or who processes it, we'll update this page and the date at the top before the change takes effect.

Contact

CommentScraper, Portland, Oregon, USA. Email: hello@comment-scraper.com.