Privacy Policy

Draft, pending legal review. This text may change before PeakMere launches.

Last updated: November 8, 2026

This policy explains what the PeakMere app and the peakmere.com website collect, why, how long it is kept, and how to delete it. It is written to match what our software actually does today. PeakMere is operated by PEAKMERE LLC ("we", "us").

1. The short version

  • No accounts: the app has no sign-up and never asks for your name or phone number. It asks for your email only if you write to us with "Contact us" or "Suggest an idea" (optional for an idea; see "The peakmere.com website").
  • No ads in the app, no selling or renting of personal information, and no third-party analytics or tracking tools in the app. The website counts visits as anonymous totals, records how each visitor moves through it under a random ID (never your name, email or IP address), and uses Google and Meta measurement and advertising tools unless you turn them off (see "The peakmere.com website").
  • Your settings and history stay on your phone, except assistant conversations you choose to save (see "PeakMere AI (assistant)").
  • Your location is sent to us only after you tap "Agree" on the app's one location consent screen (or turn on "Share my location" in Settings). That single consent turns on anonymous sharing of waits and speeds and exact-location sharing. If you choose "Only on this phone" (or turn on "Use my location on this phone only" in Settings), the app uses your location on your phone only and sends nothing about it to us. Nothing is collected if you choose "Not now".
  • If you share, only rounded areas, times and speeds go to us with a random code that changes every day. We never store your IP address with them, never show anything based on fewer than 3 daily codes, and never sell location data.
  • Exact-location sharing works only in app versions that include it. Once you agree, your exact positions go to us linked to a random install ID (not your name, email or phone), are seen only by PeakMere, are never sold, and can be deleted from the app at any time.
  • You can stop sharing at any time in the app.
  • Airport alerts are off until you turn them on in Settings. If you do, we store your phone's push token with your airport, language and chosen alert types, only to send you those alerts, and we delete it when you turn them off.
  • PeakMere AI (optional, in app versions that include it) sends your messages to our server and to our AI provider, Anthropic, to answer them. You choose whether your conversations are saved: if you choose "Don't save", we store nothing about them; if you choose "Save my conversations", we keep them and a short memory about you for up to 5 years, and you can delete them at any time in the app.
  • The website stores what you type into its contact or waitlist form, only to answer you or tell you about the launch.

2. Information kept only on your phone

The app saves these on your device, using the phone's own app storage. We cannot see them:

  • Your language, the airport (city) you selected, and your shift preferences (which days and times you like to drive).
  • Which alerts you have already seen.
  • A reminder you set yourself, if any.
  • Copies of recent data the app downloaded (for example arrivals and weather for your airport), so it can still show something when your signal is poor.
  • Your answer on the location consent screen and the "Share my location" and "Use my location on this phone only" switches (both off until you choose).
  • If you agree, or choose "Only on this phone": your own past waits, used to show your personal patterns. Each wait is stored as an area of about 0.6 mile (1 km), the start time, the minutes waited and the city, for up to 90 days. This history is never uploaded. You can delete it with one button in Settings.
  • If you agree: the items waiting to be sent and the current daily code. Both are deleted from the phone when you stop sharing.
  • Your "Airport alerts on this phone" switch and the alert types you chose (what our server keeps for alerts is described under "Notifications").
  • If you agree (in app versions with exact-location sharing): your random install ID, the positions waiting to be sent, and any deletion request waiting for a connection. Positions waiting to be sent are deleted from the phone when you switch sharing off.
  • If you use PeakMere AI (in app versions that include it): your random assistant ID, your choice to save or not save conversations and, if you chose "Don't save", the current conversation (what our server keeps is described under "PeakMere AI (assistant)").

Deleting the app deletes all of this.

3. Location

The app asks for location permission only after you choose "Agree" or "Only on this phone" on its location consent screen (shown once when you first open the app; you can also choose later with the "Share my location" or "Use my location on this phone only" switch in Settings), and it uses your location only while the app is open. It does not track you in the background. Nothing is collected if you choose "Not now".

  • Wait detection turns your movements into "waits", speeds and trips on the phone. It never sends raw GPS positions; the rounded results described below are sent to us once you agree to location sharing.
  • Exact-location sharing is the only feature that sends your exact GPS positions to us. It is turned on by the same consent. See "Optional exact-location sharing" below.

You can withdraw location permission at any time in your phone's settings.

4. Optional anonymous sharing of waits and speeds

Drivers can choose to share anonymous waiting times, road speeds and coarse trips, so that every driver can see typical waits by area, sudden traffic slowdowns, where riders from the airport tend to go, and how many drivers are already heading to a large event. Sharing is opt-in: nothing is collected until you tap "Agree" on the app's location consent screen (or turn on "Share my location" in Settings), which explains it and links to this policy. That one consent turns on both this sharing and the exact-location sharing below. It runs only while the app is open.

If you agree, the app sends, at most every 5 minutes:

  • Waits: an area of about 0.75 by 0.4 mile (1.2 by 0.6 km), a start time rounded down to 5 minutes, the minutes waited, whether you drove off afterwards, and whether you tapped "Got a ride".
  • Speeds while moving above about 3 mph (5 km/h): an area of about 500 feet (150 m), the minute, a speed rounded to 5 km/h (about 3 mph) and one of 8 compass directions, at most once a minute per area.
  • Trips between two waits at least 1.2 miles (2 km) apart: a start and end area of roughly 25 by 12 miles (40 by 20 km), a start time rounded down to 15 minutes, the duration, and whether you tapped "Got a ride".
  • The city (airport) you selected in the app.
  • A random code that the phone creates every day. It is not made from anything on your phone and is not linked to you, your phone or your other days.

This feature never sends your exact GPS positions (only the exact-location sharing below does), your name, your contact details, your rideshare account or anything about your riders.

What our server keeps, and for how long:

  • Recent items: waits for 2 hours after they end and speeds for 30 minutes, to show what is happening now.
  • Summaries by area and hour (minutes waited, speeds, counts of trips between areas) for up to 29 days. Waits and speeds more than about 93 miles (150 km) from the selected airport are discarded.
  • Only the first half of each daily code is stored, and only for 2 days. After that the summaries keep just the number of different codes, so nothing on the server can connect a sample to a device.
  • This data is kept in our server's memory and saved to its disk every 5 minutes, replacing the previous copy.

Our server does not store your IP address with shared data, and the content of each upload is never logged. To prevent abuse, it counts uploads per IP address using a salted fingerprint (hash) that is held in memory only, and holds the full daily code in memory for at most 2 days (6 hours after its last upload).

Because one day's speed samples carry the same daily code, for up to 2 days the stored hourly summaries could in principle show roughly which 500-foot (150 m) areas one phone passed through in a given hour. We do not use them that way, and after 2 days that link is removed.

Who sees what: anyone who uses the app, or our public data service, can see only the combined results: typical waits by area, slowdowns, the share of airport trips going to each large area, and how many drivers are heading to an event venue. A result is shown only when at least 3 different daily codes contributed to it. Because the code changes every day, for the "where riders go" shares one phone on 3 different days counts as 3. Individual samples and daily codes are never shown. We can access the stored data on our server, which is hosted by DigitalOcean. We do not give it to anyone else unless the law requires it.

We do not sell or rent location data, and we do not share it for advertising.

How to stop: in the app, turn off "Share my location" (Settings, "Location sharing"); this stops both kinds of sharing. Nothing more is sent, and the items waiting on your phone are deleted. Withdrawing location permission in your phone's settings also stops new samples. Shared data is not linked to you, so we cannot find or delete your past samples on request; they expire as described above.

5. Optional exact-location sharing

Exact-location sharing is turned on by the same single consent as the anonymous sharing above: nothing is collected until you tap "Agree" on the app's location consent screen (or turn on "Share my location" in Settings), and it stays off if you choose "Not now". It works only in app versions that include it and once we switch it on on our server; until then your consent is kept and nothing is collected. We ask for it so that PeakMere can learn how drivers actually work (where they wait, which areas and roads they use, how long trips take) and give more accurate predictions in the app.

If you agree, the app collects, only while the app is open (never in the background):

  • Your exact position (latitude and longitude) and its time, and, when your phone reports them, your speed, your heading (direction of travel) and the accuracy of the position.
  • About one position every 15 seconds while you are moving faster than about 3 mph (5 km/h), and one every 2 minutes while you are stopped.
  • The airport (city) you selected in the app.
  • A random install ID that the app creates when you first agree. It is not made from anything on your phone and is not linked to your name, email, phone number or rideshare accounts.

The app sends the collected positions about every 2 minutes and when you leave the app. It never sends your name, your contact details, your rideshare account or anything about your riders.

How we use it: only to improve PeakMere's predictions and features, for example how long drivers wait in an area, which areas are busy at which hours and how traffic changes. We do not sell or rent it, we do not share it with anyone for advertising or any other purpose, we do not use it to profile you for anything else, and we never publish one driver's positions or trails. Anything the app ever shows from this data is combined across drivers.

Trips and waits worked out from your positions: our server also estimates from the same positions, automatically, when you wait (at an airport queue lot or in the city), drive to a pickup, pick up a rider, drive with a rider, drop off, drive empty afterwards or are offline, with the times of pickups and drop-offs and the area where each happened, airport queue waits, empty-driving time and distance, and trips per hour. These are estimates made from location alone (nothing comes from any rideshare company or account). For pickups, drop-offs and waits in the city we store only an area of about 0.6 mile (1 km), never the exact spot, because it may be a rider's home; nothing about riders themselves is ever recorded. They are linked to the same random install ID, are used only to improve PeakMere's predictions and, in app versions that offer it, to show you your own statistics, are seen only by us in our private dashboard, are never sold, and are never shown to other drivers or anyone else.

Who can see it: only us, in a private dashboard that requires the owner's sign-in. The dashboard shows a short form of the install ID, never your name or contact details, because we do not have them. The positions are stored on our server in the United States, hosted by DigitalOcean, and reach the dashboard through Cloudflare over encrypted connections. We do not give them to anyone else unless the law requires it.

How long we keep it: each position is kept for at most 30 days, and each trip or wait worked out from the positions for at most 90 days (a day's positions, or a day's trips and waits, are deleted together, once the first of them is 30 or 90 days old). After that we keep only daily totals per city (how many install IDs and positions; how many trips and airport pickups, their total distance, the number and total length of airport queue waits, and the total empty-driving time and distance), which contain no install ID and no position. If our storage limit is reached, new positions are refused until older ones are deleted.

Security: positions travel over encrypted connections (HTTPS) and are stored in files that only our server program can read. Our server does not store your IP address with them and never logs what the app sends. To prevent abuse, it counts requests per IP address and per install ID in memory only, using a salted fingerprint (hash) for IP addresses. The owner's dashboard is protected by Cloudflare Access sign-in, and our server answers it only with a secret key.

How to stop and delete: turn off "Share my location" at any time in Settings (this stops both kinds of sharing). Nothing more is collected, and positions not yet sent are deleted from your phone. The "Delete my exact-location data" button in Settings deletes every position stored on our server for your install ID, and every trip or wait worked out from them, forgets that ID and switches exact-location sharing off; it works even after you turn sharing off, and if your phone is offline the request is sent as soon as there is a connection. "Reset my ID" also deletes the old ID's positions, trips and waits and starts a new ID. If you delete the app, the install ID is deleted from your phone and we can no longer tell which positions were yours, so they stay until they expire (positions after 30 days, the trips and waits worked out from them after 90 days): use the delete button first. Withdrawing location permission in your phone's settings also stops collection.

Your rights: exact location is "sensitive personal information" (also called sensitive data) under California's privacy law and several other state privacy laws. We collect it only with your opt-in consent, describe it here and in the app before collection, use it only for the purpose above, never sell or share it, and let you delete it at any time from the app. You can also write to [email protected] with any question about it.

6. What the app sends to our servers

To show live information, the app asks our server for data about the airport you selected. The request contains the airport code (for example DEN). It does not contain your name, email, location, advertising identifier or any device identifier. The only exceptions are optional features you turn on yourself: anonymous sharing sends rounded location data and a daily random code, and exact-location sharing sends exact positions and a random install ID, only after you agree to location sharing; airport alerts send your phone's push token, only after you turn them on (see "Notifications"); and PeakMere AI sends the messages you type to it with a random assistant ID, only when you use it (see "PeakMere AI (assistant)").

To tell our real app from copies and scripts, the app also asks our website for a short "app ticket" about every 15 minutes and sends it with these requests. The ticket carries a random ID that the app creates for this purpose only (it is not your install ID for location sharing, not the assistant ID, and not made from anything on your phone), your phone type (iPhone or Android) and its time limit. It is not linked to your name or contact details. We use it only to protect the service and to limit how often each install can ask.

Like every internet service, our server necessarily receives your IP address in order to answer. See "Server logs and security" for what happens to it.

7. Server logs and security

Our app data server is hosted by DigitalOcean in the United States.

  • Our application logs each request's method, path (without the airport code), result code and time. These lines do not contain your IP address.
  • Our web server does not keep access logs. Its error messages may include the IP address involved.
  • To prevent abuse, the server counts requests per IP address in memory only. These counts are never written to disk and are lost whenever the server restarts.
  • System logs are rotated automatically and older entries are deleted.

We use logs only to keep the service running and secure, never to identify or profile users. All connections are encrypted with HTTPS.

8. Notifications

Reminders and test alerts that you schedule yourself are created on your phone and never involve our server.

Airport alerts on this phone (optional, off until you turn them on in Settings): our server sends alerts about the airport you selected, such as a wave of arrivals, a ground stop or planned stop, the last airport train, or many cancelled flights. When you turn them on, the app asks for your permission to show notifications and then sends our server:

  • Your phone's push token: an address issued by the Expo push service so notifications can reach this app on this phone. It does not contain your name, phone number, email or location.
  • The airport you selected, the app language, and the alert types you chose.

We store only these items, the personal alerts and quiet hours you save (see below), and a random number that our own logs use instead of the token. We do not store your IP address with them. They are used only to send you the alerts you chose, never for advertising or profiling, and they are never sold or shared. To deliver an alert, its title and text and your push token pass through Expo's push service (Expo is the company behind the tools the app is built with) and Apple's or Google's notification service, under their own privacy policies.

The token is deleted from our server when you turn airport alerts off in Settings (if your phone is offline, the request is sent as soon as there is a connection), or when the push service tells us the phone no longer accepts our alerts (for example after you delete the app or turn off its notifications). Turning off notifications for PeakMere in your phone's settings stops the alerts at once.

Personal alerts (optional, in app versions that include them): when PeakMere AI suggests an alert and you tap "Save alert" (for example "tell me when the ground stop at DEN ends"), the alert is sent to our server with your airport alerts: what to watch, the airport, optional hours, whether it is for one time only, and when you saved it. Nothing you typed is stored for it. In the same way you can save quiet hours, during which our server sends this phone no alerts at all. You can have up to 20. Our server checks them every few minutes and sends the alert to this phone. They are deleted when you delete them in Settings, when you turn airport alerts off, or, for a one-time alert, 24 hours after you saved it.

9. PeakMere AI (assistant)

PeakMere AI, the PeakMere assistant, is an optional chat in the app (on the Now tab) that answers your questions about driving, your airport and the app. It works only in app versions that include it and once we switch it on on our server. To answer, it uses PeakMere's live airport data, our guide to the app and an AI model, Claude, provided by Anthropic, PBC ("Anthropic") through its API. The assistant has no account and never asks for your name, email or phone number.

The first time you open it, you choose "Save my conversations" or "Don't save". You can switch saving off at any time.

What the app sends with each message:

  • The text you type (up to 1,000 characters), the airport you selected, the app language and whether you chose to save.
  • A random assistant ID that the app creates for the assistant only. It is not made from anything on your phone and is not linked to your name, your contact details, your rideshare accounts or the install ID used for exact-location sharing.
  • If you chose "Don't save": up to 10 earlier questions and answers of the current conversation, kept on your phone, so the assistant can follow the conversation.

What goes to Anthropic: to write each answer, our server sends Anthropic your message, up to 10 earlier questions and answers of the conversation, your memory (only if you chose to save, see below), the airport's live data from PeakMere and our guide to the app. If an answer fails our automatic checks, the same request is sent once more. In app versions with personal alerts, your message is also sent once on its own (with the airport code only) to recognise whether you are asking for an alert. If you chose to save, our server also sends Anthropic your memory and the last 6 questions and answers of the conversation after your first saved message and then about every 4 messages, so that the memory can be updated. Under its commercial terms, Anthropic may not train its models on this content, and it states that it deletes API inputs and outputs within 30 days, except where its own policies or the law require it to keep them longer. Anthropic handles this content under its own terms and privacy policy.

Reports and tips (whichever you chose): if you tap "Report" under an answer, our server keeps that question and answer, with the app language and the airport, WITHOUT your assistant ID, for up to 2 years, to fix the assistant. If you share a local tip in the chat (for example a good pickup spot or how an airport lot works), the assistant may note it as one short sentence, also without your assistant ID, kept for up to 2 years to improve PeakMere for all drivers. Do not put names or personal details of other people in your messages.

If you choose "Don't save": our server does not store your messages, the answers or anything else about the conversation. It only uses them to get the answer and send it back to you.

If you choose "Save my conversations", our server keeps, under your random assistant ID only:

  • Each question and answer, with its time, the app language and the airport, grouped into conversations. A conversation's title is the beginning of its first question.
  • A short memory about you (at most 800 characters) that the assistant writes from your saved conversations, so it can personalize its answers: for example the name you want to be called, your home airport or city, your usual hours, your languages, your car type and your preferences. The assistant is instructed never to keep anything about your riders, phone numbers, email or street addresses, health, legal matters, or bank and account details.

Before anything is saved, email addresses, phone numbers and long card-like numbers (13 to 19 digits) are replaced by "[hidden]". Everything else you type, such as names or places, is saved as written, so please do not type your riders' details, addresses or other sensitive information.

How we use saved conversations: to show you your past conversations, to remember you and personalize the answers, and to improve the assistant, for example by reading conversations to find and fix wrong or missing answers. We do not sell or rent them, we do not use them for advertising, and apart from Anthropic, as described above, we do not give them to anyone else unless the law requires it. We may use totals that contain no text (for example how many messages were sent) to improve PeakMere.

Where they are kept: on our server in the United States, hosted by DigitalOcean, in files that only our server program can read. Messages travel over encrypted connections (HTTPS). There is no password: the app opens your saved conversations with the random assistant ID kept on your phone, and anyone who had that ID could do the same.

How long: each saved conversation is kept until 5 years after its last message and then deleted (a very long conversation keeps only its latest 500 questions and answers). The memory is deleted once you have no saved conversations left and it has not changed for 5 years.

How to delete or stop: in the assistant you can delete one conversation, or delete all your conversations together with the memory; they are deleted from our server at once. Switching saving off stops new messages from being saved; conversations already saved stay until you delete them or they expire. If you delete the app, the assistant ID is deleted from your phone and we can no longer tell which conversations were yours, so they stay until they expire: use the delete button first.

Limits and logs: each assistant ID can send up to 50 messages a day. To apply the daily limits and prevent abuse, our server counts messages per assistant ID and per IP address in memory only; these counts are never written to disk and start again every day. It also keeps daily totals for about 400 days (number of messages and AI requests, amount of text processed, cost, and how many answers failed a check), which contain no text, no assistant ID and no IP address. Our logs record only that the assistant was used, never your messages, the answers, your assistant ID or your IP address.

10. The peakmere.com website

The website is hosted by Cloudflare. It sets no cookies of its own (Cloudflare's security protection may set a strictly necessary cookie). Your language choice is part of the page address. If you pick a light or dark background with the button at the top, your browser remembers that choice on your device; it is never sent to us.

To see how the site is used, we use four tools, none of which sets cookies:

  • Cloudflare Web Analytics: a small Cloudflare script reports each page view (the page, the referring site, the browser and device type, the country and how fast the page loaded), which we see only as totals. It sets no cookie, stores nothing in your browser and does not follow you to other sites. Cloudflare processes it under its own privacy policy.
  • Our own counters: when a page opens, or when you tap an App Store or Google Play badge, change the language or the background, or send a form, the site adds one to a daily total of that event, the page, the page language and where the visit came from (a search engine, a social network, another site or a direct visit, taken from the referring address or a link's "utm_source"). Only these fixed names are stored, never your IP address, a visitor ID, your email or anything you type. The page keeps where your visit came from in your browser's session storage until you close the tab. To limit abuse, these requests are counted with the same daily salted fingerprint described below.
  • Share links: when you open a page, the site adds a short random code to the address in your browser ("?s=" followed by 8 letters and digits). It is new for each browser tab and is not linked to you. If you copy the address and send it, the visits it brings are counted under your code; if you arrived through a link that already had a code, your code is recorded as coming from that one, so we can see how far a link spread. Links we post or send ourselves carry codes too. For each code the site adds one to daily totals of visits and other pages opened in that tab (with the address of the page), waitlist sign-ups, taps on a store badge and sent forms, together with the approximate place of the request as Cloudflare reports it (country, region and city) and the device type (phone, tablet or computer). We never store your IP address, a visitor ID or anything you type with these counts, and we do not link share codes to people. Your browser keeps the code you arrived with and your tab's code in session storage until you close the tab, and your own recent codes in local storage so that opening your own link again is not counted. We remove the code before the address reaches Google Analytics. The Meta Pixel, if you allow it, sees the page address as it is, code included. If a link with a code was sent to you alone, these counts could describe your visit. Codes nobody opened are deleted after 7 days, the others with their counts after about 400 days.
  • Visitor journeys: to learn which pages help visitors and where they stop reading, the site records each visit as a journey. Your browser keeps a random visitor ID (16 letters and digits) in local storage and a random ID for the visit in the open tab in session storage; neither contains your name, email or IP address. For each page we store its address, when it opened, how long it was in view while you were using it, how far down you scrolled (in quarters), the last section heading you reached, and which links (our page addresses, or only the name of another site), buttons (their label) and actions (joining the waitlist, sending a form, tapping a store badge, changing the language) you used. With the visit we store where it came from (as for our counters), the page language, the share-link code you arrived with, the approximate place of the request as Cloudflare reports it (country, region and city) and the device type. We never store your IP address or anything you type. Because the visitor ID stays in your browser, we can see that the same browser came back and what it read each time, but not who you are. The visitor ID is replaced by a new one 13 months after it was made (visiting again does not extend it), so after that your later visits are no longer linked to your earlier ones. Detailed journeys are deleted 25 months after they were recorded, so that we can compare the same season from one year to the next; after that only daily totals per page remain (views, reading time, how far pages were read and where reading stopped), without any ID, for up to 5 years. Turning Measurement off under "Privacy choices" (or "Reject" in the cookie notice) stops it: your browser deletes its IDs and asks our server to delete the journeys recorded under them, including under any earlier ID it replaced. A Global Privacy Control signal also keeps it off. Visitors in the European Economic Area, the United Kingdom and Switzerland are recorded only after they choose "Accept" or "Accept all", or switch Measurement on themselves, and until then nothing is stored in their browser for it.

Unless you turn them off ("Reject" in the cookie notice, or the switches under "Customize": Measurement for the first, Advertising for the second), the website also loads:

  • Google Analytics (Google LLC), to see how visitors use the site. It sets cookies (names starting with _ga) and sends Google the pages you view, the site you came from, your device and browser, an approximate location and a random identifier. We switched off Google signals and ad personalization. Google processes this under its own privacy policy.
  • The Meta Pixel (Meta Platforms, Inc.), to measure and improve our ads on Facebook and Instagram. It sets cookies (_fbp, _fbc) and sends Meta the pages you view, when you join the waitlist, send a message or tap a store badge, and your browser and device details; Meta may connect this with your Facebook or Instagram account. We switched off its automatic reading of forms, so your email and anything you type are never sent to Meta. Under California law this can count as "sharing" personal information for cross-context behavioral advertising, which you can refuse.

If you choose "Reject", or your browser sends a Global Privacy Control signal, none of these load from then on. "Privacy choices" at the bottom of every page lets you change your choice at any time, switch each category on or off, and opt out of the "sale" or "sharing" of your personal information for targeted advertising ("Do not sell or share my personal information"); turning a category off also deletes its cookies from this site. Your choice is kept in your browser.

If you use a form, we receive:

  • Waitlist: your email, the city or airport if you give one, your preferred language and the time.
  • Contact (on the website or in the app's "Contact us" and "Suggest an idea"): your message, its type (a question, an idea or, in the app, a problem), your email (optional for an idea or a problem), your name if you give one, the language, whether it came from the website or the app, the app's version number when it came from the app, and the time. The app sends nothing else with it: no location and no device or install identifier.

This is stored in a Cloudflare D1 database and used only to answer you or to tell you once that PeakMere is available. Contact messages may also be forwarded to our company inbox.

To limit spam, we keep a one-way, salted fingerprint (hash) of your IP address together with a counter. The salt is secret and the fingerprint changes every day, and these counters are deleted within 2 days. We never store your raw IP address. Like any website host, Cloudflare processes your IP address to deliver and protect the site, under its own privacy policy.

We keep waitlist addresses until we have sent the launch notice and contact messages for as long as we need them to help you, and we delete either one earlier if you ask.

11. Links to other services

Event details in the app may link to the ticket seller's website, and the app shows credits for data sources. When you open another service, its own privacy policy applies.

12. What we do not do

  • We do not sell or rent personal information. Unless you opt out, we share website visits with Meta for advertising through the Meta Pixel (see "The peakmere.com website"); "Do not sell or share my personal information" under "Privacy choices", "Reject" in the cookie notice, or a Global Privacy Control signal stops it.
  • The app does not track you across other apps or websites. On the website, Google and Meta tools run unless you turn them off.
  • We do not use data brokers.
  • We do not connect to, read or control any of your driver accounts.
  • If PeakMere is ever sold, merged or reorganized, the information described in this policy may move to the new owner as part of that business. The new owner must keep the promises in this policy for the information collected under it, or ask for your consent before using it in a new way. We will tell you before that happens, in the app or on peakmere.com.

13. Children

PeakMere is made for adult drivers. It is not directed to children under 13, and we do not knowingly collect information from children. If you believe a child sent us information, write to us and we will delete it.

14. Your choices and how to delete your data

  • In the app: change or delete your settings in Settings, turn location sharing Off at any time, delete your own wait history with the delete button, or delete the app to remove everything stored on your phone.
  • Anonymously shared location data: it is not linked to you, so we cannot look it up or delete it for one person. It expires on the schedule described in "Optional anonymous sharing of waits and speeds".
  • Airport alerts: turn off "Airport alerts on this phone" in Settings; your push token is then deleted from our server.
  • Exact-location data: delete it at any time with the "Delete my exact-location data" button in the app (Settings). It is linked only to the random install ID on your phone, and otherwise positions are deleted within 30 days, and the trips and waits worked out from them within 90 days, as described in "Optional exact-location sharing".
  • PeakMere AI (assistant): choose "Don't save" to keep conversations off our server, switch saving off at any time, and delete one saved conversation, or all of them together with the memory, in the assistant. Otherwise saved conversations are deleted 5 years after their last message, as described in "PeakMere AI (assistant)".
  • Website forms: write to [email protected] from the address you used, and we will delete your waitlist entry or messages. We answer within 30 days.
  • You can ask us what we hold about you, ask us to correct it, or ask us to delete it. U.S. state privacy laws may not apply to a company of our size, but we honor these requests anyway.

15. Where data is processed

PeakMere is a U.S. service for drivers in the United States. Our servers are in the United States, and our providers may process data wherever they operate.

16. Changes to this policy

If we change this policy, we will update the date at the top. For important changes, such as collecting new kinds of data, we will also tell you in the app before they take effect.

17. Contact

Email: [email protected]. You can also use the form on our Support page.