Security & Data Architecture

For clinicians, coaches, HR teams, and enterprise IT · Last updated:
The one-paragraph summary: The text a user decodes or imports, and the structured analysis of it, are stored only in that user's private vault so future analyses remember the relationship. Data is stored in Google Firebase (EU), protected by per-user Firebase security rules, deletable by the user at any time, and never used to train AI models. Shared professional profiles are explicitly user-created, read-only, contain no raw messages, and are revocable at any time.

1. What Is Stored — And What Is Not

Data type Stored? Where
Message text you decode or import✓ YesFirebase — your private vault (decode history + imported-conversation excerpts + derived summaries), so future analyses remember the relationship; visible only to you; deletable anytime
Analysis result (EQ score, flags, headline)✓ YesFirebase — user's private vault, ~2 KB/entry
Relationship context (relationship 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 ever feed their EQ profile, their stats, or anything they share — never the other person's. When a message exchange is analysed, the derived EQ signals describe the behaviour of the person using the app. If a user imports a conversation, its text (both sides) is stored as private memory in their own vault so future analyses have context — it is never shared, never surfaced to anyone else, and never mixed into another user's data.

This means a clinician viewing a shared profile sees their client's communication tendencies — not raw conversations or 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 the Google Gemini API (paid tier). The message text is transmitted to Google's servers solely to generate the analysis; under the Gemini API paid-tier terms Google does not use it to train or improve its models, and may retain it only briefly for abuse monitoring under those terms. ALYGN's AI layer keeps nothing beyond producing the response. Conversations the user imports (a chat export, a pasted email exchange, or an email they forward to their personal ALYGN import address) are processed the same way and only at the user's request. The result and the analysed text are then stored in the user's own private Firebase vault — the decoded text becomes their history, and imported-conversation excerpts become private memory so future analyses remember the relationship. This data lives only in the user's space, is visible only to them, and is deletable at any time (see §7).

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 of Service Security & Data Architecture