Pool Car Booking by Crosstown Tech

Privacy & security

Last updated: 18 November 2026

Pool Car Booking for Microsoft 365 is built by Crosstown Tech, a software studio based in Toronto, Canada. It works on the Outlook car mailboxes (equipment mailboxes) your organization already has: one board of all cars, bookings made through Exchange, a driver's licence check, and a Return the car form. This page says exactly what it reads, what it keeps, and for how long.

What it reads

Once, with your administrator's consent

An administrator of your Microsoft 365 (Global Administrator or Privileged Role Administrator) connects the app once and grants these Microsoft Graph application permissions, and no others:

Microsoft grants application calendar permissions for the whole tenant. The app opens only the calendars of the mailboxes added as cars, and your administrator can limit the permission to those mailboxes with Exchange Online RBAC for Applications (see the help page). No mail permissions are requested: the app never reads email.

While each person uses the app

Each person signs in with their own Microsoft work account. The app asks for these delegated permissions:

Your Microsoft token stays in your browser. It is sent to our backend for one request at a time, checked with Microsoft, and never stored.

What it stores

WhatWhy
Your organization: Microsoft tenant id, name, default domain, who connected it and when, and when the car calendars were last read To keep each organization's cars apart and show when the board was last updated
People who signed in: Microsoft user id, name, email address and department, whether they are a fleet admin in the app, first and last sign-in Shown on bookings and the Drivers list; counting usage
Each car: its mailbox address and Microsoft id, and the name, plate, parking spot and odometer the fleet admin entered or the last return recorded That is the car
A copy of the car calendars: start, end, organizer's name and email, and whether a booking waits for approval, from yesterday to 15 days ahead; past bookings are kept as the car's history The board and the car history
Bookings made in the app: car, driver, times, the purpose the driver typed, and the Return the car link The board shows the purpose, which Exchange removes from the car's calendar
Returns: odometer reading, who returned the car and when, and any damage photos, with when a fleet admin marked the damage repaired Distance per trip and the car's damage history
Driver's licences: licence number, expiry date and a photo of the front Only drivers with a valid licence can book; fleet admins of the same organization can see it
Sign-in sessions: a hash of the session secret, expiring after 30 days Keeping you signed in
A short-lived Microsoft access token for your organization (about an hour) Reading the car calendars every few minutes

Photos are resized in your browser before upload (long side 1600 pixels). An uploaded photo that no licence or return uses is deleted after a day. When a driver replaces a licence, the old photo is deleted.

Who can see what

Every stored record is keyed to one Microsoft 365 organization, and the backend serves a request only for the organization of the signed-in person. Everyone in the organization who signs in sees the board: which car is booked, when, and by whom. Licence numbers and photos, the Drivers list, licence warnings on the board, damage photos and car settings are shown to fleet admins only. The administrator who connected the app is a fleet admin and can add others.

Where it is stored

Application data and photos are held on Convex Cloud, in the United States. The app is served by Vercel. It carries no advertising trackers.

Product analytics

We count how the app is used — for example, that a car was added or booked — with PostHog, at the organization level. Events carry the organization's name; no names, email addresses, licence details or typed text are sent. No cookies are set and no sessions are recorded. These web pages count visits with PostHog, without cookies.

Sub-processors

No data is sold, shared with advertisers, or used to train models.

Retention and deletion

Data is kept while your organization uses the app. Removing a car from the app stops reading its calendar; its past trips stay in the history. Bookings stay in Outlook: the app never deletes a meeting it did not just create.

To have everything for your organization deleted — cars, bookings, returns, photos, licences and the people list — email support@crosstowntech.com from an address in that organization; it will be deleted within 30 days. Removing Pool Car Booking under Enterprise applications in your Microsoft Entra admin center stops all access to your calendars immediately.

Changes

If this page changes materially, the date at the top changes with it. Continued use after a change means the updated page applies.

Contact

Crosstown Tech — support@crosstowntech.com. For privacy requests, please include your organization's name.