privacy policy
Plainly, what we do with your data.
What we collect, why we're allowed to, and where it goes — the whole of it, stated plainly enough to be held against us. The panel to the right is the machine-readable version of everything written below.
last_updated · 2026-08-17
$ cat privacy.json
{
"policy": "itzgee_privacy",
"version": "2.3.0",
"last_updated": "2026-08-17",
"data_controller": "GEE_DIGITAL_SOLUTIONS_LTD",
"user_data": "encrypted_at_rest",
"analytics_engine": "umami_self_hosted",
"third_party_trackers": 0,
"tracking_cookies": 0,
"advertising_cookies": 0,
"data_sold": false,
"data_shared_for_ads": false,
"data_location": ["UK_Coventry", "UK_Maidenhead"],
"hosting": "uk_servers",
"your_rights": "UK_GDPR_full",
"admin_snooping": "disabled"
}
the difference
Corporate cloud vs the vault.
The same question — where does your data actually go? — asked of a typical Big Tech cloud, then of the way itzgee.com is built.
| metric | Big Tech Cloud | The Vault · itzgee.com |
|---|---|---|
| Data location | Scattered across global data centres | UK · Coventry & Maidenhead |
| Analytics | Google Analytics + ad-tracking cookies | Self-hosted Umami · zero cookies |
| Cookies | Tracking & advertising cookies | Essential session only · none for tracking |
| Access to your data | AI scanning · algorithmic profiling | Isolated Docker containers · zero admin snooping |
| Ownership | Monetised, shared with partners | Yours — never sold, never shared for ads |
| Third-party trackers | Many | 0 |
what we collect
The short list. Nothing hidden beneath it.
- website analytics
- Umami — a self-hosted, open-source analytics tool — runs on our UK servers, not a third party's. It is cookieless by design and counts page views anonymously: page URL, referrer, approximate country, browser and device type, and nothing that identifies you. Nothing is sent to Google, Meta or any advertising network. Your IP is used for a moment to derive country and a daily-rotating hash that de-duplicates a visit, then discarded — never stored.
- account data
- If you hold a plan, we process only what's needed to run it: your email, username, chosen tier, authentication handled by our own Pocket ID SSO, and the storage figures required to enforce your quota.
- keeping you in the loop
- If you sign up to the network updates list on the site, we store the name and email you give us and — so we can show the sign-up was genuine and stop the form being abused — the IP address and browser it came from, and which page it came from. If instead you turn updates on from your account page, or while accepting the network terms, we store the email address already on your account and which of those two places it came from, and nothing else. The lawful basis is your consent. A sign-up on the site is confirmed by email: nothing joins the list until you click the link we send. Turning it on from inside your own account is not, because we had already reached you at that address to give you the account — there, the switch itself is the consent. Either way we record the exact wording you agreed to and the moment you agreed. Every update carries a one-click unsubscribe. When you unsubscribe we delete your name and keep a one-way hash of your address, so that nobody else can put you back on the list without your say-so — you can always sign up again yourself, it just asks you to confirm by email like the first time. Ask us to erase it and it goes entirely.
- when you buy from the store
- Placing an order gives us what fulfilling it requires: your name, email, delivery address and the items ordered. Payment is taken by Stripe — your card details are entered directly on Stripe and never touch our servers; we retain only the card brand and last four digits against the order, so you and we can tell one payment from another. Order records are kept as long as tax and consumer law require. To protect against card fraud we also record the IP address and browser the order was placed from, and Stripe's assessment of the payment — its risk score and the checks it ran on the card. These sit against the order as evidence if a payment is ever disputed, and are kept as long as the order record itself.
- when you contact us
- If you email us or open a support ticket, we keep your message, your email address and our reply — to answer you and for our records, nothing more. A support ticket also records the IP address it was raised from, so abuse of the form can be traced; it stays with the ticket and is used for nothing else.
- server logs
- Our servers keep standard operational logs — the IP address a request arrives on, basic request metadata, service health and authentication events — used to keep the service secure and to debug problems, never to build a profile. They stay on our servers and are kept only as long as security and the law need, then rotated out.
- DNS, if you are on the network VPN
- If you are on the network VPN, your device's DNS lookups are resolved and filtered by our own AdGuard Home. Both of the servers we run in UK data centres have a resolver, and your device uses the one at the end of the tunnel it is connected to. Filtering happens there — advertising, tracking and malware domains are refused before your device connects to them. A local query log is kept on that server for up to 90 days to diagnose and tune the filtering, then rotated out; it is never shared with anyone. Client IP addresses in that log are anonymised, so a lookup is recorded without being tied to a device. If you are not on the VPN, your own resolver handles DNS and we see none of it.
- what we never collect
- No advertising pixels, no fingerprinting, no social embeds, no cross-site tracking, no data brokers. There is no profile of you here to sell, because we never build one.
why we're allowed to
Lawful basis, in plain terms.
- controller
- GEE DIGITAL SOLUTIONS LTD is the data controller under UK GDPR, operating itzgee.com. You can reach us at [email protected]. We rely on four lawful bases and nothing else.
- legitimate interests
- Aggregate, anonymous analytics that never identify you — used only to see which pages earn their place — and keeping the service secure through operational logs. Preventing fraud on store payments and abuse of the ticket form sits on the same basis.
- contract
- The processing required to give you the account you signed up for, or to fulfil an order you place in the store.
- legal obligation
- Records we're required to keep, such as billing and tax.
- consent
- Where we ask for it explicitly and separately — such as registering your interest to be kept in the loop by email. You can withdraw consent at any time, and we act on it.
where it lives
On our hardware. Inside the UK.
- where data lives
- On servers we run in two UK data centres — Coventry and Maidenhead. Encrypted backups stay inside that footprint. Data at rest never leaves the UK.
- in fairness
- Where Cloudflare's proxy fronts a route, the initial request may transit its global edge before reaching our UK servers; the stored data itself stays in the UK. We'd rather say so than overclaim.
- sub-processors
- Kept to a minimum. Cloudflare handles DNS and edge protection; Brevo delivers our email — enrolment, recovery and security notices, store order and support notifications, and the network updates you can opt into; Stripe processes card payments for store orders and for donations via /appreciate, with card details entered directly on Stripe and never touching our servers; ipapi.is classifies the IP address a connection arrives from, so the network can tell you whether you are on the VPN and what is carrying your traffic — for the indicator in the site header that lookup is made by our server and carries only the IP address, while on ip.itzgee.com it is made by your own browser, so ipapi.is sees that request directly. None of these receives anything for advertising.
- retention
- We keep personal data only as long as the purpose needs and the law requires, then delete it. The analytics carry no identifier to expire.
- who can read your files
- Data is encrypted at rest, and backups are encrypted before they leave the machine. Access to tenant data is limited to what running the service actually requires — no algorithmic snooping, no browsing out of curiosity.
your rights
Your data, your call.
- your rights
- Under UK GDPR you can ask for access, correction, deletion, restriction, a portable copy, or object to processing. We action valid requests without fuss.
- how to exercise them
- Email [email protected]. We may need to confirm it's really you before acting on account data.
- the regulator
- You can complain to the Information Commissioner's Office at ico.org.uk at any time — though we'd like the chance to put things right first.
- changes
- If this policy changes materially, the version and last_updated date at the top change with it.