Security

1. Where data lives

Customer data is stored in the European Union (Germany) and backed up daily. Some of the companies that do part of the work, such as AI model providers, process data outside the EU; the Data Processing Agreement sets out how those transfers are protected, and customers can ask for the current list of sub-processors.

2. Encryption

• All traffic between your browser or API client and the service is encrypted in transit.
• Secrets we must store, such as mailbox passwords, mailbox authorisation tokens and integration keys, are encrypted before they are written, with a key that is kept outside the database.
• Passwords are stored only as salted one-way hashes. Nobody, including us, can read them.
• API keys are stored only in hashed form and are shown to you once, when you create them.

3. Workspace isolation

Every customer's data lives in its own Workspace, and every query is limited to the Workspace of the person asking. Automated tests check both halves: that one Workspace cannot read another's data, and that its owner still can. A request for something in another Workspace is answered as if it did not exist, so the answer does not even confirm that it does.

4. Accounts and sign-in

• Every new account is approved by a person, and its email address is verified, before it can be used.
• Repeated failed sign-ins are locked out for a period.
• The session cookie cannot be read by scripts on the page, and a session lasts at most 24 hours.
• Inside a Workspace, roles decide who can change settings and invite people.

5. Our own access

Access to the tools we use to operate Revnox is limited to named administrators, and use of them is recorded in an audit log.

6. Sending safeguards

• Sending is off in every new Workspace until the customer turns it on.
• A campaign can hold every message until a person has read and approved it.
• Before every send, the recipient is checked against the Workspace's suppression list. If that check cannot run, the message is not sent.
• Every message carries an unsubscribe link and header, and an opt-out takes effect immediately.
• An emergency stop halts all sending at once, including messages already scheduled.

7. AI and your data

AI models process the account and contact information needed to research a company and draft a message you then review. We do not use your data to train AI models, and we do not sell it or share it with other customers.

8. What we do not claim yet

Revnox is in closed beta, and we would rather be precise than impressive. We do not hold a SOC 2 report or an ISO 27001 certificate, and we have not yet commissioned an independent penetration test. The service runs in a single region, without a service level commitment during the beta.

We will update this page when any of that changes.

9. Reporting a vulnerability

If you believe you have found a security problem, please write to nikola@revnox.io with enough detail for us to reproduce it, and give us a reasonable time to fix it before telling anyone else. Please do not access other people's data or disrupt the service while testing. We will acknowledge your report and keep you informed.