Privacy Policy
Version 2026-10-26. Last updated October 26, 2026.
This policy explains what information FLOORHOLLER collects, how it is used and shared, and what choices you have. FLOORHOLLER is run by [OWNER: the legal name of the person or company that runs FLOORHOLLER]. It was written to match how the site is built. Where something depends on settings or services outside our code, we say so.
1. The short version
- Your username, threads and replies are public. Everything else about you is private.
- Your Google name, email address and photo are not shown to other users and are not stored with your posts.
- We do not run ads, we do not use advertising or analytics trackers, and we do not sell your personal information.
- There are no private messages. Nothing you post is private.
2. What we get when you sign in with Google
Sign-in is handled by Google through Firebase Authentication. When you sign in, Google gives our website a sign-in token that includes a unique account ID, and may include your name, email address, whether Google has verified that email, and your profile photo. Our server checks the token with Google. It uses the email address only to (a) make a one-way "fingerprint" so that a ban cannot be avoided by creating a second account with the same Google email, and (b) recognize the administrator. Our database does not store your email address, name or photo.
Google itself keeps your profile details in the Firebase Authentication user list for this project, which the site owner and administrators of that project can see. Your use of Google sign-in is also covered by Google's privacy policy.
3. What we store
| Information | Public? |
|---|---|
| Username you choose, and when you posted | Yes |
| Threads and replies you write (text, time, where in the conversation, and your chosen position on statements), and upvote totals | Yes |
| Your account ID from Google sign-in (not shown to others), and the date you created your username | No |
| The one-way fingerprint of your verified email (cannot be turned back into your email) | No |
| Which versions of the Terms, Privacy Policy and Guidelines you accepted, and when | No |
| Which items you upvoted and which you reported, with the reason you gave and the time | No |
| Moderation records: suspensions and bans with the reason, the administrator's actions, hidden or removed content, and automated-screening results | No |
| Abuse-prevention counters: how often an account posted recently, fingerprints of recent text (to catch repeats), and any automatic cooldown | No (kept for about a day) |
| Requests you send through the content and legal request form (your name, email, any phone or address you give, and what you wrote) | No |
Your username and posts can be copied, quoted, indexed by search engines and archived by others. Even if you delete a post, copies outside our control may remain.
4. IP addresses, logs and browser storage
- We do not store IP addresses in our database or with your posts.
- Our hosting providers (Google Cloud Run and Firebase Hosting) and Google's sign-in service receive your IP address and browser details when your browser contacts them, and Google keeps request logs for a period set by Google and by the project settings. [OWNER: confirm the log retention period in Google Cloud Logging; the default is about 30 days]
- Our own server logs record only error events, with tokens and email addresses removed. They do not record what you post.
- Firebase keeps your signed-in state in your browser's storage. We do not set advertising or tracking cookies.
- The site loads fonts from Google Fonts, so your browser contacts Google when pages load.
5. How we use information
- to run the discussion: show posts, count votes, let you reply and report;
- to keep the Service safe: limit spam, review reports, hide or remove content, restrict accounts, investigate threats, and keep evidence;
- to respond to copyright, privacy and other legal requests, and to follow the law;
- to email the administrator alerts. These emails say that something happened and link to the dashboard; they do not contain the text of posts.
6. Moderation and reporting records
When content is hidden or removed, we keep a private copy of it (with sensitive numbers such as card or Social Security numbers masked), the account ID of its author, who reported it and why, and what the administrator decided. We keep this so decisions can be reviewed and so evidence exists if a threat or other serious matter is referred to the appropriate authorities. We may disclose information to law enforcement or others when we believe in good faith that the law requires it, or that it is necessary to prevent imminent harm or protect people or the Service.
7. Who else handles your information
- Google (Firebase Authentication, Firestore database, Cloud Run, Firebase Hosting, Google Fonts) runs the infrastructure.
- Resend delivers the administrator's alert emails. It receives the administrator's email address and the alert text (which includes usernames and counts but not the text of posts).
- Search engines and the public can read everything that is public.
- We use no outside AI service. Posts are not sent to any AI provider; automated screening runs on our own server with fixed rules.
8. How long we keep information
We keep information for as long as we need it for the purposes above and to meet legal obligations. In general: public posts stay until you or an administrator remove them; removed content disappears from the site but a private copy and the related records stay in the moderation history while needed; abuse-prevention counters expire after about a day; accounts stay until they are deleted. We do not currently delete moderation records automatically. [OWNER: set specific retention periods for moderation records, evidence and legal requests, with your attorney]
9. Your choices and requests
- You can delete your own threads and replies at any time with the Delete button.
- To ask for help with your personal information (for example to ask what we hold about you, to correct it, or to ask us to delete your account), use the content and legal request form or write to [OWNER: a contact email address, set CONTACT_EMAIL]. We will review the request. We may keep records we need for safety or legal reasons.
- Depending on where you live, laws such as the California Consumer Privacy Act may give you additional rights. [OWNER: attorney: confirm which state privacy laws apply to this site and add any required notices]
10. Security and incidents
The database cannot be read from visitors' browsers; only our server can reach it. Sign-in is checked with Google on every request, and moderation tools check administrator status on the server. Connections use HTTPS. No system is perfectly secure. If we learn of a security or privacy incident that affects personal information, we will investigate, take steps to contain it, assess who is affected, and notify affected people and authorities where the law requires.
11. Children
FLOORHOLLER is not for children under 13, and we do not knowingly collect information from them. If you believe a child under 13 has an account, contact us and we will review it and take it down.
12. Changes and contact
We may update this policy. For a material change we will ask you to accept the new version. Contact: [OWNER: a contact email address, set CONTACT_EMAIL] [OWNER: mailing address, set LEGAL_ADDRESS].