Security & trust
Built for data you can’t afford to lose.
Blipbind holds inspection records, asset history, and field evidence that has to stand up to audit. This overview describes the controls that protect that data — in transit, at rest, and in the way access is granted. It doubles as a reference you can share with your security team; use Download as PDF for a printable copy.
Encryption everywhere
- All traffic between clients, our API, and databases is encrypted with TLS. Plaintext database connections are refused in production.
- Data is encrypted at rest, including database storage, object storage for photos and audio, and backups.
- Presigned, short-lived URLs gate every media download — links expire and can't be shared indefinitely.
Tenant isolation & data residency
- Every record is scoped to a company and filtered on that boundary on every request — one company can never read another's data.
- Standard-tier data lives in Blipbind's managed cloud, isolated per company and backed up daily.
- Enterprise customers can bring their own database (BYOD): operational data — reports, assets, org structure, access control — lives in a PostgreSQL database you own, in your region, under your retention rules.
- Under BYOD, authentication data (emails, credentials, OAuth links) intentionally stays on Blipbind's control plane, so sign-in and password reset keep working even if your database is briefly unreachable. Your operational data resides with you.
Access control (RBAC)
- Granular, policy-based permissions govern every action — who can view reports, approve them, manage assets, invite teammates, or change roles.
- Roles and groups are configurable per company; the effective permissions are computed server-side and embedded in each session, never trusted from the client.
- Individual accounts get an isolated workspace with no cross-tenant surface at all.
Authentication
- Sign in with email and password or federated identity — Google, Microsoft, or Apple.
- Sessions use short-lived access tokens (60 minutes) so a leaked token has a narrow window; the platform can revoke a session at any time.
- On mobile, sessions resume with a rotating refresh token. Users can raise their security level so that resuming a lapsed session requires Face ID or a fingerprint — the token is exchanged only after a successful biometric check.
Infrastructure & availability
- Blipbind runs on AWS. Databases are managed, encrypted, and backed up daily with point-in-time recovery.
- A failed schema migration on a dedicated database quarantines that tenant — requests pause rather than run against a mismatched schema — and alerts our team.
- Field capture works fully offline: photos, voice notes, and reports are stored on-device and sync when connectivity returns, so an outage never costs you evidence.
Data ownership & deletion
- Your data is yours. Account deletion severs every sign-in method, drops group memberships, releases the email, and scrubs personal data.
- Records that must be retained for audit integrity are kept only as long as necessary and remain scoped to your company.
Reporting a vulnerability
If you believe you’ve found a security issue, we want to hear from you. Email admin@blipbind.com with details and we’ll respond promptly. Please give us a reasonable window to remediate before public disclosure.