Privacy Policy

1. Who we are

CurbMinder is a street-cleaning parking reminder for Los Angeles. This policy covers our Android and iOS apps and website. Contact [email protected] about personal data.

2. Optional accounts

You may use the app and subscribe through Google Play without a CurbMinder account. If you choose Google sign-in on Android, Firebase Authentication processes your sign-in credentials. We store your account ID, your verified email when available, account creation information, settings and any complimentary-access grant. We do not receive your Google password.

We use verified email addresses to match approved complimentary-access invitations. An administrator may also grant access to your account ID.

3. Settings backup and sync

Signing in on Android automatically enables sync of supported preferences: whether to show feedback prompts and the selected car's Bluetooth address and name. These settings are associated with your account and stored with Cloudflare. Bluetooth identifiers describe the car/device you selected; they are not a record of where it has been. The current iOS app does not sync settings.

We do not sync current or past parking spots, driving trajectories, location caches, location corrections, queued reports, device-attestation keys, OS permission grants or system notification settings. iOS Shortcuts/CarPlay automations must be configured on each phone. Restoring settings does not restore report-sharing consent or bypass device setup.

Signing out stops sync and removes the account's local settings and complimentary grant. Cloud settings remain until you delete your account.

4. Location stays on your device except for reports

The app uses precise or approximate location, background location where permitted, motion, and car connection events to identify a parking spot and resolve street-cleaning restrictions against bundled city data. Current parking state and recent detection samples remain local. There is no automatic server-side location history.

Parking files are excluded from operating-system cloud backups and device transfer where the platform supports these controls. Signing in does not upload them. Location is never attached to account, settings, crash or analytics requests.

5. Optional parking reports

When you confirm a result or report a mistake, you can keep the correction on your phone, send an anonymous report, or explicitly link the report to your signed-in account. Local corrections work without sending a report. Sharing defaults to asking; a sharing choice remembered on one phone is not restored from cloud settings.

A sent report includes the spot's coordinates and accuracy, street/block/side and schedule, resolution evidence and location-reading diagnostics, the answers or correction text you supplied, app/OS/city-data versions, timestamps, and how the report was initiated. It includes the reported parking event, not a trip or parking-history upload. Submitted text or coordinates may themselves reveal identity.

Anonymous reports: stored without an account ID, name, email or persistent installation identifier. Device attestation and temporary replay/rate-limit records protect the upload service but are kept separate from report storage. We do not maintain a device-to-account mapping. This is not a guarantee that a place or free text cannot identify you.

Account-linked reports: contain your authenticated account ID and can be associated with the email in your account. Signing in alone never links reports. Reports queued offline retain the identity and consent selected when created and cannot be uploaded under a different account.

The phone stores a deletion receipt for each delivered report. Use Settings to delete reports sent from that phone. If you lose the receipt after reinstalling, we cannot reliably identify an anonymous report as yours. Account deletion also deletes account-linked reports. Legacy named reports are not automatically matched to new accounts.

Reports are retained for up to 24 months unless deleted sooner. They are used to investigate mistakes and improve city data. We do not publish reports with account identity or precise coordinates attached. Older app versions may need an update to send reports under this policy.

Older Android versions and the current iOS app can still send legacy named reports containing the name/email supplied in their consent screen and an installation identifier. These are not automatically linked to a new account. The account-linked choice and per-report deletion receipts described above apply to Android 1.6.0 and later. Anonymous reports from older clients are also stripped of names, emails and persistent installation links before storage.

6. Subscriptions and complimentary access

Google Play or Apple handles subscription payments and refunds. We never receive card or bank details. Store subscription checks remain on the device; paid subscriptions remain specific to the store. Our backend stores complimentary grants separately. Cached lifetime grants work offline; explicit revocation takes effect when the app next receives it.

A complimentary grant does not cancel a paid subscription. Manage or cancel it separately in your store settings. Deleting your CurbMinder account does not cancel store billing.

7. Crash reports, analytics and service providers

Firebase Crashlytics and Analytics receive crash logs, technical diagnostics, pseudonymous app-instance identifiers and coarse product interactions to maintain and improve the app. Subscription milestone events are purchase history; Google may automatically log product/currency/quantity for an in-app purchase. We do not attach account IDs, report contents, Bluetooth identifiers, streets or precise location to these events.

Firebase Analytics derives coarse geography from masked IP addresses. This is not a parking or driving history and does not include the parking coordinates used for on-device street matching. Firebase Authentication also processes IP addresses for sign-in security and abuse prevention.

Firebase Authentication (Google) provides identity services; Cloudflare provides API hosting and D1 storage; Google Play Integrity and Apple App Attest verify app installations. These providers process data for service delivery under their own security and contractual arrangements. Data may be processed outside your country. We do not use advertising identifiers, sell personal information, share it for cross-context advertising, or track you across other companies' apps.

8. Deletion, access and retention

Delete an account from Settings or our account deletion page after verifying your identity. Account deletion removes cloud settings, profile, grants and account-linked reports and deletes the Firebase identity. A minimal account-ID deletion marker prevents outstanding sign-in tokens from restoring deleted data. Interrupted identity deletion is retried.

Anonymous report deletion requires its receipt. Reports composed but not sent remain on the device. Uninstalling removes local parking data and receipts; account data is not deleted by uninstalling. Temporary anti-abuse records expire within seven days. Infrastructure recovery copies follow provider retention and may take additional time to expire; deleted data must not be restored into active service.

For access, correction, export or deletion questions, including legacy reports and Firebase diagnostics, email [email protected]. Do not send a location history to verify ownership.

9. Security and your rights

We use encrypted transport, account authorization, hardware-backed device signing where available, restricted administrative access and protected local credential storage. No system can guarantee absolute security.

Depending on your jurisdiction, you may have rights to access, correct, delete or export personal data, restrict or object to processing, withdraw report-sharing consent, and complain to a supervisory authority. California residents may exercise applicable CCPA/CPRA rights without discrimination; we do not sell or share personal information for advertising. Precise geolocation is sensitive personal information and is submitted only with an optional report.

For EEA/UK users, account and sync processing supports the requested service; optional reporting relies on consent, and limited diagnostics support our legitimate interest in maintaining the app. Contact us to exercise these rights.

10. Children and policy changes

CurbMinder is intended for drivers and is not directed at children under 13. Contact us if a child has submitted personal information. Material privacy changes update this page's effective date and the in-app terms acceptance gate.

Privacy: [email protected].