Privacy Policy
What SiteVigilante does with personal data, what it keeps, for how long, and how to have it deleted.
Version 1.0 · in effect from 30 August 2026 · TEAMDIGITAL BV, Zaventem, Belgium
This policy describes what SiteVigilante does with personal data. It covers two different relationships, and keeping them apart is the whole shape of this page: the data about you, the agency that holds the SiteVigilante account, for which TEAMDIGITAL BV decides the purposes and is the controller; and the data inside your workspace about your own clients and their websites, for which you decide the purposes and we act only on your instructions. The second relationship is governed by the Data Processing Agreement.
Who we are
SiteVigilante is operated by TEAMDIGITAL BV, Excelsiorlaan 10, 1930 Zaventem, Belgium. Enterprise number 0759.548.701, VAT BE0759.548.701.
For anything in this policy, including a request to see or delete your data, write to support@sitevigilante.com.
What we hold about you, and why
| What | Why | Basis |
|---|---|---|
| Your email address, a password we store only as a hash, your display name, your language, timezone and theme, and — if you switch it on — your two-factor secret and recovery codes. | To give you an account and let you sign in to it safely. | Performance of the contract. |
| When you last signed in, and when your email address was confirmed. | To keep the account recoverable and to notice a dormant one. | Performance of the contract. |
| Your company name, address, VAT number, phone number and website, and your billing and alert email addresses. | To issue invoices that are legally complete and to send you the alerts you asked for. | Contract and legal obligation. |
| Your Stripe customer reference, your card brand and its last four digits. We never receive or store a card number — you enter it on Stripe's own form. | To take subscription payment. | Performance of the contract. |
| An audit record of actions taken in your workspace, each carrying the email address of the person who took it. | So an agency can see who changed what. It is a security feature and you are the one it protects. | Legitimate interest in a secure product. |
| Support messages you send us, with your email address. | To answer them. | Performance of the contract. |
| The version of the Terms and Privacy Policy you accepted, and when. | To be able to show what you agreed to. Recorded at signup and never invented for an account that predates it. | Legal obligation. |
What is in your workspace about other people
When you use SiteVigilante you put data into it about your own clients and their websites. We hold it for you and act on your instructions:
- Client records you create: a client name and your own notes.
- Client contacts: a name, an email address and a role, for people who have no SiteVigilante account and never agreed to anything with us. They are in the product because you put them there, and the DPA is what governs them.
- Technical facts about the websites you connect: the address, the WordPress and PHP versions, which plugins and themes are installed and at what version, page performance results, and whether the site was reachable.
- Error text taken from the website when an update fails. It is written by the website rather than by us, so it can contain a file path or, occasionally, a name.
- Security evidence: file paths, file digests, sizes and short excerpts of file contents, and — where the website reports them — WordPress administrator usernames. This is the most sensitive material the product holds and it is treated as such.
Who else sees any of it
A short list, published in full and kept honest by a test that sweeps this application for outbound connections and fails if one is undisclosed. See sub-processors for what each one receives and where it runs. In summary: Stripe for billing, Mailgun EU for email, Anthropic for explaining an update that failed or was rolled back — automatically when one does, and when you press Explain — Google for page-performance measurement, when you ask for one or when you buy and confirm a Growth Scan, WordPress.org for looking up whether a plugin still exists, and Hetzner, which hosts the platform itself.
We do not sell personal data, we do not share it for advertising, and there is no advertising, analytics or tracking product embedded anywhere in SiteVigilante.
Where it is
The SiteVigilante platform runs on a single server in Germany, and the database, the queue and uploaded files are all on that machine. Two of the sub-processors above process data outside the EU — Anthropic and Google, both in the United States — and they do so only for the specific, narrow purposes named on the sub-processors page, only when something you did causes it, and not at all while the credential for that provider is unconfigured. Section 3.1 of the Data Processing Agreement states each condition exactly.
Cookies
SiteVigilante sets one cookie: the session cookie that keeps you signed in. It is marked HttpOnly and Secure, it is scoped to the host that set it, and it exists only so the application can recognise your session. There is no analytics cookie, no advertising cookie and no third-party cookie, which is why you are not being asked to consent to any. The marketing site loads its font from our own server and contacts no third party at all.
How long we keep it
- Your account data: until you delete it. We do not expire it on a timer.
- Uptime observations: 30 days, enforced by the job that writes them.
- Finished run records: 7 days.
- Everything else attached to a website or a workspace lives exactly as long as that website or workspace does.
Deleting it
You can delete a single website, or the whole workspace, from inside the product. Both are real deletions rather than a flag:
- Deleting a website erases the twenty tables of data attached to it, including every uptime observation ever taken of it and the whole of its security evidence.
- Deleting the workspace cancels the subscription first, then erases every table that carries your account, then your users and their sessions, then the account itself — in one transaction, so it either completes or leaves nothing half-removed.
Both paths are held by tests that read the database schema at run time rather than a list somebody maintains, so a table added to this product without an erasure rule fails the build on the day it lands.
Backups, stated exactly
TEAMDIGITAL BV does not currently operate a backup or snapshot mechanism of its own for the SiteVigilante platform database. We checked for one before writing this sentence and there is none, so when the deletions above run there is no backup copy of ours from which the data could come back. Whether our infrastructure provider keeps snapshots at the infrastructure layer is not established, and we would rather tell you that than imply an answer either way.
This paragraph is about the platform's own data. It is not a statement about backups of your clients' websites — SiteVigilante does not take those, and nothing in the product should be read as doing so.
Your rights
You can ask for a copy of your data, ask us to correct it, ask us to delete it, object to a processing we base on legitimate interest, or ask for it in a portable form. Write to support@sitevigilante.com. We will not charge you for it and we will not make you explain why.
You can also complain to a supervisory authority. In Belgium that is the Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données) in Brussels.
Security
Each agency's workspace is isolated from every other one, and that isolation is enforced at the point where the application looks a record up rather than by a check somebody has to remember to write. Passwords are hashed, two-factor authentication is available, the connection is encrypted with HSTS in force, and credentials are excluded from the data the application serialises. No system is perfect and this paragraph is a description of what we do, not a guarantee.
Changes
This is version 1.0, in effect from 30 August 2026. If we change it materially we will publish the new version here with a new version number. The version you accepted when you signed up is recorded against your account, and publishing a new one does not silently rewrite what you agreed to.
Questions, or a request about your data, go to support@sitevigilante.com.