NetaaqPRE-LAUNCHDRAFT · LEGAL REVIEW PENDING
The local control database stores account name, email, hashed passwords, sessions, language preferences, plan selections, project metadata, usage observations, job records and audit events. The interest form stores email, optional plan and project description. The support form stores email, subject, message and language with a request reference. Customer SQL data stays inside its project instance.
These records support account access, resource ownership, operation recovery, evaluating early interest and reviewing support requests. No external analytics, email delivery or payment processing is configured. The local machine operator can access the control database and Docker resources; do not treat this development setup as a hostile-tenant production boundary.
Everything is stored on the local computer. Customer connection secrets and backup archives are encrypted with environment-supplied keys. Account password hashing and session handling belong to Better Auth. Local HTTP and loopback PostgreSQL connections do not provide production TLS. Protect the computer, environment files and recovery keys.
Interest submissions expire after 180 days while the worker runs. Support requests remain locally until removed by the operator; automatic support retention is not configured. Sessions expire under the authentication policy; audit and usage records expire after 90 days. Backups use the plan’s 7- or 14-day retention, enforced while the worker is available. Project deletion removes the instance and data volume; retained backups expire on their recorded date unless explicit purge is selected. Account removal is an operator-assisted local procedure described in the runbook. No deletion of offline copies can be guaranteed.
This is a development privacy draft, not a claim of PDPL compliance. Legal entity, privacy contact, jurisdiction, production subprocessors and legal review are pending before any hosted launch. No contact details have been invented.