Your data, explained.

What we collect and why

• Discord sign-in: your Discord user ID, display name and avatar, plus encrypted OAuth access and refresh tokens. We use these to sign you in, check server access and keep your session working. We do not receive your Discord password or request your email address.
• Server management: server IDs/names, channels, categories, role names, permissions and member-role information needed to check your authority. We store designs, drafts, permission edits, structure snapshots, publishing records and starter-post information you create or review.
• Your app work: templates, channel styles, tutorial progress and practice data, beta invitations and feature access.
• Support: your Discord user ID, messages you submit and the owner's replies. Requests are private to you and the beta owner. Do not include passwords, bot tokens or other secrets.
• Operational records: account/server IDs and outcomes of management actions; hosting providers also process connection information such as your IP address. Our app does not deliberately record request bodies or sign-in credentials in public logs.

Layout generation currently uses rules on our server. Your descriptions are not sent to an external AI service. The app is not intended to archive server conversations; it may check starter posts it manages so it can avoid repeating or overwriting them.

Where data goes

The backend and database run on our Oracle Cloud VM in Sydney, Australia. Discord receives sign-in and server-management requests. Oracle and the server's operating system process data needed to host the service. HTTPS uses Caddy and a certificate authority; the public hostname uses sslip.io. Avatar images load from Discord's CDN. Opening a third-party bot link takes you to that provider, whose own privacy terms apply.

The beta has no advertising, analytics trackers, data sales or billing integration. We use data to provide the beta, enforce invitations, investigate problems and recover from failures. We may disclose information when required by law or needed to address abuse or a security incident.

Cookies and this computer

Essential secure session and sign-in-flow cookies are used for authentication; sign-in flows expire after ten minutes and app sessions after seven days. Draft recovery and tutorial progress are also saved in your browser or desktop-app profile. These are not advertising cookies. Clearing site data removes the browser copies; signing out alone does not erase saved designs.

Retention and backups

Saved account work remains until you delete it or ask the owner to remove it. Expired sessions/sign-in flows are periodically removed. Support requests are removed after 90 days without an update, or sooner when you delete your account data.

Encrypted database backups are kept separately: up to 14 daily and four weekly representatives on the server, and up to 30 independent encrypted copies on the owner's private PC. Old copies expire through rotation; offline copies and manual recovery backups may remain longer. Backups are not individually rewritten when you delete an account.

A separate encrypted recovery ledger keeps a keyed fingerprint and deletion time, without your raw Discord ID or message content. It is retained to reapply deletion when an older database is restored. The owner must use the latest available ledger before reopening a restored service; deletions newer than the last surviving off-site copy may need to be reapplied manually.

Delete your account data

Open Support & account or Help & settings → Account data. Deletion is available even when your beta invitation expires. You must sign in to verify which account to delete, stop any publishing job, and type DELETE to confirm.

This removes your stored drafts, designs, versions, templates, tutorial progress, personal publishing history, support requests, feature access and invitation, and signs out all your sessions. It removes your direct audit entries and invitation references from the active database. Other people's saved designs and shared server-management records remain.

Deletion does not remove your Discord account, bot, channels, roles or messages, and does not undo work already applied to Discord. It clears this account's current browser drafts; other devices clear their recovery copies after reconnecting with the updated app. Offline copies, exported files and old app windows may remain on those devices. You can clear their site data manually.

Signing in again creates a fresh session but does not restore your beta invitation or deleted designs. The beta owner's account requires an owner-configuration transfer before self-service deletion to avoid losing administration. You can separately revoke Server Studio in Discord's Authorized Apps settings.

Questions, corrections or a copy of your data

Use the private support inbox and select Privacy or data. Requests work for signed-in accounts without an active invitation. Saved designs and history also have download options in the app. If you cannot sign in, contact the person who invited you and ask them to connect you with the beta owner; do not send credentials. Support is handled manually, with no guaranteed response time.

You must meet Discord's applicable minimum-age requirements and have authority to manage the server. Only include information needed for testing. Material changes to this notice will be dated here and announced to testers through the app's support/invitation channel.