PRIVACY
Data practices, without invented legal claims.
This implementation allows users to create private company workspaces with email and password. Production operators must complete a jurisdiction-specific legal review before accepting sensitive client data.
Data handled in this build
Registration stores name, email, company name, country and optional sector. Password credentials are stored as secure hashes by the authentication service, with session records. Company records are tenant-scoped.
Development email and storage
Email verification is temporarily disabled because email delivery is not configured. Password reset links still require working email delivery. Production requires verified email, managed encryption, retention rules, processor terms and an approved data region.
Your choices
Do not submit real client or sensitive personal data to a development deployment. The production owner must publish verified contact, retention, lawful-basis, transfer and data-rights information after legal review.
See the method in a working workspace.
Explore real calculation flows using isolated synthetic data.