Skip to main content
iCall
ქართული
Contact us

Security and trust

Your customers' calls stay under your control

The database is in the EU, access is governed by roles and an audit log, and the assistant introduces itself as an AI. We do not claim certifications, and what we cannot prove is stated plainly.

Request the 7-day trial

Trial: 7 days and 60 minutes, with no card. It starts at your first test call from your phone

A call is personal data

  • A voice and a name are personal information

    Calls often carry names, phone numbers and details about health or an order. Protecting them is your business's responsibility.

  • Where does the data go in an AI service?

    Many services do not say where data is stored and who sees it. A buyer should know this before signing.

  • Callers should know who they are talking to

    Nobody should discover late that they were talking to a machine. That impression erodes trust.

How data is protected along the call

  1. Step 1

    During the call

    The assistant introduces itself as an AI assistant and answers only from information you allowed. Personal details are never given out just because a phone number matches.

  2. Step 2

    After the call

    Data is kept in your company's own space. Access is governed by roles, and key changes are written to an audit log.

  3. Step 3

    Review

    Each call shows on the call page with its transcript and the actions taken, so your team can check everything.

What we do, and where each stands

Every line carries a status.

  • Data location

    What we do
    The database and storage for accounts, calls, and transcripts are in the EU, in Frankfurt.
    Status
    Database and storage in the EU

  • Encryption

    What we do
    TLS on the web and API and platform-level encryption of the database and storage.
    Status
    Platform-level on web and database; phone line encryption depends on the carrier

  • Access and roles

    What we do
    Each company has its own space, enforced by database-level rules. Team members have roles. KCall support sees nothing by default.
    Status
    Built at database level and covered by tests

  • Access audit

    What we do
    Key changes and every access grant are written to an audit log. The log is append-only: it cannot be edited or deleted.
    Status
    Built at database level and covered by tests; not yet used with real data

  • Support access

    What we do
    The KCall team sees company data only through time-limited access, for 30 days at most. The access can be granted by you or by a platform administrator who has signed in with a second factor (MFA). Every grant is written to the audit log and records who granted it. You can revoke it at any time.
    Status
    Built at database level and covered by tests; not yet used with real data

  • AI disclosure

    What we do
    The assistant opens the call by introducing itself: "Hello, I am this business's AI assistant". It never claims to be a person.
    Status
    Built into the assistant scenarios

We do not claim certifications such as ISO 27001 or SOC 2 yet.

You decide who sees what

Team members have roles, and KCall support sees nothing by default.

  • Roles decide who sees calls and who changes settings
  • Adding and removing a member on one screen
  • Support opens a call only through time-limited access, granted by you or by a platform administrator with MFA
  • Every access grant is written to the audit log

Plain words about AI

AI is useful, but it can be wrong. That is why the rules are set in advance.

  • The assistant introduces itself as an AI

    The caller knows who they are talking to. The assistant never claims to be a person.

  • It does not invent what it does not know

    If it has no answer, it says it will confirm, then saves the request for your team. Every call stays available for review.

  • No deception

    The terms of use forbid misleading callers.

What we claim

This page describes the architecture and the rules that are built. At database level we have company separation and roles, an append-only audit log and time-limited support access. We do not claim certifications such as ISO 27001 or SOC 2.

Call → Action → Evidence

One access, from request to audit trail. The example uses a fictional company.

  1. Call

    You ask support to review a call

    This call ended wrongly, please take a look

    Your request to KCall support

  2. Action

    Access is limited and time-bound

    • Time-limited access is granted by you or by a platform administrator with MFA, 30 days at most
    • Support opens the call only through that access
    • The grant is written to the audit log
    • When the period ends, access stops by itself
  3. Evidence

    What the audit log shows

    Who
    A support team member
    What
    One call
    When
    19 Oct, 14:20
    Revocation
    You can do it at any time

ExampleDemo data: a fictional company and team member. Access grants are built at database level.

Questions about security

Let's go through your security questions

Send us your questions or questionnaire and we will answer.

Request the 7-day trial

Trial: 7 days and 60 minutes, with no card. It starts at your first test call from your phone

More modules

iCall is one platform: phone lines, knowledge, actions and evidence work together