Help

Support and security

One contact for product, billing, privacy, and responsible disclosure.

Product and account

Include the account email, project ID, what you expected, what happened, and the approximate time. Use the Work Log or request ID when available.

[email protected]

Billing

Include the charge date, amount, plan, and last four digits only if needed. Never send a full card number, payment-provider key, or webhook secret.

Report a billing issue

Privacy requests

State whether you seek access, correction, export, deletion, restriction, or another privacy right. We may verify account ownership.

Submit a privacy request

Security disclosure

Send a concise impact statement, safe reproduction steps, affected URL or component, and contact details. Do not access other users’ data or disrupt service.

Report a vulnerability

Before contacting support

Refresh the current project status and save the request ID from any structured error.
Export important source before destructive account, project, or database actions.
Do not email passwords, access tokens, API keys, database passwords, private source, or personal data that is not necessary.
For an immediate security concern, disconnect the affected integration, revoke provider access, rotate credentials, and stop active runs before reporting.

Autonomous output

Support can investigate platform behavior but cannot certify generated software as secure, lawful, accessible, or fit for your use. Review and test every material change before deployment.

Response expectations

Support requests are prioritized by security impact, loss of access, active billing harm, and service severity. Admas does not promise a specific response or resolution time unless a written order or service-level agreement says otherwise. Preserve request IDs and exact evidence while avoiding secrets and unnecessary personal data.