Security & Data Architecture

For clinicians, coaches, HR teams, and enterprise IT · June 2026
The one-paragraph summary: ALYGN never stores the raw messages your users type. Only structured analysis outputs (a few KB of JSON per decode) reach our servers. Data is stored in Google Firebase (EU), protected by per-user Firebase security rules, and never used to train AI models. Shared professional profiles are explicitly user-created, read-only, and revocable at any time.

1. What Is Stored — And What Is Not

Data type Stored? Where
Raw message text✗ NeverSent to AI, immediately discarded
Analysis result (EQ score, flags, headline)✓ YesFirebase — user's private vault, ~2 KB/entry
Relationship context (nest goal, contact name)✓ YesFirebase — private to that user's UID
Chat context scan (aggregated patterns from export)✓ YesFirebase — private to that user's UID
Shared professional profile✓ If createdFirebase — read-only token, user-revocable
Email / name✓ If providedFirebase Auth — optional, account recovery only
Wearable health data (HRV, sleep, cycle)✓ If connectedFirebase — private to that user's UID, encrypted
Usage analytics✓ AnonymousPostHog EU cloud — no PII, no message content

2. The 50% Rule

ALYGN is designed around a core privacy principle: only the user's own patterns are ever stored or shared, never the other person's data. When a message exchange is analysed, the AI extracts only the communication behaviour of the person using the app. The other person's identity, content, and patterns are not stored anywhere in the system.

This means a clinician viewing a shared profile sees their client's communication tendencies — not a record of conversations with named third parties.

3. Authentication Model

ALYGN uses Firebase Anonymous Authentication by default — no email or login required. Each device receives a random UID (e.g. uid_7f3a...) which is used as the partition key for all stored data. Users can optionally link an email or Google account to persist their data across devices.

Firebase security rules ensure that each user can only read and write to their own data path (/userVaults/{uid}/*). Server-side rules are enforced at the database level, not just at the client — a compromised client cannot access another user's vault.

4. Professional Shared Profiles

When a user chooses to share a profile with a clinician or coach, they:

Share tokens expire automatically after 90 days. The token contains only the aggregated profile snapshot — no raw messages, no third-party names, no full conversation history.

5. AI Processing

Message analysis is performed via Anthropic Claude API (claude-haiku-4-5-20251001). The raw message text is transmitted to Anthropic's servers solely for the purpose of generating an EQ analysis, and is not retained by Anthropic under our API agreement (zero data retention). The structured result (flags, scores, headline) is returned to the app and stored in the user's Firebase vault. The raw text is never written to any database.

ALYGN does not use your data to train any AI models, and will not do so without explicit opt-in consent.

6. Infrastructure

7. Data Retention & Deletion

User data is retained as long as the account is active. Users can delete their account and all associated data from Settings → Delete account. Deletion is permanent and propagates to Firebase within 24 hours. Shared profile tokens are also deleted on account deletion.

Anonymous accounts (no linked email) that have been inactive for 12 months may be purged automatically.

8. Compliance

ALYGN is designed to be compatible with GDPR requirements for EU users. We act as data controller for user vault data and data processor for any data shared in professional contexts. Data Processing Agreements (DPAs) for enterprise and clinical deployments are available on request at legal@alygn.me.

ALYGN is a self-reflection and communication tool, not a medical device (not classified as SaMD under EU MDR / FDA). It does not generate clinical diagnoses and should not be used as the sole basis for clinical decision-making.

9. Incident Response

In the event of a data breach affecting personal data, we will notify affected users and relevant supervisory authorities within 72 hours as required by GDPR Article 33. Security issues can be reported to security@alygn.me.

10. Enterprise & Clinical Deployment

For organisations deploying ALYGN across teams or clinical practices, we offer:

Contact enterprise@alygn.me to discuss your requirements.

Questions? Contact security@alygn.me for technical security questions or legal@alygn.me for compliance and DPA requests.
← Back to ALYGN Privacy Policy Terms Security