AI Consulting for SMEs: Privacy Before Your Project Starts
An AI assistant could search internal documents, draft customer responses or analyse service reports. The benefits seem clear. Yet essential questions often remain unanswered before work begins: What personal data will enter the system? Who can access it? And what evidence will privacy and legal teams need?
When choosing AI consulting for SMEs, you should expect more than a tool recommendation. Good advice creates a sound basis for deciding on the use case, technical implementation and necessary reviews. This guide explains what business leaders and IT directors should prepare.
In short: Before introducing AI into your business, document the data involved, processing purposes, data flows and participating providers. Your privacy and legal teams can then assess lawful bases, contracts, international transfers and whether a data protection impact assessment is required. A pilot should process real personal data only once responsibilities are clear and appropriate safeguards are in place.
Introducing AI into your business: Which privacy questions should you answer first?
Data protection starts with the specific processing activity, not the AI model you choose. What matters is which data is processed, for what purpose and who can access it.
Begin with a short use-case brief. “We want to use generative AI” is not specific enough. A better description would be: “Customer service staff will generate draft responses using approved product documentation and review every draft before sending it.”
What your use-case brief should contain
- Purpose: Which task will AI support, and how will you assess its value?
- People affected: Does the data concern customers, employees, applicants or other groups?
- Data categories: Will the system process contact details, contracts, performance reviews or health data?
- Sources: Will information come from a CRM, document repository, email or business applications?
- Outputs: Who receives the results, and will they inform decisions?
- Retention: How long will inputs, outputs, logs and backups remain stored?
Include derived data. Search indexes and embeddings may still contain personal data. Pseudonymised data generally remains subject to the GDPR; only genuinely anonymised data falls outside its scope.
Also consider whether the pilot can start with synthetic data or carefully selected documents without personal information. This reduces risk but does not replace an assessment of the eventual production system.
Which providers and data flows should you assess?
A privacy assessment must cover the entire processing chain, not just the provider behind the chat interface. That chain may include cloud platforms, model providers, search services, logging systems and external support teams.
Map the journey from the source system through to deletion. For each stage, identify storage locations, authorised users, contractual parties and potential onward transfers. Include telemetry, error logs and support access.
Questions to ask potential providers
Request answers for the specific product, subscription tier and configuration you intend to use:
- Are inputs or outputs used for model training or product improvement?
- What retention periods and deletion options apply?
- Which subprocessors are involved, and how are changes communicated?
- Where is data processed, and from which locations is administrative access possible?
- What controls support roles, encryption, audit logs and tenant isolation?
European data storage does not automatically rule out access from third countries. Equally, cloud use is not inherently unlawful. The actual processing activities, contracts and safeguards determine the assessment.
For Microsoft Azure, Microsoft Fabric and Databricks, the same principle applies as for specialist AI services: a product name does not establish GDPR compliance. Assess the services and settings you will actually use rather than approving an entire platform indiscriminately.
What documentation do privacy and legal teams need?
Privacy and legal teams need a clearly defined use case, a data-flow map and reliable provider documentation. A general claim that a provider is “GDPR-compliant” cannot replace this evidence.
Schedule the review before procurement. Otherwise, contractual gaps or unresolved access arrangements may emerge only after licences have been purchased and integrations built.
Lawful bases, roles and contracts
The responsible teams should establish the lawful basis for each processing activity and whether existing data may be used for the new purpose. Special categories of personal data, such as health data, require additional conditions to be assessed. Consent is not a universal solution, particularly in employment relationships.
Roles also matter: is the provider acting as a processor, joint controller or independent controller? Each arrangement has different contractual implications. International transfers must also be assessed against Chapter V GDPR requirements, potentially including Standard Contractual Clauses and a transfer assessment.
Risks, individual rights and AI regulation
A data protection impact assessment is required where processing is likely to create a high risk to individuals’ rights and freedoms. Not every AI project requires one, but the decision and its reasoning should be documented.
Preparation should also cover:
- Reviewing or updating records of processing activities and privacy notices.
- Procedures for access, rectification and erasure, including search indexes and stored outputs.
- Assessing Article 22 GDPR where solely automated decisions could produce legal or similarly significant effects.
- Classifying the use case and your organisation’s role under the EU AI Act, then checking applicable obligations and application dates.
- Involving the works council early where participation rights are affected.
The GDPR and EU AI Act are separate, partly overlapping review areas. This guide helps structure preparation but does not replace case-specific legal advice.
AI consulting for SMEs: How we work
We structure preparation so that business leadership, IT and privacy teams can make decisions using the same evidence. Technical design and legal assessment are coordinated, while their responsibilities remain clearly separated.
1. Define the use case and its boundaries
Together with business stakeholders and IT, we clarify expected value, data requirements and exclusions. An assistant working with approved product documentation can be a sensible starting point before confidential personnel records are considered.
2. Document data flows and architecture
We identify sources, interfaces, providers and permissions. The outputs are an architecture overview and a list of unresolved review points. For document-based search, for example, the assistant must not expose content that the current user cannot access in the source system.
3. Assemble the review package
We help prepare technical and organisational information for privacy and legal teams, including provider documentation, deletion procedures, access controls and documented risks. Legal assessment and required approvals remain with the responsible functions.
4. Plan a pilot with clear approval criteria
Before launch, define the permitted data, test users, quality requirements and stopping criteria. Tests should address unauthorised data requests, prompt injection and accidental disclosure of confidential information. Logging itself needs a defined purpose and limited retention periods.
Ailio supports this preparation with expertise in Data Science, data platforms and AI, working from Bielefeld in the Ostwestfalen-Lippe region and Hamburg.
When is your AI project ready for a pilot?
An AI pilot is ready when its data scope is limited, its risks have been assessed and the necessary reviews are complete. A time-limited trial still has to meet applicable data protection requirements.
Use this checklist to support the launch decision:
- The business purpose, project owner and authorised users are identified.
- Data sources, data categories and required lawful bases are established.
- Provider roles, necessary contracts and potential international transfers have been reviewed.
- Access controls, deletion procedures and security tests are prepared.
- Required privacy assessments are documented; outstanding risks have owners and mitigation measures.
- Employees know what data they may enter and when outputs need human review.
- Security and privacy incidents have reporting channels and a shutdown procedure.
If important items remain unresolved, the entire initiative does not necessarily have to stop. Often, the pilot can initially use less sensitive data and a narrower user group. That does not, however, substitute for a missing lawful basis or a required contract.
For additional background, see our article on trustworthy AI, GDPR and ethics for SMEs.
Start with a sound basis for your decision
Want to introduce AI without discovering privacy issues after implementation? Our Data & AI Strategy consulting helps you structure use cases, data flows and review steps before the project starts. Turn your AI idea into a next step you can properly assess.
