Security
Responsible operation starts with clear boundaries.
Two scopes, described separately: the public website, and the product as deployed for customers. Only verified controls are listed.
This website
Informational only
- No accounts and no payments
- One form, the demo request
- Delivered as one email to our mailbox
- HTTPS only, no framing
The product
Working today
- By invitation, a one-time setup link
- Hashed passwords or a passkey
- A salesperson sees only their own book
- No path that sends to a prospect
1
In the product. Working today.
- Access is invitation only
- Accounts are created by invitation with a one-time setup link. There is no self-service signup. A deactivated account is refused on its next request, everywhere.
- Sign in
- Passwords are stored only as salted, iterated hashes (PBKDF2-HMAC-SHA256, 600,000 iterations, a random salt for each user), never in plain text. Passkeys (Touch ID, Face ID, Windows Hello) can be used to sign in instead of the password. Failed attempts are limited per address and per account, and the counters survive a deploy.
- Sessions
- Sessions live in HTTP-only, secure cookies. The server keeps only a hash of the session token, ends every session sixteen hours after sign-in, and an administrator can end a person's sessions at any time.
- Roles and visibility
- Roles are additive and explicit. A salesperson-only account sees its own book and nothing else, across every screen, report, and export. Management roles see the team.
- The audit trail
- Every change to a lead writes a revision row recording who changed what. Reporting reads from those rows, which is what makes the numbers trustworthy.
- Data and backups
- Product data lives in a managed cloud Postgres database, which the application reaches over the hosting provider's private network. A full dump is taken every night and restored onto a second machine under our control, where its schema is checked against the application, and a dump is taken before every schema change. Multi-company installations keep each company's configuration, content, and data separate in the same database, with the separation enforced by the application on every read.
- Transport and headers
- The application is served over HTTPS only, with strict transport security, no framing, no content-type sniffing, and a content security policy enforced on every response.
- Seller control
- External outreach stays subject to salesperson review and personal sending. There is no path that sends to a prospect.
2
This website. Informational only.
- No accounts, no payments
- No user accounts, no payments, no file uploads and no self-service signup. The only input is the request-a-demo form.
- The demo form
- A submission is validated, then delivered as one email to our mailbox. No database, CRM, analytics, advertising or marketing automation sits behind it.
- Providers and transport
- Hosting, edge security and email providers are named in the privacy notice. HTTPS only, strict transport security, no framing, no sniffing, a restrictive permissions policy.
Not claimed here: certifications, penetration test results or formal conformance. When an evaluation needs deeper evidence, we walk through it directly, under NDA where appropriate.
Request a security review
Report a website security concern to support@revbraid.ai. Please leave sensitive data out of the first message.