Trust

Your data, your customers, your rules.

The questions a data protection officer, a works council or an IT lead asks before a pilot, answered the way we answer them in writing. Salesteq is a Swiss company in Zug.

Where your data lives

Servers and data storage in Finland, inside the EU. Notifications to customers are sent from the EU. Language models run under standard contractual clauses.

No subprocessor uses your content to train its models. Your conversations are not used to train third party models. Anonymised evaluation to improve the service is governed by the processing agreement, with a right to object.

Where a channel adds a processor, for example WhatsApp adds Meta, it is named in the subprocessor list you receive with the agreement.

What we sign

A data processing agreement under Art. 28 GDPR, with the technical and organisational measures and the list of subprocessors as annexes. We provide it before the first conversation runs.

Requests from data subjects are forwarded to you without delay, and we deliver the information, the export or the deletion for that person from the system.

We deliver the paragraph for your privacy notice: purpose, data, recipients, retention, rights.

Retention and deletion

Conversations and leads are kept for twelve months, leads for six months after handover into your CRM, visitor data for six months, logs for thirty days, backups for at most thirty days beyond that. At the end of the contract, return and deletion within thirty days.

You can set other periods. They only need to be defined and tied to a purpose.

Consent

The chat sets no cookie and stores nothing in the browser before it is opened. When the visitor opens it, only the chat session id is stored so the conversation continues across pages. No consent banner is required for that.

The assistant answers messages customers send you. On its own it only writes to customers whose consent is on file, with approved templates.

A customer who leaves a request receives a confirmation of that request, and nothing else.

What the assistant may and may not say

It names only what is in your data. Prices, availability and opening hours come from your systems, never from the model. Binding commitments, appointments and prices are always confirmed by a member of your team, and the assistant says so to the customer.

It shows your total price including VAT as you publish it. It does not invent discounts, savings or financing conditions; for financing it points to your advisers. For new cars it states consumption, CO2 emissions and CO2 class with the first mention of engine or price.

It shows only your own content: your photos, your texts, your vehicle data.

Human oversight

The customer sees that they are talking to an AI, and sees the person when a handover happens. A customer facing sales assistant is not a high risk system under the EU AI Act; a short briefing of your staff on takeover and limits is part of onboarding.

Your team can take over any conversation at any moment, with the full context. The inbox shows who took over and when. Which evaluations you allow on top of that is your decision; performance statistics per employee are switched on only on your instruction.

Every conversation, booking and handover is recorded and reviewable. Your team sees what the assistant did and why.

Security

Transport encryption, keys encrypted at rest, tenant isolation in the data layer, access only for named people, daily backups. The measures are listed in the annex to the agreement.

We hold no certification. We disclose the measures and have them reviewed.

The chat can be operated by keyboard and is labelled for screen readers.

Questions on any of this go to [email protected].

Book a call