Security

Your data stays yours, and stays separate

• One workshop cannot see another's data. Every record is tagged with the workshop it belongs to, and the database itself refuses to return or change a row that belongs to a different workshop. This does not depend on the application getting a filter right; the rule lives in the database and is checked by automated tests that try to break it.
• You can take it with you. Settings → Privacy & data exports everything in your account, and exports or erases a single customer when they ask you to.
• You can delete it. Deleting your workshop erases its data from the live system immediately; backups are overwritten within 30 days.
• We do not sell data, and we do not look at yours except when you ask us for help or we have to fix a fault.

Where it lives

The database, sign-in system and file storage are in the European Union (Frankfurt, Germany). The application code runs in Frankfurt too. The providers we use and where each one processes data are on the Sub-processors page.

Encryption

• In transit: every connection uses TLS 1.2 or later. Plain HTTP is redirected and browsers are told to use HTTPS only.
• At rest: the database, files and backups are encrypted with AES-256.
• Passwords: stored only as salted hashes. Nobody at RevvoHub can read your password.

Signing in

• Email addresses are confirmed before an account can be used.
• Passwords need at least 8 characters with an upper-case letter and a number.
• The sign-in cookie cannot be read by scripts running in the page and is sent only over HTTPS.
• Repeated sign-in attempts are rate-limited.

The AI assistants

• Nothing goes to the AI model until a mechanic, or a customer in the customer app, sends a message.
• When a car is attached to a mechanic's chat, we send its technical details only. The registration plate, the owner and the serial part of the VIN are left out.
• The assistant in the customer app works for one workshop and one customer at a time. It can only do what that workshop allows, every action it takes is checked again by the database, and it never receives names, contact details, registration plates or VINs.
• Our AI provider, Anthropic, does not use this content to train its models and deletes it within 30 days.
• AI processing takes place outside the EU; see the Privacy Policy for the safeguards.

The application

• Every request is checked on the server for a valid session, and every input is validated on the server.
• A content security policy and other security headers limit what a page can load and run.
• API keys and other secrets stay on the server and never reach the browser.
• No analytics or advertising scripts, and no third-party trackers.
• Server logs are written without the content of your records.

Notifications

• Notification emails say only that something is waiting for you, with a link to the app; they never contain messages or records.
• Push notifications are encrypted end to end, so the push service that delivers them cannot read them.

Backups and recovery

The database is backed up every day. Backups are encrypted and held separately from the live system.

Our people

Only the people who run RevvoHub have access to production systems, with multi-factor authentication, and only as far as their work needs.

If something goes wrong

If a security incident affects your data, we tell you without undue delay and no later than 48 hours after we become aware of it, with what we know and what we are doing about it. The details are in the Data Processing Agreement.

Reporting a vulnerability

If you have found a security problem in RevvoHub, please tell us at security@revvo-hub.com.

• Include enough detail for us to reproduce it.
• Give us a reasonable time to fix it before making it public.
• Do not access, change or delete data that is not yours, and do not run tests that degrade the service for others.

We acknowledge reports within 3 working days, keep you informed, and will not take legal action against anyone who reports in good faith and follows these rules.