Privacy

This page covers two separate things: what this website does, and what the products do with data you put into them.

These pages are static files. There is no analytics script, no tracking pixel, no advertising network and no cookie banner, because there are no cookies to consent to. Nothing you do while reading this site is recorded against you.

The web server keeps ordinary access logs — the requesting address, the page, the time — which are used for diagnosing faults and abuse and are not combined with anything else or shared.

If you email us, we hold that email and our reply to it, because that is what email is.

When you run IronMesh, the data in it is yours. We process it on your instruction, as an operator acting for you as the responsible party under the Protection of Personal Information Act.

Where we host it, it sits on infrastructure we operate in South Africa. Where you host it, it never reaches us at all — that is the reason the on-premises option exists. Which of the two applies to you is set out in your service agreement, not here.

Support staff do not browse customer data. Where an administrator has to act inside a tenant to resolve a fault, that access is explicit and written to an audit log you can ask to see.

Rivet for desktop can sign in to a Gmail account with Google. When you do, Rivet asks Google for one permission, full access to your mail (https://mail.google.com/), because that is the only permission Google offers for connecting a mail client over IMAP and SMTP. Rivet uses it to read, search, move, flag, delete and send your messages in every folder, as any mail client does.

• Your Gmail messages and the sign-in token are processed on your own computer. Mail travels between Google and your computer, and not through IronMesh servers. The token is kept in your operating system's keyring.
• We do not sell this data and we do not use it for advertising.
• We do not use it to train any model.
• Nobody at IronMesh reads it, because it never reaches us. Where we help you with a fault, we do not ask for it.
• Retention and deletion: Rivet keeps your Gmail messages and sign-in token only on your own computer, in your Rivet profile and your operating system's keyring, for as long as the account is added. Removing the account in Rivet deletes that account's local mailbox copy and its stored credentials. Uninstalling Rivet and deleting its profile folder removes everything else Rivet holds. We keep no copy, so there is nothing for us to delete.
• Revoking access: from Rivet 0.2.34, removing a Google account in Rivet also asks Google to revoke Rivet's access to that account. The request is made once, when you remove the account, so if the computer is offline at that moment it can fail, and earlier versions do not make it. To be certain access has ended, or to end it without opening Rivet, remove Rivet at myaccount.google.com/permissions.

Rivet's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

This section covers Rivet for desktop. Other IronMesh apps that handle Gmail, if any, are covered by their own terms when they are released.

Rivet for Android is a mail, calendar, contacts and notes app. It signs in to the mailbox you give it (your own mail server, or one we host for you) with that mailbox's address and password. It does not use Google sign-in and does not request access to Google user data.

• Kept on your phone: your messages, calendar, contacts and notes as synchronised from your mailbox, and the password, all in the app's private storage, which other apps cannot read. If you allow it, Rivet also reads the phone's contacts to suggest addresses while you write a message; those are not uploaded.
• Exchanged with your mail server: mail, calendar entries and contacts travel directly between the app and your mail server over an encrypted connection.
• Sent to the IronMesh notification service: to tell your phone when new mail arrives, the app registers your mailbox address, mailbox password, a device identifier and the Firebase Cloud Messaging push token with the IronMesh push relay, which runs on our infrastructure in South Africa. The relay uses the login only to watch the mailbox for new mail and sends Google's push service a notification without the message body. Handwritten and typed notes and your signatures are also stored there so that they reach your other devices. Removing the account in the app removes it from the relay.
• We do not sell this data, show advertising, use any advertising identifier or analytics service, or use it to train any model. Nobody at IronMesh reads it.
• To delete your data, remove the account in the app (this also removes it from the relay), or email us at the address below and we will delete anything held for you.

Under POPIA you may ask what personal information we hold about you, ask for it to be corrected, and object to how it is processed. Emailinfo@ironmesh.cloud and we will respond. You may also complain to the Information Regulator of South Africa.

The formal privacy policy that forms part of a service agreement is issued with that agreement and takes precedence over this summary. Ask us for a copy before you sign anything.