Privacy policy

Effective date: August 27, 2026 · Applies to the Beepr mobile app and getbeepr.com

1. Who we are

Beepr Technologies, LLC ("Beepr," "we," "us") makes a driver-awareness app that alerts you as you approach known red-light, speed, and school-zone cameras — and, if you switch it on, as you pass license-plate-reader cameras. Contact: privacy@getbeepr.com.

2. What the app processes on your device

To work, Beepr processes the following entirely on your device:

• Location, speed, and heading (from your device's GPS), including in the background with the app closed or the phone locked, to determine when you're approaching a camera. This data is compared against a camera database stored on your device and used for the alert decision in the moment. It is not logged or transmitted anywhere — driving with Beepr sends nothing about you to us.
• Your settings (which alerts are on, beep counts, thresholds), stored locally on your device.
• A short list of your most recent beeps (which camera and when — not your route or position), kept on your phone for a day so you can report a wrong beep after you park. Deleting the app deletes it.
• The camera database (public-knowledge camera locations, enforced directions, and posted enforcement hours). A copy ships inside the app so everything works offline.

2a. Driving data we collect (telematics)

Beepr collects data about how you drive with the app so we can improve it and make informed product and marketing decisions. This collection is on by default. You can turn it off at any time in the app under Settings, and turning it off stops the collection immediately.

What we collect when this is on:

• Trips: when a drive started and ended, how long it lasted, and how far you travelled.
• Enforcement zones: which red-light, speed, and school-zone camera areas you passed through, identified by camera.
• Alerts: the alerts Beepr played for you, including the camera involved, your speed at the time, and the applicable limit.

We do not collect a continuous record of your coordinates: trips are summarized, and zone events name the camera rather than your position.

We use this data to understand how Beepr is used, decide where to expand camera coverage, measure which marketing brings people to the app, and build audience segments for our own marketing. Where this involves tracking as defined by Apple, we ask for your permission through the system tracking prompt, and we honor your answer.

This section describes collection going forward from its effective date. Data collected under our previous policy, which stated that alert data stayed on your device, remains governed by that policy.

3. Network requests the app makes

• Camera-database updates. Roughly once a day the app checks our content server (api.getbeepr.com) and downloads updated camera data for the regions we cover. This request contains no location, no identifier, and nothing about you — like any web request, our infrastructure provider (Cloudflare) sees standard connection metadata such as your IP address, which we do not use to identify anyone.
• Plate-reader data (only if you turn that alert on or open the coverage map). License-plate-reader locations come from OpenStreetMap (© OpenStreetMap contributors, ODbL) and are published by state. When the alert is on — or when you open the in-app coverage map, which shows these cameras too — the app downloads the file for the state you are in and neighbouring states, based on your phone's last known position, which stays on the phone — the request reveals only which state-level file was fetched, never your precise location or route. With the alert off and the map closed, no such downloads happen.
• Camera reports you choose to send — see Section 4.
• Ad-measurement events (from app version 1.2) — see Section 3a.

That's the complete list. Beyond the Meta ad-measurement SDK described in Section 3a, the app contains no other advertising, analytics, crash-telemetry, or social-media SDKs, and we never collect your location history, driving speed, routes, name, or email.

3a. Advertising measurement (Meta)

We advertise Beepr on Meta's platforms (Facebook/Instagram). So we can tell which ads actually bring people to Beepr — and stop paying for the ones that don't — the app includes Meta's measurement SDK, which sends Meta a small set of app events:

• App lifecycle events: the app was installed and opened.
• Subscription events: a free trial started, or a subscription was charged, with the product and its list price. Your payment details stay with Apple/Google — we and Meta never see them.
• Standard device signals that accompany any such request: IP address, device model and OS version, app version, and — only if you allow tracking at the iOS prompt — your device's advertising identifier (IDFA), which lets Meta match the install to the ad you saw.

Never sent to Meta or any ad platform: your location, routes, speed, alert history, camera reports, or anything about your driving. The on-device promise in Section 2 is unchanged. (Beepr Protect subscribers can consent to a separate, first-party record described in Section 4b — that data goes only to Beepr, never to Meta.)

Your control: if you decline the iOS tracking prompt (or turn it off later in Settings → Privacy & Security → Tracking), no advertising identifier is shared and Meta only receives Apple's privacy-preserving, aggregate ad attribution (SKAdNetwork), which is not tied to you or your device. Alerts and every other feature work identically either way.

4. Camera reports — what you send when you choose to

Beepr lets you report a wrong beep, a missing camera, or a new camera. Reports are voluntary and only sent when you tap Send. A report contains:

• A random ID generated by the app on your phone — used to group your reports, limit abuse, and (in future versions) show you the status of your reports. It is not your name, email, phone number, advertising ID, or hardware serial, and we cannot link it to your identity. Deleting the app deletes the ID; a reinstall generates a fresh one.
• What you tell us: the report type, the camera or place it concerns, direction, and any notes you type.
• Your precise location at that moment — only if you choose "I'm at it right now" when reporting a new camera, so the pin lands where the camera is. If you instead describe the place in words, your location is not included. Wrong-beep reports are anchored to the camera's database record, never to where you are.
• Technical context: app version, camera-database version, and the report timestamp.

We use reports to review, corroborate, and improve the camera database — that's the entire purpose. Reports become the property of Beepr Technologies, LLC as described in our Terms. We do not sell them, share them with advertisers, or use them for anything other than database accuracy and abuse prevention.

4a. Other narrow cases

• If you contact us (support@, data@, privacy@, hello@getbeepr.com), we receive your email address and whatever you write. We use it only to respond, and we don't add you to marketing lists or share it.
• If you make a purchase, the transaction is processed entirely by Apple's App Store or Google Play. We never see your payment details. Apple notifies our server of subscription lifecycle events (trial started, renewed, cancelled, refunded) tied to a random purchase identifier the app generates — not your name, email, or Apple ID. We use this to operate subscriptions, measure trials and cancellations in aggregate, and administer Beepr Protect.
• Product analytics: the app sends Beepr a small number of first-party usage events (for example, "the upgrade screen was viewed") tied to the same random identifiers. These never include your location, routes, or speed, and are deleted after 90 days. They are never shared with ad platforms.

4b. Beepr Protect — the one exception, and only with your consent

Beepr Protect's Ticket Defense Guarantee only works if we can verify what the app did at a specific enforcement zone at a specific time. If — and only if — you subscribe to Beepr Protect and accept the Beepr Protect terms, the app keeps a claim-evidence record on our servers:

• Enforcement-zone events: which camera zone you entered, when, whether an alert played, and — only when an alert played — your speed and the applicable limit at that moment.
• App health snapshots: whether monitoring was running and which permissions were granted, recorded on change and at most daily, plus the camera-database version the app was running.
• If you submit a defense request, Ticket Check, or attorney review request: the citation details you enter, documents you upload, and the contact information you provide (name, email, phone) so an attorney can reach you.

Still never collected, Protect or not: your routes, continuous location, driving outside enforcement zones, or speed except at the moment an alert plays. Claim-evidence records are deleted after 18 months (the rolling claim window plus review time); uploaded citation documents are deleted 90 days after a request is closed. Cancel Protect and the recording stops; you can request deletion at privacy@getbeepr.com.

4c. Ticket Check ("Ticket Scan") — citation photos, extracted details, and attorney sharing

Ticket Check is optional and does nothing until you photograph a notice, citation, or court document and start a check. When you do:

• Your citation photo is sent to our server and read by our AI service provider (Anthropic) solely to extract the citation's printed details into structured fields. Per Anthropic's commercial API terms, the content is not used to train models; Anthropic may retain API inputs for up to 30 days for trust-and-safety purposes, and individual requests cannot be deleted ad hoc from that window. On Beepr's side the photo is ephemeral: we delete it within 72 hours unless you affirmatively choose to keep the original for attorney review.
• The extracted, user-confirmed details (dates, times, location text, speeds, plate as printed) and the resulting factual findings, sources, and checklist are stored with your check so you can revisit the report. Checklist answers you type are stored and always labeled as provided by you.
• Evidence photos you attach to checklist items are stored like citation documents.
• Follow-up documents you scan — a uniform traffic citation that a notice converted into, or a court hearing notice — are handled exactly like citation photos: read only to extract their printed details, ephemeral on Beepr's side within 72 hours, with the extracted dates and details stored with your check.
• What you decided to do: if you tell Ticket Check how you're handling a notice — pay it, contest it, or wait — that choice is stored with your check and counted in the first-party product analytics described in Section 4a, tied to the same random identifiers, so we can understand which paths people take and improve the feature.
• Nothing about Ticket Check — photos, extracted details, findings, checklist answers, outcome choices, reminders, or attorney requests — is ever sent to Meta or any advertising platform.

Reminders are scheduled on your device. When a check extracts an upcoming date — a payment window ending, a notice that may convert into a citation, a hearing date — the app schedules local notifications on your phone. No server sends them, and turning off notifications stops them.

The in-app browser for county sites. Tapping a status or payment link opens the issuing authority's own website inside the app. So Beepr can tell whether your matter still needs reminders and improve the flow, the app records which pages you visit on that site — the web addresses and when — and the outcome it can infer from them (for example, that a payment confirmation page appeared, or that a case-status page indicated a citation was issued). The app does not record what you type there: anything you enter on the authority's site — including payment details — goes to the authority and its payment processor, never to Beepr. These navigation records are tied to the same random identifiers as your check (never your name or account), are used only to operate reminders and improve Ticket Check, are stored with your check and deleted with it, and — like everything else in this section — are never sent to Meta or any advertising platform. The authority's site itself is governed by its own privacy practices.

Attorney sharing is consent-gated per request: if you tap Get Attorney Review, we show you exactly what would be shared (your check's facts and sources, checklist answers, contact details, and any optional items you toggle on) and nothing is transmitted until you confirm. If you simply indicate that you'd like to speak with an attorney, we store that request and the contact details you provide (name, email, phone) so a connection can be arranged — that alone shares nothing from your check with anyone. The recipient is the participating attorney matched to your request; access is through an expiring, revocable, audited link — not an open URL. For Beepr Protect covered matters, sharing is governed by the Beepr Protect terms you accepted. Failed checks are deleted within 7 days; you can request deletion of any check at privacy@getbeepr.com.

5. Permissions we request, and why

• Location ("Always" / "Allow all the time"): Beepr's sole function is alerting while you drive, with the phone locked and the app closed. Background location is the only way to do this. It is processed as described in Section 2 — on-device, and never uploaded while you drive. The only exception is a location you explicitly attach to a camera report ("I'm at it right now" — Section 4).
• Notifications (optional): used only for local, on-device reminders — the weekly reminder if you've turned off your highest-risk alert, and, if you use Ticket Check, reminders about dates extracted from documents you scanned (a payment window ending, an upcoming hearing — Section 4c). No push infrastructure exists; nothing is sent from a server.

You can revoke either permission at any time in your device settings; the app explains what stops working.

6. The website

getbeepr.com is a static informational site. It sets no cookies and embeds no third-party trackers. We use Cloudflare Web Analytics, a privacy-preserving, cookieless measurement tool run by our hosting provider: it counts page views and load performance without cookies, without fingerprinting, and without tracking you across sites, and shows us only aggregate numbers. Our hosting provider may also keep standard, short-lived server logs (IP address, page requested) for security and operations, which we do not use to identify anyone.

7. Data retention and deletion

Everything the app uses day-to-day lives on your device, so deleting the app deletes your settings, beep history, local camera data, and your random reporter ID. Camera reports you sent us are retained on our servers for as long as they are useful for database accuracy, corroboration, and abuse prevention — the camera-location facts they contain may be kept indefinitely as part of the database. To have the reports associated with your app's ID deleted, email privacy@getbeepr.com from within the app's support flow or include your report details, and we'll handle it promptly. Support emails are retained only as long as needed to resolve the issue. First-party usage events are deleted after 90 days; Beepr Protect claim-evidence records after 18 months; uploaded citation documents 90 days after the request closes.

8. Your privacy rights (GDPR, CCPA/CPRA, and similar laws)

Laws like the EU GDPR and the California Consumer Privacy Act give you rights to access, delete, correct, and opt out of the sale or sharing of personal information. The personal information we may hold is what's described in Sections 4 and 4a — camera reports keyed to a random app-generated ID, and support emails. We do not sell personal information. The ad-measurement events described in Section 3a may constitute "sharing" for cross-context behavioral advertising as the CCPA/CPRA defines it; to opt out, decline the iOS tracking prompt or turn tracking off in Settings → Privacy & Security → Tracking — with tracking off, no advertising identifier is shared. We do not use or disclose sensitive personal information beyond the user-initiated report locations described above. To exercise any right, write to privacy@getbeepr.com and we'll handle it promptly.

9. Children

Beepr is a driving app intended for licensed drivers and is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect information from children — or, for that matter, from anyone.

10. Security

The most effective security measure is holding as little data as possible, which is our architecture. Data on your device is protected by your device's own security (passcode, biometrics, encryption). Report data on our servers is transmitted over TLS and stored with access restricted to Beepr's administrators.

11. Changes to this policy

When we change how Beepr handles data, we update this policy and the effective date above, and describe material changes in the app's release notes. (This update adds Ticket Check's follow-up document scanning, outcome logging, local deadline/hearing reminders, and in-app browser navigation records on issuing authorities' sites; the mid-August 2026 update added the Meta advertising-measurement events introduced in app version 1.2; the July 2026 update added the camera-database update service and the voluntary camera-report system.)

12. Contact

Questions or concerns: privacy@getbeepr.com.