AtmoShaper may handle account, authentication, role, profile, membership, billing metadata, calendar, booking, support, diagnostics, app preference, education progress, and client-owned wellness self-tracking information.

Stripe handles payment processing. AtmoShaper does not intentionally store full payment card numbers.

AtmoShaper does not sell user data and does not use advertising, ad targeting, marketing retargeting, or ad personalization to fund the project.

The current funding posture is paid memberships, optional one-time support, and product revenue so development can proceed without selling user attention or user data.

SOAP notes, intake forms, journals, therapist ROM sessions, body maps, and related therapist professional-record content stay in the user's encrypted browser vault during this alpha unless future hosted clinical storage passes documented compliance gates.

The local vault passphrase is not sent to AtmoShaper. Encrypted local storage and exports do not replace device security, backups, staff policies, or professional recordkeeping obligations.

Signed-in wellness entries are client-owned self-tracking records. They are separate from therapist professional records and are not diagnosis, emergency monitoring, medical advice, or automatic therapist-facing data.

Anonymous wellness practice flows run in browser memory only unless the user signs in and saves entries.

AtmoShaper uses privacy-scrubbed diagnostics to improve reliability. Diagnostic and support paths should not include client PHI, clinical notes, or sensitive professional-record content.

Support requests should avoid client-identifying health information or sensitive clinical details.

Users may use direct export tools where available, such as wellness exports and local vault exports. Broader account export and account deletion request workflows are planned separately.

Some records may need to be retained when legally, professionally, operationally, security, payment, dispute, or audit needs require it.