California Speed Cameras — Privacy Policy

Effective date: November 8, 2026. Version: 2026-11-08.2.

1. Who we are and what this policy covers

MOVINGNOW LLC, a California limited liability company (referred to here as MovingNow LLC), provides California Speed Cameras, its camera-data update service, and related pages at californiaspeedcams.com. Our mailing address is 27564 Sunny Creek Dr, Valencia, CA 91354, United States. For privacy questions, access or deletion requests, or complaints, email [email protected] or write to that address, marked “Privacy.”

This policy covers our handling of information for this Service. Independently operated city websites, Android and vehicle hosts, email and file providers, Google Play, and other third-party services have their own policies. An announced platform or feature is not necessarily available. The 1.0 series has no purchase flow, subscription enforcement, ads, MovingNow account, or third-party analytics/crash-upload SDK.

2. The main privacy choices

Camera reminders, the bundled street map, and local history operate using information on your device. The app does not send GPS coordinates, speed, bearing, routes, or History to MovingNow as part of monitoring or database updates. It does not record a continuous route. Local history still reveals visited camera locations and times and should be treated as sensitive.

Internet connections are used to check or download the shared camera database. Cloudflare processes normal connection metadata to provide and protect that service. You can disable automatic checks and keep using your saved data. If you choose to email support, we receive the message and sender information; a diagnostic attachment is optional, off by default, and previewable. If you choose to export history, it goes to your selected storage provider, not to us. These are separate choices; none starts a payment.

3. Information processed on the device

When permitted and enabled, the app processes precise location, location accuracy, speed and speed uncertainty, bearing, and elapsed timestamps to determine proximity, direction, reminder eligibility, and inferred passages. Processing continues in the background while monitoring is enabled, including when the app is closed or not in use. New reminder and initial passage eligibility use sustained usable GPS speed of at least 5 MPH; this is not a vehicle classifier, and brisk walking, jogging or cycling may qualify. GPS alone does not reliably identify a vehicle or determine a legal speed. A bounded recent set of GPS fixes may be kept in memory for movement/approach evidence; it is not saved as a route or included in support diagnostics.

After you agree to the Terms and complete the first setup, monitoring turns on automatically. A persistent notification provides status and a Disable control. A manual Disable remains off until you choose Enable; reopening the app or granting permissions does not reverse it. Resume after restart is on by default for monitoring you have enabled, can be turned off, and remains subject to Android restrictions and permissions. No monitoring starts merely from installation.

The foreground map may use fresh location and speed in memory to show your position and adjust its view. It reuses monitoring fixes when available; otherwise its location listener runs only while the foreground map is visible and active. No location or viewport is sent to a map or tile provider. The bundled modified Census road data is public geography, not a travel log.

4. Local camera-event history

History is on by default while monitoring runs and can be paused separately. It stores a random event ID, an inferred observation time, camera/location and source references, street/corridor and direction, camera status, approximate GPS speed and uncertainty when available, published limit, and the database/source version or date. Camera details are frozen at observation; later changes, deletion, or rollback of the shared database do not rewrite saved events. Raw user coordinates and continuous routes are not stored in History.

A location can be inferred from a camera reference and time even without latitude/longitude. History may be inaccurate, incomplete, or duplicated and is not proof of an offense. Pause recording, delete individual events or all history, and select retention in History. The default keeps records until deletion, subject to a 20,000-event cap that removes oldest records; optional periods are 30, 90, or 365 days. Retention is enforced on history access and writes, rather than by a continuously running cleanup service. Pausing preserves existing records. Clearing app data or uninstalling removes our on-device history and settings.

5. Local settings, consent, and technical state

The app stores appearance, alert and timing preferences, enabled/auto-resume choices, permission/setup flags, the last monitoring-choice time and origin, and local history settings. It may store the selected offline TTS voice identifier and a reference to audio outputs for route-change reminders; those local references can include output names. They are not included in diagnostic reports. Current GPS/alert state is held in memory. The app does not maintain a new persistent diagnostic event journal or copy system logcat for support.

The accepted Terms version, exact document hash, and local acceptance time are saved to remember agreement, not to establish a server account or purchase. The shared catalog, previous verified copy, update preferences, ETag, last check/install times, categorized result, source-check dates, and recovery/anti-replay state are stored for updates and recovery. These local records are not uploaded as telemetry. Uninstalling or clearing app data removes them; previously exported files or copies outside the app are unaffected.

6. Shared database connections and website requests

For database checks the app requests a small common signed manifest from data.californiaspeedcams.com over HTTPS. A full common catalog is downloaded only for a changed published release or recovery of a verified copy. Requests use a common app user-agent and cache validators; they contain no location, History, MovingNow account, advertising ID, or persistent device ID. A source check that finds no camera changes does not require another full database download.

Cloudflare provides our R2 storage, CDN delivery, and network/security functions. It necessarily processes IP addresses, request time and resource, HTTP/user-agent and connection details, cache/security results, and potentially approximate network-derived region. An IP address and related metadata can be personal information. Cloudflare describes its practices at https://www.cloudflare.com/privacypolicy/. We can receive aggregate traffic information and security or operational information made available through these services. A database request does not identify which cameras you visited, but normal network metadata should not be treated as anonymous.

Visiting our website or legal pages similarly sends normal browser request information to the hosting/network providers. We do not use the website to collect trip History or precise GPS, and do not operate advertising pixels or cross-site behavioral profiles for this Service. City links open the external browser; that connection is governed by the city site and browser and can expose normal request metadata to them. Our source collector fetches public city materials on our infrastructure; it does not receive or require user travel data.

7. Cookies, local storage, and tracking signals

The native app uses local application storage for its functions, not advertising cookies. The website does not use advertising or cross-site analytics cookies. Hosting/security functionality can use necessary browser storage or cookies, for example Cloudflare security or challenge cookies when those functions are invoked. Their purpose is delivery, abuse prevention, and security, rather than behavioral advertising. Blocking necessary storage can affect site availability. Browser storage controls do not delete the app's local History.

We do not sell personal information or share it for cross-context behavioral advertising, and we do not permit advertising partners to track users across unrelated services through our app or website. We do not use personal information to train a general-purpose AI model. Do Not Track signals do not change these practices because we do not conduct that tracking. Global Privacy Control is treated consistently with an opt-out of sale or advertising sharing; no account or additional opt-out step is needed for practices we do not perform. Security and necessary service processing can still occur.

8. Support messages and optional reports

If you choose Contact support, the app opens a draft addressed to [email protected] in an email app you select. You decide whether to send it. If sent, we receive your sender address, name if supplied by your email provider, message and email headers, correspondence, and any attachment you include. We use these to respond, investigate, resolve issues, maintain security, and handle privacy or legal requests. Do not send passwords, card details, or unnecessary trip information; your own written text and independently added attachments are not automatically scrubbed.

An optional app-generated diagnostic report is off by default. When selected, it is generated on demand and the exact JSON is shown for review. It contains allowed technical fields: app/build and Android API versions, permission/GPS/notification and channel state, enabled/running monitoring and coarse GPS-quality category, background restrictions, alert/audio choices, the reminder filter, keep-screen-on preference and notification-vibration state, and output types without device names, mute/DND/voice-confirmation state, Android Auto connection state, and shared-database sequence/counts and categorized update result/error with coarse relative age.

That generated report excludes coordinates, routes, History, camera visits, GPS speed or bearing, exact passage times, device/account/advertising identifiers, Bluetooth/output names, passwords, keys, payment information, arbitrary exception messages, and full system logs. You may uncheck it, cancel, or send a message without it. No diagnostics are uploaded in the background. Opening a draft or returning from the email app does not confirm delivery.

The temporary app attachment is shared through a restricted, read-only content URI. New reads are blocked after 24 hours; Android may remove the cache sooner, and may schedule physical cleanup later. Up to five small temporary reports are retained within the app cache. No file is created merely to view the report or cancel the form. A selected email app and recipients may keep their own copies; our cache expiration cannot delete those copies.

Our support address uses Cloudflare email forwarding to a Google Workspace mailbox operated for MovingNow. Cloudflare and Google process message delivery, spam/security information, and mailbox storage as appropriate to their services. Your own email provider also processes what you choose to send. Google describes its general privacy practices at https://policies.google.com/privacy and its Workspace-related service-data practices at https://cloud.google.com/terms/cloud-privacy-notice. We do not promise end-to-end encryption for ordinary email or automatically publish support correspondence.

9. Manual history exports and device providers

Manual export uses password-encrypted backup files and the Android system file picker. You choose a local file or your own cloud/file provider; MovingNow receives no copy. Exported backups can contain sensitive history and should be protected even though encrypted. There is no forgotten-password recovery. Deleting History or uninstalling does not delete an exported file or a provider's copy. Manage those with the selected provider. Import validates and merges records under the app's displayed retention/import choices and does not restore permissions, payment entitlements, or legal agreement.

Automatic app cloud backup and app-controlled device transfer are disabled by application configuration. This does not control a compromised/rooted device, a screenshot you take, third-party device tools, or your separately exported files. The app queries compatible TTS and email handlers for the features you request, not to upload an installed-app inventory.

10. TTS, audio, notifications, and vehicle hosts

Speech uses an installed English voice reported by the system as offline. The app may speak a published street and limit; it does not upload text or location for remote speech. Voice installation initiated in system settings and provider behavior are governed by the relevant provider. We cannot independently audit every installed system component. Chimes are generated app assets without a network service.

Camera-reminder filters can select all or live locations, optionally requiring a reliable above-limit estimate. These affect reminders rather than local History recording. An in-app banner is used on app screens; the selected system notification covers other apps and a locked or noninteractive display. The selected app sound applies in both contexts. Vibration follows Android camera-category and system settings; new categories initially enable it and existing system choices are preserved. A private/generic lock-screen preview reduces incidental disclosure, but your notification settings may permit full text. Sound, displays and notifications can reveal a nearby street or camera to people or services with authorized notification access.

The VIBRATE permission is used for local reminder haptics, and WAKE_LOCK for short offline speech startup or chime playback with the display off. These functions do not send data, wake the display, bypass the device lock, or override DND. The background-location explanation names the actual localized system choice, such as Allow all the time, and you can decline and browse cameras.

The authorized Android Auto host receives directory entries and reminder text it displays. On compatible hosts, a rendered offline map can show cameras and your current position for a following view. Map gestures are processed locally, and the bundled street reference is used locally for same-street approach distance, direction-at-arrival and in-area checks. These in-memory calculations are not a saved route or a new upload. The app-rendered map uses bundled offline roads and makes no map-provider request. An older host-rendered map may use the host or map provider’s own network services and policies. Your GPS is not uploaded to MovingNow by this car interface. Continuous GPS/background operation and a visible map or keep-screen-on preference can increase battery use. Nearby ordering or a displayed reminder can reveal your area to that host or people who see or hear it. Phone/vehicle notification, audio, screenshots, and operating-system services are controlled in part by their own settings and policies. Detailed History, consent, permissions, passwords, and deletion controls remain on the phone. We do not receive your GPS or History from the car host as part of this integration.

11. Payments if you later subscribe

There is no payment flow, trial charge, purchase-token upload, or subscription enforcement in the 1.0 series. The following describes processing applicable only if you later choose an actual Google Play purchase in a subscription-enabled release; accepting this policy or the Terms is not a purchase.

Google Play processes checkout and your payment details under Google's policies. We do not receive your full card number or payment credentials. For a paid subscription, purchase and entitlement verification can process the purchase token, product/offer, transaction/order reference, purchase/expiry and renewal state, and cancellation, refund, or revocation status, together with normal server connection metadata. These records are used to supply and restore access, verify purchases, prevent fraud, process required notices/refunds, and comply with legal/accounting obligations. Purchase verification does not require us to receive GPS, camera History, or a MovingNow registration, and payment records are not joined to trip data for advertising.

Google may provide developer transaction, settlement, tax, or customer-service information under its platform arrangements. Contacting support about a payment can also provide an order reference or receipt you choose to share. Do not send payment credentials. Purchase records needed to verify active rights, handle adjustments or disputes, or satisfy statutory accounting obligations may need to be retained after app deletion; cancellation and privacy deletion are distinct actions. No record of a purchase is created by accepting the current app's Terms alone.

12. Why information is used and when it is disclosed

We use the information described above to provide the features you request, deliver and protect shared data, respond to support/privacy inquiries, improve reliability using the technical information voluntarily supplied, and meet legal obligations. We limit information to what is reasonably needed for these purposes. We do not use your local trip data for marketing, insurance scoring, employment screening, or sale to enforcement or data brokers.

Service providers such as Cloudflare and Google process information for delivery, email, security, and, where applicable, platform purchases. People handling support or technical/legal issues receive access only as needed for their responsibilities. We may disclose information we actually hold when reasonably necessary to comply with valid legal process, protect rights and safety, investigate fraud/security incidents, or carry out a lawful business transfer with applicable privacy protections. A transfer does not give a new owner permission to disregard this policy or mandatory rights. Public sources or a corporate acquisition do not give us remote access to your on-device History.

We cannot provide travel records that we do not hold. This is not a promise that device data is immune from access by someone with your device, a selected provider, or lawful process directed to those parties.

13. Retention and deletion

Live location and map/alert state are held in working memory for the relevant session; no continuous route file is retained. Local History follows the choices and limits in section 4. Settings, consent, downloaded data, and technical check/recovery state remain until replaced, reset, or removed with app data. Database recovery retains a limited previous-copy mechanism rather than a permanent history of every check. Temporary support-file access expires as described in section 8. User-selected exports and mail-provider copies have their own retention.

For support correspondence and voluntarily supplied reports we retain identifiable information only as reasonably needed to investigate and respond, address recurring or security issues, resolve disputes, and meet legal obligations. The period depends on whether a case is open, the nature and sensitivity of its contents, the last relevant interaction, an unresolved incident or dispute, and any applicable legal retention duty. When those purposes end, information is deleted or de-identified; legal holds can require restricted retention instead. This is a purpose-based retention policy, not a promise of automatic deletion of every mailbox copy after a fixed number of days. Request deletion at [email protected].

Network/security records and aggregates held through hosting providers follow the operational/security need, available service settings, and providers' applicable retention arrangements; retention may differ by record and provider. We do not assert a fixed universal Cloudflare or Google deletion period. We use available controls and provider assistance for valid requests and do not retain identifiable records longer than reasonably necessary for the disclosed purposes. Required transaction, tax, fraud, or legal records, if paid features are used, may be kept longer than routine support content. Restricted backups and legal records may not be removed immediately from every storage copy; they are not used to resume ordinary marketing or unrelated processing.

14. Your controls and privacy requests

Use Android settings to revoke location/notification permissions, disable monitoring in the app or persistent notification, turn off automatic updates, manage History retention, or delete local data. Revoking permissions can prevent the corresponding feature. Deleting app data or uninstalling removes our local settings/history, but does not cancel a future Google Play renewal or remove your exports or emails. Cancel a subscription in Google Play separately.

For information we hold, email [email protected] or write to our postal address to request access, correction, deletion, a portable copy where applicable, or an explanation of processing. Tell us the service and relevant correspondence, without sending a password, full payment credential, or unnecessary trip details. We may reasonably verify identity/control of the address or transaction and request limited clarifying information. An authorized agent can act with appropriate proof of authority, subject to any verification the law permits.

We respond within applicable legal periods, explain any lawful exception or permitted extension, and do not discriminate for exercising privacy rights. If a request is declined, you may seek review by replying with “Privacy appeal,” and may complain to the appropriate regulator. We cannot look up or remotely delete on-device data we never receive; use the local controls for that data. We do not require creation of a MovingNow account to make a request.

California residents have rights, where the CCPA/CPRA applies, to know/access, correct, and delete covered information, opt out of sale or cross-context advertising sharing, limit certain uses of sensitive information, and receive equal treatment. We do not sell or engage in that advertising sharing, or use sensitive information for unrelated profiling, so there is no sale/advertising-sharing process you must enable to opt out. Local precise location is used for requested app functions. Other jurisdictions may provide additional access, objection, restriction, portability, consent-withdrawal, appeal, or complaint rights. Nothing here waives mandatory rights or claims an exemption based solely on the absence of an account.

15. Security and international processing

We use app-private storage, HTTPS for our data service, signed catalog validation, restricted attachment access, and access controls appropriate to the information processed. History event details use Android Keystore-backed encryption; some private database indexes, settings, and consent records are not separately encrypted. Password exports use authenticated encryption. No system is completely secure, and these protections do not guarantee safety on a compromised device or protect an exported file if its password is disclosed.

MovingNow is based in the United States and the Service concerns California. Providers can process information in the United States and other countries where they operate; protections can differ from those in your location. Where applicable law requires a transfer mechanism or additional safeguard, processing must use the applicable lawful mechanism. This statement is not a request to waive privacy rights by using the Service. We do not treat acceptance of general Terms as a substitute for consent where specific consent is legally required.

16. Children, policy changes, and contact

The Service is not directed to children under 16, and we do not knowingly collect personal information online from children under 13. We do not ask for a date of birth or perform a claim of verified age. If you believe a child has provided personal information to us, contact [email protected] so we can investigate and take appropriate deletion or other required action. A minor's lawful local use does not authorize undisclosed collection or advertising.

We update this policy when practices or applicable requirements change, show the effective date and version, and provide a prominent in-app or website notice of material changes as appropriate. If a new use requires separate consent, we obtain it before that use. A privacy-policy update does not itself authorize a subscription, revive disabled monitoring, or authorize previously declined diagnostics. Published changes do not retroactively remove accrued rights.

Privacy and support: [email protected]. Mail: MovingNow LLC, 27564 Sunny Creek Dr, Valencia, CA 91354, United States.