Privacy, in plain words

This website

This site collects nothing. There are no accounts, no forms, no analytics, and no advertising — and it stores nothing in your browser: no cookies of ours, no local storage. It is served by Cloudflare, whose infrastructure handles requests the way any host does.

On your phone

The app works phone-first. Trips, edits, and delay reports save on your device the moment you make them, and planning needs no signal. Until you join a team, your trips exist only on your phone — we don't receive them, which also means we can't back them up or restore them for you; your account and team are what carry your work beyond one handset.

Your phone also holds a private key that identifies the device. It never leaves the phone and is never backed up anywhere — a new phone gets a new key, and signing in is what reconnects it to your account.

Signing in

You can sign in with Apple or with your email address. Signing in by email sends you a short code — the code is stored only as a hash, and it expires. If you use Apple, we receive a stable account identifier from Apple; if you choose Apple's "Hide My Email," what we get is Apple's relay address, not your real one.

We keep your email address on your account — it's how you sign in on a new phone, and how we reach you about the beta. The name drivers see is whatever you type into the app.

There is no password to steal. The service never issues or stores one: each request is signed by your device, and the service keeps only the public half of that key. A copy of our database contains nothing that lets anyone sign in as you.

What the service stores when you use a team

Syncing with a partner means the service holds, for your team:

• Trip documents — routes and stops as you entered them, times, miles, fuel plans, delay reports, and the driver names you typed. Trips are shared with your team: your partner sees them, by design.
• Your team — its name, who's on it, who added whom, and when. Pairing takes both drivers' confirmation.
• Your record — which trips you drove, the teams and partners you worked with, and the tips and comments you write. Tips are attached to the places you name. Free-text fields hold whatever you put in them, so write accordingly.
• Invite codes, when you use one instead of scanning — stored only as a hash, so a copy of the database can't reveal a usable code.

Your account also holds your email address and, if you add one, your phone number — the number is there so the other half of your truck can reach you. Your email is yours alone: the roster your partner sees never includes it, and the only door that returns it answers for your own account. Your phone number is shared with your teammates, which is the point of giving one.

What the service does not store: passwords (none exist), payment details (nothing takes payment), and your device's location — the app does not read GPS today. If a future live-trip feature uses location, this page will describe exactly what's kept before that feature ships.

What we keep, honestly

Some records persist on purpose. When a driver is removed from a team, the removal is recorded rather than erased — that record is what keeps a removed device from talking its way back in. Leaving a team is recorded the same way, including whether a load was running at the time. Trip history belongs to the team that drove it.

Account deletion isn't built yet. It will be before the beta opens to drivers — nobody's real data is in the system today, and we won't invite anyone in without a working way to leave, data and all.

Third parties

Two, and only as infrastructure: Apple, to verify sign-in, and Cloudflare, which hosts this site, the sync service, and its database. There are no advertising or analytics companies involved, no tracker code in the app or on this site, and nothing here is sold or shared beyond that.

Questions

A monitored contact address ships with the beta. Until then, this page — dated and kept in step with the code — is the record of how TrueTeam treats your data.