01Data
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.
02Drafts, 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.
03AI 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.
04Call 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.
05Access 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.
06Contracts
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.