This page describes how Relia currently works. It is product documentation, not legal advice, and has not been reviewed by counsel.
Privacy
Last updated 10 September 2026.
What Relia stores
Relia stores the account you create (name, email, password hash) and the workspace data you add: organizations, memberships, accounts, contacts, timeline events, risks, opportunities, commitments, tasks, documents, search chunks, and AI usage events.
Relia does not receive or store card numbers. When Stripe is configured, Checkout and the Customer Portal run on Stripe-hosted pages. Relia stores plan, subscription status, and Stripe identifiers returned by webhooks.
How data is used
- Your workspace — to provide the product: CRM, timeline, intelligence, dashboard, and collaboration.
- Optional language models — if an OpenAI or Anthropic key is configured on the server, interaction text and retrieved chunks are sent to that provider to polish briefs or answers. Without keys, Relia assembles output only from stored records.
- Optional embeddings — if an OpenAI key is configured, text is embedded for retrieval. Otherwise Relia uses a local hashing embedder.
- Stripe — only if you start a paid checkout; Relia never sees the raw card.
Tenancy and access
Business rows are scoped by organization. The API filters by the signed-in workspace. Production Postgres policies (row-level security) repeat that rule. Members cannot read another organization’s accounts. Sessions use an HttpOnly cookie. Service-role, Stripe secret, and model keys are not exposed to the browser.
What Relia does not do
Relia does not currently offer a single “download all my data” or “delete my entire account” button covering every workspace at once. Account records and timeline events can be managed from the authenticated application according to your role. Relia does not claim SOC 2, ISO 27001, HIPAA, or GDPR certification on this site.