What we collect
Account information includes username, display name, contact email, password verifier, age eligibility declarations and profile fields you provide. Community data includes messages, reactions, attachments, memberships, roles, preferences, support requests and reports. Security and technical data can include session identifiers, IP address, browser/device information, access timestamps, account restrictions and audit events. Connected services provide the identifiers and authorised fields described during connection.
Why we use it
We use information to authenticate you, deliver conversations and files, save settings, administer permissions, handle support and privacy requests, prevent abuse and comply with applicable law. Quest activity supports rewards where enabled. Optional cosmetic settings do not grant employees access to your device. We do not claim messages are end-to-end encrypted.
Who can see it
Profiles and community content are visible according to their settings and memberships. Authorised employees may access relevant records for moderation, security, support and legal handling. We use Cloudflare for hosting, database storage and enabled AI processing; connected providers process their own account data. Platform information may be processed overseas. We do not sell account data or provide a blanket assurance that all processing remains in Australia.
Maurice and AI assistance
Maurice can process information you include in a support request to classify it, suggest guides and assist authorised staff. Avoid unnecessary sensitive information and never include passwords, secret keys or full payment details. AI can make mistakes and cannot promise legal outcomes or override a staff decision. Review and escalation remain available through support.
Developer workspace data
Sauce Developers stores uploaded command source, application configuration, project invitations and roles, configuration activity, volunteer applications and technical helpdesk cases. Accepted project members can read source; authorised editors can change it. Site staff and an assigned, approved community volunteer can read a technical case after you acknowledge that visibility. User code receives only a command name and input, runs in a bounded separate interpreter and is not given account credentials or database access. Do not upload secrets or unnecessary personal information. Source is kept with its project until replaced or removed; helpdesk records remain subject to the retention and deletion process below.
Cookies and local storage
Essential cookies keep your main account, support account and developer session signed in. Browser local storage saves client preferences such as theme and language. The desktop app stores its own settings and an isolated website session on your device. Clearing a desktop sign-in does not delete your server-side account. Optional tracking must not be treated as required for registration.
Retention and deletion
We retain information as needed to provide the service, protect accounts and resolve legitimate safety, legal and operational obligations. Retention varies by record and we do not promise immediate deletion from every backup. Account deletion requests are reviewed by Trust & Safety; some data may be retained where required or justified by law. Other users’ copies and published announcement copies may persist.
Your choices and requests
Open Settings → Data & Privacy to request an account export or deletion and review its status. The same controls are linked from the Legal hub. Request access, correction or raise a privacy concern through support. Identity and authority may need verification; we do not request your password as evidence.
Security and complaints
We apply access controls and abuse limits but cannot guarantee absolute security. Report suspected account compromise through support. If an Australian privacy complaint remains unresolved and applicable requirements are met, you may contact the Office of the Australian Information Commissioner. This policy does not claim certification or that every provision of the Privacy Act applies to every operator.