Security

Your customer list is the business.

Your customers, your prices and your margins are what the shop down the road would most like to see. Velotri was built security first: identity, separation between shops, roles and automated tests came before any feature, and every feature since has had to pass them.

What protects your data

All of these are enforced on our servers, not just by hiding buttons in the app.

identity

Two-step sign-in, required by the database

Owners and staff sign in with a password and an authenticator app. The database checks that the second step happened before it returns any shop data, so a stolen password alone opens nothing. Computers can be remembered for a limited time and removed from anywhere.

separation

One shop can never see another

Every table carries access rules by shop and by role. Which shop a request belongs to is worked out on the server from verified membership, never from anything the browser sends. A dedicated test suite makes thousands of attempts to cross between shops on every change. Owners with several locations see them together without the locations' records ever mixing.

roles

Roles that mean something

Owner, manager, sales, front desk and technician see and do different things, and those limits are held by the server. An installer never sees prices, invoices or margins. Discount limits, team changes and settings are the owner's to set.

audit

A tamper-evident activity log

Important actions are written to an append-only log. Each entry includes a SHA-256 hash of the entry before it, so any change to history breaks the chain and is detected.

attempts

Limits on guessing

Sign-in, two-step codes and customer links all have attempt limits, so passwords and links can't be guessed by brute force.

browser

Strict pages, no trackers

Every page carries a strict content security policy and modern security headers. Injected scripts don't run, the app can't be framed by another site, and there are no third-party analytics watching your customers.

sensitive actions

A fresh code for the big decisions

Connecting a lead source, rotating its key and other sensitive owner actions ask for a two-step code entered in the last few minutes, so an unattended laptop can't hand your shop to someone else.

signatures

Approvals that hold up

When a customer approves a quote or signs a waiver, Velotri keeps a fingerprint of exactly what they agreed to and when. If anyone later says the terms were different, the record shows whether anything changed.

assistant

AI that can't act on its own

Sales Intelligence can only suggest changes, each backed by the customer's own words. It has no way to message a customer, send a quote, book a job or take a payment, and text inside a message can't instruct it.

location

Installer location, only on a tap

For mobile installs, a phone's location is taken once when the installer taps a step, only after they've read the notice, never tracked continuously. Sales and the front desk see times, never locations, and old locations are cleared automatically.

customers

Private links for your customers

Quotes and pictures are shared on long, random links with their own tighter rules, so a customer sees their own job and nothing else.

payments

Card details stay with Stripe

Subscriptions are paid on Stripe's hosted checkout. Card numbers are typed into Stripe's page and never reach Velotri. Stripe's notices to us are signed and checked before we act on them.

secrets

Keys kept out of the code

Every key lives in a secret manager, never in the source. If one ever leaks, there's a written runbook for rotating it.

messaging

A gate in front of every message

Texts and emails to your customers pass a compliance gate that checks consent and opt-outs first. A message the gate refuses is never sent.

How changes get made

A feature is done when its tests pass, not when its screen exists. Every change is tested against the database's access rules, scanned for leaked keys, and checked for leaks between shops before it reaches you. A whole job, from enquiry to final payment, is run end to end by an automated test with every role signed in.

  1. Owned end to end.

    Source code, build, hosting, database, secrets and integrations are controlled by Velotri, not rented from a page builder.

  2. Audited in writing.

    The system is audited against its own security requirements, and every finding is tracked until it is closed.

  3. Runbooks before incidents.

    Leaked keys, account takeover, a broken activity-log chain, a lost authenticator: each has a written, step-by-step response.

Reporting a problem

If you believe you've found a security problem in Velotri, please report it privately to security@velotri.app. Please don't open a public issue.

Tell us what you found and how to reproduce it, using your own test account only. If you come across another shop's data, stop, don't keep a copy, and say so in your report. A person reads every report, and we'll credit you in the fix notes if you'd like.

Questions about security?