Privacy policy

vord · 29 August 2026

I'm one person running vord (a private mail bridge) for my own email. There's no company involved and there are no other users.

What it can see

vord uses the Gmail API with the gmail.modify scope, on Gmail accounts that belong to me. That lets it read messages, attachments, headers and labels in those accounts, and change labels and move messages around.

It can't permanently delete anything. gmail.modify doesn't allow that. When vord removes a message it moves it to Trash and lets Gmail's usual thirty-day timer finish the job.

Every account it connects to is mine. It can't be pointed at anyone else's.

Where the mail goes

Onto a mail server running on a machine I own. That server accepts no connections from the internet.

What I don't do with it

I don't sell it, share it, or hand it to anybody. It isn't used for advertising, analytics or profiling, and it isn't used to train models of any kind. Nobody but me reads it. Nothing is sent anywhere except the API calls to Google that fetch it in the first place.

Limited Use

vord's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Turning it off

Access can be revoked at any time from Google Account permissions, and vord's credentials stop working immediately. Mail already copied across stays on my server, because by then it's simply my own mail on my own computer. I delete it by deleting it there.

This site

Two static files. No cookies, no scripts, no trackers, no analytics, nothing loaded from anywhere else. Cloudflare (the host) presumably keeps ordinary request logs, and those have nothing to do with anybody's email.

Contact

There's no support desk since it's a personal project for my sole use. If you need to reach me about how it uses Google APIs, the support address on its OAuth consent screen is the place to do it.