Privacy policy
Plain words on what FRAME stores, where it lives, and how to remove it. Last updated October 2026.
Identity and sign-in
When you create an account, Firebase Authentication (Google's free auth service) stores your email address, display name, and profile photo. FRAME receives a signed token proving who you are — your password never touches FRAME's servers. You can sign in with email/password or with Google.
Forum content
Your posts, replies, likes, bookmarks, follows, reports, and messages are stored in a Cloudflare D1 database so the community can read and interact with them. Public posts are visible to everyone; private messages are visible only to conversation participants and are never used for advertising.
Images you upload
Images uploaded through the Upload buttons go directly to ImgBB, a free image-hosting service, which returns a public link. FRAME stores only that link — never the image file itself. Anyone with the link can view the image, so avoid uploading sensitive photos.
Cookies and local storage
FRAME keeps small preferences in your browser's local storage: your light/dark theme, accent color, and demo drafts. No third-party tracking cookies are set by FRAME itself. Firebase may set cookies required for secure sign-in sessions.
Deleting your data
Edit or remove your profile details anytime from Edit profile. Deleting a post removes it and its replies permanently. To erase your account entirely — including your Firebase sign-in record and all forum content — contact support through the Help page and request erasure.
Children's privacy
FRAME is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact support and the account and its data will be removed.