Driving Duty

Privacy Policy

Effective date: October 2, 2026

This policy explains what information Driving Duty (https://drivingduty.com) collects, how it is used, and the choices you have.

Who we are

Driving Duty is a private carpool app run by Jed Fonner, an individual (not a company) in Fairfax County, Virginia, USA. It is used by exactly two people, Jed Fonner and his wife, to decide which driver handles each school day's dropoff and pickup runs.

The app is not offered to the public. Sign-up is not open, and any account other than the two drivers' accounts gets no access to the app's data. In this policy, "we" means Jed Fonner, and "you" means one of the two drivers using the app.

What information we collect

When you sign in with Google, the app receives:

  • Your name
  • Your email address
  • The web address (URL) of your profile photo
  • A user ID assigned by Firebase Authentication

While you use the app, it stores:

  • Which driver is assigned to each dropoff and pickup slot
  • Each slot's time and status
  • Who last changed a slot, and when

Features we may add later would also store:

  • Notes on a slot
  • Availability blocks (times a driver cannot drive)
  • Default weekly assignments
  • A device push token, if push notifications are added

The app does not store children's names. Calendar events use generic titles such as "School dropoff".

How we use it

We use this information only to run the app:

  • To sign you in and confirm you are one of the two drivers allowed to use the app
  • To show and update the dropoff and pickup schedule
  • To show who made a change and when
  • To put your assigned runs on your own calendar (see "Calendar access" below)

We may add email and push notifications about schedule changes, and a daily summary email. If we do, they would use the email address you signed in with and, for push notifications, a push token from your device.

Calendar access

The app adds calendar events for each driver's assigned runs to that driver's own personal calendar, in either Google Calendar or Zoho Calendar. It only works with a dedicated calendar named "Driving Duty" that you created yourself and shared with the app.

  • In that one calendar, the app creates, updates, reads, and deletes events for your assigned runs.
  • It does not read events in your other calendars.
  • It never connects to work calendars.

Calendar access happens only on the server, never in your browser. For Google Calendar, the app's server acts as its own Google service account, which can reach only calendars shared with it, so no Google password or key is stored. For Zoho Calendar, the access credentials are stored in Google Secret Manager.

Where it's stored and who processes it

App data is stored in Google Cloud Firestore, in the Google Cloud region us-east4 (Northern Virginia, USA). These service providers process data so the app can work:

  • Google: Firebase Authentication (sign-in), Cloud Firestore (database), Cloud Functions (server code), Firebase Hosting (serving the website), Secret Manager (storing calendar credentials), and the Google Calendar API
  • Zoho: the Zoho Calendar API, for a driver who uses Zoho Calendar

If we add email notifications, we may also use an email delivery service to send them. We would update this policy if we do.

What we don't do

  • We do not show advertising.
  • We do not use analytics or tracking tools. Google Analytics is deliberately turned off.
  • We do not sell your information.
  • We do not share your information with anyone for marketing.

Browser storage

To keep you signed in, Firebase Authentication saves your sign-in session in your browser (using local storage or IndexedDB). The app does not use advertising or tracking cookies.

Retention and deletion

We keep app data for as long as the app is in use. You can ask us to delete your data at any time by emailing support@drivingduty.com.

Deleting the app's data does not remove events already in your calendar, unless you ask us to remove them too. You can also delete the "Driving Duty" calendar yourself at any time, which removes all of its events.

Database backups may be kept for a limited time after data is deleted, and are then removed.

Children

The app is not directed to children, and children do not use it. It holds a child's school dropoff and pickup schedule, but no child's name and no child's account.

Security

Database security rules limit access to the two drivers' accounts. Data is encrypted in transit (HTTPS) and encrypted at rest by Google Cloud. No system is perfectly secure, so we cannot guarantee that information will never be accessed without permission.

Changes to this policy

If this policy changes, we will update this page and change the effective date at the top.

Contact

Questions or requests about this policy or your data: support@drivingduty.com

Back to Driving Duty