Privacy Policy
What personal data ambivalence collects, why, who it is shared with, how long it is kept, and how to exercise your rights. If your organisation invited you, it is the controller of your learning data and we process it on its behalf.
Deviant Botanicals Limited (trading as DevBot) · ambivalence.app · Last updated: 19 November 2026
1. Who we are
Deviant Botanicals Limited (trading as DevBot) operates the ambivalence platform (ambivalence.app), a civic e-learning and participatory news service.
Data Controller: Deviant Botanicals Limited, or the organisation that invited you, as explained below
Contact: hello@dev-bot.co.uk
Subject line for privacy enquiries: Privacy Enquiry
If your organisation invited you, it is the Data Controller for your account, learning progress, answers and badges while you use the Service. We process that data for it, as Data Processor, under a Data Processing Agreement. Your organisation’s own privacy information explains its purposes and lawful basis, and it decides requests about that data; if you send one to us, we pass it on and help it respond. We are the Data Controller for visitors who watch the open preview episodes without an account, for the record that keeps a badge verifiable after an account is deleted (section 6), and for running our own business, such as invoicing and support.
2. What personal data we collect
We collect and process the following categories of personal data:
| Category | Examples | Purpose |
|---|---|---|
| Account data | Email address, display name, password (hashed), department, role | To create and manage your account; to authenticate you |
| Organisation data | Tenant/organisation identifier | To associate you with your employer or organisation (where applicable) |
| Learning progress | Episode and sequence completion, time spent, session count | To track your progress and display your learning history |
| Interaction data | Quiz answers, reflection responses (please do not include sensitive details about yourself or others, such as health or political views), interaction type, score, time taken | To assess competency and award badges. Your organisation’s administrators can see your reflection responses |
| Badge data | Badge awards, persona, tier, domain, the learning outcomes evidenced | To issue and display your digital badges; to support competency records |
| Usage data | Login timestamps, last activity | To support the service and security |
| Communications | Emails you send us; support enquiries | To respond to you |
| Technical data | IP address, browser and device type, and request logs, on our servers and Cloudflare’s network | To deliver the Service securely and investigate faults |
3. Where we get your data from
From you: When you set up your account from an invitation, complete interactions, or contact us
From your organisation: If you are invited by an employer or institution, we receive your email and role from the inviter
Automatically: Progress, interactions, and usage data are generated when you use the Service
4. Why we process your data (lawful basis)
| Purpose | Lawful basis |
|---|---|
| Account creation and management | Your organisation’s lawful basis, as its privacy information explains (we act for it) |
| Delivering learning content and tracking progress | Your organisation’s lawful basis, as its privacy information explains (we act for it) |
| Assessing competency and awarding badges | Your organisation’s lawful basis, as its privacy information explains (we act for it) |
| Keeping an issued badge verifiable after your account is deleted | Legitimate interest (yours, and that of anyone checking a badge you have shared) |
| Communicating with you about the service | Your organisation’s lawful basis for service messages; legitimate interest for our own notices about the Service |
| Improving the platform and content | Your organisation’s instructions, using aggregated, anonymised statistics only; identifiable data is analysed only where your organisation asks |
| Security, fraud prevention, legal compliance | Legitimate interest; Legal obligation |
| Marketing (e.g. product news) | Consent (where we ask for it explicitly) |
Where we rely on legitimate interest, we have recorded an assessment that balances it against your rights, which you can ask us for. You may object (see section 8).
Where we rely on consent, you may withdraw it at any time without affecting the lawfulness of processing before withdrawal.
5. Who we share your data with
We share your data only as necessary:
| Recipient | Purpose | Location |
|---|---|---|
| IONOS (hosting and email) | Hosting the platform, database and content; sending invitation and account emails | Germany (EEA) |
| Cloudflare | Network protection and secure connection in front of the platform; carries traffic but stores no learner records | Global network (UK traffic normally via London); covered by the UK International Data Transfer Addendum |
| Your organisation | For institutional licences: your progress, badges and reflection responses, through its administrators’ dashboard and reports | As agreed |
| Anyone you share a badge with | Each badge has a public verification page so others can check it is genuine. It shows the badge, the learning outcomes and the issuer, with your identity held only as a protected (hashed) value - never your email address or your answers. Adding a badge to LinkedIn happens only if you choose to | Public web |
| Legal/regulatory | Where required by law (e.g. court order, ICO) | UK |
We do not sell your personal data. We do not use your data for advertising or profiling beyond what is needed to deliver the service.
6. How long we keep your data
| Data type | Retention |
|---|---|
| Account data | Until you or your organisation delete your account, or your organisation’s contract ends (see below this table) |
| Progress and interactions | As account data |
| Badge records | The full record, including the answers that earned it, until your account is deleted. A badge is yours and is not revoked when your account is deleted, and a badge you have downloaded stays valid. So that it keeps verifying, we then keep only a minimal verification record, as controller: the badge, its learning outcomes, the issue date, the issuer and your identity as a one-way hashed value. It holds no email address, answers or evidence, and we keep it while the badge may need to be checked. If you ask us to erase it and we uphold your request, we delete it and the badge stops verifying. The same applies if your organisation’s account with us is deleted. |
| Invoicing records (organisations we license) | As required for tax and accounting (typically 7 years) |
| Support communications | Typically 2 years after resolution |
| Backups | Server: 14 daily and 8 weekly copies (about two months); encrypted off-site copy in the UK: 90 days; then deleted |
| Logs | Web request logs: 14 days. Application and audit logs: 12 months |
After the retention period, we securely delete or anonymise your data. When your organisation’s contract with us ends, it can ask for a copy of its data; we then delete it within 30 days, and from backups as they cycle out within 90 days.
7. International transfers
We store your data in Germany (European Economic Area), with an encrypted backup copy in the United Kingdom. Written reflections are scored on your own device and are not sent to any artificial intelligence service. Cloudflare, which carries traffic to and from the platform, runs a global network, so your connection may pass through its servers outside the UK and EEA. It stores no learner records, and these transfers are covered by the UK International Data Transfer Addendum.
8. Your rights
Under UK GDPR you have the following rights:
| Right | What it means | How to exercise |
|---|---|---|
| Access | Obtain a copy of your personal data | Request via hello@dev-bot.co.uk or use the in-app data export (Settings) |
| Rectification | Correct inaccurate data | Update your profile or contact us |
| Erasure | Have your data deleted (“right to be forgotten”) | Use “Delete account” in Settings or contact us |
| Restriction | Limit how we use your data in certain circumstances | Contact us |
| Objection | Object to processing based on legitimate interest | Contact us |
| Portability | Receive your data in a machine-readable format | Use the in-app data export (JSON) or contact us |
| Withdraw consent | Where we rely on consent, you may withdraw it | Contact us or use any opt-out mechanism we provide |
| Complain | Lodge a complaint with the supervisory authority | ico.org.uk |
We will respond to your request within one month. We may need to verify your identity.
Data export: You can export all your data (account, progress, badges, interactions) directly from the platform via Settings.
Account deletion: Deleting your account triggers permanent deletion of your personal data, subject to any legal retention requirements, with one exception: the minimal verification record for each badge you earned, which you can ask us to erase (section 6). Your badges are not revoked, and any you have downloaded or added to LinkedIn stay valid.
9. Security
We implement appropriate technical and organisational measures to protect your personal data, including:
Encryption in transit (TLS 1.2 or higher)
Secure storage and access controls
Regular security reviews and updates
Organisations we work with can ask us for a fuller description of our security measures.
10. Children
The Service is for adults. Organisations invite only people aged 18 or over. If someone under 18 has been invited by mistake, tell us or the inviting organisation and we will delete the account.
11. Cookies and similar technologies
The Service sets no cookies of its own and uses no advertising or third-party analytics trackers. It keeps a few items in your browser’s local storage, each needed for something you have asked for: your sign-in session, your accessibility, language and subtitle settings, your place in an assessment, and any privacy choice you make. These are strictly necessary, so they do not need consent. Cloudflare, which protects the platform, may set a short-lived security cookie to tell people apart from automated traffic.
12. Changes to this notice
We may update this Privacy Policy from time to time. We will notify you of material changes by email or via the Service. The “Last updated” date at the top indicates when it was last revised.
13. Contact and complaints
Deviant Botanicals Limited (trading as DevBot)
Email: hello@dev-bot.co.uk
Subject: Privacy Enquiry
To exercise your rights, or to complain about how we handle your data, email us at the address above. We aim to reply within 5 working days. We acknowledge every complaint within 30 days, look into it, and tell you the outcome. If you are not satisfied, you can complain to the ICO.
Supervisory authority:
Information Commissioner’s Office (ICO)
ico.org.uk
Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF