Your account, payment, and data — kept safe

Sign in with an email code; balance lands after payment is confirmed. Never email login codes, full card numbers, or private secrets.

ClaudeUpublic trust
Sign-inOne-time email code
Mail anti-spoofingSPF / DKIM / DMARC
Support mailboxhello@claudeu.com

Sign-in

Email code

No extra password to manage.

Payment

Credited after confirmation

Balance lands once payment is confirmed.

Your conversations

Not kept as billing detail

Usage shows only time, model, usage, and debit.

The basics that keep you safe

A few rules that protect your account, payments, and support chats.

Email-code sign-in

Sign-in uses a one-time code. Enter it only on ClaudeU pages and never forward it to anyone.

  • One-time code
  • Resend after expiry
  • Never forward codes

Desktop authorization

After the web account is confirmed, Desktop can continue with that account. Logout or re-authorization follows the current session state.

  • Confirm account
  • Authorize local app
  • Sign in again when needed

Payment and balance

After payment confirmation, balance credits the current account. Orders and usage show related changes.

  • Order records
  • Balance records
  • Usage records

Conversation content

Billing details do not store raw questions and answers. They show only the usage information needed for review.

  • Request ID
  • Model and time
  • Usage and debit

Domain mail anti-spoofing

SPF limits sender sources, DKIM signs mail, and DMARC connects validation results to domain policy to reduce impersonation risk.

  • SPF
  • DKIM
  • DMARC

Sensitive-data boundary

Support does not need login codes, full payment card details, private secrets, or sensitive raw conversation content.

  • No login codes
  • No full card numbers
  • No private secrets

If something looks off

Secure your account first, then contact support with the order or page state.

  1. 01

    Suspicious mail

    Forward suspicious mail to support

    Forward suspicious ClaudeU mail to hello@claudeu.com for review. Do not reply with login codes, full card details, or private secrets.

  2. 02

    Account issue

    Sign in again and check the current account

    If authorization or balance looks wrong, first confirm the signed-in email, then review orders, balance, and usage in the user center.

  3. 03

    Payment issue

    Keep the order ID

    Do not duplicate a pending payment. Keep the order ID, payment time, and current status, then contact support.

ClaudeU