Privacy Policy
Effective date: July 23, 2026
This policy explains what Chabad Router (“we,” “us”) collects and does with information when you use our website, web application, and mobile app (the “Service”). Plain-English summary first: we collect what’s needed to run a route-planning service, we don’t sell anyone’s data, and we don’t run third-party advertising or tracking.
1. Two kinds of people, two roles
- Account holders (organization admins and field volunteers): you give us information directly and this policy applies to you in full.
- Household members (the people organizations visit): organizations enter information about you into their directory. The organization controls that data and decides how it’s used; we process it on the organization’s behalf to provide the Service. If you want your information corrected or removed, contact the organization that serves you — or email us at hello@chabadrouter.com and we will help route your request.
2. What we collect
You provide it:
- Account details: name, email address, phone number (if you use phone sign-in), and a password (stored only as a secure hash).
- Organization details: organization name, address, timezone.
- Household directory data (entered by the organization): names, addresses, phone numbers, email addresses, household notes, labels, and visit preferences.
- Visit records: outcomes, notes, and photos taken at stops.
- Anything you send us in feedback or support messages.
Collected automatically:
- Location (mobile app): with your device-level permission, the field app uses your location to show your position on the route map, power navigation handoff, and (when your organization uses live mode) show progress to your organization’s managers during active runs. We do not track location outside of using the app.
- Usage and device data: sign-in timestamps, app version, device/browser type, and logs needed to keep the Service working and secure.
- Cookies: we use only the cookies required for sign-in sessions. No advertising or cross-site tracking cookies.
Payments: handled by Stripe. Your card number goes directly to Stripe and never touches our servers; we store only Stripe’s reference IDs and your billing status.
3. How we use information
To provide the Service (accounts, directories, routing, live progress, reports); to geocode addresses and compute routes; to process payments; to send transactional email (receipts, renewal reminders, account notices); to provide support; to keep the Service secure and debug problems; and to comply with law. We do not sell personal information, and we do not use it for third-party advertising.
4. Address processing (how routing works)
To place households on a map and compute routes, addresses are sent to our geocoding and routing providers (see §5). Coordinates and drive-time estimates come back to your organization’s account. This is a core function of the Service.
5. Service providers (processors)
We share data only with the providers that run the Service, only as needed:
| Provider | What they do for us | Data involved |
|---|---|---|
| Supabase | Database, authentication, file storage, hosting | Account + Customer Data, photos |
| Stripe | Payment processing | Billing details, card (Stripe-only) |
| Google (Maps Platform, Cloud) | Address geocoding; cloud infrastructure for route computation | Addresses/coordinates |
| PowerSync | Syncing data to the mobile app (incl. offline use) | Customer Data for your org |
| Vercel | Web application hosting | Traffic to the web app |
| Expo | Mobile app build and update delivery | App/device metadata |
Each provider processes data under its own contractual and security obligations. We will update this table when providers change (e.g., adding error monitoring or an email provider).
6. Retention and deletion
- Customer Data is kept while the organization’s account exists — including between seasons and after a plan lapses (lapsed accounts become read-only; nothing is deleted for lapsing alone).
- You can delete your own account at any time, from the web app or the mobile app (Menu → Account → Delete my account) — unless you’re the only admin of an organization, in which case you must first make someone else an admin or delete the organization. An organization’s admin can delete the whole organization from its Settings page. Both are immediate and permanent: once confirmed there is no undo and no grace period. Deleting your own account removes your login and profile; work you did while using the Service (stops delivered, notes, photos) stays with your organization but no longer identifies you, because every record that names who did something is designed to survive with the name removed. Deleting an organization first cancels its Stripe subscription — any remaining paid time is forfeited and not refunded — and then permanently deletes the organization’s data. When an organization is deleted we keep a minimal payment record — including the organization’s name, purchase amounts and dates, its Stripe customer ID, and the deleting admin’s email address — for tax and accounting. You can also request deletion by emailing hello@chabadrouter.com from the account email; we will complete verified email requests within 30 days, except for records we must keep (e.g., payment and tax records).
- Backups roll off on a fixed schedule after deletion.
7. Your choices and rights
- Access, correct, export, or delete your data: in-app where features exist, or by email. We answer within 30 days.
- Location: controlled entirely by your device’s OS permission for the app.
- Emails: transactional emails (receipts, renewal notices, security) are part of the Service; any future marketing email will include unsubscribe.
- Depending on your state (for example, Minnesota’s Consumer Data Privacy Act or the California Consumer Privacy Act), you may have additional statutory rights to access, correct, delete, or port personal data, and the right not to be discriminated against for exercising them. Use the contact below; we honor these requests regardless of whether a statute technically applies to us.
8. Security
Data is encrypted in transit; access is controlled with per-organization row-level security so one organization can never read another’s data; passwords are hashed; payment data is isolated at Stripe. No system is perfectly secure — if we learn of a breach affecting your data we will notify you as required by law.
9. Children
The Service is for adults organizing community routes and is not directed to children under 13. We do not knowingly collect personal information from children under 13. Household records may include family details entered by organizations (e.g., names of children in a household); organizations are responsible for that data (see §1).
10. Changes
We will post any changes here and, for material changes, notify the account email or show an in-app notice before they take effect.
Questions? hello@chabadrouter.com