| Account and operation | Email, a user code, a display name where chosen, language, and session signals needed to sign in and operate a channel. | No required social sign-in and no sale of this data. This landing page keeps only a language preference locally in the browser. |
| Voice sample | A sensitive mathematical voice representation, extracted on the device, to help bind an account to its person and prevent duplication. | It is not a password or legal identity. An ordinary enrolment sample is not public content. Any optional recording donation for model development must stay separate from enrolment and have its own stated consent and retention period. |
| Private bunker | Sealed bytes and operational data such as size, identifiers, and technical path, so an owner can keep material in a bunker. | Where the bunker feature is enabled, the client seals content before upload. This is not a claim of absolute immunity from every compromise; security review and key-management design are gates before any strong production-privacy claim. |
| Channel and library | Work its maker chooses to publish, plus data required for display, distribution, and abuse prevention. | Public work is not end-to-end private messaging. Do not put something in a channel or public library if it must remain private. |
| Security and logs | Technical data such as operation time, success or failure, and log information required to protect the service and investigate faults or abuse. | We do not yet promise a single retention period. It will be published before public testing and enforced in deletion and export, not only written on a page. |
| Payments | The platform does not collect card or bank-account data through this page or through the sandbox support release today. | When channel support is enabled in the future, bank and card data will enter a licensed payment provider’s hosted flow, with a separate notice explaining that provider’s role and data. |