Bon Vent

How we keep our promise

A privacy app should be able to prove it. Here’s how Bon Vent is built, and how to check it yourself.

In short: Bon Vent has no servers. Your device talks to your email provider and to the companies’ public websites, and to nothing of ours. You can watch it do so.

The design, in plain words

Bon Vent is just the app. There is no Bon Vent account, no user database and no backend for the app to report to. When you connect a mailbox, your device connects straight to your email provider, the same way a mail app does. The app reads your mail on your device, works out which companies hold your data, and keeps the results in its private storage on that device.

When you send a request, it goes out from your own mailbox, like any email you write. Replies come back to you, and Bon Vent reads them on your device too.

What connects where

Connects toWhen and whyWhat is sent
Your email provider (for example Gmail or Outlook)To read mail, send the requests you approve and, if you choose, move processed bounce notices to Trash.Your login, and the messages you choose to send.
Microsoft’s sign-in page (Outlook only)When you choose “Sign in with Microsoft”.You sign in on Microsoft’s own page. Bon Vent receives an access token, never your password.
A company’s public websiteTo find its privacy contact, or to check whether it has moved or been acquired.An ordinary page request. The site sees your IP address, as with any web visit. No personal data is sent.
An unsubscribe link provided by a senderOnly when you tap Unsubscribe.The one-click unsubscribe request the sender asked for in its own email.
Websites you open in the built-in browserOnly when you open one: an account-deletion page, or a people-search site’s opt-out page.An ordinary visit. What you type there goes to that site, as in any browser.
A web search (DuckDuckGo)Only when you tap the button to search who acquired a company.The company’s name and domain, in your browser.
Bon VentNever.Nothing.

This mirrors the table in our privacy policy. If the two ever disagree, the privacy policy is the one we’re bound by, and we’ll fix this page.

Check it yourself

You don’t need to trust us. Any of these will show you every server the app talks to.

On iPhone: App Privacy Report

  1. Open Settings › Privacy & Security › App Privacy Report, and tap Turn On App Privacy Report.
  2. Use Bon Vent as usual for a while: connect a mailbox, look at your companies, send a request.
  3. Go back to the App Privacy Report and tap Bon Vent under App Network Activity.
  4. You’ll see the domains it contacted: your mail provider (for example imap.gmail.com), the websites of the companies it looked up, and nothing that isn’t in the table above.

On any device: a debugging proxy

  1. Install a proxy such as mitmproxy (free), Charles or Proxyman on your computer.
  2. On your phone, set the Wi-Fi network’s HTTP proxy to your computer’s address and the proxy’s port.
  3. To see inside encrypted web requests, install and trust the proxy’s certificate on the phone, following the proxy’s own instructions.
  4. Use Bon Vent. Every web request it makes appears in the proxy: ordinary page requests to company websites, and the unsubscribe requests you tapped. None of them contains your mail.
  5. When you’re done, remove the proxy setting and delete the certificate you installed.

Mail itself travels over the IMAP, POP and SMTP protocols, which don’t pass through a web proxy: they go straight from your device to your provider. To see those connections too, use the App Privacy Report on iPhone, a network monitor such as Little Snitch or LuLu on Mac, or PCAPdroid on Android.

In the App Store

Apple asks every developer to declare what data their app collects. When Bon Vent is published, its App Store privacy label will read Data Not Collected.

Seen a connection you can’t explain? Tell us at [email protected].

What we’d never do

Security notes

Report a security issue

If you find a vulnerability in the app or this site, please email us before telling anyone else, so we can fix it first. Include what you found and how to reproduce it. We’ll reply as quickly as we can and keep you posted until it’s fixed.

[email protected]

Also published in /.well-known/security.txt.