Last updated: 2 June 2026
I’m not trying to be clever here, and I’m not going to hide anything behind a paragraph of legal Latin. I’m a digital agent that lives, as a plugin, inside other people’s WordPress sites — and to do that job properly, I need access to a small, specific set of things about your site. Nothing more. This page is the full list, the reason for each item, and the button that wipes it all in one click if you ever change your mind.
The short version, before the long one: your site’s content stays on your site. I send a small health-report layer out to my home base at da-ve.ai so I can keep an eye on broken links, slow pages, downtime, and the like — and I send only that. Your posts, your customers, your orders, your settings, your secrets: those never leave the building. If at any point you’d like me to forget every last thing I know about your site, there is a single button that makes it so, and I will use it without complaint.
The operator of DA-VE is DA-VE-AI, registered in Victoria, Australia. Contact details are at the bottom. The rest is detail.
DA-VE-AI’s jurisdiction is Victoria, Australia. If you’d prefer a data-protection authority closer to home (UK ICO, EU DPAs, US state Attorneys General), your rights under those bodies still apply — see Your rights, plainly below.
Who this applies to
If you have installed the DA-VE plugin on a WordPress site you own or operate, this policy applies to you and to the data flowing between your site and the DA-VE service. Your site visitors — the humans reading your posts, buying your things, filling in your forms — are not the subject of this document. I have nothing to do with them; that’s between you and your existing privacy policy.
What I collect, and why
Here is the whole list. If something isn’t on it, I am not collecting it. The pattern is the same each time: I need X to do Y. Nothing else.
Site identity. Your site’s URL and the version of WordPress it’s running. I need the URL to know which site I’m talking to when you ask me a question, and I need the WordPress version so I can warn you when there’s a security update worth installing.
Findings. When my monitors notice something — a broken link, a page that loads slowly, the site going down, an image that could be lighter, an SEO issue, a plugin update — I record the finding (what it is, where it is, when I noticed it, how bad I think it is). I keep these in my own database so I can show you a running list in your DA-VE inbox. I do not record the content of the page the finding is about; I record the address of it and the nature of the problem.
Telemetry and analytics. Small operational signals about how the plugin and the service are working — request counts, error rates, how long things took, which tools I called, how many tokens an LLM round-trip used. Used to keep the lights on, spot regressions, and figure out the bill. I also count what kinds of questions customers ask me — how many chats per day, how often each action succeeds. No words, no content — just tallies. It helps me get better at the WordPress work. No personal data, no visitor data.
Profile. What you tell me about yourself when you set up your DA-VE: your name, what you do, the voice you want me to write in, the bits of context you’d like me to remember. You give me this; I keep it; I use it to help you. You can edit or delete it from the bubble at any time.
Magic-link tokens. A magic link is a one-time link emailed to you so you can open your DA-VE inbox without remembering a password. The token inside is HMAC-signed, scoped, and time-limited; nothing identifying is encoded inside it.
Email contact. The address you set DA-VE up with, so I can email you the weekly digest, send you a magic link when you ask for one, and reach you about service or billing.
Owner tokens. When you become the owner of a DA-VE bubble, your browser stores a long random string that proves to my plugin that you are the owner. The plugin stores a one-way hash of that string, not the string itself — so even if my database were stolen, the tokens couldn’t be used.
Conversations. When you talk to DA-VE in the bubble, the messages and my replies are recorded in your own site’s database (in a table prefixed wp_bdc_chats) so I can remember what we were discussing. They are also passed, mid-conversation, to the language model behind me (currently OpenRouter; see below). I do not store your conversations in my central database at da-ve.ai. They live on your site.
Billing. If you pay for DA-VE — credits, subscriptions, whatever the current arrangement is — Stripe handles the payment itself and tells me which event happened. I keep a record of those events (Stripe event ID, what kind of event, when it happened, how much, against which site) so I can reconcile your balance. I never see or store your card number; Stripe does.
What I will never collect
This part matters. The whole architecture is shaped around it.
- The text or media of your posts and pages — only the URLs and titles I need to talk to you about them.
- Customer records, order details, contact-form submissions, anything in your CRM or shop.
- WordPress settings, secrets, API keys, database credentials, FTP credentials, SFTP credentials, file-system contents.
- Anything about your visitors — their email addresses, their IPs, their browsing patterns. (Your existing analytics and CRM, if you have them, are theirs alone. I do not look at them and I do not duplicate them.)
- Your password to anything. I cannot log into anything as you, and I never want to be able to.
Cookies and browser storage
I don’t set third-party cookies. None. No advertising trackers, no Facebook pixel, no Google Analytics, no fingerprinting beacons.
The bubble does store a small bit of state in your browser’s localStorage — your owner token, your current session ID, whether you’ve closed the bubble in this browsing session — so it remembers who you are between pageviews and doesn’t keep popping open after you’ve dismissed it. That’s the only thing it remembers, and it’s strictly necessary for the chat to function. Under GDPR and PECR, that’s the category that doesn’t need a consent banner. So you won’t see one.
How long I keep things
For as long as you are an active DA-VE customer, I keep what I have indefinitely — because the whole point is the running history, and a history that resets every six months isn’t a history.
When you go dormant — when the plugin has gone quiet on your site, or your subscription has lapsed — I follow what I think of as the dormancy ladder. After roughly twelve months of complete silence I will auto-delete everything I have about your site, in the same shape that the right-to-delete button would have done it. You will not get a sentimental email about this; it just happens.
If you delete the plugin from your site without using the forget button first, your local data (the wp_bdc_* tables on your own database) is yours to drop or keep as you see fit. I cannot reach those tables — they are on your server, not mine.
The forget button
In your DA-VE inbox there is a single button labelled, more or less, “Wipe everything DA-VE knows about my site.” Clicking it does the following, in this order, in one go:
- Deletes every row about your site from my gateway database — findings, telemetry, profile, contacts, conversation pointers, the lot.
- Asks your site’s copy of the DA-VE plugin to delete the same things from its own local tables.
- Invalidates every magic-link token issued for your site, so any existing email link stops working.
- Sends you one final email confirming what was deleted and when.
It is instant. There is no soft-delete, no grace period. I will ask you to type REMOVE in the box to confirm. That’s the only friction — but it’s there because this can’t be undone.
After you press it, the bubble returns you to the very first thing you saw when you met DA-VE — the Have a look around card — with a small note above it confirming that everything’s been cleared. From there you can either start fresh (which will ask for fresh consent) or close the bubble for good.
Who else sees this stuff
DA-VE uses three third parties to do its job. Each gets only the slice of data they need; none get anything else.
- OpenRouter routes my conversations to the language model that powers them. Your messages to me and my replies pass through OpenRouter on their way to the model and back. OpenRouter does not, per their terms, retain or train on this traffic.
- SendGrid sends the emails I send you — digests, magic links, billing receipts, the forget-button confirmation. They see your email address and the email body.
- Stripe handles payments. They see your billing details. I see only the events Stripe tells me happened.
That is the entire list of processors. I do not share your data with anyone else, and I never sell it. There is no advertising layer; there are no analytics resellers. If at any future date a fourth processor is added, this page will say so before the change goes live.
Your rights, plainly
If you are in the EU/UK, GDPR gives you the right to know what I have, to get a copy of it, to correct it, to have it deleted, and to take it somewhere else. If you are in California, CPRA gives you broadly the same rights plus the right not to have your data sold or shared — which I am not doing in either case. Australian users have equivalent rights under the Privacy Act 1988 (Cth), enforced by the OAIC.
You can exercise any of these rights by emailing the address below. The deletion right is the one most people want; that’s the forget button, available to you without asking anyone’s permission.
I will respond to a written request within thirty days. If I cannot fulfill a request — which I expect to be rare — I will tell you why, in writing, and what your options are.
Contact
For data requests, complaints, or any question this document didn’t answer: privacy@da-ve.ai.
For everything else: hello@da-ve.ai.
When this policy changes
If I change anything material here, I will update the date at the top, send a one-line note to every active DA-VE email on file, and put a small notice in the bubble for two weeks so you can read the diff. I will not change anything material retroactively — anything new applies from the date it is announced. Data already collected before any change stays governed by the policy that was in effect when it was collected.
This document supersedes any earlier version.