Privacy Policy
How this guestbook handles personal data.
This policy page describes how the y2k Guestbook ("the Site") handles information. The policy is written for visitors who choose to leave comments in the guestbook, and for visitors who use Ask the Documentation chatbot.
What We Collect
| Data | Who | Purpose |
|---|---|---|
| Display name & message body | Anyone who comments | Displayed in posted comments |
| Optional email | Commenters | Visible to admins only — will not be used to contact you unless requested in your comment |
| IP address (stored hashed) | Commenters | Rate-limit abuse |
| Page-view / analytics events | Visitors | Traffic & hit-counter stats |
| Docs chat prompts & replies | Visitors who use Ask the Documentation | Answer questions from these documentation pages |
docs_chat_id cookie | Visitors who use Ask the Documentation | Resume the same-browser chat |
| IP address (stored hashed) | Visitors who use Ask the Documentation | Rate-limit docs chat (5 questions per hour, 10 per day) |
Interactive API Library Reference
The API Library on these documentation pages is a reference explorer. Values you type there are not guestbook comments and are not stored in the Site database.
If you use Test Request:
- A Supabase project ID you apply stays in your open browser tab only (
sessionStorage). Closing the tab clears it. - Anon keys and JSON Web Tokens (JWTs) you paste into request headers stay in the explorer until you reload or remount it. We do not save them.
- Send goes from your browser to your Supabase project. We do not proxy or log those requests.
How We Use It
- Run and manage the guestbook (edit and delete comments as needed).
- Limit spam and abuse (profanity checks, rate limits).
- Measure visits to display hit counter / track visitor interactions with PostHog.
- Answer questions through the Ask the Documentation chatbot.
- Resume the same-browser Ask the Documentation chat and limit chat abuse.
Who Processes It
- Google Cloud OAuth Client — SSO for admins
- Google Gemini — Embeddings and generate for Ask the Documentation
- Supabase — Auth sessions, database storage, and chatbot history
- Vercel — Serves the site on the cloud
- PostHog — Analytics tracking
Retention and Deletion
- Guestbook comments (and optional emails) stay until an admin removes them or the database is cleared.
- Rate-limit keys are temporary.
- Docs chatbot messages stay in Supabase until you click Clear Chat in Ask the Documentation or clear your browser's cookies.
- Analytics retention follows the PostHog project settings.
Your Choices
- Do not submit an email if you prefer not to share one.
- Click Clear Chat in Ask the Documentation to delete your browser's chat session, stored prompts and replies, and the related cookie.
- You can ask us to delete a comment or stored contact email you provided.
Changes
We may update this policy when the Site's features or processors change. The version on this page is the current one.