Privacy Policy

Last updated November 17, 2026

This policy explains what Odomo, LLC ("Odomo", "we", "us") collects, why, who helps us process it, and what you can do about it. It covers Hosts who use Odomo to run a rental business, the renters they deal with through Odomo, and visitors to our pages. It is a beta draft and will be replaced by an attorney-reviewed policy before general availability.

1. Two kinds of people, two roles

Hosts are our customers. A Host creates a workspace and enters information about their cars, their renters and their bookings. For that information the Host decides what is collected and why; Odomo stores and processes it on the Host's behalf.

Renters interact with a Host through pages Odomo provides: a booking page, a deposit page, an agreement to sign, a license check, and the Host's text and phone number. If you are a renter, the Host is the business you are dealing with. This policy tells you what Odomo does with your information on the Host's behalf; the Host may also have their own notice.

2. What we collect

From Hosts and their team:

  • Account: name, email, password (stored hashed by our authentication provider), optional profile photo, and, if you turn it on, a two-factor authentication secret.
  • Workspace: business name, plan, operating state and city, booking-page settings, deposit rules, message templates and the rental agreement template.
  • Fleet: year, make, model, color, plate, VIN, mileage, rates, photos, home address and parking notes, maintenance and expense records.
  • Payments setup: your Stripe connected account id and whether onboarding is complete. Bank and tax details are collected by Stripe, not Odomo.
  • Your Odomo plan: the plan, its status, renewal date, Stripe's customer and subscription ids, and whether the money-back refund was used. Your card is entered on Stripe's checkout page and stored by Stripe; Odomo never sees the card number.
  • Phone: the number provisioned for your workspace and its settings.
  • Device: push-notification subscriptions you opt into, the app version, and standard server logs (IP address, browser, timestamps).

About renters (entered by the Host or provided by the renter):

  • Contact: name, email, phone number.
  • Driver's license: number, issuing state and expiry as typed by the Host or renter, and a license photo if the Host uploads one.
  • Insurance: carrier, policy number and expiry as typed by the Host, and a photo of the insurance card if the Host uploads one. Odomo does not verify insurance.
  • Identity verification (only if the Host turns it on): the result of a Stripe Identity check, namely verified or not, the name, date of birth, document type and issuing state read from the document, and flags such as an expired document. We do not receive or store the document images or the selfie; Stripe holds those under its own policy.
  • Bookings: dates, vehicle, pickup and return locations, prices, deposits and their payment status. Card numbers never touch Odomo; Stripe processes them and we store the amount, status and Stripe's reference ids, plus the card's brand and last four digits and a Stripe reference to it, so the Host can charge post-trip amounts the renter agreed to (tolls, fines, fuel, cleaning, mileage, damage) for up to 60 days after return.
  • Post-trip charges: what the Host charged after a trip, why, when, a receipt if the Host attached one, and, for tolls imported from a statement, the plate, plaza and time on the statement.
  • Agreements: the text of each rental agreement, the drawn signature, the signer's typed name and license details, and the time, IP address and device of signing. We also log when an agreement is opened and any screenshot or screen-recording attempts inside the app.
  • Messages: texts sent and received on the Host's number, and messages drafted or sent in the app, with delivery status. Phone calls answered by the AI receptionist are transcribed and the transcript is stored in the Host's inbox; audio is not retained by Odomo.
  • Inspections and damage: checklists, odometer and fuel readings, photos, videos and notes from pre- and post-trip inspections, and any damage reports.
  • Host notes, tags and an AI-generated risk summary based only on the Host's own records about that renter.
  • Leads: name, contact details and message left through a Host's booking page.
  • Vehicle location (live location is coming soon; once released, only if the Host turns it on for a car): the car's position, heading, speed, odometer and fuel or charge level, the street address we look up for a position, a 30-day trail of positions, and events such as the car moving without a booking or leaving the Host's state. During a rental this is information about where the renter has driven. It comes from the car maker's connected-car service through Smartcar or from a Bouncie device in the car.

From visitors to odomo.ai:

  • Standard server logs (IP address, browser, timestamps), and the cookies and browser storage described in section 5.
  • The live fleet map on our home page loads Apple MapKit, so Apple receives your IP address when you view it, as with the maps in the app.
  • Website demo: if you talk to the demo receptionist in your browser, your microphone audio is streamed to OpenAI to hold the conversation, and a transcript is stored in our demo workspace for up to 30 days, then deleted. We keep your IP address in memory for one hour to limit how often the demo can be used. If you call or text the demo phone number, the same 30 days apply; your phone number is stored with the conversation so Jenny can reply, but it is not shown to other visitors of the demo. Do not give the demo real personal information.
  • Car compatibility check: the year, make and model or VIN you type is sent to Smartcar's compatibility service and, for a VIN, to the U.S. vehicle database, and is not stored.

We do not use advertising trackers or third-party analytics on Odomo pages. Section 5 lists every cookie and browser storage item we use.

3. How we use it

  • To run the service: show a Host their fleet and bookings, take deposits, send agreements and links, deliver texts and emails, answer calls and texts on a Pro Host's behalf, show a Host where their tracked cars are and alert them when a car moves without a booking, and notify the Host.
  • To power AI features: when a Host uses the assistant, or the receptionist answers a renter, the relevant workspace data (for example availability, prices and the conversation so far) is sent to OpenAI to generate a reply. OpenAI's API terms prohibit it from training on this data.
  • To keep the service secure and reliable: authentication, abuse prevention, debugging, backups.
  • To meet legal obligations, including payment-network and tax rules that apply through Stripe.
  • To contact Hosts about the service. We do not send marketing to renters, and Hosts may only text renters who have asked to hear from them.

We do not sell personal information and we do not share it for cross-context behavioral advertising.

4. Who we share it with

Only providers that do a job for us, each limited to what that job needs:

  • OVH (hosting) – our servers run in OVH's Virginia data center in the United States. That includes the mail server we operate ourselves, which sends invites, agreements, pay links and confirmations (the recipient address and the contents pass through it) and receives mail sent to our support address.
  • Supabase (database, authentication, file storage) – all workspace data, in the United States.
  • Stripe (payments, payouts, Odomo plan billing, identity verification) – payment amounts and references, and for plan billing the Owner's name and email; for identity checks, the renter's document and selfie go directly to Stripe.
  • Callnode (phone numbers, texting, calls) – phone numbers and message contents on a Host's number; for AI-answered calls the audio passes from Callnode through servers we operate to OpenAI, without being recorded.
  • OpenAI (AI assistant, receptionist, transcription, speech) – the text and workspace data needed for a given request, audio for AI-answered calls, and microphone audio for the website demo.
  • Smartcar (connected-car data) – the Host's workspace id and the Smartcar account the Host signs in with; Smartcar returns the car's position and readings. Odomo pays Smartcar per connected car.
  • Bouncie (plug-in trackers) – the Host's Bouncie account authorization; Bouncie sends the device's position and readings.
  • Apple – map tiles for the maps in the app are loaded from Apple, which receives the viewer's IP address; push notifications to iPhones go through Apple's notification service with the device token and the notification text.
  • OpenStreetMap's Nominatim and OpenFreeMap – coordinates only, to turn a position into a street address and to draw the fallback map; no personal data.
  • U.S. National Highway Traffic Safety Administration (vehicle catalog) – VINs and make/model queries only; no personal data.
  • Hosting on servers in the United States.

We may also disclose information if the law requires it, to protect people or the service, or as part of a merger or sale of Odomo, in which case this policy continues to apply.

Within a workspace, owners and co-hosts can see renter records; inspectors can only see inspections for cars assigned to them.

5. Cookies and browser storage

Odomo uses only what it needs to work. We do not use advertising, analytics, social-media or cross-site tracking cookies, and no third party sets cookies through Odomo pages. Because everything below is strictly necessary or a preference you set, there is nothing to consent to or opt out of, which is why we do not show a cookie banner.

  • Sign-in cookie (Supabase, first party, names beginning "sb-"): keeps you signed in and refreshes your session. It is set only when you sign in or open the app demo, and lasts until you sign out or the session expires.
  • Theme (browser storage, "theme"): remembers light, dark or system appearance.
  • Setup checklist and prompts (browser storage): remember that you hid the setup checklist or dismissed the push-notification, add-to-home-screen or time-zone prompt ("odomo.tz.dismissed"), so we do not ask again.
  • Push token (browser storage, app only): the device token for push notifications you turned on, so we can turn them off again when you sign out.
  • Reload guard (session storage, "odomo.reloaded"): after an update, stops the page from reloading itself more than once. Cleared when you close the tab.
  • Offline copies (service worker cache): the app keeps copies of its own files and recently viewed pages on your device so it opens faster and shows an offline page without a connection. Clearing your browser's site data removes them.

Renter pages (booking, deposit, signing and license check) set no cookies unless the renter is also signed in to Odomo. Card and identity pages are served by Stripe, which uses its own cookies for fraud prevention under its privacy policy.

You can block or delete cookies and site data in your browser settings. If you block the sign-in cookie, you will not be able to stay signed in.

6. If you are a renter

  • If you give your phone number on a Host's booking page or question form, that Host may text you about your request and rental, sometimes through an AI assistant. Odomo never texts you for its own marketing.
  • You can reply STOP (or stop, quit, end, cancel, unsubscribe, revoke or opt out) to a Host's number at any time; no more texts will be sent to you from that number except one confirmation. Reply START to receive texts again, or HELP for help.
  • When you call a Host's number and an AI receptionist answers, it will say so and tell you the call may be transcribed. You can ask for a person at any time.
  • Identity verification is optional for the Host to require and for you to complete; if you do not complete it, contact the Host directly.
  • You receive an emailed summary of any agreement you sign. Ask the Host for a full copy.
  • A Host may track the location of a car you rent, through a device in the car or the car maker's service. The Host must tell you this in the rental agreement; ask them what is tracked and for how long.
  • To see, correct or delete information a Host holds about you, contact that Host first; they control it. If you cannot reach them, write to us and we will help.

7. How long we keep it

Workspace data is kept for as long as the workspace exists. Hosts can edit or remove renters' details and uploaded files in the app; to erase a renter entirely, or to close a workspace, the Host writes to us and we act within 30 days. When a workspace is closed we delete its data within 30 days, except records that must be kept for legal, tax, payment-network or dispute reasons, which are kept for as long as those rules require and then deleted. Signed agreements and their signing records are kept while the booking they belong to exists, because they may be needed in a dispute.

Vehicle position trails are kept for 30 days; the last known position is kept while the car stays linked. Alert locations are kept for 30 days; after that an alert keeps its type, time and distance moved, but not where the car was. Unlinking, disconnecting or archiving a car deletes its trail. In-app alerts (the bell) are kept for 60 days. Website demo transcripts are kept for up to 30 days. Server logs are kept for up to 90 days. Backups roll off within 30 days of deletion.

8. How we protect it

Data is encrypted in transit. Every database query is scoped to the caller's workspace by row-level security, so one Host cannot read another's records. License photos, inspection media and agreements live in private storage reachable only through short-lived signed links. Secrets are stored only on our servers. Two-factor authentication is available to every account. No system is perfectly secure; if we learn of a breach affecting your data we will notify you as Florida law requires.

9. Your choices and rights

  • Access and export: Hosts can download renters, fleet and finances as CSV from Settings at any time.
  • Correction: edit your profile and records in the app.
  • Deletion: edit or remove records in the app. Delete your own account in Settings, Delete account; a workspace's only owner closes the workspace and its data with it (https://odomo.ai/delete-account explains what goes). Or write to us to erase a renter's personal details or close a workspace; we act within 30 days.
  • Notifications: push notifications are opt-in and can be turned off on the device or in Settings.
  • Do Not Track: we do not track you across sites, so there is nothing to opt out of.

If you live in a state with a consumer privacy law (for example California, Colorado, Virginia, Texas or Florida's Digital Bill of Rights, to the extent it applies), you may have rights to access, delete, correct and port your data and to opt out of sales or targeted advertising. We do not sell data or advertise, and you can exercise the other rights by writing to us. We will not treat you differently for doing so.

10. Children

Odomo is for adults running a business and for adult renters. We do not knowingly collect information from anyone under 18; if you believe we have, write to us and we will delete it.

11. Changes

We will update this policy as the product changes and before general availability. Material changes are announced to Hosts by email or in the app; the date at the top is the current version.

12. Contact

Privacy questions or requests: Odomo, LLC, [email protected].