This Privacy Policy and Notice at Collection describes how Last 1 Enterprises, a Texas business, doing business as Fourth Watch / Meter Watch ("Meter Watch," "we," "us") collects, uses, and discloses personal information. Last 1 Enterprises is formed in Texas. It applies to the Meter Watch iOS app, meterwatch.app, city hosts, app.meterwatch.app, related APIs, emails, and B2B pages. The Terms of Service govern use of the Service.
This notice is intended to satisfy the California Online Privacy Protection Act (CalOPPA, Business and Professions Code §22575 and following), the California Consumer Privacy Act as amended by the CPRA (Civil Code §1798.100 and following), and similar U.S. state laws. We give every user the California rights described below, wherever they live. Nothing in this policy limits non-waivable rights under CCPA/CPRA or under the privacy laws of any other state, for residents of those states.
Notice at Collection
We collect the categories of personal information listed below, for the purposes listed below, and retain them for the periods in the Retention section. We do not sell personal information or share it for cross-context behavioral advertising. Sensitive personal information we may hold (precise location you send for a feature you start, and license plates an account adds) is used only to provide that feature. We do not use or disclose sensitive personal information for purposes that require a right to limit under Civil Code §1798.121, other than the service uses described here.
The table is the notice we provide at or before collection, including when you create an account, send a Quick Report, share a spot, set an alert, park a fleet vehicle, buy a subscription, submit a contest packet, or send a B2B form.
| Category (CCPA) | Examples we actually collect | Sources | Business purpose |
|---|---|---|---|
| Identifiers | Email address, account id, public account UUID used for Apple purchases, Stripe customer id, Apple transaction ids, salted IP hash, SHA-256 hash of a device id, and the device id stored on a city-request row | You; the app or browser; Stripe; Apple | Accounts, security, payments, rate limits |
| Commercial information | Alerts subscription status, contest-packet purchases, donations, organization billing period, card brand and last four when Stripe returns them for an organization | You; Stripe; Apple | Fulfill orders, tax records |
| Internet / network activity | Session cookie, IP address used for rate limits, user agent on B2B forms, basic security logs. No advertising or product-analytics profile. | Your browser or app; Cloudflare | Security, fraud prevention, operations |
| Geolocation | Precise coordinates on a Quick Report, shared spot, confirmation, saved alert, or fleet parking session. City-check coordinates used for that request and not stored. City-request coordinates rounded to about 1 km. | You, when you use the feature | Map reports, alerts, fleet tools, city coverage |
| Vehicle information | License plate (encrypted), state, and optional make, color, year, and notes. Fleet VIN (encrypted) if an organization adds one. The product shows plate state and the last four characters. | You or your organization | Alerts and fleet tools you use |
| User content | Contest-packet fields you type, optional Quick Report notes, flag corrections, support and B2B messages. Photos you take for a packet stay on the phone and are not uploaded. | You | Provide those features |
| Activity records | Server points ledger keyed to a hashed device id. On the iOS app, XP, level, badges, and streaks stay on the phone. | You, when you report, confirm, or share a spot | The points and rewards features |
| Professional information | Organization name, member role, invite email. On B2B forms: company name, contact name, title, work email, work phone, message, city of interest. | You; your organization; public business listings we use for outreach | Fleet, firm, and district products, and B2B outreach |
| Inferences / public records | Meter flags and citation aggregates derived from government open data. These are about meters and blocks, not about a named person, and not about an enforcement officer. | City open data | Public map and scorecards |
| Push credentials | Web Push endpoint and keys, if you enable notifications in the browser. The iOS app schedules reminders on the phone and does not send us an Apple push token. | You; your browser | Deliver alerts you opted into |
We do not collect Social Security numbers, government ID images, bank account numbers, full payment card numbers, biometrics, your contacts or address book, or precise location in the background. We do not collect enforcement officer locations, officer names, badge numbers, or officer rankings. The API rejects a report whose kind is an officer location.
Categories collected and sources
No account needed for the public map
You can view city maps, scorecards, and rights guides without an account. Those pages read public meter and citation files. They do not require you to identify yourself. Your browser will still send standard request data (IP address, user agent) to our servers and to Cloudflare, which we use for security and operations.
If you create an account
Sign-in is email magic link only. There is no password. The iOS app and the website both use that email link. We store your email, account timestamps, a public account UUID (used so an Apple purchase can be matched to the account), hashed magic-link and session tokens, and, on the web, a session cookie named mw_session (httpOnly, 30 days, SameSite=Lax). The iOS app stores access and refresh tokens in the Keychain. We store only hashes of those tokens. Access tokens last up to 1 hour. Refresh tokens last up to 30 days.
If you use paid or optional features
- Alerts: a label and precise lat/lng you save, sweep and meter-expiry preferences, email, and optional web push.
- Quick Reports: broken meter or unclear sign, precise lat/lng, optional pole or space id, optional note of up to 500 characters, and a device id that we store only as a SHA-256 hash.
- Shared spots: precise lat/lng, optional pole or space id, and a hashed device id. A "looking nearby" pin uses the same pattern and expires after about 30 minutes.
- Contest packets: citation fields and written-statement text you enter. We generate a PDF. Photos stay on the phone.
- Payments: Apple or Stripe handles the card. We store transaction and subscription ids, product, status, and amounts. Organization billing may store card brand, last four, and expiration month and year returned by Stripe.
- Vehicles and fleets: encrypted plate, state, and optional make, color, year, nickname, and notes. A fleet may also store an encrypted VIN. See Fleet organizations below.
- Reports and corrections: kind, optional note, coordinates, pole or space id. Quick Reports are not stored under your email.
- City requests: coordinates rounded to about 1 km, city name, optional email, the device id, app version, and a salted IP hash.
- B2B and sponsor forms: company and contact fields, message, IP address, and user agent.
Government data
We ingest parking meter, sweep, closure, and citation datasets that cities publish. We drop license plates, VINs, and similar vehicle identifiers from those government files before they go into public tables. Raw citation archives stay private. We do not publish officer names, badge numbers, real-time officer locations, or officer rankings. We do not collect officer locations from the app.
How we use information
We use personal information to:
- Operate accounts, magic links, and sessions.
- Show Quick Reports and shared spots for the short windows described below.
- Send transactional email (sign-in links, alert notices you opted into, receipts, B2B replies).
- Deliver web push if you enable it, and let the iOS app schedule local reminders.
- Process payments and subscriptions via Apple and Stripe.
- Run fleet organizations: members, vehicles, and company-vehicle parking sessions.
- Award points for reports and spot shares, and show XP and levels that stay on the phone.
- Build contest packets from the fields you enter. You file the contest. We do not submit it.
- Rate-limit abuse, secure the Service, and debug outages.
- Respond to inquiries and provide fleet, firm, or district outreach.
- Publish de-identified, aggregated map statistics from government data.
- Comply with law, including valid legal process and tax recordkeeping.
We do not use personal information for advertising networks, do not sell it, and do not train public AI models on your account or contest-packet contents.
Location data
Precise location is optional and starts when you use a feature. The iOS app asks for location while the app is open. It does not ask for Always location, and it does not collect a background track. The website uses the browser geolocation prompt when you choose to place an alert, check a sign, or request a city. Turning off location stops new GPS reads. IP addresses can indicate a coarse region. We use IP for rate limits and security, not to map your driveway.
A personal parked pin, the one you drop for yourself, stays on the phone. It is not the fleet parking session described below.
Quick Reports
A Quick Report is a broken meter or an unclear sign. When you send one, the app sends precise coordinates, the report type, an optional pole or space id, an optional note, and a device id. We store the coordinates and the note. We store a SHA-256 hash of the device id, not the raw id, and we do not attach the report to your email.
The public map shows the report type, pole or space id, and precise coordinates for about one hour. The optional note is stored and is not included in that public response. After about one hour the report is no longer returned to the map. We do not run a job that deletes the stored row. The row remains so the hashed device id can enforce a limit of three reports per hour. Deleting your account does not delete these rows, because they are not filed under the account. Email hello@meterwatch.app if you want a specific report removed.
Confirming or disputing a report also sends precise coordinates, so we can check that the confirmation is near the report. Those coordinates are stored with the confirmation and are not placed on the public map as a separate pin.
Shared spots
When you share a spot you are leaving, the app sends precise coordinates, an optional pole or space id, and a device id. We store a hash of the device id. People looking in that map area can see the spot while it is open. An open share lasts about five minutes, then it is marked expired and drops off the map. We do not run a job that deletes the stored row. The row does not include your email.
If you mark that you are looking for a spot, we store a precise pin and a radius for about 30 minutes so a nearby share can be matched. That pin is not a public map marker. You can stop looking, which deletes that pin for the device id.
Saved alerts and city coverage
Alert coordinates are stored on the account so we can send sweep or meter-expiry notices for that pin. Delete the alert to remove that pin. Checking whether a city is supported sends precise coordinates for that request. We answer yes or no and do not write that check to the database. A request to add a city stores coordinates rounded to two decimal places, about 1 kilometer, plus the city name and the device id.
Do not use location features while driving. Pull over first.
Fleet organizations
A fleet is an organization on your account. An owner invites people by email. Each member has a role: owner, admin, member, or viewer. We store the organization name, the member email, and the role.
Vehicles on the roster can include a nickname, plate state, make, color, year, and notes. The full plate is encrypted with a key stored outside the database. Organization members see the plate state and the last four characters. A VIN, if someone adds one, is encrypted the same way and is not returned to the app or the roster list.
When a driver parks a company vehicle, the app sends precise coordinates, an optional meter id, and the start time. We store that location on the parking session and on an alert owned by the vehicle's account, so sweep and meter reminders can use that pin. Organization members can access session records for their organization. Owners and admins see open sessions on the fleet page (time, meter id, and whether the session is still open). The public map does not show fleet parking locations. Viewers can read fleet records and cannot record a session.
An open fleet session ends when the driver ends it, or automatically after 24 hours unless the operator has set a different limit between 1 and 168 hours. The stored location stays on the organization's vehicle record after the session ends. If the driver deletes their account, the session is ended and their user id is removed. The location remains with the vehicle and the organization.
Points, XP, and levels
Sending a Quick Report, confirming one, or completing a shared spot can add points. Those points are stored on our servers under the SHA-256 hash of the device id, not under your email. The balance is there so the rewards feature can count them. Deleting your account does not erase that device-hash ledger. Email us if you want it deleted and can identify the device.
The iOS app also keeps XP, a level from 1 to 10, badges, and streaks on the phone. That record is not uploaded as a profile. Deleting the account from that phone removes it from the phone. Signing out does not.
Purchases
The iOS app sells Alerts and contest packets through Apple In-App Purchase. Apple processes the payment. We receive a signed transaction: product id, transaction ids, environment (Sandbox or Production), and renewal status. We match it to the account with the public account UUID. We do not receive your card number, bank account, or Apple ID password from that purchase.
The website sells subscriptions, contest packets, and donations through Stripe. You enter the card on Stripe's form. We store Stripe customer and subscription or payment ids, product, status, and amounts. For an organization, we may also store the card brand, last four digits, and expiration month and year that Stripe returns. We do not store the full card number or the security code.
Deleting your account cancels an active Stripe subscription and replaces the email on the Stripe customer. An Apple subscription stays active until you cancel it in the App Store. The delete screen says so.
Notifications
On iOS, meter-expiry and street-sweep reminders are scheduled on the phone after you allow notifications. We do not collect an Apple push token for those reminders, and we do not send them through our servers.
On the web, Alerts can email you and, if you turn it on, use Web Push. We store the push endpoint and keys until you remove them or delete the account. Alert email is transactional. You can stop it by turning off the alert or canceling Alerts.
Contest packets
A contest packet is a document you prepare from a citation you type in. The fields we store are the ones you enter: citation number, citation date, issue time, violation code and description, location text, fine amount, meter number, what happened, meter condition, signage notes, whether you have photos or receipts, and any additional facts. We generate a PDF and store it on the account. If you file the packet against a fleet vehicle, the vehicle owner can read that packet.
The iOS app can use the camera or the photos you pick so you can attach a meter, sign, or citation to the packet on the phone. Those photos are not uploaded. The app can drop photo metadata before the copy stays on the phone. Time and GPS stay in that on-phone copy only if you opt in. We do not receive the photo.
You submit your own contest to the city. We do not file it for you.
Sharing and service providers
We disclose personal information to service providers that process it on our instructions, and in the limited cases below. We do not allow them to use it for their own advertising.
| Recipient | Role | What they receive |
|---|---|---|
| Apple | In-App Purchase and App Store Server notifications | The purchase you make in the App Store, and the signed transaction we verify. Apple's privacy policy covers Apple's own processing. |
| Stripe, Inc. | Web payments, subscriptions, customer portal, tax on charges | Email, payment details you enter on Stripe's form, subscription and charge metadata |
| Twilio SendGrid | Email delivery | Recipient email and message content (magic links, alerts, receipts, B2B mail) |
| Cloudflare, Inc. | DNS, reverse proxy, tunnel, DDoS protection | Request data (IP, URLs, headers) as any HTTPS reverse proxy sees |
| Last 1 Enterprises | Application, PostgreSQL, object storage, and backups on servers we operate | Stored Service data. The app and database are not hosted on Supabase or Railway. |
We may also disclose information: (a) to a government agency only when compelled by a valid subpoena, warrant, or court order, after we try to narrow it, and after we notify you unless the law or an emergency involving death or serious injury forbids notice; (b) to professional advisors under confidentiality; (c) to a buyer in a merger or sale of assets, who must keep these commitments for data collected under this policy, with 30 days' notice so you can delete your account first; (d) with your direction, including to other people in your fleet organization as described above.
The iOS app does not include an analytics SDK or a crash-reporting SDK. There is no Sentry, Crashlytics, Firebase, or Google Analytics in the app, and the app does not use the advertising identifier. Self-hosted Umami analytics exists in our infrastructure for internal use. It is not currently embedded on public Meter Watch pages. If we add a cookieless, first-party analytics script later, we will update this policy first. We do not use advertising pixels or third-party map tile hosts on the public map. The iOS map uses Apple MapKit.
TikTok is a marketing channel for videos we produce. Meter Watch websites and the iOS app do not include a TikTok pixel or similar advertising tracker.
No sale or sharing for cross-context behavioral ads
We do not sell personal information as California law defines "sell." We do not share personal information for cross-context behavioral advertising. We do not rent data to brokers, insurers, advertisers, towers, or collection companies. Because we do not sell or share in those ways, there is no additional opt-out step, and we do not provide a "Do Not Sell or Share My Personal Information" toggle that changes a tracking configuration. If that ever changes, we will add a working opt-out link before any sale or share begins.
We do not use financial incentives that trade a discount for extra personal information.
Your California CCPA / CPRA rights
If you are a California resident (and, as a matter of policy, if you are not), you may:
- Know and access: request the categories and specific pieces of personal information we hold about you, the sources, purposes, and categories of recipients.
- Delete: request deletion, subject to exceptions (for example completing a transaction, security, free speech, or legal records).
- Correct: request correction of inaccurate personal information.
- Opt out of sale or sharing: we already do not sell or share for ads. You may still send a request and we will confirm that.
- Limit use of sensitive personal information: we already limit precise location and plates to the features you use.
- Non-discrimination: we will not deny the Service, charge a different price, or provide a different quality because you exercised a right, except as the statute allows for a bona fide loyalty program we do not currently operate.
How to exercise a right
Email hello@meterwatch.app from the address on your account, with the subject "Privacy Request," or write Last 1 Enterprises, att. Privacy, 1401 Lavaca St. Unit #140, Austin, TX 78701, and tell us whether you want to know, access, delete, or correct. We will verify by confirming control of that email. We will respond within 45 days, or notify you if we need up to an additional 45 days as the statute allows. An authorized agent may submit a request with your signed permission and proof of the agent's authority. We will not charge a fee for a request unless it is excessive, repetitive, or manifestly unfounded, in which case we will explain.
You can delete the account yourself. On the web, open Account, type DELETE, and confirm. In the iOS app, open Settings, then Account, then Delete Account, and type DELETE. That removes the email address (we replace it with an anonymized address), sessions, saved alerts on that account, vehicles that account owns, contest packets, web push subscriptions, organization membership, and firm lookup history. It cancels active Stripe subscriptions. It does not cancel an Apple subscription, and it does not delete Quick Report or shared-spot rows stored under a device hash, or a fleet parking location that remains on the organization's vehicle. To download a copy of your account data before you delete it, email hello@meterwatch.app. There is no in-app export button.
Retention
We keep personal information only as long as needed for the purposes above, then delete or de-identify it. Backups are removed on a 35-day window. A legal hold can pause deletion for the data it covers.
| Data | Typical retention |
|---|---|
| Account email and profile | Until you delete the account. The email is replaced immediately. Anonymized payment records can remain for up to 7 years. |
| Session cookie and session tokens | Web sessions up to 30 days. iOS access tokens up to 1 hour. iOS refresh tokens up to 30 days. All are revoked when you sign out or delete the account. |
| Magic-link tokens | 15 minutes |
| Saved alert locations and web push tokens | Until you remove them or close the account |
| Quick Report coordinates and note | Shown on the map for about 1 hour. The stored row, including the hashed device id, is kept after that and is not on the map. |
| Shared spot | Shown while open, about 5 minutes. The stored row is kept after it expires and is not on the map. |
| Fleet parking session | Open for up to 24 hours (or the configured limit, 1 to 168 hours), then ended. The location stays on the organization record until the organization or we delete it. |
| On-phone XP, level, and badges | On that phone until you delete the account there |
| Server points ledger | Under the hashed device id until you ask us to delete that device's rows |
| Contest-packet form data and PDF | Until you delete the account, or until you ask us to delete the packet |
| Payment and donation records | Up to 7 years, as tax and accounting rules require |
| IP addresses used only for in-memory rate limits | Hours, not a long-lived store. A city request also stores a salted hash of the IP with that row. |
| B2B lead IP, user agent, and contact fields | Until the inquiry is closed, you opt out, or we no longer need them for outreach records, then suppression as required by CAN-SPAM |
| City-request rows (rounded location, device id, optional email) | Until the city launches or you ask us to delete the row. Deleting the account clears the email and user id on the row. |
| Security logs | Kept for operations and incident response, not for advertising |
| Inactive free accounts | May be deleted after 24 months without a sign-in, with email notice when we have an address |
Security
We use TLS 1.2 or later in transit. The application, PostgreSQL database, and file storage run on servers Last 1 Enterprises operates. They are not hosted on Supabase or Railway. License plates, VINs, and similar identifiers are encrypted at the field level with a key stored outside the database. Private tables use row-level security so one account cannot read another account's rows, except where this policy says an organization member can read fleet records. Access to production is limited to people who operate the Service. No security program is perfect. If unencrypted personal information is acquired by an unauthorized person, we will notify affected people as California Civil Code §1798.82 requires.
Children under 13, and under 16
Meter Watch is not directed to children. We do not knowingly collect personal information from anyone under 13, and we do not knowingly sell or share personal information of consumers under 16. Accounts are for people 18 or older. If we learn we have collected personal information from a child under 13, we will delete it. If you believe a child under 13 (or a person under 18 with an account) has given us information, email hello@meterwatch.app.
Do Not Track and Global Privacy Control
We honor browser Do Not Track (DNT) signals and Global Privacy Control (GPC) by not selling personal information and not sharing it for cross-context behavioral advertising. We do not currently run a third-party advertising or analytics stack that would need to be switched off in response to those signals. Essential cookies, including mw_session, still operate so you can stay signed in. We do not treat GPC as a request to delete an account or to stop transactional email you asked for.
Email, marketing, and CAN-SPAM
We send transactional email through SendGrid: magic links, alert notices you configured, purchase receipts, and replies to messages you sent us. Those messages are not marketing. We do not send SMS.
If we send marketing email to consumers, we will include a working unsubscribe method and our identity, and we will honor opt-outs within 10 business days, as CAN-SPAM requires. Alert email is not marketing. You can stop alert email by turning off the alert or canceling Alerts. You can stop account email by closing the account, except that we may still send legally required notices.
To opt out of optional email, reply with "unsubscribe" or write hello@meterwatch.app.
B2B contact data used for outreach
We market Meter Watch to businesses and fleets in San Diego, Los Angeles, and nearby markets. Contact information may come from: (a) forms you submit on /fleets, /firms, /districts, or /sponsors; (b) your email to us; (c) public business listings, websites, and professional directories. We use that information to contact the business about fleet, firm, or district products, by email or phone.
Work emails and business phone numbers used for B2B outreach are treated as business contact data. You can opt out of further outreach at any time by emailing hello@meterwatch.app or using an unsubscribe link in the message. We keep a suppression record so we do not contact you again. B2B forms also store IP address and user agent for spam and fraud control.
International users
The Service is intended for the United States. If you access it from another country, you understand that information is processed on servers in the United States, which may not have the same data-protection laws as your country. Do not use the Service if you are not allowed to transfer personal information to the United States.
Changes
We will post updates to this policy with a new date. This version was last updated on November 20, 2026. Operator and contact details have been in place since November 9, 2026. If a change materially reduces your protections, we will email the address on your account at least 30 days in advance where we have that address. The prior policy continues to apply to data collected under it unless you agree otherwise or the law requires a different result.
Contact
Privacy questions and CCPA/CPRA requests: hello@meterwatch.app, or mail Last 1 Enterprises, att. Privacy, 1401 Lavaca St. Unit #140, Austin, TX 78701.
Last 1 Enterprises, a Texas business, doing business as Fourth Watch / Meter Watch. Formed in Texas. Last updated: November 20, 2026.
This policy was written to match what the product actually does. It is not legal advice to you, and it was not a counsel review.