Vero Privacy Policy
Last updated: November 3, 2026 Effective: November 3, 2026
Summary
This is the short version. The numbered sections below give the full detail.
- Vero Transportation, LLC runs Vero, a van service for groups of friends in and around Oxford, Mississippi. This policy covers the Vero app, the Vero App Clip, our website at ridevero.app, our waitlist, and our texts.
- We collect what we need to run your rides: your name, phone number, date of birth, the pickup and drop-off you choose, payment details (which Stripe holds), the messages in your ride's chat, and information about how the app is working.
- Vero does not receive your phone's live location unless you share it in a Safety message. The app uses it on your phone, and Mapbox's map software may collect it (Section 6.3). Vero receives the pickup and drop-off you choose, and the riders in your group see the van's location during the ride.
- Your driver and the riders in your group see your name, profile photo, and pickup point.
- We use outside companies to run the service, and Section 6 names each one. Some features send information to AI providers, and Section 8 lists each one. Before your search or chat text goes to one, the app asks for your permission.
- We do not sell your information, we do not show ads, and we do not track you across other companies' apps or websites.
- You can delete your account in the app. You have 30 days to change your mind. After that we delete or de-identify your account data, and we keep only the records listed in Section 12.5.
- Vero is only for people 18 and older.
1. Who we are and what this policy covers
1.1 Who we are. Vero Transportation, LLC ("Vero," "we," "us") is a Mississippi limited liability company. Vero provides rides in its own vans with drivers it employs. You can reach us at team@ridevero.app, [support phone: new Telnyx number forwarding to Chris, digits pending], or [mailing address: LLC registered address from the Mississippi Secretary of State filing, pending].
1.2 What this policy covers. This policy covers riders, App Clip guests, waitlist members, and visitors to ridevero.app. It explains what we collect, how we use it, who receives it, how long we keep it, and the choices and rights you have. Charter customers are covered by this policy for the information the van and its head unit collect during a charter. Vero's drivers receive a separate notice about the information Vero collects while they work (Section 19).
1.3 United States only. Vero operates only in Mississippi, and this policy is written for United States law.
1.4 Third-party beneficiary. Spotify is a third-party beneficiary of this Privacy Policy and of our Terms of Service.
2. Information we collect
| Category | What it includes | Why we use it |
|---|---|---|
| Identifiers | Your Vero account ID, your sign-in account ID at Clerk, the App Clip device token kept in your phone's keychain, push notification tokens, an analytics installation ID, and your IP address | To sign you in, keep your account secure, send notifications, measure how the app works, and prevent fraud and abuse |
| Contact details | Your name, phone number, and email address if you add one | To create your account, send sign-in codes, show your name to your driver and group, and answer support requests |
| Date of birth | The birthday you enter at sign-up | To confirm you are 18 or older, and to show which version of our Terms you accepted at what age |
| Payment information | Your card or Apple Pay details, which Stripe collects and stores; the holds, charges, refunds, and receipts for your rides; and your Vero credit balance | To take payments, release holds, issue refunds and receipts, prevent fraud, and keep accounting and tax records |
| Precise location | Your phone's location while the app is open, if you allow it, which the app uses on your phone without sending it to Vero; the pickup and drop-off you choose; destination searches; places you have confirmed; and the location you choose to share in a Safety message | To show your position and pickup on the map, quote prices and wait times, send the van to you, and help you in a safety situation (Section 4) |
| Ride details | The rides you create or join, your group, seats and guest seats, check-in and no-show records, cancellations, ratings and feedback, and your van preferences (light colors, light effects, cabin temperature) | To run your rides, settle payments, keep ride records, and set up the van the way you like it |
| Messages and calls | Group chat messages, one-on-one messages with your driver after a ride, and call records showing who called, when, and for how long (never the audio) | To let your group and driver coordinate, keep a record of the ride, handle reports, and help with lost items |
| Van Bluetooth and Wi-Fi | The Bluetooth name of the phone you connect to the van's speakers, that phone's Bluetooth address (MAC address) linked to your profile for that van, van logs of devices that connect, and the Wi-Fi name and password issued for your ride | To connect your phone to the van, recognize your phone the next time you ride that van, and troubleshoot the van's systems |
| Device and diagnostics | Device model, operating system and app version, crash reports, error logs, and battery and temperature readings from the app | To find and fix bugs and keep the app stable |
| Phone permissions | What the app can reach on your phone when you allow it: the camera (to scan ride QR codes and to send photos to support), the microphone (only while you record a voice message to support), the photo library (to choose a profile photo), device motion (to keep the map heading pointed the way you face), the local network (to control the van lights while you are on the van Wi-Fi), and Face ID (to protect the sign-in details the app keeps on your phone, if you turn it on). Each one is optional and asked for only when the feature needs it | To run the feature you chose; none of these sends recordings or sensor data to Vero except what you send to support |
| Usage and session replay | Events recorded when you use the app (such as creating a ride, joining a ride, adding a payment method, or searching for a destination, including the destination), taps on named buttons, and, for some accounts, session replay recordings (Section 9) | To understand how the app is used, fix problems, and improve features |
| Support conversations | Messages, photos, files, and voice messages you send to support, and the ride or lost-item details you include | To answer your questions and resolve problems |
| Music service connections | Spotify sign-in tokens (stored encrypted), the Spotify information you allow us to use (your playlists, saved music, what is playing, and your Spotify account name and email), Apple Music access on your phone, and the title and artist of songs played | To play and control your music in the van and to match the van's lighting to it |
| Photos | The profile photo you choose. Profile photos are stored at a web address that anyone who has the address can open. | To show your driver and group who you are |
| Reports and blocks | Reports you file or that others file about you, and the riders you block | To keep riders safe and enforce our Terms |
| Agreements | The version of our Terms and this policy you accepted, when you accepted it, and your 18+ confirmation | To show what you agreed to |
The current app does not ask about your health. Accounts created with an earlier version of the app may hold an answer to a question about sensitivity to flashing lights or loud sound. You can ask us to delete that answer at team@ridevero.app.
App Clip guests. If you join a ride through the App Clip, we collect your display name, an optional avatar color, your agreement to our Terms and this policy with the version and time, your 18+ confirmation, a device token kept in your phone's keychain, and your payment through Stripe. The App Clip can send you notifications for up to 8 hours after each launch, and you can turn that off from the App Clip card. When you look up a ride code, we log your IP address and a scrambled form of the code for 24 hours to stop abuse.
3. Where the information comes from
3.1 From you. You give us your name, phone number, date of birth, email, profile photo, pickup and drop-off, messages, ratings, reports, and support requests.
3.2 From your phone. With your permission, your phone gives the app its location, and the app collects device, diagnostic, and usage information as you use it.
3.3 From your group and your driver. The host and other riders add information when they invite you, add guest seats, chat, or report a problem. Drivers add check-in, no-show, and ride records, and notes about anything that happened on the ride.
3.4 From the van. The van records the Bluetooth name and address of a phone that connects to its speakers, and the number of devices on its Wi-Fi.
3.5 From service providers. Clerk confirms your phone number. Stripe tells us whether a payment succeeded. Spotify and Apple Music provide music information when you connect them. Mapbox returns search results and map data.
4. How we use information, and how location works
4.1 Purposes. We use information to:
(a) provide rides, including your account, invitations, pickups, the van's route, and in-van features;
(b) take payments, release holds, issue refunds and receipts, and keep accounting and tax records;
(c) keep riders and drivers safe, including the 18+ check, reports, blocks, ride removals, Safety messages, and fraud and abuse prevention;
(d) communicate with you through sign-in codes, push notifications, support replies, and waitlist texts;
(e) find and fix problems and improve the app;
(f) meet legal duties, resolve disputes, enforce our Terms, and keep records of what you agreed to; and
(g) build a shared list of popular destinations (Section 4.5).
We use information only for the purposes in this policy. Before we use information we already hold for a new purpose that is materially different, we will ask for your consent.
4.2 Your phone's location. Riders are asked to allow location only while the app is in use. The app uses your live location on your phone to show where you are on the map and to help you set a pickup. Vero does not upload your live position, and your driver and group do not see it. Mapbox's map software in the app may collect it, as Section 6.3 explains.
4.3 Pickup and drop-off. The pickup and drop-off you choose are sent to Vero to quote prices, estimate wait times, and send the van. Your driver and the riders in your group can see your pickup point. You can type a pickup address instead of sharing your location.
4.4 The van's location. While your ride is active, the riders in your group see the van's live location on the map. The app also shows where Vero vans are while their drivers are online, so you can see one coming before you book.
4.5 Destinations and saved places. When you confirm a destination, we save it to your account so it appears in your future searches. When three different riders confirm the same place, it joins a shared list of places that appears in everyone's search. The shared list shows the place, not who chose it.
4.6 Safety messages. If you send a message from the Safety screen, your name, ride, van, note, and the location you choose to share go to Vero's on-call team.
4.7 Location is never sold. We do not sell location information, and we do not use it for advertising.
5. What other people in your ride see
5.1 Your driver and your group see your name, profile photo, and pickup point, and the messages you send in the group chat.
5.2 Riders who pay for others see the seats they covered and the receipt for their own payment. A receipt is shown only to the rider who paid.
5.3 Riders in the van can see the Bluetooth name of the phone connected to the van's speakers, and the van's spoken announcements can say the name of the destination and, if the rider controlling the music allowed AI features, that rider's first name.
5.4 Your group receives the Wi-Fi name and password issued for your ride.
6. Companies that receive information
6.1 Our service providers. We share information with these companies only so they can provide their services to Vero:
| Company | What it does for Vero | What it receives |
|---|---|---|
| Clerk | Sign-in | Phone number, name, optional email, profile photo, sign-in sessions; sends sign-in codes by text |
| Supabase | Hosting, database, and file storage | All app data |
| Stripe | Payment processing | Card or Apple Pay details, payment amounts, and ride details attached to each payment |
| Intuit QuickBooks | Bookkeeping | Payment records that Stripe sends for Vero's accounting |
| Mapbox | Maps, search, and directions | Search text, map coordinates, and map usage and device information (Section 6.3) |
| PostHog | Product analytics, crash reports, and session replay | Your Vero account ID, name, phone number, IP address, usage events, crash and error logs, and replay recordings for some accounts |
| Intercom, including its Fin AI agent | Customer support | Your account ID, name, email, support messages, photos, files, voice messages, and ride and lost-item details |
| Telnyx | Masked calls, waitlist texts, and Safety messages | Phone numbers, call routing and call records, waitlist codes and texts, and Safety messages to Vero's on-call phone, with your name, ride, van, note, and any location you share |
| Expo | Push notifications for the app | Push tokens and notification content |
| Apple | Push notifications, Live Activities, Apple Pay, Apple Music, and the App Clip | Push tokens, notification content, Apple Pay payment details, and Apple Music requests |
| Spotify | Music playback, if you connect it | Playback controls and requests made on your Spotify account |
| TypeSafe, an outside AI provider | AI place search, suggested replies, lighting, and van troubleshooting | Destination search text and known places, recent group chat messages from people who allowed AI features, the title and artist of songs from Apple Music or Bluetooth (never Spotify), and van system log lines with device Bluetooth addresses removed (Section 8) |
| ElevenLabs | The van's spoken announcements | Announcement text, which can include the destination name and, if the rider controlling the music allowed AI features, that rider's first name |
| Cloudflare and Vercel | Hosting Vero's web pages, including the App Clip and ride pass pages at app.ridevero.app and Vero's staff console | IP addresses and device information from page visits, and the ride and account information Vero staff view |
| Base44 | Hosting our website, ridevero.app | Website visit data and form entries (Section 17) |
6.2 Equal protection. Every company listed in Section 6.1 that receives your information from us provides the same or equal protection of that information as this policy describes and as Apple's App Store rules require. Apple, Spotify, and Stripe also handle information under their own privacy policies when you use their services directly.
6.3 Mapbox. Mapbox's software in the app collects information about how the map is used, and your device's location when you allow it, to provide and improve its maps. You can turn off Mapbox data collection from the information button on the map. Mapbox's privacy policy is at https://www.mapbox.com/legal/privacy.
6.4 Other times we share information. We also share information:
(a) with the police, emergency services, or others when we believe in good faith it is needed to protect someone's safety;
(b) when the law requires it, such as in response to a valid subpoena or court order;
(c) to protect Vero's rights, investigate fraud, or enforce our Terms;
(d) as part of a merger, acquisition, or sale of Vero's business, under this policy's protections; and
(e) with your consent.
7. What we never do
7.1 No sale. We do not sell personal information, including precise location, and we do not rent it or give it to data brokers.
7.2 No ads and no tracking. Vero does not show ads, does not use your information for targeted advertising, and does not track you across other companies' apps or websites.
7.3 Text messaging consent. This applies to every company and every kind of sharing described in Section 6. We will not share your opt-in to an SMS campaign with any third party for purposes unrelated to providing you with the services of that campaign. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
7.4 No cabin cameras or audio recording. Vero vans have no cabin cameras, dashcams, or audio recording. The van's lighting controller has a small microphone that it uses only to sync the lights to the music. It processes sound on the controller as the music plays, and it does not record, store, or send audio. If Vero ever adds cameras or audio recording to its vans, we will update this policy, tell you before you book, and post a notice in the van.
7.5 No call recording. Vero does not record calls between riders and drivers.
7.6 AI training. Vero does not use your personal information to train AI models. [AI training confirmation: state whether TypeSafe, any model provider TypeSafe uses for Vero requests, Intercom (Fin), and ElevenLabs may train models on information Vero sends them.]
8. Third-party AI
8.1 What goes to AI providers. These features send information to outside AI providers:
(a) Place search. When you type a destination search, Vero sends your search text and places you know to TypeSafe, an outside AI provider, to understand the search and rank results.
(b) Suggested replies. To suggest quick replies, Vero sends the last few chat messages (each up to 280 characters, labeled with the sender's role, such as host or driver) to TypeSafe. A message is included only if the person who sent it allowed AI features. If you do not allow it, your messages are never sent and you will not see suggested replies.
(c) Lighting. For songs from Apple Music or Bluetooth, Vero sends the title and artist to TypeSafe to choose how intense the lighting should be. Vero never sends Spotify track information to an AI provider.
(d) Van troubleshooting. Vero sends van system log lines to TypeSafe each night to look for problems, after removing device Bluetooth addresses.
(e) Support. Intercom's AI agent, Fin, answers support chats using the information in your conversation, your account and ride details, and Vero's help articles.
(f) Van voice. ElevenLabs turns announcement text into the van's spoken announcements. The text can include the name of the destination. It includes the first name of the rider controlling the music only if that rider allowed AI features.
8.2 Your permission. The app asks whether you allow AI features on the permissions screen at sign-up (riders who signed up earlier see the same choice once, at their next launch), and you can change the answer any time in Profile, under Preferences. Nothing you type goes to TypeSafe before you allow it. Your choice also covers AI features Vero adds later that use the same kinds of information, in the app or through the van's systems; we update this section before any such feature goes live, and a feature that would collect a new kind of information, such as a recording of your voice, gets its own notice and permission at the time. If you allow them, Vero sends your search text and chat messages to TypeSafe as described in 8.1(a) and (b), and the van's announcements can use your first name as described in 8.1(f). If you do not allow them, place search uses standard map search, your chat messages are never sent, you will not see suggested replies, and the van's announcements do not use your name. You can change your choice in the app at any time.
8.3 In-ride assistant. Vero does not currently offer an in-ride AI assistant. If we turn one on, we will update this policy and ask for your permission before it receives your messages.
9. Session replay in the app
9.1 What it is. Session replay records what appears on your screen while you use the app, so we can see where something went wrong. Vero uses PostHog for session replay. Replay is currently turned on only for a small number of accounts that Vero chooses, such as test accounts, and only after the account holder has signed in and accepted this policy.
9.2 What it captures and hides. A recording captures about one frame per second of the screens you visit and the taps you make. It hides what you type into text fields, images, and the payment screen. It does not hide other text the app displays, such as names, ride details, and chat messages. It does not record network traffic or the app's console logs.
9.3 How long we keep it. Recordings are kept for 30 days.
9.4 Your choice. You can ask us to keep your account out of session replay by emailing team@ridevero.app. Before we record anyone outside test accounts, we will ask for permission in the app and show an indicator while recording is on.
10. Texts and calls
10.1 Vero's texts. Vero sends one-time sign-in and sign-up codes through Clerk when you request them. Vero also runs one text program, Vero waitlist texts. If you check the box to receive texts when you join the waitlist, you receive:
(a) a code to confirm your phone number;
(b) a text confirming that you joined the waitlist; and
(c) one text when your access opens.
Vero does not send marketing texts. Ride updates come as push notifications in the app.
10.2 Frequency, cost, STOP, and HELP. Message frequency varies. You receive a code each time you request one, and waitlist members receive up to two status texts. Message and data rates may apply. Reply STOP to any Vero waitlist text to stop receiving Vero waitlist texts. Reply HELP for help, or contact team@ridevero.app or [support phone: new Telnyx number forwarding to Chris, digits pending]. Wireless carriers are not liable for delayed or undelivered messages.
10.3 Calls. Calls between riders and drivers go through a Vero bridge number provided by Telnyx, so neither side sees the other's real number. Calls are not recorded. We keep a record of who called, when, and how long the call lasted. The person receiving a call hears a short recorded announcement first.
11. How long we keep information
| Information | How long we keep it |
|---|---|
| Account profile (name, phone, email, photo, date of birth, van preferences) | While your account is open, plus the 30-day undo period after you ask to delete it. Then we delete it. If you ever hosted a ride, we replace your profile with a "Deleted rider" record that has your personal details removed, so your group's ride and payment records stay complete. |
| Your phone's live location | Vero does not receive or store it, except a location you choose to share in a Safety message |
| Saved places | Until you delete your account |
| Ride and payment records (rides, seats, pickup and drop-off, fares, holds, charges, refunds, Vero credit, ratings, and agreement records) | Seven years after the ride, for tax, accounting, chargeback, and legal reasons. These records remain after you delete your account. |
| Group chat messages | The chat locks 4 hours after the ride and stays readable to the group as a record. We keep messages with the ride record for seven years. They remain after you delete your account, linked to your Clerk sign-in ID instead of your profile. |
| One-on-one messages with your driver | The thread closes 72 hours after the ride. We keep the messages until you delete your account. |
| Call records (no audio) | Until you delete your account |
| Reports | We keep reports as safety records. When you delete your account, we remove the link between the report and your profile. |
| Blocks | Until you remove the block or delete your account |
| Van location history | 30 days |
| Van Bluetooth record (your phone's Bluetooth address linked to your profile for a van) | About one year after the van last sees your phone |
| Van system logs that list connected devices | 90 days |
| App Clip ride code lookups, with IP address | 24 hours |
| Security and rate-limit logs | 1 to 7 days |
| Analytics events and crash reports (PostHog) | While your account is open. When you delete your account, we ask PostHog to delete them. |
| Session replay recordings | 30 days |
| Support conversations (Intercom) | While your account is open. When you delete your account, we ask Intercom to delete them. |
| Spotify information | Until you disconnect Spotify. We delete it within 5 days after you disconnect, or when you delete your account. |
| Push tokens | Until you delete your account or the token stops working |
| App Clip guest information | Kept with the ride's records. The device token stays in your phone's keychain until you remove the App Clip. |
| Waitlist information | Until you create an account and later delete it, or until you ask us to remove you from the waitlist |
| Ambassador applications | For as long as the ambassador program runs, unless you ask us to delete yours sooner |
| Website analytics | 12 months |
| Backups | Deleted information may remain in encrypted backups for up to 7 days before the backups are overwritten |
12. Deleting your account
12.1 How to delete. Go to Edit profile in the app, tap Delete account, and type DELETE to confirm. You do not need to call or email us.
12.2 What happens right away. We sign you out, remove you from your rides, and schedule your account for deletion 30 days later.
12.3 Changing your mind. Sign back in within 30 days to restore your account.
12.4 After 30 days. Our nightly deletion job removes your profile, or replaces it with a "Deleted rider" record if you ever hosted. It also deletes your ride memberships and invitations, push tokens, notifications, one-on-one messages, and call records. It then deletes your price quotes, App Clip claims, blocks, location records, Spotify connection, waitlist entry, saved cards and Stripe customer record, and profile photo files. We also ask Clerk, PostHog, and Intercom to delete your information. Those providers can take additional time to finish, and we retry until they confirm.
12.5 What remains. These records remain after deletion, for the reasons and periods in Section 11:
(a) ride and payment records, which we need for tax, accounting, chargebacks, and legal claims;
(b) a "Deleted rider" record without your personal details, if you ever hosted a ride, so your group's records stay complete;
(c) the text of group chat messages you sent, linked to your Clerk sign-in ID instead of your profile;
(d) reports, with the link to your profile removed; and
(e) Stripe's own records of charges and refunds, which Stripe keeps under its own policies.
12.6 Confirmation. If you would like confirmation that deletion is complete, email team@ridevero.app and we will confirm.
12.7 Vero credit. When your account deletion completes, Vero refunds any credit that came from a refund of your own payment to the payment method you used (Terms, Section 8.6).
12.8 App Clip guests. Email team@ridevero.app with the ride code and the name you entered, and we will delete what we are not required to keep.
13. Your choices
13.1 Location. You can allow or stop location access at any time in your phone's settings. If you do not share location, you can type a pickup address.
13.2 Notifications. You can turn push notifications off in your phone's settings, and turn off App Clip notifications from the App Clip card.
13.3 AI features. You can turn AI features on or off in Profile, under Preferences, at any time (Section 8.2). Turning them off stops AI place search and suggested replies, keeps your chat messages out of suggested replies for others, and stops the van from using your first name in announcements.
13.4 Music services. You can disconnect Spotify in the app at any time, and we delete your Spotify information within 5 days. You can manage Apple Music access in your phone's settings.
13.5 Texts. Reply STOP to any waitlist text.
13.6 Session replay. Email team@ridevero.app to keep your account out of session replay.
13.7 Mapbox. Vero turns off Mapbox's usage data collection in the app. Mapbox still receives the map requests described in Section 6.3, which are needed to draw the map.
13.8 Bluetooth. You can forget the van in your phone's Bluetooth settings, and ask us to delete the van's record of your phone.
13.9 Withdrawing consent. You can withdraw any consent you gave by changing the setting above or by emailing us. When you withdraw consent, we stop the use it covered. This does not undo use that happened before you withdrew it.
13.10 Your profile. You can change or remove your profile photo, name, and email in Edit profile.
13.11 Phone permissions. You can turn the camera, microphone, photo, motion, local network, and Face ID permissions on or off at any time in your phone's Settings. Turning one off only disables the feature that uses it.
14. Your rights
14.1 Rights for every rider. Wherever you live, you can ask us to:
(a) tell you what personal information we hold about you and give you a copy;
(b) correct information that is wrong;
(c) delete your information, apart from the records in Section 12.5; and
(d) stop a use you consented to.
Email team@ridevero.app or write to us at [mailing address: LLC registered address from the Mississippi Secretary of State filing, pending]. We will confirm your identity, usually by sending a code to the phone number on your account, and answer within 45 days. If we need more time, we will tell you why and take up to 45 more days. We will not treat you differently because you used these rights.
14.2 Appeals. If we turn down your request, you can appeal by replying to our answer within 60 days. We will answer the appeal within 60 days. If we deny the appeal, you can contact the attorney general in your state.
14.3 California. Neither our app nor our website tracks you across other companies' sites or apps for advertising. The companies in Section 6 collect information through our services only to provide their services to us, except that Mapbox also uses map usage information to improve its maps (Section 6.3). Our practices are the same whether or not your browser sends a Do Not Track or Global Privacy Control signal. We do not share personal information with other companies for their own direct marketing.
14.4 Texas. Vero does not sell personal data, including sensitive data such as precise location.
14.5 Connecticut. Precise location is sensitive data. Vero processes two kinds of precise location: your phone's location, which you allow in your phone's permission prompt, and the pickup and drop-off points you choose, which you consent to when you accept this policy and book. We use both only for the purposes in Section 4. You can withdraw consent to your phone's location at any time in your phone's settings, and you can stop sharing pickup and drop-off points by not booking rides. We do not sell personal data, use it for targeted advertising, or use it for automated decisions that have legal or similarly significant effects on you. If we deny an appeal, you can contact the Connecticut Attorney General.
15. Age
Vero is only for people 18 and older. We do not knowingly collect information from anyone under 18. If we learn that we have, we close the account and delete the information, apart from records the law requires us to keep.
16. Security and breach notice
16.1 How we protect information. We encrypt information in transit and at rest. Every table in our database has access rules that control who can read and change each record. Spotify tokens are stored encrypted. Stripe holds full card details, and Vero never stores them. No system is perfectly secure, so we cannot promise that information will never be exposed.
16.2 Breach notice. If a security breach affects your personal information, we will tell you without unreasonable delay, even when the law does not require it, unless law enforcement asks us to wait. When Mississippi Code § 75-24-29 or another law requires notice, our notice meets that law.
17. Our website
17.1 Hosting. Our website at ridevero.app is built and hosted on Base44.
17.2 Website analytics. Base44, the platform that hosts our website, counts visits and page views on every page load as part of running the site; we cannot turn that off. Our own analytics start only after you accept the notice shown on your first visit: the pages you view, the labels of links and buttons you click, and how far you scroll. The website does not record your screen, and it does not record what you type into forms.
17.3 Browser storage. The website stores identifiers in your browser's local storage, such as a visitor ID and an analytics session ID. As of the date above, it sets no cookies.
17.4 Waitlist. When you join the waitlist, we collect your first and last name and phone number, and you can add an email. If you check the box to receive texts, you agree to receive Vero waitlist texts as described in Section 10: a code to confirm your phone number, a confirmation text, and one text when your access opens. Message frequency varies. Message and data rates may apply. Reply STOP to opt out and HELP for help.
17.5 Ambassador applications. If you apply to be a Vero ambassador, we collect your full name, email, phone number, and when you applied.
17.6 App Clip pages. The App Clip and ride pass pages at app.ridevero.app do not use analytics or session recording.
17.7 Retention. Website analytics are kept for the period in Section 11.
18. Changes to this policy
18.1 Notice. When we make a material change to this policy, we tell you in the app at least 30 days before it takes effect and ask you to accept it. Other changes take effect when we post them, and the date at the top shows the latest version.
18.2 No retroactive changes. We will not apply a material change to information we collected before the change without asking for your consent first.
18.3 Change log. We list each version below.
| Date | Change |
|---|---|
| November 3, 2026 | New policy covering the app, App Clip, website, waitlist, and texts |
19. Drivers
Vero's drivers are Vero employees. Vero collects information from drivers while they work, including their location while they are online, and explains it in a separate notice for drivers. While your ride is active, the riders in your group see the driver's name, photo, the van's plate code, and the van's location. A driver's position is recorded every few seconds whenever the driver is online for Vero, including in the background, and is shown to riders in the app as the van's position.
20. Contact us
Vero Transportation, LLC [mailing address: LLC registered address from the Mississippi Secretary of State filing, pending] Phone: [support phone: new Telnyx number forwarding to Chris, digits pending] Email: team@ridevero.app