chat™ /

privacy policy

last updated: june 9, 2026

this privacy policy was mostly generated by AI. i'm not a lawyer, claude is not a lawyer, this policy isn't perfect (or good really) but it's here purely so someone doesn't come yelling at me. if you have a concern or suggestion or anything really, DM me on Slack — you can email me but i probably won't reply unless it's about data.

1. introduction

this privacy policy explains what data chat™ collects, how it is stored, and how it is used. by using chat™, you agree to the practices described here.

2. data we collect

when you use chat™, the following information is collected and stored:

guest accounts

if you use chat™ without logging in, you are assigned a temporary guest session. guest sessions may generate data such as messages and IP addresses, however this data is not linked to any account, email address, or persistent identifier. as a result, it cannot be traced back to you specifically.

local storage

chat™ uses your browser's local storage to save certain information on your device. this includes your user ID and username, which are stored locally to keep you logged in and maintain your session.

2.5. eligibility

age requirement

chat™ does not have a strict minimum age requirement, however it is not directed at children. if you are under 13, please be aware that this service was not designed with you in mind and parental guidance is advised. chat™ does not knowingly collect data from children under 13.

3. how your data is stored

all locally stored data — including messages, email addresses, and IP addresses — is stored as plain text and is not encrypted. you should be aware of this when deciding what information to share on the platform. images and all other files uploaded while using the website are publicly accessible by anyone, at any time.

4. how your data is used

stored data (logged messages, emails, and IP addresses) is not actively accessed or reviewed except when necessary — for example, to investigate abuse or resolve technical issues.

we do not sell, share, or otherwise distribute your personal data to third parties.

transparency

chat™ is an open source project. the source code is publicly available and can be inspected to verify how data is collected, stored, and handled. we encourage technically inclined users to review the codebase if they have concerns about data practices.

5. third-party services

hack club CDN

images and files uploaded to chat™ are served and stored via the Hack Club CDN. their handling of that data is governed by the Hack Club CDN Privacy Policy.

nest

chat™ is hosted on Nest, a hosting platform controlled by Hack Club. as a result, all data and activity on chat™ is also subject to the Nest Privacy Policy.

hack club auth

if you log in using Hack Club, your authentication is handled by Hack Club's auth service. that process is subject to Hack Club Auth's own Privacy Policy and Terms of Service.

6. data retention

messages and account data (email, username, IP) are retained indefinitely. there is currently no automated deletion process.

7. breaches

in the event of a data breach or unauthorized access to stored data, affected users will be notified on a best-effort basis via a notice posted on the site. given that data is stored unencrypted, you are encouraged to avoid sharing sensitive personal information on the platform.

8. contact

if you have questions or concerns about this Privacy Policy or your data, please contact me (Emma) either via the Hack Club Slack or over email, at emma@csarcade.wiki.

data deletion requests

to request deletion of your data (messages, email, username, IP address), please contact me (Emma) at emma@csarcade.wiki. deletion requests will be handled on a best-effort basis, and may take some time to fully review and take action. for the quickest reply, please use the same email you used to log into the site.

note: if you have only ever used chat™ as a guest, you cannot submit a deletion request — guest session data is not tied to any identifiable account and cannot be traced back to you specifically, unless you directly reveal what your guest username was. in that case, that's on you.