DATA

Every agent has an identity, permissions and a log

An AI agent that calls a customer and reads their work order history has access to the same things a BDC employee does. We treat it the same way: it has its own identity, it has a scope of permissions, and everything it did stays in the log.

The group management can see which agent reached for which data, when, and what it did with it.

Least privilege

An agent gets access only to what it needs in its role. The CRM Controller reads, it does not write. The Prospector sees service work orders, it does not see invoicing.

Permissions are set per group, per site and per role.

Action log

Every query, every recommendation and every customer contact is recorded with the time, the agent and the data source.

Available to the group administrator and for audit.

Isolation per group

The data of one dealer group never touches the data of another. Separate keys, separate backups.

How the separation works is described in the processing agreement.

GDPR in the contract, not in a statement

The processing agreement is an annex to the master agreement. Data retention, processing subcontractors and how data is deleted when the cooperation ends are all written into it.

Call recordings are processed under the monitoring regime of art. 22³ of the Polish Labour Code, with notice to the staff.

SPECIFICS

Data encrypted at rest and in transit

Read-only access to dealer systems everywhere a module does not need to write

Company-account sign-in with SSO and MFA for users of Sufler and Sufler Connect

Retention of recordings and transcripts as agreed in the SOW

Security testing before every major release

WHAT WE DO NOT DO

We do not join data across groups.

We do not give an agent access that a human in the same position would not have.

Security lives in the contract, in the permissions and in the log. Not in a tab on a website.

Ask for the DPA and the architecture description How we roll out