FINEME NOT

Speed cameras ahead. Keep your cash.

Fine Me Not gives you a heads-up as you approach mapped speed and red-light cameras. Set it up once, leave it running in the background, and keep your eyes on the road.

Free. No ads. No subscriptions.
Getting a ticket is expensive enough.

For iPhone running iOS 17 or later. Check your iPhone.

A heads-up before the camera.

Fine Me Not gives you one short, loud siren when you approach a known speed or red-light camera. Turn it on, put your phone away, and use whatever navigation app you like. No map to watch. No ads, accounts or subscriptions.

Background location uses battery. Fine Me Not keeps monitoring requested in Low Power Mode, but iOS, GPS reception and audio conditions can still delay or prevent a warning. It cannot guarantee every camera or every alert.

Set it up while you’re parked.

  1. Turn on Camera warnings.

    Open Fine Me Not and switch Camera warnings on. At the first location prompt, choose Allow While Using App, with Precise enabled. Avoid Allow Once: it does not give the app lasting access.

  2. Give it background location access.

    If iOS asks to change access to Always, approve it. Otherwise open Settings → Privacy & Security → Location Services → Fine Me Not. Select Always and turn Precise Location on. Location Services must also be on at the top of that settings page.

    If Always isn’t listed yet, return to the app, enable warnings and approve the first location request, then check Settings again. If you previously chose Don’t Allow, change it here. The app cannot approve permission for you.

  3. Allow notifications and sound.

    Choose Allow at the notification prompt. Then check Settings → Notifications → Fine Me Not: turn on Allow Notifications, Sounds and Time Sensitive Notifications where available. Allow Lock Screen and banner alerts if you want to see them.

    If you use a Focus, check Settings → Focus and allow Fine Me Not and time-sensitive notifications where those options appear. Driving Focus has different controls; test with the Focus you actually use. Apple’s Focus instructions.

  4. Allow camera-list updates.

    In Settings → General → Background App Refresh, enable Fine Me Not. Choose Wi-Fi & Cellular Data and allow the app cellular access if you want downloads away from Wi-Fi. Low Power Mode disables Background App Refresh; you can still use Update now inside the app.

  5. Test the sound in your car.

    Connect Bluetooth or CarPlay, select the correct stereo input, and tap Test warning. Start at a comfortable volume, then raise the phone’s media volume and the car volume until the short siren is easy to hear. Try Silent mode too. The ringtone-volume setting is separate.

    If sound comes from the wrong place, check the output shown beneath Test warning and the audio-output control in Control Center. A sound test checks your current audio connection, not future background GPS reception.

  6. Check the list and Status.

    Tap Update now while connected. Confirm the database shows warning locations and a publication date. Status should show Monitoring or Ready · waiting for movement once a usable location is available. Resolve permission or database messages first. Then leave Camera warnings on.

The app needs location and notifications. It does not request camera, microphone, contacts, photos, or Motion & Fitness access. Ordinary car-audio playback has no separate Bluetooth permission prompt.

iPhone. iOS 17 or later.

Works on iPhone XS, XS Max, XR and newer, plus iPhone SE (2nd generation and later). Supports iOS 17, 18, 26 and 27. Check Settings → General → About for your model and iOS version.

Older iOS support starts with version 1.0.2, available to TestFlight testers. The initial App Store release is still awaiting Apple’s approval.

Something not working?

I passed a camera and heard nothing.

When parked, check Camera warnings, Always and Precise Location, then try Test warning on the same audio connection. Tap Update now. With Quiet below speed limit on, silence may be expected. Missing cameras, poor GPS, direction of travel and interrupted monitoring can also explain it.

The siren is silent or uses the wrong speaker.

Raise media volume, check the output beneath Test warning and select the right car-stereo input. End any call and try again. A Bluetooth connection can send sound to the car even when you expect the phone speaker.

I’m below the posted limit but it still warns.

The app may have an uncertain speed, an unknown limit or a lower estimate for the road. School-zone cameras may use the reduced limit throughout the day. Red-light and combined cameras always warn. Follow posted signs; a siren does not establish that you were speeding.

How do I stop it?

Turn off Camera warnings to stop location monitoring. Permissions can also be changed in iPhone Settings. For a permission problem, follow the setup steps.

Found something weird? Tell me.

While parked, open Fine Me Not and tap Report a problem. Tell me what happened, add anything that might help, then review and send. Your reports help me make the app better.

Nothing is sent automatically. Reports are public, so leave out personal information. What’s included?

The camera list.

Fine Me Not combines OpenStreetMap with public city, county and transportation-agency records. Albuquerque and its surrounding metro get particular attention, alongside selected major U.S. metros. Coverage is incomplete and varies by place.

Possible speed camera means the position or current equipment presence is uncertain. Some records cover a stretch of road or a known mobile-camera deployment area. They are not live sightings. Separate travel directions can count as separate warning locations.

The current list contains 2,695 warning locations. Of the speed-camera directions in that list, 1,305 of 1,765 have enough limit information to use Quiet below speed limit (73.9%). That includes 38 of 40 listed Albuquerque city directions. Some values are conservative estimates; this is not a count of verified speed-limit signs.

Limits come from agency records, community data and matching cameras to roads. Some are estimates. Where several supported limits might apply, the app uses the lower one to decide whether to stay quiet. It cannot see school beacons, temporary signs or changing road conditions.

Source checks run Sunday at 9 p.m. Mountain Time, before publication at midnight as Sunday becomes Monday. The schedule follows Denver daylight saving time. Your phone catches up when iOS and its connection allow it. Failed downloads keep the saved list in place.

Coverage by metro · Albuquerque locations · Download the list

Sources and licenses

Camera data includes © OpenStreetMap contributors, under the Open Database License. Road data also includes Overture Maps Foundation and its contributing sources, including OpenStreetMap and TomTom where identified.

Local sources include Albuquerque’s camera list and speed-limit information, Bernalillo County and Rio Rancho. Records retain source references; listing an agency does not imply endorsement.

The app, original icon and siren use the MIT license. Separate terms cover the data. Anyone can inspect the code, source research and speed-check method.

Your driving stays on your phone.

Location and speed are used on your iPhone to check for cameras. They are not attached to camera-update requests or the automatic details in a problem report. There are no accounts, ads, tracking or automatic analytics uploads.

What stays on the phone

The app keeps settings, camera lists and recent encounter identifiers and times to avoid repeated sirens. Local diagnostics include the latest sound attempt, which can name a camera and audio output. The app does not record a continuous trip log.

Version 1.0.1 also keeps a limited, location-free troubleshooting history for up to 24 hours, and up to five filtered Apple crash or hang diagnostics and five report drafts for seven days. This reporting folder is excluded from backups. Use Delete local report history inside Report a problem to clear it.

What you choose to send

Only tapping Send report uploads a reviewed report. It can contain app and iOS versions, iPhone model, permissions, recent warning decisions, audio and database status, selected crash details and your explanation. Reports pass through the Cloudflare-hosted service at crash.dustwave.xyz and become public GitHub issues. There is no advertising or tracking use.

The service keeps retry receipts for 30 days and bounded summaries to group reports. Public issues may remain indefinitely. A report can identify you if you put identifying information in it; it is not guaranteed anonymous. Deleting local history does not remove published reports, and removing an issue cannot erase copies others have made.

Connections and your choices

The website and camera downloads use GitHub Pages and Cloudflare. Those providers receive normal connection information, including IP addresses, under their Cloudflare and GitHub privacy policies. The reporting service uses short-lived keyed hashes for abuse limits; it does not put IP addresses in issues. Apple handles any information shared through TestFlight.

You can stop monitoring, change permissions, discard drafts or delete the app. Other local app data may be included in backups according to your settings. For privacy questions, contact Alonso Indacochea through support; do not post private information publicly.

Updated .