Privacy policy
Last updated 7 September 2026.
This describes what Tiepost collects, why, who sees it, and how long we keep it. It is written against what the software actually does rather than against what a marketplace might do.
What we collect, and why
| What | Why |
|---|---|
| Email address | Sign-in. We use Sign in with Apple and Google; we never see or store a password. |
| Mobile number | So a host can reach a driver about a handover, and so we can reach either of you if a trip runs over. Verified by a one-time code. |
| Name, date of birth and home address | A.R.S. § 28-9610 requires a car sharing programme to record the driver's name, address, licence number and place of issuance before an agreement. |
| Driver's licence | Verified before you can book. We keep the issuing state, expiry, place of issuance and the last four digits only — never the full number. |
| Last four digits of a Social Security number (optional) | To identify you if a vehicle is damaged or not returned and we have to follow it up. We never ask for the full number and never store one. |
| A licence photograph and a selfie | Used once, to check the licence is genuine and that it is you. Both are destroyed as soon as the check completes — the database enforces this, not a policy. |
| Photographs of the vehicle | Condition before and after a trip. This is the evidence that settles a damage dispute. |
| Trip and location data | Where a car is parked, where a trip started and ended, and the times. |
| Payment details | Handled by our payment processor. Card numbers never reach Tiepost's systems. |
| Taxpayer identification number (hosts) | The IRS requires one before we can report what a host earns. Stored encrypted; only the last four are ever displayed, including to the host. |
Text messages
We send a one-time verification code by SMS, to a number you type in yourself,
and only after you tap to request one. One message per request. Message and data
rates may apply. Reply STOP to opt out or HELP for help.
We do not send marketing texts. Mobile numbers and SMS consent are not sold, rented, or shared with any third party for their own marketing or promotional purposes. The only third party that sees your number for messaging is the carrier and our messaging provider, and only in order to deliver the message you asked for.
Who sees what
What a host sees about a driver
Their first and last name, whether Tiepost verified their licence and identity, the issuing state of that licence, and how many trips they have completed. A host never sees a driver's address, date of birth, email, phone number, licence number, or any part of a Social Security number.
What a driver sees about a host
A first name for an individual host, or the full name of a registered business; how long they have hosted, how many cars they list, how often they accept requests and how quickly they respond. Nothing a host writes about themselves, because every figure is derived from what actually happened.
Insurers
A.R.S. § 28-9605 entitles an insurer to trip records on request, and we provide them. If a claim is made, the insurer or their adjuster receives the trip record for that trip, including the driver's name.
Everyone else
We do not sell personal information. We do not share it for anyone else's advertising. We disclose it only to the service providers who make Tiepost work (payment processing, identity verification, messaging, hosting), to an insurer as above, or where the law requires it.
How long we keep it
Two different clocks, on purpose.
- Records of what happened — trips, verifications, agreements, the driver record § 28-9610 requires — are kept for six years, because § 28-9605 sets that floor and gives insurers access within it.
- Sensitive raw material — the licence photograph, the selfie — is destroyed as soon as the check that needed it has finished. We keep the fact that a check passed and a fingerprint of what was examined, not the image.
Your choices
- Ask us what we hold about you, and we will tell you.
- Correct anything wrong. Your details can be edited in the app at any time; correcting them creates a new record rather than erasing the old one, because the old one may be part of a trip record we are required to keep.
- Ask us to delete your account. We will, except for records § 28-9605 requires us to retain, and we will tell you which those are.
- Stop the texts by replying
STOP.
Security
Traffic is encrypted in transit and the database verifies its server certificate rather than merely encrypting to it. Taxpayer identification numbers are encrypted at rest with a key held separately from the database. Verification codes are stored hashed, never in readable form. Photographs of vehicle condition are held in private storage that is not publicly reachable.
Children
Tiepost is not for anyone under 18, and we do not knowingly collect information from anyone under 18.
Changes
If this policy changes materially we will say so in the app before the change takes effect.
Contact
Questions about this policy, or a request about your own information: armona.office@gmail.com.