Built to be answerable.

When an institution brings its relationships and money into one place, trust has to be built into the record.

A shared obligation.

Under India’s Digital Personal Data Protection Act, 2023, compliance is shared. This page describes our architecture. It is not legal advice, and it makes no certification claim.

How Atrium is built.

Who can see what

Tenant isolation
Every organisation’s tables carry its id and are protected by row-level security. An automated test fails if a table is left uncovered.
Access
A new object or field is invisible to members until granted. Access follows profiles, permission sets, the role hierarchy and sharing rules.
Field-level security
Hidden fields are left out of every read, and a filter or sort that names one is refused.

Personal details

Masking
Mobiles and emails are masked in lists, records and exports. Each reveal is logged and chained into the audit log.
Consent
WhatsApp, SMS and email each hold their own consent state. A marketing template needs an opt-in, and a STOP reply opts the person out.

People’s rights

Requests
Access, correction and erasure requests are tracked from received to done, with a due date 30 days after receipt.
Erasure
A verified erasure deletes the record with its activities, tasks and history, and masks the matching values in the audit log.

The record of what happened

Audit
A hash-chained log for each organisation, kept for seven years, that can verify itself.
Field history
Tracked changes are kept for as long as their record.

A log that checks itself.

Each change is chained to the one before, and Atrium verifies that nothing was changed or removed.

A real Atrium screen. Meridian Institute is fictional, and every record is sample data.

Hosted in Mumbai.

Atrium’s web application and API run in Vercel’s Mumbai region. The database runs on Supabase in AWS Mumbai (ap-south-1).

Security headers are set on the web application and API. API requests are rate limited per person, and personal data is kept out of logs and URLs.

What leaves Atrium.

An honest description of how the assistant works today.

Janus takes its facts from Atrium’s API, limited to what the person asking may see. To understand a question and word the answer, Janus sends the question and those facts to a third-party AI model provider, which may process them outside India.

Those facts can include figures, stages, amounts and people’s names. Phone numbers and emails are not included, and staff are never identified by email. Janus can’t carry out an action by itself.

The AI providers and the terms that apply are confirmed with each deployment.

Your side of the line.

  • Give notice and obtain consentBefore personal data goes into Atrium
  • Set access deliberatelyDecide who holds which profile and permission
  • Answer data requestsAtrium tracks them, and your team verifies and decides
  • Take care with children’s dataYour legal counsel should review any such use
The Atrium glass canopyFour equal panes of tinted glass holding the four wings of Atrium.

Bring your questions.

Ask to see roles, sharing, masking and the audit log during your deployment discussion.