KNOW WHAT IS STORED

Privacy and data

Understand the records, their purpose and available controls.

2026-11-17 / LOCAL EDITION
01

Scope

This notice covers local use and production-mode rehearsals with external channels disabled. The planned operator is 幸会新知科技(深圳)有限公司. Actual contact channels and processing rules will be published before public service.

We are responsible for our system’s data handling, security and operations. Customers using results in their businesses must also meet applicable data-processing obligations.

02

Accounts and security

The system stores names, email addresses and password hashes, and uses session cookies for sign-in. Customer keys are shown when created or rotated; the server retains digests, prefixes, permissions, expiry and management information.

Authentication, rate limiting and security checks process necessary network identifiers and activity. Do not paste passwords or full keys into public code, URLs, tickets or free-text fields.

03

Business records

The database stores test orders, metering entries, usage, receipts, tasks, tickets and notifications for history, diagnosis and reconciliation. Parameters, results and tickets may contain information you submit. Provide only what the task needs.

Some business reports can be exported. They are not a complete copy of all personal data. Signing out or revoking a key does not delete historical records.

04

External services and email

The current safe mode disables live suppliers, production payments and external email. Local previews test email flows; they do not prove delivery or address ownership. Historical request or delivery records do not imply a channel is enabled now.

Before enabling an external service, its recipients, required parameters, purposes and rules must be explained. An integration or configured account does not replace checks of data rights and supplier permission.

05

Retention, backups and removal

Persistent records currently remain until explicitly cleared. There is no universal fixed-day deletion schedule for all results and parameters. Backups may retain earlier records; removal must account for the active database, backups and relevant copies.

There is no self-service account closure or one-click permanent deletion of all data. Signed-in users may request help with access, correction or removal through tickets. Handling and required retention depend on actual storage and applicable duties.

06

Content and rights concerns

For privacy, copyright or other concerns, use the Other category in account tickets. Include the platform, a content link or identifier, the basis of your concern and requested action. Do not submit unrelated identity documents, passwords or keys.

Tickets require sign-in. A public channel for people without accounts and automatic deletion across systems are not configured. Stop unnecessary use and sharing of disputed content rather than gathering more to demonstrate a concern.

Understand the service and your choices.Help and support →