ZEROFANS…
Privacy Policy

Privacy Policy

Last updated 16 November 2026

1. Who processes your data

The ZeroFans service at zerofans.org (“ZeroFans”, “we”). This policy explains what personal data we process, why, where it is stored and what you can do about it. For questions about your data or to exercise your rights, email 1awqfes@gmail.com or visit our support page.

2. What we collect

  • When you choose Google, Google authenticates you and supplies your account identifier, email and basic profile information to Supabase. We use the provider identifier to restore unused credit after account deletion.
  • From your GitHub account, when you sign in: your GitHub account id, username (login), email address and avatar link.
  • For a managed review account we store a label, an internal sign-in address, a hash of the invitation secret and its expiry. To close the account, contact support.
  • What you enter: product links, the threads you save (kept 7 days), and which threads you mark replied or skipped.
  • What the service makes for you: your maps (matched communities, briefs), the live threads found and the karma helper's question list.
  • Billing: your balance and a record of every movement (top-ups, packs bought, refunds).
  • Your consent: when you accepted the Terms and this policy, and which version.
  • Technical: when the account was created, the last sign-in and session activity; the hosting provider's request logs (IP address, browser), kept briefly.
  • Cookies — see section 7.

3. What we do not collect or keep

  • No first or last name. GitHub may send the display name from your GitHub profile when you sign in; we delete it right after sign-in and never use it. Your login is a nickname you chose.
  • No passport or ID details, postal address, phone number or date of birth.
  • No bank card or wallet details — you pay on the payment provider's page.
  • No special categories of data (health, beliefs and the like) and no biometrics.
  • No advertising or analytics trackers, no tracking across sites.

4. Why we process it

  • To create your account and sign you in.
  • To provide the service: analyze your product, build maps, search live threads, run the karma helper.
  • To keep the balance, sell packs and handle refunds.
  • To protect the service: per-account limits, abuse prevention, blocking accounts that break the Terms.
  • To notify the operator about sign-ups, maps, purchases, top-ups and deleted accounts.
  • To answer your requests.

Legal grounds: performing our agreement with you (the Terms), your consent, and our obligation to keep payment records.

5. How it is processed

When you submit a link we fetch that public site and send its text, with our catalog of Reddit communities, to OpenAI's API, which returns a product summary and the communities that fit. When you search for live threads, the product's summary and the problem it solves go to OpenAI with the public Reddit posts found, so it can keep the ones that fit; the karma helper does the same with new public questions. Nothing about you besides the product goes with them. The community catalog is built from public Reddit data (rules, member counts, activity); none of your data goes into it. We never post anywhere for you.

6. Where your data is stored — outside Russia

All of the service's data is stored and processed outside the Russian Federation. We have no servers in Russia. We share data with the providers listed below as needed to deliver the services described here. We may also disclose information when required by law or with your consent.

  • Supabase (Supabase Inc., USA) — the database and sign-in. The database server is in Germany (Frankfurt, EU).
  • Vercel (Vercel Inc., USA) — hosting of the site and its server code; requests are handled on Vercel's servers outside Russia (by default in the USA), which keep short-lived logs.
  • OpenAI (USA) — product-page analysis and picking threads and questions: the text of the site you submit and your product's summary with public Reddit posts. Response storage is turned off.
  • GitHub (GitHub, Inc., USA) — sign-in, and the encrypted database backups (section 8).
  • Apify (Apify Technologies s.r.o., Czech Republic) — fetches public Reddit data. It receives only search phrases and community names — no data about you.
  • Telegram — operator alerts in a private chat: your GitHub login, the email your GitHub account exposes, your account id and product link.
  • Platega (platega.io) — the payment provider for top-ups; it receives the amount, your account id and GitHub login for its anti-fraud checks, and processes the payment under its own terms.

Some of these countries (for example, the USA) are not on Russia's list of countries that ensure adequate protection of personal data. By ticking the box when you sign in (or in the consent dialog) you agree to your personal data being transferred to and stored in these countries. If you don't agree, don't create an account — or delete it (section 10).

7. Cookies and browser storage

We set four first-party cookies and nothing else:

  • Supabase session — keeps you signed in. Strictly necessary.
  • zf_lang — the language you picked.
  • zf_theme — light or dark theme, if you picked one.
  • zf_consent — only for the minutes of a sign-in: carries the consent you gave in the sign-in dialog to our server, then is deleted.

None of them is used for advertising, analytics or tracking, so there is nothing to opt in to or out of — a one-time notice just says they are there. Your browser's own storage keeps three flags (the welcome tour's two and that you closed the cookie notice); they never leave your device.

8. How long we keep it, and security

  • Account data and maps — until you delete them or the account.
  • Payment records — kept after deletion because we must keep them, with their link to you removed (amounts and dates only).
  • Backups — an encrypted copy of the database every six hours, kept 30 days in a private GitHub repository; deleted data leaves the backups within 30 days.
  • Hosting request logs — a short time, set by the provider.

Row-level security lets you read only your own account and maps; balances and purchased searches can be changed only by our server. Traffic is HTTPS-only.

9. Payments

Your account holds a small prepaid USD balance. When payments are available, you can top it up (from $2.90) on Platega's hosted checkout; we receive only a confirmation, re-checked with Platega server-to-server before crediting. Packs are deducted from that balance on our server.

10. Your consent and your rights

You can't use an account until you accept the Terms and this policy: two boxes when you sign in, and again before continuing when either document changes materially. We record the date, time and version.

  • Ask what we hold about you, get a copy, or have it corrected — via the contact page.
  • Delete your account and every map at any time on your profile page — immediate and irreversible.
  • Withdraw consent: delete the account, or write to us. Processing then stops, except the payment records above; without consent the account can't be used.

11. Blocking and deletion

We can block an account that breaks the Terms: it can still open its maps but can't run analyses, searches, purchases or top-ups. The block is recorded on the account.

Deleting a map removes that map and its threads only; your balance and searches stay on the account. Undelivered reserve posts belong to the map and are removed with it; posts older than seven days are excluded and cleared when its reserve is next checked. Post IDs, subreddit names and first-delivery dates are kept in account history until account deletion to prevent repeats across recreated maps. When an account is deleted — by you on the profile page, or by us at your request — it disappears at once with everything tied to it: maps, threads, marks and consent record. Two things remain: the payment records described in section 8, with no link to you; and a short record of what the account held — your GitHub account's numeric id and username, the unspent balance and searches, how many maps it had and the date — kept so that if you sign in again with the same sign-in account, the balance and searches come back to you. It holds no email, maps or other content. Backups lose the rest within 30 days.

12. Changes

We may update this policy; the date above shows the current version. A change in substance is shown to every signed-in user, who has to accept it before continuing.