Trust

What a system may do, and what it may never do.

The rules every system we build runs under: where the data stays, who presses send, how customers are told about the assistant, and what access we hold. In plain words; the legal version is in the privacy policy.

01

Data

A system reads only what it needs to answer: the message, the customer record, the calendar slot, the price list. It runs on accounts in your name, so the data stays where it already is. We do not copy your customer base to our servers, and we do not use your conversations to train anything.

02

Drafts, not sends

By default the system prepares replies and a person approves them. Sending on its own is switched off unless you decide otherwise for a specific process, in writing, and even then money questions, complaints and anything unclear stop at a person.

03

AI disclosure

People you message are told when a reply comes from an assistant, in the first message of a conversation and again if they ask. Where the law requires a label, it is there. Pretending an assistant is a person is not something we build.

04

Call recording

Calls are recorded only with a notice at the start that names the reason and how long the recording is kept. Transcripts serve the reply and the customer record; they are deleted on the schedule agreed with you, and the notice text is yours to approve.

05

Access and keys

We ask for the narrowest access that lets the work happen: read-only where reading is enough, a separate user we can be removed from, keys that you can revoke at any time. Access is listed in the quote, and it ends with the project unless you keep us on.

06

Contracts

Every project runs on a written contract with the scope, the price and the data rules above. A data processing agreement is available on request; for Polish companies we can work under KSeF invoicing, confirmed by your accountant.

These texts describe how we work today. Before the site moves to its final domain they are reviewed by a lawyer; the contract you sign is the binding version.

Questions

Questions people ask about data and control

Do you store our customers’ messages?

No, not on our side. The system reads messages inside your accounts to draft a reply and to update the record you already keep. What is stored, and for how long, stays under your rules; we do not keep a copy.

Can the system send anything without a person?

Only if you switch that on for a named process, in writing. The default is drafts. Even with sending enabled, money questions, complaints and anything it cannot classify go to a person with a summary.

Are customers told they are talking to an assistant?

Yes, in the first message of a conversation and whenever they ask. It is part of every system we build and it is written into the rules you receive at handover.

What access do you need, and can we revoke it?

The narrowest that lets the work happen: a separate user or key per tool, read-only where possible, listed in the quote. You can revoke any of it at any time; at handover we ask you to.

Want the rules in your contract?

Tell us what the system should never do. We write it in before the work starts.