Legal
Privacy Policy
How we handle personal data. Effective 10 November 2026. Last updated 10 November 2026.
The short version
- What we collect: only what we need to run Forumcat. That is your email, your name and photo if you add them, what you post, and billing records. Stripe handles card details.
- We never sell personal data. We do not show ads.
- No passwords. You sign in with an emailed link, a 6-digit code, or Google.
- Stored in the EU. Our main database and app servers are in Frankfurt, Germany.
- Public by default. Forum questions can show up in Google and AI tools. A private question is only shown to its author and the forum's team.
- Delete any time. You can delete your own account. Forum teams can erase a visitor on request.
- One email for everything: meow@forumcat.com.
Who we are
Forumcat is run by Superblog, the company behind the Superblog blog platform. We are based in India. In this policy, "we", "us" and "our" mean Superblog. Payments for Forumcat go through Superblog's billing account, so charges show as Superblog on card statements.
This policy covers:
- our website at forumcat.com, including the docs and the blog at forumcat.com/blog,
- the team dashboard at dashboard.forumcat.com,
- every customer forum we host, on myforumcat.com or on a customer's own domain,
- our REST API and our MCP server (the connection AI tools use).
We have not appointed a representative in the EU or UK. You can contact us directly at meow@forumcat.com.
Our two roles: controller and processor
When we are the controller. We decide why and how we use this data:
- your dashboard account (your email, name and photo),
- billing and payment records for the company that pays us,
- visits to our website, docs and blog,
- emails you send us,
- security and abuse data we use to protect the whole service.
When we are a processor. A company that runs a forum on Forumcat is the controller for its forum. That covers forum accounts, questions, replies, votes, images, and the analytics the company sees about its forum. We only use this data to run the forum for that company, as it tells us to. A Data Processing Agreement is available on request: email meow@forumcat.com.
If you post on a forum, the company that runs it is responsible for your data. Read their privacy policy and send privacy requests to them first. If you write to us, we will pass your request to them, or help where the law requires.
Each forum is separate. If you use the same email on two forums, they are two different accounts. We do not link them or build a profile of you across forums.
What we collect and why
Dashboard accounts (people on a customer's team)
| Data | Why we use it |
|---|---|
| Email address | To sign you in, send sign-in links and codes, team invites, and trial and billing notices. |
| Name and profile photo | To show who you are to your team. If you sign in with Google, we get your name, email and photo from Google. |
| Which forums you belong to, and your role | To decide what you can see and do. |
| Sign-in sessions | To keep you signed in. Each session record holds your browser's user agent (the short text that names your browser and device). We do not store your IP address with it. |
| Google sign-in tokens | If you sign in with Google, we keep the tokens Google returns, linked to your account. |
The company that pays us
| Data | Why we use it |
|---|---|
| Forum name, address and settings | To run the forum. |
| Plan, trial dates and subscription status | To apply the right limits and send trial and payment reminders. |
| Payment records | Amount, tax, currency, date, receipt link and Stripe reference numbers. Stripe handles the card itself. We never see or store full card numbers. |
| Business name and tax ID | Only if you add them at checkout. Stripe collects them and shows them on invoices. |
Forum accounts and content (we process this for the forum's company)
| Data | What it is |
|---|---|
| Email address | To sign in and to receive sign-in links and codes. Not shown publicly. |
| Display name, photo and bio | Shown next to posts. |
| Questions, replies, votes and images | What people post. Public by default unless marked private. |
| Sign-in sessions | The same as dashboard sessions above: a user agent, no IP address. |
| Google sign-in tokens | Only if the forum turned on Google sign-in. This uses the forum company's own Google app, not ours. |
Forum analytics (we process this for the forum's company)
We count page views per question per day, with no cookies and no tracking script. We store daily totals only. We do not store the visitor's IP address, device or identity for this. We also count what people search for on a forum, and whether the search found anything. Search words are stored as typed (after cleanup). If a visitor types personal details into the search box, those details could stay there.
Security, abuse prevention and records
| Data | Why we use it |
|---|---|
| Shortened IP address | When a team takes an action we record in the audit log, or an AI tool registers with our MCP server, we store only the first part of the IP address (the first 3 of 4 parts of an IPv4 address, or the first 3 of 8 parts of an IPv6 address). Never the full address. |
| Audit log | A permanent record of team and admin actions, such as role changes, invites, deletions and settings changes. Each entry holds the action, who did it (an account ID), what it changed, the time and a shortened IP address. Entries for team invites and badge changes also hold the team member's email address. |
| Email send records | Who we emailed, when, what kind of email, and whether it was sent. We never store the email's subject or body. We use this to stop email abuse. |
| Bot checks | Cloudflare Turnstile checks sign-in and new-question forms for bots. See "Who we share data with". |
Our website and dashboard analytics
We use Google Analytics on forumcat.com (including the docs) and on the dashboard to understand how people find us and use the product. Google Analytics uses cookies (see "Cookies"). Our server also sends Google a short list of product events, such as "forum created" or "question created". Each event carries only its name, a forum ID and, for sign-ins, how the person signed in (link, code or Google). Events never include emails, names, IP addresses or post text.
Forums never load our Google Analytics. A forum's company can add its own scripts to its forum (for example its own analytics or chat widget). Those scripts are the company's choice and responsibility, not ours.
When you contact us
If you email us, we keep your email and what you wrote so we can reply. When a new forum is created, our support inbox gets an alert with the forum name, address and the owner's email.
Our legal bases (for people in the EU, UK and similar places)
Where we are the controller, we rely on:
- Contract. To create your account, sign you in, run the forum you pay for, and bill you.
- Legitimate interests. To keep the service secure and stop spam and abuse. Also to keep an audit log, send service notices, see how our website and product are used, and improve them. We balance these against your rights, and you can object (see "Your rights").
- Legal obligation. To keep tax and accounting records, and to answer lawful requests.
You can block or delete analytics cookies in your browser settings at any time. Google also offers a browser add-on that turns off Google Analytics.
Where we are a processor, the forum's company chooses the legal basis for its forum.
Cookies and similar storage
We keep cookies to a small set. We do not use advertising cookies.
On forums, Forumcat itself sets only sign-in cookies. A forum's company may add scripts that set their own cookies. Ask that company about those. Our blog runs on Superblog, our own blog platform, and this policy covers it too.
| What | Where | Why | How long |
|---|---|---|---|
Sign-in session cookie (__Secure-forumcat_dash.session_token) | Dashboard | Keeps you signed in | 30 days, renewed while you use it |
Sign-in session cookie (__Host-forumcat.session_token, locked to the forum's own domain) | Each forum | Keeps a forum account signed in | 30 days, renewed while you use it |
Google sign-in check cookie (ends in .state) | Dashboard, and forums with Google sign-in | Protects the Google sign-in step | 5 minutes |
Google Analytics cookies (_ga, _ga_*) | forumcat.com, its docs, and the dashboard | Counts visits and how people use our site | Up to 2 years |
Cloudflare security cookies (for example __cf_bm) | Pages served through Cloudflare, when its bot protection is active | Tells people apart from bots | Short-lived, set by Cloudflare |
| Browser storage (not a cookie) | Dashboard and forums | Remembers display choices, such as light or dark mode, chart style and page size | Until you clear it |
Cookies and browser storage set by Forumcat, checked against our code on 10 Nov 2026. Names may change.
Who we share data with
We share personal data only with:
- Service providers that help us run Forumcat (listed below). They may only use it to provide their service to us.
- The forum's company. A forum's team can see the email addresses and activity of its own forum accounts.
- The public. Anything posted on a forum that is not private can be read by anyone, and by Google and AI tools. That includes your display name and photo next to your posts.
- Tools a forum's company connects. A company can connect its own tools through our API or MCP server, for example an AI assistant. Those tools act for the company, under the company's control.
- Authorities, when the law requires it, or to protect people from harm.
- A buyer, if we sell or merge the business. We would tell you first.
We do not sell personal data, and we do not share it for advertising.
| Provider | What they do for us | What they receive | Where |
|---|---|---|---|
| Amazon Web Services | Runs our app servers (App Runner) and keeps a backup copy of uploaded images (S3) | All account, billing record and forum data that passes through the app; uploaded images | EU, Frankfurt (eu-central-1) |
| Supabase | Hosts our main database (Postgres) | All account, billing record and forum data | EU, Frankfurt (eu-central-1) |
| Cloudflare | Network in front of the dashboard and forums, custom domain routing, image storage (R2), bot checks (Turnstile), and hosting for forumcat.com | All web traffic, including IP addresses; uploaded images; browser signals for bot checks | Global network, in many countries |
| Stripe | Payments, subscriptions, invoices and tax | Billing contact email, card details, billing address, business name and tax ID | Several countries, including the US |
| Plunk | Sends our emails | Recipient email address and the email content (sign-in links and codes, team invites, trial and payment notices) | Plunk's own servers, which may be outside the EU |
| Google Analytics; Google sign-in for the dashboard; Google Workspace, which hosts our support inbox | Analytics: page views, device and browser data, IP address (used, then dropped by Google Analytics) and product events with forum IDs. Sign-in: your Google email, name and photo. Inbox: emails you send us, and alerts with new forum owners' emails | Several countries, including the US |
Service providers that handle personal data for Forumcat, checked against our code and settings on 10 Nov 2026.
International transfers
Our main database, app servers and image backups are in Frankfurt, Germany. Some providers, such as Cloudflare, Google, Stripe and Plunk, may handle data in other countries, including the United States. Our team works from India, so we may also reach data from there.
When EU, UK or Swiss law requires it, we protect these transfers with Standard Contractual Clauses. You can ask us for a copy at meow@forumcat.com.
How long we keep data
- Dashboard account: until you delete it. You can delete it yourself from your account page once you no longer own a forum.
- Sign-in sessions: they expire after 30 days without use. Sign-in codes and links expire after 10 minutes.
- A forum and everything in it: until the forum's owner deletes it or asks us to delete it. Deletion is immediate and permanent: accounts, posts, votes, images and settings. Images are removed from storage and from the backup copy.
- Trials that never become paid: a trial lasts 7 days, then a 7-day grace period. If no plan is bought, we delete the forum and everything in it automatically. We email the owner before that happens.
- Canceled or inactive forums: we keep the content until the owner deletes the forum or asks us to delete it.
- Images that were never posted: removed after 24 hours.
- Forum analytics and search words: kept while the forum exists.
- Audit log: kept permanently, even after a forum is deleted, so there is a record of what happened. IP addresses in it are shortened. Some entries hold a team member's email (see "What we collect").
- Email send records: kept to stop email abuse, with no fixed end date yet. Records tied to a forum are deleted when the forum is deleted.
- Billing records: as long as tax and accounting law requires. Stripe keeps its own records.
- Backups: deleted data may stay in our database backups for a limited time before it is overwritten.
- Technical logs: our hosting and network providers keep server logs for a limited time, for security and fixing problems.
- Google Analytics: Google keeps this data for the period set in our Google Analytics account, then deletes it.
Your rights
Depending on where you live, you may have the right to:
- see the personal data we hold about you and get a copy,
- correct it,
- delete it,
- get it in a format you can move to another service,
- object to how we use it, or ask us to limit it,
- complain to your data protection authority.
How to use them:
- Dashboard account: edit your name and photo on your account page. Delete your account there too. You will need to hand over or delete any forum you own first.
- Forum account: you can delete your own forum account from your profile page on that forum. This removes your email, name, photo, sign-ins, votes and the questions and replies you posted. Replies you wrote as part of the forum's team stay, shown as "{forum name} Team" instead of your name. For anything else, contact the forum's company.
- Forum teams handling a request: owners and admins can erase a forum account from the Members page. This removes the same data as above.
- A copy of your data: forum companies can get their data any time through the API. Or email us and we will send you an export.
- Everything else: email meow@forumcat.com. We reply within one month at the latest. We may need to check who you are first.
California and other US states: we do not sell personal information, and we do not share it for cross-context behavioral advertising.
Children
Forumcat is a business tool. You must be at least 16 to use the dashboard or to create a forum account. We do not knowingly collect personal data from children under 16. A forum's company decides who may use its forum and must follow the law on children's data for its audience. If you think a child has given us personal data, email us and we will delete it.
How we protect data
- All traffic uses HTTPS.
- There are no passwords to steal. You sign in with an emailed link, a code, or Google.
- Forum sign-in cookies are locked to the forum's own domain, so scripts a forum adds cannot reach the dashboard. Billing and script settings live only on the dashboard.
- API keys and AI tool access tokens are stored only as one-way hashes.
- A forum's own Google sign-in secret is encrypted (AES-256) before we store it.
- Every database query is limited to one forum, so one forum cannot read another's data.
- We store only shortened IP addresses, and only in the audit log and abuse records.
- Team roles limit who can see and change what. The audit log records team actions.
No system is perfectly secure. If a breach affects your personal data, we will tell you and the authorities as the law requires.
Note: images are served from a public address. An image in a private question can be opened by anyone who has its exact link. Do not put anything in an image that must stay secret.
Changes to this policy
We will update this page when our practices change and change the date at the top. If a change matters, we will email account owners at least 30 days before it takes effect.
Contact us
Privacy questions and requests: meow@forumcat.com. We read every message and usually reply within two business days.
If you are in the EU or UK, you can also complain to your local data protection authority.