Data residency and storage

This article covers where HelmXP stores your data, for how long, and what happens to it when you cancel.

Data residency

All HelmXP infrastructure runs in AWS US-East-1 (Northern Virginia). There is no option to choose a different AWS region at this time.

Data does not leave the United States. The Anthropic Claude API calls made during AI drafting are subject to Anthropic's data handling terms; Anthropic processes API requests in the United States and does not use API data for model training.

What data HelmXP stores

HelmXP does not store credit card numbers. Payment data is held by Stripe and subject to Stripe's PCI DSS compliance.

Retention

The 7-year Logbook retention is a default. You cannot configure a shorter retention period. You can export the Logbook at any time in JSON format from your Hub's admin section.

Data export

You can export all of your Hub's data at any time. The export includes:

• All briefings and sections (JSON and PDF)
• All audit Logbook entries (JSON)
• All uploaded data files (original format)
• Seat and Sub-seat profiles (JSON)

Exports are produced on demand and delivered to your CEO Seat's email address as a download link. Large exports may take up to 30 minutes to generate.

Data deletion on cancellation

When you cancel your HelmXP subscription:

1. Your Hub enters a 90-day grace period. Data is retained and accessible during this period.
2. At the end of the grace period, a deletion notice is sent to the CEO Seat email address.
3. Seven days after the deletion notice, your Hub's data is hard-deleted from the database and from S3.
4. Logbook entries are retained for 7 years from the date of the original entry, even after Hub deletion, in an anonymized archive for legal hold purposes.

If you reactivate your subscription within the 90-day grace period, your data and Hub configuration are fully restored.

AI-generated content and your data

The Anthropic Claude API receives excerpts of your uploaded data files as context for AI drafting. These excerpts:

• Are sent over TLS 1.3
• Are not retained by Anthropic beyond the API call
• Are not used by Anthropic to train models
• Are scoped to your Hub's data only — no data from another Hub is included in your prompts

See Anthropic's API data usage policy at anthropic.com/legal/privacy for the full terms.

See also

• [[helmxp-security-overview]] — security architecture overview
• [[how-your-hubs-data-is-isolated]] — tenant isolation at database and storage layers
• [[managing-your-subscription]] — billing, invoices, and cancellation