Privacy policy
Your face, your conversations, and your control over them.
Your photo and data. Supabase handles authentication, database and private photo storage; Vercel hosts the app and checks browser signals to help block automated activity. Bot checks do not prove identity, age or that a person is continuously present. We store your session or account identifier, public screen name, optional bio, fitted head photo, outfit, rule acceptance, blocks, friend requests, friendships and limited activity metadata. Saved accounts also retain comfort preferences. Your device resizes the photo and removes metadata before server-side detection and fitting. An unconfirmed portrait expires after 15 minutes and is removed during cleanup. The fitted photo and generated head views are kept after saving. To complete small cropped hair edges, the resized photo may be processed by OpenAI through Vercel AI Gateway. Existing photographed pixels are preserved and you review the fitted result before using it. The same providers process fitted photos when estimated side and back views are prepared. These views are estimates, not a 3D scan; the front view remains your original fitted photo. Face detection does not prove identity, age or liveness. We do not store face recognition templates. Your email is not displayed to other players.
Safety reports and restricted records. A report includes its category, the location and explanation you provide, optional contact email, and any player reference. An intimate-image removal notice also requires a contact email, your typed signature, whether you are the depicted person or their representative, and a good-faith nonconsent statement. We record receipt times, deadlines, operator actions and access, and any reporting or preservation references. When a reported player can be identified, we may preserve their existing account and portrait records, generated views, related reports and available conversation context, including private messages, to investigate and meet legal duties. Image hashes help identify identical copies. These records are restricted to authorized operators and service providers that support storage and processing; they are not shown to other players. A private receipt link shows limited status information, not report text or contact details. When email alerts are enabled, Resend delivers the report category, case reference, receipt time, any deadline and a link to the restricted queue to designated operators. These alerts do not include the reported content, signature or reporter contact information. Necessary information may be disclosed to NCMEC or law enforcement as permitted or required by law.
Conversations and saved copies. Public chats are visible to nearby people, including visitors exploring without a character. Recent public messages appear above their speakers. Public portraits, bios and group membership are visible during a spirit visit; visitors do not appear as players. Private chat messages are only delivered to members, and changing a private chat back to public does not publish its previous private messages. A private 1:1 requires both people to be in the same public conversation and the recipient to accept. It moves only those two people into a new room. Changing the whole group’s privacy requires everyone’s agreement. Private chats restrict entry; they are not end-to-end encrypted. Messages sent while a saved-account participant is present are kept in that participant's private chat history for up to 90 days. This includes messages sent by guests. Saving an account starts history for future messages, not messages you missed. Participants may copy, screenshot or report messages. Guests do not receive a saved archive. Live chat and reconnect history is limited to recent messages, which expire after 30 minutes or when a room ends.
Your control. Delete your saved chat copies in Saved chats, or delete your character, photo and generated head views in Profile. This does not delete other participants' copies or submitted abuse evidence. Guest character data becomes eligible for cleanup after expiration; scheduled deletion runs daily, in bounded batches, and may take longer during outages or backlogs. Anonymous authentication metadata follows Supabase's retention policy. Ordinary in-game abuse reports and activity metadata become eligible for cleanup after 30 days. Hosting backups follow the providers' retention policies.
Safety preservation. Safety cases, captured context and decision/access records are kept separately and are excluded from that routine 30-day cleanup. Images and records needed for an open investigation or legal hold may be retained after account deletion or photo replacement. Material included in a completed NCMEC provider report and applicable context must be securely preserved for at least one year after submission; additional legal holds can extend that period. Closing a case does not end an unexpired preservation requirement. Once image preservation ends, detached images become eligible for cleanup; images still in lawful use are not deleted merely because a report was dismissed. See the safety and reporting process, or contact safety@stick.town about a report or retained safety information.
Safety and removal requests. Report non-consensual intimate imagery or a child-safety concern without signing in. Do not upload, download, or redistribute suspected child sexual abuse material to make a report. Use the reporting instructions to identify its location.