Privacy
AfterLayOops shows published stories, nicknames, avatars, and selected roles publicly. You don’t need to provide an email address to browse or create a guest identity.
What is stored
When the community backend is enabled, it stores your guest account ID, nickname, avatar, optional former role, stories, votes, reports, and notifications. It preserves existing replies even though replies aren’t available in this release. Your browser may store a topic choice and unfinished draft.
If you request Jobs updates, we separately store your email address, consent, confirmation, and unsubscribe status. This does not require or link to a guest identity.
Optionally, you can sign in with Google or link Google to your guest identity to keep access across devices. Supabase stores the linked Google identity and email for authentication. Your Google email is not displayed publicly, and your chosen nickname and avatar stay in use.
Your choices
You can browse without a guest identity. Avoid posting personal or confidential details in public stories. Clearing browser data or switching devices may remove access to an unlinked guest identity. A linked account can sign in again with Google. Nicknames are unique and fixed after setup; avatars remain editable. To request access, correction, or deletion, email hello@afterlayoops.lol.
Optional analytics
With your permission, PostHog receives page categories and selected interaction events to help us understand use of the site. A random identifier lasts for your browser tab session. We do not send your story text, nickname, email, search terms, or individual story URLs. PostHog receives technical connection information when your browser sends events. Your choice is stored in this browser and you can change it below.
Analytics: off.
Service providers
Anonymous authentication and community data use Supabase when configured. The guest identity form uses Cloudflare Turnstile for a security check; this can process technical connection and browser information. Supabase verifies the result and maintains the authentication session. When enabled, Redis protection keeps short-lived hashed source counters to limit abusive traffic. Jobs confirmation emails use Resend when configured.
Jobs updates require email confirmation. Use the cancel/unsubscribe link in your email to stop alerts or cancel a pending request. We don’t run advertising trackers.