AI Policy
Where we use AI, what it is trained on, what it never sees, and how to get a person involved.
This is version 1.0, archived on 26 July 2026. It is kept for reference and is not the current document — read the current version.
- Version
- 1.0
- Effective
- 26 July 2026
- Applies to
- Drentova Group Ltd
- History
- 1 version
Our position
AI assists, people decide. Your content is not used to train anyone’s model.
We use AI where it makes a product genuinely better and we can explain what it is doing. We do not use it to make decisions about people without a person involved, and we do not treat customer data as training material.
Your content is not training data
We do not use customer content to train, fine-tune or improve any AI model — ours or a third party’s. Where a feature sends content to an AI provider to produce a result for you, we use that provider’s zero-retention arrangement where one is available, and we say so in the product.
Any AI provider we send personal data to appears in our subprocessor list, with the transfer safeguard covering it, like any other processor.
Automated decisions and human review
Article 22 of the UK GDPR gives you the right not to be subject to a decision based solely on automated processing that produces legal effects or similarly significantly affects you. We do not make decisions of that kind by automated means alone.
Where AI contributes to a decision that affects you — such as flagging content for review — a person makes the final call. If you believe an automated system has affected you unfairly, ask for a review through our data rights centre and a person will look at it.
Accuracy and limitations
AI output can be wrong, and can be wrong confidently. Where a product presents AI-generated content, we label it. You should check anything you rely on, and you remain responsible for what you do with the output.
How we build
We assess a feature’s data protection impact before it ships where it processes personal data at any scale, keep a record of which models are used for what, and review that record as models change. We prefer providers who contract on UK GDPR terms and who will tell us where processing happens.
How to contact us
- Privacy and data protection
- [email protected]
- Product support
- [email protected]
Change log
- v1.0 · 26 July 2026First published version.