BeiGe Privacy Policy

Last updated: 2026-05-14

1. Data collection

The current version displays demo account data, wallet placeholders, billing records, products, and support entries. Authentication data is stored locally for the development database flow, while payments, wallets, support, and news remain mock or reserved.

2. Future data processing

Future phases may process account profiles, email verification records, login records, wallet binding addresses, product orders, billing records, support conversations, notification status, operation logs, security logs, and upload metadata.

3. Security measures

The codebase reserves password hashing, captcha, login failure limits, sessions, admin permissions, operation logs, security logs, error logs, upload limits, and configuration models for future security hardening.

4. Third-party services

The current phase does not connect real Telegram APIs, email services, wallet SDKs, chain listeners, payment callbacks, or news APIs. Future third-party integrations should clearly document providers, purpose, and data scope.

5. Retention and deletion

Prisma models reserve deletedAt fields for soft deletion and metadata fields for extension. Production retention periods should be defined according to business and legal requirements.

6. Contact

Privacy questions may use the demo support email support@beige.ai. This address is mock configuration and may later be maintained from the admin support settings.