
A record you can check.
People make real decisions on what Cardog tells them about a vehicle, so every fact we serve points back to where it came from. We hold your data to the same standard. This page says what we do and where to find the documents behind it.
- Company
- Canadian, based in Newmarket, Ontario
- SOC 2
- Preparing for our first audit
- Infrastructure
- Canada and the United States
- Staff sign-in
- Two-factor required
- Code changes
- Second-person review, every repository
- Backups
- Daily, with restores tested
Compliance
Where we stand on audits and privacy law, said plainly. We'd rather tell you what we don't have yet than let you assume it.
SOC 2In preparation
We're preparing for a SOC 2 audit against the Security criteria, starting with a Type I report and following with a Type II. We don't have a report yet and won't suggest otherwise. We'll post it here when we do.
Canadian privacy lawFollowed
We handle personal information under PIPEDA and the provincial laws that apply, including Québec's Law 25. We have a named Privacy Officer, and our privacy policy says what we collect, why, and who we share it with.
Our providersReviewed
The cloud, database and payment providers we build on hold their own SOC 2 and ISO 27001 certifications. We track each provider's certifications in our provider register. The full list, with what each one receives, is in the trust room.
Data
How your data is protected, where it lives, and how it leaves when you ask.
Encryption
Every connection to Cardog uses TLS. Our database and storage providers encrypt data at rest.
Where it lives
Our infrastructure runs in Canada and the United States, with established cloud providers. Files and the website are served through a global edge network.
Provider types and regionsBackups
The database is backed up every day, and we test restoring those backups and record the results.
Deletion
Delete your account in settings or ask us. Documents provided under an agreement are deleted with a signed certificate.
Separate workspaces
Each organization's documents, vehicle lists and threads sit in its own workspace. Anyone outside it gets a not-found page, not a locked door.
Data agreements
Most organizations we work with sign an agreement that sets how their data is used, kept and deleted. Send us yours, or ask for ours.
Ask for our agreementAccess
Who can get in, on your side and ours, and how every change to the product is checked.
No passwords
Sign in with a passkey, a one-time code by SMS or email, or Apple, Google or GitHub. There's no password to leak or reuse.
Roles and invitations
Nobody joins an organization without an invite. Owners and admins set each member's role and can remove access at any time.
Verified domains
An organization can verify its email domain, so people on that domain can join and nobody else can claim it.
API keys
Keys belong to an account or organization, can be revoked at any time, and every request is logged against the key that made it.
Staff two-factor
Everyone on the team signs in to our code host and database with two-factor authentication, and access is granted by role.
Reviewed changes
No change reaches production until a second person approves it. Secret scanning and dependency alerts run on every repository.
Controls
What we have in place today. The full control set, with the evidence for each, is in the trust room.
Access
- Two-factor sign-in required on our code host and database
- Staff access to production limited by role
- Passwordless sign-in for every customer account
Changes to the product
- Every change goes through a pull request
- A second person approves before it merges
- Secret scanning on every push
- Automatic alerts and fixes for vulnerable dependencies
- API releases roll out through staging and a canary, with automatic rollback
Data protection
- Encrypted in transit (TLS) on every public endpoint
- Encrypted at rest by our database and storage providers
- Each organization's data kept in its own workspace
- Deletion on request, with a signed certificate for documents under agreement
Resilience
- Daily database backups
- Restores tested, results recorded
- Uptime monitoring and a public status page
Providers
- Register of every provider, what it receives and its certifications
Providers
We use what you give us for the reason you gave it to us, and nothing else. We don't sell it. We share it only with the providers who run the service for us, or when the law requires it.
These are the kinds of providers we use. The trust room names each one, says exactly what it receives, and has its certifications. The privacy policy covers what we collect and why.
| Provider type | What it does for us | Where |
|---|---|---|
| Cloud hosting and database | Runs the app, the API and the databases | Canada and the United States, with a global edge network |
| Payments | Card payments and subscriptions on the web | United States |
| Email and SMS | Sign-in codes and account email | United States |
| AI model providers | Answers in the Cardog assistant | United States |
| Error tracking and analytics | Finding bugs and understanding product use | United States |
| Maps and web search | Maps, locations and live answers in the assistant | United States |
Documents
Public
In the trust room
- Information security programOur twelve policies: access, change management, secure development, logging, incident response, continuity, vendors, risk, retention and more.
- System descriptionHow Cardog is built, where data flows, and which controls apply where.
- Provider registerEvery provider by name, what it receives, where it processes, and its certifications.
- Security questionnairePre-filled answers to the standard questions, as a spreadsheet you can drop into your review.
- Backup and restore recordsOur backup setup and the results of each restore test.
- Proof of insuranceOur certificate of insurance.
- Sample deletion certificateWhat you receive when we delete documents provided under an agreement.
The trust room is free. You agree to a short confidentiality term first, unless you've already signed an agreement with us. Email us with your name, your organization and what you're reviewing, and we'll set you up.
Questions reviewers ask
Where is my data stored?
With established cloud providers in Canada and the United States. Files and the website are served through a global edge network. The trust room lists every provider and where each one processes data.
Is my data encrypted?
Yes. Every connection to Cardog uses TLS, and our database and storage providers encrypt data at rest.
Do you have a SOC 2 report?
Not yet. We're preparing for a SOC 2 audit against the Security criteria, starting with a Type I report. Until then, the trust room has our written program and the evidence behind it.
Who at Cardog can see my organization's data?
Only staff whose role needs it, signed in with two-factor authentication.
Can we sign our own agreement or data terms?
Yes. Most organizations we work with sign an agreement that sets how their data is used, kept and deleted. Send us yours, or ask for ours.
How do I get my data deleted?
Delete your account in settings, or write to privacy@cardog.app. For documents provided under an agreement, we delete them and send you a signed certificate.
What happens if there's a security incident?
If an incident affects your data, we tell you in writing, within the time your agreement sets and the law requires.
Can we send you our security questionnaire?
Yes, but start with ours. The trust room has pre-filled answers to the standard questions, and we'll fill in whatever yours asks beyond them.
Security updates
- November 18, 2026Two-factor sign-in is now required for everyone on our code host and our database.
- November 18, 2026Every repository now requires a pull request and a second person's approval before a change merges.
- November 18, 2026Vulnerable dependency alerts and automatic fixes are on for every repository.
- November 18, 2026Database restore test passed; results recorded.
Found a security problem?
Email security@cardog.app with what you found, how to reproduce it, and how to reach you. We'll reply within two business days and keep you posted until it's fixed.
Please give us reasonable time to fix it before you go public, and don't access, change or delete anyone else's data while you test. If you stick to that, we won't take action against you. Our machine-readable contact is at /.well-known/security.txt, and live status and incident history are at status.cardog.app.


