Curent

Privacy Policy

Effective November 6, 2026

What this policy covers

This policy explains how Curent handles information when you use our website, dashboard, Discord bot, verification tools, Curent CAD, ER:LC integrations, economy features, and related services.

Information we process

  • Discord account details such as your user ID, username, avatar, linked servers, roles, and permissions.
  • Roblox account details you choose to connect for verification, including account identifiers and public profile information.
  • Verification API key prefixes and secure key hashes, server scope, request counts, reset times, and Discord-to-Roblox verification mappings.
  • Server configuration, moderation actions, appeals, security events, command activity, logs, and automation settings.
  • Curent Economy balances, transactions, shop purchases, game activity, cooldowns, and anti-abuse records.
  • Curent CAD communities, characters, records, vehicles, licenses, departments, and other content submitted by users.
  • ER:LC server identifiers, API responses, configuration, and activity required to provide connected features.
  • Basic technical information such as timestamps, request information, and diagnostics used to secure and operate Curent.

Billing information

Payments and subscriptions are processed by Stripe. Curent receives identifiers, subscription status, plan details, renewal information, and limited billing information needed to manage access. Curent does not store complete payment card numbers.

How we use information

  • Authenticate users and determine access to servers and dashboard features.
  • Provide moderation, verification, security, logging, economy, CAD, and ER:LC features.
  • Process subscriptions, activate plans, and provide support.
  • Prevent abuse, enforce limits, investigate incidents, and protect Curent and its users.
  • Maintain, troubleshoot, and improve reliability and product performance.

Credentials and connected services

Verification API keys and other service credentials are handled on the server. Verification keys are stored as secure hashes and the complete key is shown only when created. Server owners are responsible for protecting and rotating credentials. Discord, Roblox, ER:LC, Stripe, Vercel, Neon, and other connected providers process information under their own policies.

Sharing

We share information only when needed to operate Curent, complete a requested integration, comply with applicable requirements, protect the service, or work with infrastructure and payment providers. We do not sell personal information.

Retention and deletion

Information is kept while needed to provide Curent, maintain security and audit records, resolve disputes, and meet operational requirements. Server owners can remove managed servers and associated settings from the dashboard. Some records may remain in backups or security logs for a limited period.

Your choices

You can sign out, disconnect linked services, revoke Curent Verification API keys, remove managed servers, stop using Curent, or contact Curent support to ask about account or server data. Subscription controls are available in Settings → Billing. Third-party credentials should be revoked through the provider that issued them.

Security and updates

We use reasonable technical and organizational safeguards, but no online service can guarantee complete security. We may update this policy as Curent changes. The effective date above will show when the latest version took effect.