Privacy Policy

Ametrix is built for Discord and Roblox RP communities. This policy explains which data the beta service processes, why it is needed and how verified requests are handled.

Last updated: July 19, 2026

Data we process

Discord identifiers, usernames, avatars and server membership information needed for sign-in, workspace discovery and permission checks.
Workspace configuration such as channels, roles, application questions, ticket settings, verification rules, staff access roles and enabled modules.
Application submissions, ticket metadata and transcripts, moderation decisions, dashboard actions, configuration history and audit logs created through Ametrix.
Roblox usernames, user IDs and optional group/rank information when a workspace enables Roblox verification.
Limited technical information needed for security and reliability, such as timestamps, request outcomes, error details and process health. We do not intentionally store passwords for Discord or Roblox.

Why we use data

To provide applications, tickets, Roblox verification, staff access, analytics, logs and workspace configuration.
To authenticate users, enforce owner/staff permissions and prevent one workspace from accessing another workspace's data.
To investigate bugs and abuse, maintain service reliability, enforce beta limits and support testers.
To communicate operational or security information when contact details are provided to support.

Service providers and data sharing

Ametrix relies on Discord for authentication and bot functionality, Roblox APIs for optional verification, Supabase for hosted database/storage services, and the hosting provider used to run the web and bot processes.
Data is shared with these providers only as needed to operate the configured feature or infrastructure.
Ametrix does not sell personal data. Payment processing is not enabled in the public beta, so Ametrix does not intentionally collect card details.
Information may be disclosed when required to protect users, investigate abuse or comply with a valid legal obligation.

Retention and deletion

Retention depends on the module, workspace plan and server-owner configuration. Some operational logs and transcript links may have separate retention periods.
Removing the bot does not guarantee that all dashboard records are instantly erased. A verified server owner can request workspace deletion.
Backups and security logs may remain for a limited period after deletion before normal rotation removes them.
Server owners are responsible for deciding how long their community needs applications and ticket content and should avoid collecting unnecessary sensitive information.

Security and access

Dashboard access uses Discord authentication and server-side workspace permission checks. Sensitive service keys are intended to remain only on trusted backend environments.
Signed transcript links should be treated as confidential and shared only with authorized people.
No online service can guarantee absolute security. Suspected exposure or unauthorized access should be reported immediately to security@ametrix.cloud.

Your choices and requests

You may ask for access, correction or deletion of data connected to you or a workspace you control by emailing support@ametrix.cloud. We may request reasonable verification before acting, and some information may be retained where required for security, dispute handling or applicable law. Members may also need to contact their Discord server owner because the owner controls the community form and ticket content.

Beta and policy changes

Ametrix is in public beta. Features, retention settings and infrastructure may change as the product develops. Material changes will be published on this page with a new update date.