Privacy
Privacy Policy
What VergePass actually collects, why, and how long it's kept — specific to real BC driving-school data, not generic SaaS boilerplate.
What we collect
What we collect, and why
VergePass is compliance and scheduling software used by BC driving schools. When a school uses VergePass, it enters real student data into the system to run its day-to-day operations and to produce the compliance records ICBC (Insurance Corporation of British Columbia) requires.
Student records: first and last name, date of birth, email, phone, address, licence number, current and target licence class, knowledge-test status, and — for students under 19 — a guardian's name, phone, email, and recorded consent.
Lesson records: which student, instructor, and vehicle were involved, the date, time, and duration, the curriculum topic covered, the fee charged, and sign-off details once a lesson is complete.
School and account data: the school's own name, address, and ICBC licence number, and each staff account's real name, login email, and role — plus, for instructor accounts, their real ICBC instructor licence number and expiry.
Activity log: actions taken inside the app — including sign-ins and account lockouts — are recorded in an activity log: who did it, when, what changed, and the IP address the request came from (a background job has none, by design). See how that log works in full on our Compliance page. The log itself is kept for at least 6 years.
- Student records
- Lesson records
- School & account data
- Activity log (sign-ins, lockouts, changes)
- Payment data (via Stripe)
Retention
How long we keep it
There's no delete option for a lesson in the product — only status changes (cancelled, no-show, and so on). Once a lesson is signed off or completed, the database itself refuses to delete it too.
Student records are protected the same way once they have real history: a student with any real lesson, enrolment, or payment on file can never be deleted, only marked withdrawn. A student profile with zero history — a duplicate entered by mistake, for example — can be removed, but removing it leaves a permanent activity-log entry behind: the student's name, birth year, and status at the time. The database refuses to edit or delete that entry, same as every other entry in the log.
Audit export records are held to a stricter standard again: our own audit export table's real database constraint is "Audit export records are never deleted — 6-year retention applies," matching ICBC's own retention expectations for driving-school records. The activity log as a whole is held to that same standard: append-only at the database once written, apart from one narrow exception (the link to a deleted user account being cleared), and kept for at least 6 years.
6 years
How long a completed audit export record is retained — enforced at the database level, not just a policy on paper.
Payments
How payments work
VergePass processes two real kinds of payment. When a family pays an invoice online, they're taken to a real Stripe Checkout page — card details are entered there, directly with Stripe, and never touch VergePass's own backend at all. When a school pays its own VergePass subscription, that's also billed and processed through Stripe.
VergePass itself only ever stores a reference to the transaction (a Stripe customer ID, a payment confirmation) — never a card number, expiry date, or CVC.
We don't see or store your card details, ever — Stripe handles that part directly.
Declarations
How declaration data reaches ICBC
When a school completes a student's programme, VergePass generates a real Declaration of Completion document — containing the student's name, programme details, and every instructor who taught them, each listed with their own real ICBC instructor number and hours. It declares that the student has met the requirements of the applicable programme "as required by the Insurance Corporation of British Columbia (ICBC)."
The school provides this document to ICBC directly, as a normal part of a student's licensing process. VergePass itself does not operate any automated, direct data transmission to ICBC — we produce the real document; the school submits it.
This site
This marketing site specifically
This site (vergepass.ca) uses Google Analytics to understand real visitor traffic — pages viewed, general location, and device type. It does not run inside the authenticated app itself, and it never has access to any real student, lesson, or school data. The Contact page's form sends your message directly to us by email; we don't add you to any mailing list from a contact submission.
Links from inside the VergePass app back to this site — the "Powered by VergePass" mark in an email, or on a public booking page, for example — carry a tag saying which part of the product the click came from. No school is identified by it.
This marketing site's own analytics never sees real school or student data — that's a separate system entirely.
Services we use
Services we use to run VergePass
Stripe handles the two real payment flows described above — a family's invoice payment and a school's own subscription billing.
Resend sends the app's real transactional email — things like a drafted compliance alert once a staff member sends it, or a password reset. This marketing site's own Contact form is sent separately, from a dedicated sending address on its own subdomain, never mixed with a school's own app data.
Cloudflare sits in front of the app for DNS and proxying of traffic to VergePass. A nightly, offsite database backup is kept separately — backups are stored with a cloud storage provider. We're not making any claim about how either one is protected at rest — that's a real, separate improvement we have planned, not something already true today.
VergePass runs on infrastructure we operate with a hosting provider, and some of the service providers listed here may process information outside Canada. We don't claim that data stays in Canada.
- Stripe — payments only
- Resend — transactional email
- Cloudflare — DNS & proxying
- A cloud storage provider — offsite backup storage
- Google Analytics — this site only
Cookies
The cookies the app actually sets
Signing in to VergePass sets two real cookies — vp_access and vp_refresh — each marked HttpOnly and SameSite=Strict, and Secure once live in production. Neither is shared across subdomains: each is set only for the one host you actually signed in on.
This marketing site itself sets no cookie of its own. The Google Analytics script described above does set its own first-party cookies once it loads, the same way it would on any site that uses it.
Two sign-in cookies for the app itself, nothing from this marketing site beyond Google Analytics' own.
Questions and legal note
Questions about your data
If you have a question about what VergePass holds or how it's used, email us directly at [email protected] — we read every message.
This page describes what VergePass actually does, as accurately as we can state it. It is not a substitute for professional legal review — given the regulated, personal nature of the data involved, a school considering VergePass for real student records should have its own legal counsel review this policy against its specific obligations.