Security
Last updated: September 11, 2026
This page describes security measures actually implemented in the current version of Deal Intake. It will evolve as the product moves toward production - see Contact for questions about your dealership's specific compliance requirements.
Encryption
- PII fields - names, addresses, license numbers, income, MFA secrets - are encrypted at the database column level (AES via a Fernet cipher), transparent to the rest of the application.
- Uploaded documents (license photos, pay stubs) are stored in S3 and automatically purged after 7 days.
Authentication
- Dealer-portal logins require email + password plus a mandatory authenticator-app (TOTP) code - not SMS, which is more vulnerable to SIM-swap and interception attacks.
- Passwords are hashed with bcrypt, never stored or logged in plain text.
- A sales rep can only ever access their own dealership's data - a valid login for one dealership is rejected for another's records.
Access logging
Dealer-portal views of customer PII (the F&I pipeline dashboard, CRM sync actions) are logged with the acting sales rep, timestamp, and IP address, in support of PIPEDA accountability requirements.
Data residency
Infrastructure is region-locked to AWS's Canada (Central) region at both the application and infrastructure-as-code layers - deploying to any other region is rejected at startup.
Third-party processors
Equifax Canada (soft credit pulls), a biometrics/liveness provider, and your dealership's CRM (DealerTrack Canada or PBS Systems). See Privacy Policy for how each is used.