Compliance

Compliance & confidentiality

You choose, flow by flow, where your data is processed: without AI, with models running on your own servers, or with an external AI provider named in the contract. The choice is settled during scoping, written into the contract, and nothing enters your management software without human validation.

Sovereignty

Where your data is processed

Part of our work involves no artificial intelligence at all; another part needs it. Three modes are available, and they coexist: a sensitive flow can stay at your premises while another one uses an external model.

Without AI

File transfers, checks and calculations: everything follows fixed rules. No data leaves your premises, and the result is always the same.

Local AI

The models run on your own servers or with a European host, with no outbound calls. This is the mode for documents that must not leave your premises under any circumstances.

External AI

For difficult documents, a language model hosted by a third-party provider currently reaches an accuracy that local models do not. In that case: the provider is named in the contract, listed as a sub-processor in the data processing agreement, contractually bound not to retain your data or use it to train its models, and the processing location is disclosed to you.

The choice is yours, and it is reversible. For each flow we write down the mode used and its cost. Moving a flow from external to local processing, or the other way round, is a simple setting, not a rebuild.

GDPR

A processor, never the controller

AEPUR acts as a processor under the GDPR: the customer remains the controller. Our role is to carry out processing on their behalf, within the contractually defined scope.

Access scope defined during scopingDepending on the flows retained: read access to a dedicated mailbox, to a file repository, and/or to tables in your business system. Every access is listed, read-only by default and limited to what is strictly necessary. Never a blanket access to your email or your database.
MinimisationOnly the fields needed by the flow are retained. Original documents are deleted once extraction is validated (about 30 days, adjustable to your own retention policy).
Sub-processorsThe hosting provider and, where applicable, the AI model provider are named in the data processing agreement, together with the processing location. No sub-processor is added without prior notice to you.
SecurityNamed accounts, least-privilege access, full logging of every extraction, correction and validation, encryption of data in transit.
AssistanceWe support the customer in handling data-subject rights (access, rectification, erasure) and, where relevant, for a data protection impact assessment (DPIA).
NotificationAny personal data breach is reported to the customer without undue delay.
Data processing agreement (DPA)A processor agreement template is provided as part of each contract, and discussed during the scoping phase.

AI Act

Regulation (EU) 2024/1689

AEPUR has carried out a classification analysis of its system under the European regulation on artificial intelligence.

Conclusion

System classified as minimal risk

It does not fall into any high-risk category (no automated decisions about natural persons, no HR, credit, biometric or justice processing) and does not involve prohibited practices.

Systematic human validationBefore anything is written into the customer's management software, someone validates. The system decides nothing on its own: it prepares the data.
TransparencyIf a conversational component is added later, it will explicitly announce itself as an AI system.
Ongoing documentationFor each deployment, we document the models used, their version, their licence and, where they are hosted by a third party, the provider and the processing location. This classification is reviewed as the European regulatory timeline evolves.

Our product commitments

Beyond the regulatory minimum

Voluntary measures, which we hold to because they are part of the product, not because any text requires them.

No automatic writes

Only the customer's team sends validated data. Nothing is written to your systems without validation.

Full traceability

Every extraction, correction and validation is logged and auditable.

You choose the mode

Without AI, local AI or external AI: settled flow by flow during scoping, written into the contract, reversible.

No memory between documents

Each document is processed in isolation. In external mode, the provider is contractually bound not to retain your data or use it to train its models.

Training included

Customer teams are trained on the tool during the pilot.

An AI Act classification document and a GDPR processor agreement template (DPA) are provided to each customer during contractual scoping.

This page is for information only and does not replace the service agreement and its annexes, which alone govern the relationship between the parties.