Data you provide
Accounts store your email, display name, and a salted password hash. Guild profiles store recruitment details. Applications store character name, class, role, availability, and message. Event signups store character name, class, role, status, and the hash of a secret management token. Contact messages store your email, category, and message.
Who can see it
Reviewed public guild profiles are public. Applications can be read by the applicant and guild managers. Signup names, classes, roles, and status are visible to people who can access that event. Guild-only events require membership. Emails and password hashes are not exposed on profiles or event pages. Moderators review listing content and support messages.
Storage and providers
Data is stored in the configured Neon/Postgres database. Hosting uses Vercel. Open-source fonts are self-hosted; the browser does not contact Google Fonts. Providers may process connection data under their own terms.
Cookies and browser storage
Essential session cookies keep you signed in for up to 14 days. Signup cookies remember management tokens for up to 90 days. Session and signup cookies are HttpOnly, SameSite=Lax, and Secure in production. Manual plans are saved in local storage. Fictional event signups use session storage.
Website analytics
We use Google Analytics to measure page visits and how the website is used. Google Analytics may use cookies and process visited URLs, referring pages, and browser and device information. Google processes this information under its own privacy policy. No advertising is enabled.
Abuse prevention
Rate limits use a cryptographic hash of a connection identifier and server secret; the application does not store raw IP addresses in its rate-limit table. Sensitive management actions are recorded in a guild audit log. Hosting providers may retain technical access logs.
Your choices
Cancel signups with your personal link or the same browser. Reset the planner to clear its saved plan. Signed-in users can export their account and applications from the dashboard. Send correction, access, or deletion requests through the contact form. Requests are handled manually.
Retention and contact
Guild, event, application, and support records remain until manually removed. Expired session and rate-limit records are removed when maintenance is run. A public commercial launch requires a named operator, monitored contact address, and documented retention schedule; those details are not configured yet.