What we collect and why
Google sign-in supplies your account name, email address, profile picture and Google identity so we can identify invited members. We store account and session records, including timestamps and, when available, IP address and browser information. Access and refresh tokens are encrypted if stored; other provider identity records, including an ID token when supplied, may also be retained for authentication. We don’t request Gmail or Google Drive access.
We store the profile and stories you enter, their revisions, your publication consent and its version, bookmarks, moderation decisions and notes. These support drafting, review, publication and saving stories. Rate-limit records help protect the service.
What other people can see
Your chosen public name, approved dot profile and approved story snapshots are public. Your Google email is not included in your public profile. Choose a nickname if you prefer, and leave your location blank unless you want it published.
Drafts and submissions are private to you and authorized reviewers. Authorized operators can access stored information to run the service, investigate problems and handle requests. A profile change or story edit does not replace the approved version until another review.
Cookies and service providers
We use cookies for sign-in and authentication security. The application is hosted on Vercel, its database is hosted by Neon, and Google provides sign-in. Those services process information needed to provide their functions. We haven’t added advertising or analytics trackers to this pilot.
Keeping and removing information
The current pilot keeps account records, story revisions and moderation history; it does not automatically erase them when you edit or unpublish a story. Sessions expire, but expiry does not necessarily delete stored security records; this pilot does not promise automatic retention cleanup. Unpublishing removes a story from public pages while its private revision and review history remain stored.
To request access, correction, account closure or removal, contact us. We may need to verify that the request concerns your account or content. We’ll review what can be removed and explain any records that need to remain. We don’t promise immediate erasure or removal of copies someone else has already made.
Questions or concerns
Email hello@thedotsfamily.com. Include the relevant page link and a brief description; don’t send passwords, sign-in codes or unnecessary sensitive information.
Contact & report a concern ↗Last updated: 30 September 2026. The Dots Family is an independent project, not operated by or affiliated with OpenAI.