Privacy Policy

What this app is

REVNU GTM is a tool for sending work email and keeping track of the replies. You connect your own mailboxes to it, upload your own list of people to contact, and it sends on your behalf and collects what comes back.

It is used by one organisation at a time. Each account gets its own separate database file, and no account can read another account's data.

What we store about you, the account holder

• Your email address and name, so you can sign in and be told about things.
• A scrypt hash of your password. The password itself is never stored and cannot be recovered from the hash.
• If you sign in with Google, the identifier Google gives us for your account. Nothing else from your Google profile.
• The credentials for each mailbox you connect, encrypted with AES-256-GCM before being written to disk.

What we store about the people you email

Whatever you upload or the app learns from your conversations. In practice that is:

• Email address, first and last name, job title and company.
• Any other column you choose to include when you upload a list.
• The emails sent to them and the replies they send back, including the message text.
• A profile picture, where one is available from the connected Google account's contacts.
• Notes, statuses and follow-up dates you or the app record against them.

How we use Google user data

The app asks for Google permissions only to do the job you asked it to do. Each one is used for one thing:

• Signing in (openid, email, profile): to know who you are when you sign in, and nothing else.
• Gmail (mail.google.com, gmail.send, gmail.readonly): to send email from the mailbox you connected, and to read replies to threads this app started so they can be shown to you.
• Contacts (contacts, contacts.readonly, contacts.other.readonly): to look up the profile picture of somebody you are emailing, so you can see a face next to a name.
• Calendar (calendar.events): to put a follow-up you scheduled onto your own calendar.

Google API Services User Data Policy

This app's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Concretely: Google user data is used only to provide the features described above. It is never sold. It is never used for advertising. It is never used to train any machine learning or AI model. No human reads it except you, and us only where you have asked us to help with a specific problem, or where the law requires it.

Where your data lives

On a server rented from Hetzner in Helsinki, Finland. Your data is not copied to any other service except where a feature requires it, which is only the cases listed below.

Who else sees it

Three kinds of third party are involved, and only these:

• Google, when the app sends or reads mail, looks up a contact photo, or writes a calendar event on your behalf.
• The provider of the AI model configured for your install, when you ask it to draft a reply or when a lead's status is worked out from a reply. The conversation text is sent so the draft can be written, and is not used to train that provider's models under their API terms.
• Hetzner, as the company hosting the server, in the ordinary sense that a landlord holds the building.

How long it is kept

For as long as your account exists. Delete a contact and it goes from the database. Ask us to close your account and the whole database file for your account is deleted, along with the login record.

Backups of the server are kept for fourteen days and then deleted automatically, so a deletion is fully gone within fourteen days.

What you can ask for

Write to zohaibrashid062@gmail.com and you can ask for a copy of everything held about you, a correction, or deletion of your account and its data. We will do it, and say when it is done.

You can also disconnect a Google account at any time, either from the Email Accounts page here or from your Google account's security settings. Disconnecting stops any further access immediately.

Security

Traffic is encrypted with HTTPS. Mailbox credentials are encrypted before being written to disk. Passwords are stored as scrypt hashes with a per-password salt. Each account's data is a separate database file, so one account cannot query another's.

No system is perfect, and we do not claim otherwise. If something goes wrong that affects your data, you will be told.

Changes

If this policy changes, the date at the top changes with it. Anything that materially changes what happens to your data will be sent to you by email rather than quietly edited here.