Skip to content

Accounts, access and data explained

Access, data, agents and cost, answered before the call.

Control

  • What happens when I revoke access?

    The grant ends, the device sign-in ends, and the log names who did it.

    Why?

    What was collected stays with the company: it was never on their device.

  • Can an employee take the account with them?

    They can contest the account itself. The record stays with the company.

    Why?

    Whoever controls the phone number can contest any Telegram account, so holding the account itself is best effort. Conversations and contacts live on our side.

  • Can I move an account to a different person?

    Yes. Transfer moves the same account to the next person. The old grant ends first.

  • What if the session dies while nobody is looking?

    Every active owner gets an email. There is nothing to configure.

    Why?

    Collection stopped, needs re-authorization and blocked are mailed to every active owner from the day the organization is created.

  • Can the employee sign you out?

    Yes, with one tap. Every active owner is mailed within hours.

    Why?

    Our session shows in that account's Telegram devices as Nicegram Business, and we say so before you connect. Messages that arrive while our session is gone are not recovered.

  • What if we lose our only owner?

    Write to us. We restore ownership by hand, checked and logged.

    Why?

    We check against the contact named on your data processing agreement: one of us approves, a second executes, and it goes into your audit log. It is slow, and we quote no turnaround. A second owner at setup means you never need it.

Data

  • What exactly is stored?

    Messages and their metadata, chats, contacts and media. Media is encrypted with your key.

    Why?

    Media is fetched and written to storage beside the messages, encrypted with your organization's own key before it is written.

  • How long is it kept?

    Retention is 30 days. The 90-day import expires 30 days after it lands.

    Why?

    Depth is how far back the first import walks. Retention counts from the import, not from the message.

  • If someone deletes a message in Telegram, is it gone here?

    No. It stays, marked deleted and dated, until retention removes it.

    Why?

    That is a disclosure we owe your counterparties, and we make it before the first account connects.

  • Can a chat be removed from the stored record?

    Not chat by chat. Retention, an erasure request or deleting the organization removes it.

  • Are there limits on what gets stored?

    Yes. Files up to fifty megabytes, by type. A missed file shows as not stored.

    Why?

    A file we could not fetch is marked, never skipped quietly. Every account kind publishes its message and storage ceilings.

  • Where does this stand on GDPR?

    You are the controller; we are the processor. Agreement and consent come first.

    Why?

    A signed agreement, an accurate subprocessor annex and recorded consent from every person whose account is connected come before your first account connects. We hold no certification and display no badge for one. 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.

Agents and models

  • What can our own agent do?

    Read the accounts you allow. On a company account it acts only with your permission.

    Why?

    Any MCP client can connect. Your agent lists those accounts, checks their status and reads their chats. Each agent is off by default, and every read goes into your audit log. It runs on your own model, so it uses none of the included AI.

  • Which model providers are involved?

    Only for the AI features you use, on no-training terms.

    Why?

    Each provider is named in the dated subprocessor annex to your agreement, available on request, before it processes anything.

People and money

  • Is this employee monitoring?

    No. It manages accounts, never people. Each person sees what is held and consents first.

    Why?

    Every managed employee has a transparency screen showing what is collected about them, and their recorded consent comes before any connection. It never ranks or scores a person.

  • Do we have to buy accounts from you?

    No. Connect your own Telegram, adopt an account you own, or buy one.

    Why?

    All three end in the same inventory.

  • What does it cost?

    Per account per month, with AI included. We quote the price in the walkthrough.

    Why?

    Included AI is shared across your company, and connecting your own Telegram is free. One company balance pays for accounts and AI. Per account, never per person: ten people on one account cost what one costs.

  • Will Telegram limit our account?

    It can. A proxy you supply lowers the risk; nothing prevents it.

    Why?

    A long lived account signing in from datacenter egress is a known trigger for Telegram limits, and the cost of that lands on you. We say so before you connect.

  • How is this different from buying Telegram sessions?

    Marketplaces sell a login. Here the company owns the account, its access and its archive.

    Why?

    Session marketplaces give no ownership, archive, offboarding path, consent records or audit trail, and they are the gray market this product is not.

  • How do we start?

    A conversation, a signed data processing agreement, recorded consent, then the first account.

Still deciding?

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