PRIVACY &
COOKIES.
This page describes the current website, email-only contact form and player account features. It is a pre-launch draft because the project does not identify the website operator or provide a privacy contact.
Who is responsible?
The current project does not state the legal name or contact details of the person or organisation responsible for this website and its contact-form data. This information must be supplied by the operator before the notice is treated as complete.
Information sent through the contact form
The form asks for your name, email address, enquiry topic and message. When the API handles a request, it also uses the connection IP address temporarily for rate limiting. The API's rate-limit window is 15 minutes; its counters are held in process memory and are not message storage.
The API sends accepted enquiries to the configured inbox through Resend. It does not save messages to a database or local files. Resend and the recipient's email service may process or retain the email under their own service settings. This project does not define a retention period for those copies.
Player accounts and profiles
When you register, the account service processes your name, email address and password credential. The password is handled by Better Auth and stored as a password hash in the PostgreSQL account database, not as plain text. When you open your account page, BREAK DISH creates or updates a player profile containing your display name and any location or biography you choose to provide. The current API exposes these profile fields only to the signed-in account; public player pages are not available yet.
The account service uses a session cookie to keep you signed in. Account and profile data is stored in PostgreSQL. This project does not yet provide an account deletion or profile deletion feature, so the operator must set and publish a retention and deletion process before launch.
Why information is used
The form information is used to receive and respond to the enquiry you choose to send. Account details are used to create and authenticate your account and maintain the player profile you edit. The website operator has not documented the lawful basis for these uses in the project; the operator must determine and state the applicable basis before launch.
Service providers and other requests
Resend is used by the API to deliver contact emails and, when configured, account verification and password recovery emails. The site requests its typefaces from Google Fonts, so a visitor's browser connects to Google to retrieve those font files. PostgreSQL stores account, session and profile data. The API is intended to run as a separate Render Web Service; if that deployment is used, Render will also host the API and database. Confirm the actual hosting arrangement and any international-transfer details before launch.
This project does not include an analytics or advertising script, and it does not use browser local storage or session storage. The Better Auth API sets a session cookie when a visitor signs in. Check the final hosting and provider configuration for any additional cookies, logs or tracking before publication.
Retention
The contact API has no database or file archive for submitted messages. Emails may remain in the email provider or receiving mailbox according to the relevant account settings. Account and profile information remains in PostgreSQL; this project does not currently define a retention period or offer account deletion. The operator must choose and explain retention and deletion arrangements for account data and email copies before launch. Hosting and security-log retention also needs to be confirmed for the final deployment.
Your privacy rights
Depending on the circumstances and lawful basis, UK data-protection law provides rights concerning personal information. The operator must publish a real contact route for privacy requests and confirm which rights apply. Information about rights and making a complaint is available from the Information Commissioner's Office.
Changes to this notice
Update this page when the website's data use, providers or contact process changes. The website operator and an appropriate adviser should review this draft before it is used as the final privacy notice.