How CONSEN protects your applicants' data
The controls in place today, the rules every provider connection follows, and what is still on the roadmap.
Isolation and access
Tenant isolation
Each organization's data is kept apart from every other organization's, down to database keys and file paths. Automated tests check that one workspace cannot read another's data.
Accounts per workspace
User accounts belong to one workspace. The same email address at two workspaces is two separate accounts.
Role-based access
Administrator, designer, reviewer and applicant roles. Roles are set on the server and cannot be changed by the user.
Invite-only staff
Staff accounts are created by invitation from an administrator. Nobody can sign themselves up as staff.
Data protection
Encryption
Data is encrypted in transit (TLS) and at rest on Amazon Web Services, in the US East region.
Private file storage
Uploaded documents are kept in private storage, separated per workspace, and attached to the application they belong to.
Scoped access per workspace
Every request runs with short-lived credentials limited to that organization's own data and files.
Signed applicant links
Links that let applicants without an account resume their application are signed and expire. Tampered links are refused.
Provider connections
Connections to your ID, credit, screening, e-signature and payment providers are built with you during onboarding. Every connection we build follows these rules.
Only what the step needs
A provider receives only the answers its step needs. CONSEN keeps the outcome on the application, not raw provider reports.
No card data
Payments go through your own payment account using the provider's secure payment page. Card details never pass through CONSEN.
Your keys, locked away
Provider credentials are stored encrypted for your workspace only, and never sent to the browser or shown again.
Your relationship
You contract with the provider and complete its business verification. You can revoke access at any time from the provider's side.
Records and applicants
Audit history
Every step, check outcome and decision is recorded with who acted and when. Consent is recorded with the time, IP address and terms version.
Email-confirmed applicants
People who apply without an account must confirm their email address before the application starts.
Retention you choose
Applications made without an account are deleted automatically after the period you set: 7, 30, 90 or 365 days.
Protected public forms
Public forms use CAPTCHA, rate limits and spam checks on the server.
Not in place yet
We do not hold these certifications today. They are on our roadmap, and we will say so here when that changes.
SOC 2 report
HIPAA program
GDPR program
Shared responsibilities
You decide who on your team gets access and which roles they have. You contract directly with the providers you connect, and you need a lawful basis or consent for each check you run. CONSEN acts as a processor for the applications you collect.
Have a security questionnaire?
Send it to us. We answer it with what is in place today, and we are glad to walk your team through how CONSEN handles data.