Privacy
Your Reddit Ads report is read and analysed inside your browser tab. The file is never uploaded. If you choose to use the plan writer, only the audit results are sent to write your plan. If you buy credits or use the API, the details are below.
What happens to your file
When you choose or drop a CSV, your browser reads it into memory and the audit runs as JavaScript on your own device. There is no server that receives it. Closing or reloading the tab clears it. You can confirm this by opening your browser's network tab while you run an audit: no request carries your data.
The optional plan writer
If you click Write my plan, your browser sends the audit results (subreddit names, spend, clicks, conversions, the audit's estimates and calls, your target, and the optional "What do you sell?" text) to a server function on Supabase. It forwards them to DeepSeek's API, which writes the plan. Your CSV file itself is never sent.
- Cache. The plan is stored for 30 days under a fingerprint of those inputs, so an identical request gets the same answer without calling the model again.
- Rate limits. To keep the service running, each request records a one-way hash of your IP address and the time. These records are deleted after 2 days.
- Free tries. The first 3 plans every 30 days are free. To count them, the site keeps a salted one-way hash of your IP address, with a count and dates, for 30 days. The salt is a secret held on the server, so the hash can't be reversed or matched against other data. Plans served from the cache don't count.
- Your key. If you paste a key (see below), your browser sends it with the plan request so the credits can be charged. The key is kept in this browser's local storage, and you can clear it on the account page.
- DeepSeek. DeepSeek processes the request under its own privacy policy, and its servers are outside the US and EU. If that's a problem for your data, use the audit without the plan writer.
Buying credits
Credits are sold by card through Dodo Payments or in crypto through NOWPayments. You pay on their page, not ours. They process your payment details and receipt email under their own privacy policies, and this site never sees your card number or wallet.
- What we store. The order (pack, amount, provider, status and time), the email address the payment provider passes back, and your key. The key is stored only as a one-way hash, plus its first 12 characters so it can be recognised. The full key is shown to you once when you claim it and is held for up to 24 hours so a page refresh doesn't lose it, then deleted.
- No account. There's no password or login. Whoever holds the key can spend its credits, so keep it private.
- Credit ledger. Each use of a key is logged as a credit change, its reason (plan, audit, purchase or refund) and the time, so your balance and recent usage can be shown. The ledger holds no report data.
- Support email. If you write to heckitshim@gmail.com, the message and your address are kept to answer you and to handle any refund.
- Retention. Order and ledger records are kept as long as the key exists, for accounting and support.
The developer API
API requests send your rows or CSV text to a server, because the audit runs there. That's different from the website, where it runs in your browser. The request is processed in memory and the response returned. The data isn't stored; only usage is kept: the key, the credits used, the endpoint and the time. A plan request also produces the same plan-writer log described below and goes to DeepSeek as described above. Requests are rate limited to 60 per minute per key.
Visitor counts
The site uses GoatCounter to count page views and four actions: running the sample, running your own file, writing a plan and downloading results. Only the fact that the action happened is counted, never anything from your report.
GoatCounter sets no cookies and stores nothing in your browser. For each page view it records the page, the referring site, your browser and operating system, screen width, language and country. It doesn't store your IP address. It keeps your IP and browser string in memory for up to 8 hours to tell unique visits apart, then discards them.
Usage log
To find bugs and see which features get used, the site also keeps its own usage log on Supabase. It records page views, which site sent you (and any campaign tag in the link), time on page and how far you scrolled, your country, device type, browser, operating system, language and screen width, and actions: running an audit, picking a column by hand, writing a plan, downloading results, using the calculator, clicking a link to another site, and errors.
For an audit it records only counts and bands: how many rows and subreddits the file had, how many got each verdict, whether you set a target, how long the audit took, and which band the file's total spend falls in (under $1k, $1k–10k, $10k–100k, over $100k). It never records subreddit names, amounts or anything else from the file. If the audit can't find a column, it records the file's column headers (the names at the top of each column, not the values) so detection can be improved.
- No IP address is stored in the usage log. Visits on the same day are grouped by a one-way hash of your IP address and browser string, mixed with a random value that changes daily and is deleted after 2 days. The hash can't be reversed, and your visits on different days can't be linked.
- One value in your browser. A random ID for the current tab is kept in session storage, which your browser clears when you close the tab. There are no cookies.
- Plan writer. Each plan request also logs its outcome, how long it took, how many subreddits it covered, whether you wrote a product description (not the text), token counts and cost, and whether it was a free, paid or API request (with the key's ID for paid and API requests).
- Retention. The usage log is kept for up to 400 days.
What else this site collects
Nothing beyond the above. There are no accounts, no cookies and no ad pixels. Fonts load from Google Fonts, which receives the usual request information (such as your IP address) when your browser fetches them. The site is hosted on GitHub Pages, which may keep standard server logs.
Changes
If anything else is added, this page will say so first.