Skip to content

What protects your archive

Specific controls, and the gaps named beside them.

Controls as checked on 11 August 2026. The signed data processing agreement is binding.

Last updated

  1. 01One organization cannot see another
  2. 02Reads are recorded, not only changes
  3. 03Sessions stay on the backend
  4. 04Where the data sits
  5. 05Who else touches it
  6. 06You hear when collection breaks
  7. 07Losing your only owner
  8. 08What we do not claim

One organization cannot see another

Data is isolated per organization, and every query carries that scope.

Why?

Nothing is aggregated across customers: no cross-customer benchmark, no shared index, no pooled model of anybody's behaviour. This website measures its own pages only if a visitor allows it, and has no path to any archive.

Reads are recorded, not only changes

A read of message content goes into your audit log, AI answers included.

Why?

A trail of changes alone cannot tell you who looked. We do not claim the log covers everything a system does; we claim that access to your messages is in it.

Sessions stay on the backend

The Telegram session is encrypted on our side and never handed to a device.

Why?

That is why the company can end a grant without asking for a handset back. The person working the account authorizes a device from a link; the session never leaves.

Where the data sits

A European region. Transactional email metadata is the one exception, stored in the United States.

Why?

The region is on DigitalOcean, a United States provider, so the transfer relies on Standard Contractual Clauses and a transfer impact assessment. Media is encrypted under your organization's own key before it is written. Our email provider stores account data, email metadata, logs and API records in the United States whatever the sending region: recipient addresses, subject lines, timestamps and delivery events. Message content never crosses, and that is a rule in the system, not a policy preference.

Who else touches it

Number supply, model providers, hosting and email. Your agreement's annex names each one.

Why?

Number and SMS supply for provisioned accounts. Model providers, on no-training terms, for the message content the AI features you use send them. The hosting provider, for compute, the database and file storage. The transactional email provider, for the alerts. The dated annex is available on request, and adding to it requires notice under the agreement.

You hear when collection breaks

Every active owner is mailed within hours. There is nothing to configure.

Why?

Collection stopped, needs re-authorization and blocked are mailed from the day the organization is created. Our session shows in that account's Telegram devices as Nicegram Business, and one tap there ends it; we say so before you connect, detect the termination and alert every owner. Messages that arrived while our session was gone are not recovered, and no alert changes that: the honest shape of a product built on somebody else's platform.

Losing your only owner

We restore access by hand, checked against your agreement and written to your log.

Why?

It runs under dual control: one person approves, another executes. It is slow, not self service, and we quote no turnaround. Restoring an owner grants a role and opens no archive; access follows the roles you set. A second owner at setup means you never need it.

What we do not claim

We hold no security certification and display no badge for one.

Why?

The data protection impact assessment runs alongside the first outside accounts and gates general availability, so a finding can force a change to something already built.

Security questions, or something that looks wrong: contact@nicegram.ai

The page written to the people whose accounts you connect

Check it against your diligence

Thirty minutes with a person. A reply within one working day.