Your data, kept separate
Each company's records are separated by the database itself, not only by application code.
- Row-level security on every customer table, scoped to your organization for every request
- The application connects through a restricted database role that cannot see other companies' rows
- Covered by automated tests that try to read across companies
Signing in
Accounts are hard to guess, hard to steal and quick to expire.
- Passwords stored with argon2id, a modern one-way hash; easily guessed passwords are refused
- Authenticator-app two-factor sign-in, which admins can require for all staff
- Short sessions that renew on use; a stolen, reused sign-in token ends every session for that person
- An optional automatic sign-out after inactivity, set by your admins
- Repeated failed sign-ins are slowed and locked out
- Password reset links work once, expire within an hour and end all existing sessions
Sensitive details
The most sensitive fields are encrypted on top of the database's own protection.
- Owner and vendor tax IDs encrypted with AES-256-GCM; screens show only the last four digits
- Stored secrets such as webhook keys and lockbox codes encrypted the same way
- Full bank account numbers are never stored, only the last four digits
- Applicant screening happens on the screening provider's own form; StrivBridge stores no applicant Social Security numbers
Seeing who did what
You can review sign-ins, security events and everything the AI decided.
- A security log of sign-ins, refused attempts, two-factor changes and tax ID views, in Settings
- An AI audit log of what the assistant was asked, what it proposed and who approved it
- Support access you can see: if our team needs to sign in as one of your users, it takes a written reason, lasts about 15 minutes and shows up in your Settings
AI with a person in the loop
The assistant works for you, within limits you control.
- Record changes proposed by Rivr, the staff assistant, wait in an approval queue until someone approves them
- Anything that moves money or changes a lease waits for a person, by default
- Revenue management uses your own data only; it is never pooled with other companies'
- AI features are rate-limited so they cannot be abused from outside
Integrations
Partners and your own systems get only the access they need.
- API keys are stored hashed, can never exceed the permissions of the person who created them, and can be revoked at any time
- Webhooks are signed with HMAC-SHA256 so you can verify they came from us
- Partner apps are switched on per company and can be switched off in one click
Keeping only what you need
Old personal data does not pile up.
- Prospects who went quiet two years ago, and past residents after the retention period you set, are anonymized automatically
- Financial records are kept, as accounting rules require
- If you leave, you can export your data and then have it deleted
In the browser
The app ships with strict browser protections.
- A strict content security policy with a fresh nonce on every page
- HTTPS only, with HSTS, and protection against framing and content sniffing