Security & privacy
Bank confirmation letter data is sensitive commercial information. These are the controls the product is built around. Any sample records shown on this site are fictional and marked DEMO.
Single-purpose tokens
Applicant and banker links authorize one request and one action. Only cryptographic hashes are stored, never raw tokens.
One-time codes
Sensitive content is hidden until an emailed code is verified. Codes expire in 10 minutes and are never logged or stored in plaintext.
Expiry and revocation
Links default to 14 days and can be shortened, revoked or locked after repeated failures. Every access attempt is recorded.
Tenant isolation
Row Level Security scopes records to active organization membership. One vendor organization can never read another's data.
Least privilege
Salespeople cannot open bank responses, sensitive attachments or private credit notes. Users cannot change their own role.
Private documents
All files live in private storage and are served only through short-lived signed URLs. Account numbers are masked in UI and logs.
Honest verification
A response is only labelled verified when the defined control was completed. Email replies are never auto-verified.
Append-only audit
Status changes, access events, signatures and downloads are written to an audit log that ordinary users cannot edit or delete.
Compliance summary
The answers a procurement or IT reviewer will ask for, in one place.
- Data residency
- Application data and documents are stored in Canada. Verification is Canada-only: applicants, banks and branches are Canadian, and amounts are in CAD.
- Encryption
- Data is encrypted in transit with TLS and at rest by the managed database and object storage. Documents are never served from a public URL.
- Access control
- Access is scoped to your workspace by row-level security, with least-privilege roles inside it. Role changes are made by an owner and written to the audit trail.
- Authentication
- Workspace users sign in with email or Google. External parties — signers, bankers and suppliers — act through single-purpose links protected by one-time codes, never a shared password.
- Retention
- Credit files and their documents are retained for as long as your workspace is active, so you can evidence the basis of a past decision. Deleting a record removes it and its documents; the audit entry that it was deleted remains.
- Privacy
- We handle information on your behalf under a signed customer authorisation. We do not sell data, and we do not build a shared bureau file from your customers' information.
- Subprocessors
- Managed cloud hosting and database, transactional email and SMS delivery, and payment processing. The current list is available on request.
- Incident response
- Security issues can be reported through the contact page and are triaged the same business day. Affected customers are notified directly.
Pre-launch commitments
Privacy impact, threat risk, retention, incident response, malware scanning, penetration testing and Canadian legal review of the authorization, consent and e-signature process are completed before any production use with real businesses.