Manage privacy and account controls

Clan Labs user settings separate personal account controls from community settings. Changing a personal preference does not change the selected community’s staff permissions, subscription, or operational analytics.

Privacy preferencesCopy link to Privacy preferences

Open User Settings → Privacy to review the current choices. Clan Labs offers Allow performance analytics where the deployment’s consent rules apply. Necessary technologies remain on because they are required for sign-in, security, and core service operation.

Optional product analytics is separate from the community analytics feature used by staff. Withdrawing optional analytics consent does not remove a community’s operational records or disable its management dashboards.

Review sign-in sessionsCopy link to Review sign-in sessions

Use the account or session area shown in Clan Labs to inspect active sign-ins and revoke sessions you no longer recognise or use.

1. Confirm the device or session is genuinely yours.
2. Revoke an unfamiliar or obsolete session.
3. Change credentials with the relevant identity provider if you suspect compromise.
4. Review community audits for unexpected actions made from your account.

Revoking a session does not rotate a community API key. Manage API credentials separately in Settings → API Keys.

Account and data controlsCopy link to Account and data controls

Only rely on self-service export, erasure, or account-management actions that Clan Labs currently displays as available. Some data-management interfaces are deployment-controlled; this documentation does not promise a control that is hidden in the live dashboard. Contact support for an applicable privacy request when the required self-service action is not presented.

Independent community moderation records or legal retention requirements can still apply after a personal account request. Follow the explanation shown during the supported flow.

Keep the account secureCopy link to Keep the account secure

• Use an individual Discord and Clan Labs account.
• Never share browser sessions, API keys, Roblox cookies, or Open Cloud secrets.
• Re-authenticate only on official Clan Labs, Discord, or Roblox hostnames.
• Remove access promptly when a staff member changes role.
• Preserve timestamps and IDs—not credentials—when reporting suspicious activity.

For API secrets, see Create and manage API keys. Use the Clan Labs support server for a privacy request that cannot be completed through Clan Labs.