Data Export & Deletion

Authenticated account holders can request a JSON export or account deletion in Settings > Privacy & data. Sign in to access the controls. Export and deletion actions require an explicit confirmation and are scoped to the requesting account. This public page cannot request deletion or access a private account.

1. Account export scope

The export control returns JSON about inventoried account data and reports its included categories, excluded categories, workspace scope, and whether the result is complete. It excludes credentials, access tokens, ciphertext, another person's personal mailbox/vault material, and data the Service cannot safely map to the requesting account. It is not an export from a connected provider and does not prove that all provider-held data has been included.

2. Account deletion and blockers

Requesting deletion records an authenticated, durable request. A shared workspace or venture is not deleted just because one member asks to delete their account. Ownership transfers, permissions, other users' content, an active subscription, or another lawful restriction may first need resolution. Where a request is blocked, its status identifies what needs attention. Eligible cleanup is limited to inventoried application categories with verified account-owner scope; shared venture content, unresolved ownership, unknown records, and unsupported provider cleanup are preserved for review or manual action, not swept up by a generic account-wide delete.

After preflight clears, the Service may set a 30-day target for staged cleanup of supported, verified in-scope data. That is a target, not an absolute promise of deletion from every outside provider, backup, or legally retained record. The worker stops for review if inventory, ownership, upstream provider revocation, or local deletion cannot be verified. Legal evidence and shared-workspace records may remain under separate retention rules. An applicable legal deadline controls where it differs. A privacy-status page reports the stage, update time, and generic next steps without revealing a person's account identity.

3. Provider disconnect is not account deletion

Use the authenticated Settings > Privacy & data list to disconnect a supported account. It distinguishes local credential/access removal from provider-side revocation, data removal, or a manual provider action. If no verified provider deletion method exists, the status can remain incomplete, blocked, or require manual action. A general sign-out or a connector's normal Disconnect button does not imply that historic application records were erased.

4. Consent and policy history

Settings > Privacy & data also provides the supported account's recorded cookie/analytics choices, Text ATLAS consent history where present, and DPA acceptance receipts for authorized workspace administrators. A browser preference remains local to that browser; do not infer that it covers another device, user, connected provider, or older consent event not in the receipt.

5. Meta user-data deletion callback

When the Meta callback is configured and verifies a signed request, Meta may redirect the person to the public data-deletion status page using an opaque confirmation code. If callback configuration is unavailable, the callback cannot record a request; contact privacy@axiomhelm.com. A verified request is recorded for review, but an app-scoped Meta identifier is not automatically linked to an Axiom Helm account. If no independently verified account link exists, the status remains in assistance/review and no unrelated person's account is selected or deleted. The status view does not display account, email, phone, or external provider subject identifiers, and does not claim external deletion is complete.

If the public status code is missing, expired, or invalid, contact privacy@axiomhelm.com. Do not send another person's code or authentication credentials.

6. Request help

Use the authenticated Settings > Privacy & data controls or email privacy@axiomhelm.com. Privacy requests may require verification and scope clarification. We retain information required for billing, security, legal compliance, or the rights of other users where permitted by law.

Sign in to use private account controls. Public legal notice: the general page is not a substitute for an authenticated request receipt.