Accountability and contact
StationHop is accountable for the personal information under its control. The StationHop Privacy Officer is the accountable privacy role and may be contacted at privacy@stationhop.ca.
Privacy questions, complaints, access or correction requests, consent withdrawal, and deletion requests may be sent to privacy@stationhop.ca. StationHop verifies the requester before disclosing or changing account information.
Information collected
Account data includes email address, public display name, authentication records, and account status.
Adult-profile data includes the time and method of the 18-plus check, phone number, an optional emergency contact with permission evidence, and policy acceptance evidence. The exact date of birth is checked and discarded rather than stored.
Driver data includes eligibility attestations, application and review status, vehicle make, model and colour, trip details, private direct-cost estimates, and approval audit events.
Marketplace data includes driver-entered public start and destination addresses, recommended stations and permissions, rider-proposed public pickup and drop-off addresses, contribution proposals, seat requests, accepted messages, cancellations, reports, moderation notes, and technical records created by service providers. These addresses and travel times can reveal personal travel patterns even when the locations are public. Do not enter home addresses or another person's private information. The pilot does not collect licence or insurance document uploads or intentionally collect payment-card or banking details.
If you enable Google Maps address suggestions, StationHop sends the partial street-address text you type and a randomly generated session token to Google before you save a trip or send a request. If you choose Compare route distance, StationHop sends the driver route and selected or proposed public meeting locations to Google Maps even when address suggestions are off. Google may process this information outside Canada under its Privacy Policy. StationHop stores the selected public address with the trip or request. Published driver points are visible to eligible signed-in adults; rider proposals are visible only to that rider and the trip driver.
Purposes and consent
Information is used to create and secure accounts, enforce the 18-plus rule, publish and match independently planned trips, compare rider-proposed public meeting locations with a driver's route, enforce the direct-cost ceiling, enable participant messaging, apply automated chat safety rules before saving, review driver applications, respond to reports, preserve policy evidence, investigate abuse, maintain security, and meet legal obligations.
Required fields are limited to the closed pilot's current operating and safety needs. Optional uses, marketing, analytics beyond basic operations, identity verification, document uploads, and payment processing require a separate review and, where required, separate consent.
Withdrawing consent may prevent continued use where the information is necessary to provide or secure the service.
Who can see information
Public visitors may see the product explanation and corridor cities, but cannot browse member profiles, exact live trips, meeting addresses, departure times, vehicles, or participant messages.
Signed-in adults with current policy acceptance may see exact driver-offered meeting points, departure times, a driver's display name, vehicle basics, and seats. Only the rider and driver in a seat-request thread may see its proposed locations, contribution proposal, route comparison, and messages. They do not receive the other member's phone number or emergency contact through the current interface.
Authorized pilot administrators may access driver applications, reports, and audit records for assigned operational purposes. Current administrators do not have blanket chat or private account-detail access. Any future case-specific conversation access requires a documented reason, need-to-know scope, and immutable access log.
Information may be disclosed to service providers under appropriate terms, or to police, regulators, courts, insurers, emergency responders, or other parties when permitted or required by law.
Storage and cross-border processing
The connected Supabase project currently runs in the us-east-1 region in the United States. Account, profile, trip, message, report, and audit information may therefore be stored or processed outside Canada and may be accessible to foreign courts, law-enforcement, or national-security authorities under applicable law.
StationHop maintains a processor and cross-border register in its Privacy Management Program and updates it when hosting, mapping, or email providers change. A Canadian-region migration will be reassessed as the pilot grows.
Retention and deletion
The current MVP does not yet run an automated retention schedule. Account, consent, trip, request, message, report, and audit records remain in the service until deletion, pilot closure, or a documented safety, dispute, security, or legal need ends.
StationHop has adopted the record categories, retention targets, request workflow, legal and safety holds, and backup-handling rules in its Privacy Management Program. The controlled pilot uses a documented manual process where automation is not yet implemented.
Consent and audit records are append-only in normal application use but are deleted when the associated authentication account is deleted unless a lawful retention obligation or hold requires a different process.
Safeguards and incidents
The MVP uses authentication, adult-only live-inventory access, row-level database security, least-privilege grants, participant-only message access, server-enforced chat rate and content rules, administrator roles, data minimization, and audit records. No safeguard eliminates all risk.
The operator must maintain access reviews, secure secret handling, dependency updates, backups, incident response, and breach records. If a breach creates a real risk of significant harm, the operator must assess reporting to the Office of the Privacy Commissioner of Canada, notify affected individuals as required, and keep the records required by applicable law.
Your choices and contact
Members may request access to or correction of their information and may ask questions, challenge compliance, withdraw optional consent, or request account deletion by emailing privacy@stationhop.ca. StationHop must verify the requester before releasing or changing personal information.
Some records may need to be retained for safety, fraud prevention, dispute handling, or legal obligations. The operator must explain any refusal and available complaint route.
The StationHop Privacy Officer manages the documented complaint, access, correction, deletion, retention, incident, and processor-review procedures for the controlled pilot.