Privacy
How Rovebound handles local Journey State, current-data requests, aggregate metrics and contact information.
1. What stays on your device
Rovebound is designed to be local-first. Journey State can be stored in your browser's local storage so your Arc, selected interests, dates, planning preferences, Rover identity, local Group Arc Lite information, tasks and related planning state can persist on that device. Rovebound does not use that local state to build advertising profiles.
You can clear local Rovebound state using browser storage controls. Exported .rove files, printed/PDF guides and shareable artifacts are files you create and control.
Community accounts and private trips
When you request a Community sign-in code, we send your email address to Resend to deliver that code. Codes expire after 10 minutes. We store a protected code verifier, short-lived browser verification data and retry controls. After verification, we store your email address, member identifier, verification time and the version of the Community guidelines accepted. Your email is not displayed publicly. Signing in sets a secure, HttpOnly session cookie that lasts up to 30 days; signing out revokes that session.
Community drafts saved to “This browser” stay on that device. Choosing “My account” uploads the trip fields you enter to Rovebound's Cloudflare database so you can access them on other devices. Account trips are private and retained until deleted; you can delete individual account copies in Community. Signing in alone does not upload browser drafts. Browser copies remain after sign-out and account-copy deletion. Your private drafts are not sent to Rovo by the Community trip suggestion form; it sends only the trip preferences you explicitly submit.
Community contributions are stored separately from private trip drafts. Saving a contribution keeps it private; submitting it sends it to Collective admins for review. Approved text, your display name and AI or promotional disclosures become public. Moderators may edit or remove posts. Withdrawing removes a post from the public feed, but submissions, reports and decision records remain stored for moderation. Reports are visible to admins, not the public. Rovo-generated Community drafts require human approval.
For account access, correction or account deletion requests, contact contact@rovebound.ca. Sign-in emails do not subscribe you to marketing.
2. Current-data requests
When you ask Rovebound to validate or enrich a route, the site can send the minimum route information needed to the Rovebound server-side Worker. Depending on the feature, that can include destination country codes, route stops, travel dates, transport mode, origin/return point, party size and the travel-document country you entered.
These request bodies are used to produce the requested safety, logistics, calendar, geocoding or flight result. The V2.8 application code does not write those route request bodies, private notes, itinerary details, origin, passport number or raw Rover quiz answers to the D1 metrics database. Current-data providers may process the limited request information necessary to answer the check under their own terms and privacy practices.
3. Rover Census
If you complete the Rover classification, Rovebound may increment the aggregate count for the resulting Rover. D1 stores totals such as bramble: 142 rather than one row per classification. The server does not store your raw quiz answers in the Rover Census and does not keep individual classification-event history.
4. Partner-click analytics
Rovebound uses privacy-minimal aggregate counters, including daily aggregate totals, to understand whether useful partner actions are being used. Analytics are restricted to an approved partner identifier, a broad product stage and an allowlisted category-level signal such as flight_need, experience_need, road_mobility, two_wheel_mobility, connectivity_need or gear_need.
Rovebound does not store a free-text click reason, destination/place name, itinerary, origin, travel-document details or per-click event history in this analytics table. The browser also does not retain a Rovebound partner-click history in Journey State.
5. Product-use and website analytics
Rovebound may use privacy-minimal first-party analytics to understand whether core features are useful. The Rovebound D1 analytics table stores daily aggregate counters for allowlisted actions such as starting the Personal Legend planner, claiming an Arc, starting Group Arc Lite, asking ROVO a question, opening Mission Control or opening the Gear + Travel Atlas. These counters do not store a user identifier, IP address, destination, route, travel dates, itinerary, quiz answers, free-text questions or per-event history.
Rovebound may also use Cloudflare Web Analytics for first-party website traffic and performance measurement, such as page views, visits, referrers, broad geography, device/browser categories and performance information. Rovebound does not use this analytics layer to build advertising profiles or rank recommendations by commercial value.
6. Hosting, security and technical request data
Rovebound's production site and Worker are configured for Cloudflare infrastructure. As with ordinary web delivery, Cloudflare and related infrastructure can process technical request data such as IP address, requested URL, time, browser/network information and security signals in order to deliver and protect the service. Retention and processing can depend on the active Cloudflare configuration.
Rovebound does not intentionally place advertising cookies or use planner choices to create third-party advertising profiles in this V2.8 candidate. If materially different analytics, marketing, surveys, accounts or tracking are added later, this notice must be reviewed before activation.
7. Affiliate links and independent sites
Following an affiliate or provider link takes you to an independent service. That provider can receive normal request information and may use its own cookies or tracking under its own privacy notice. A referral identifier can attribute a qualifying action to Rovebound. Your payment details stay with the provider; Rovebound does not need them to receive an affiliate commission.
8. If you contact us
If you email Rovebound, we receive the email address, message and other information you choose to send. We use it to respond, investigate the issue and keep records where reasonably needed or required by law. An inquiry does not automatically subscribe you to marketing.
9. Use, disclosure and safeguards
Rovebound uses information for the purposes described here and other purposes permitted by law. Service providers process information only as needed to provide the relevant service. Rovebound does not sell personal information.
We use safeguards appropriate to the information and restrict access to operational systems. No storage or transmission method is perfectly secure. If a breach affects information under Rovebound's control, we assess and handle it in accordance with applicable law.
10. Retention
Local Journey State remains on your device until you or the browser removes it. Aggregate Rover, partner and product-use counters are retained as operational totals and do not contain per-event history. Correspondence is kept only as long as reasonably needed for the inquiry, disputes, security, legal obligations or ordinary business records.
11. Access, correction and concerns
Contact the Rovebound Privacy Lead at contact@rovebound.ca to ask about privacy practices, request access or correction of personal information under Rovebound's control, withdraw consent where applicable, or raise a concern. We may need proportionate information to verify the request.
You may also contact the Office of the Privacy Commissioner of Canada. Other rights may apply depending on where you live.
11. Changes
Rovebound will update this notice when its information practices materially change. A new feature is not treated as permission for unrelated collection or tracking.