Reports and photos
Reports may include the details you submit, photos submitted with the report, and approximate location information when device geolocation is allowed.
Direct contact
Contact, provider, and support forms only collect what you choose to send for follow-up.
Usage and reliability
Privacy-minded page and funnel events help show which pages people use, where reporting stops, and whether a technical problem interrupted them.
Security and abuse prevention
Limited session, verification, incident, and moderation data may be used to keep public tools safe, usable, and resistant to spam.
Ads if enabled later
If advertising is enabled, this page explains the cookie, ad-measurement, and third-party data disclosures visitors should expect.
Information that may be collected
- Report details such as ZIP code, description, optional contact email, and optional uploaded photos.
- Contact, provider, and account-interest details that you choose to submit.
- Approximate location information when device geolocation is allowed.
- A temporary random session identifier, page route, previous route, referrer host, browser and device family, and active visible-tab time for privacy-minded usage measurement.
- Limited named report and account funnel events, verification outcomes, support codes, and sanitized incident details needed to diagnose failures and prevent abuse.
How the information may be used
- To review, moderate, and organize reports and related submissions.
- To improve map usefulness, repeat-area visibility, contributor history, and cleanup follow-through.
- To respond to contact requests, support messages, provider questions, accessibility issues, and privacy follow-up.
- To understand which pages receive attention, where visitors stop in the report or account flow, and whether a controlled technical failure interrupted them.
- To reduce spam, abuse, unsafe submissions, duplicate content, and misleading public information.
Public report boundaries
- Public reports should focus on the litter problem, not private accusations or unrelated personal information.
- Photos should avoid faces, house numbers, license plates, and other private details unless they are necessary to understand the report.
- Reports may be edited, hidden, consolidated, or removed when needed for safety, privacy, spam prevention, or map quality.
Production usage analytics and error support
To understand whether ordinary visitors can use the site, LitterMeNot records privacy-minded page and funnel events. These may include a temporary random session identifier stored for the current browser tab, the page route, previous route, referrer host, browser and device family, active visible-tab time, and limited named actions such as opening the report flow, preparing a photo, attempting submission, creating an account, or encountering a controlled failure.
This usage log does not intentionally collect passwords, typed form contents, uploaded photo contents, precise street addresses, Turnstile tokens, authorization headers, or raw environment variables. A technical incident may include a public support code, route, release identifier, browser and device family, and a sanitized error message or stack trace so a nontechnical visitor can report what happened without exposing private application details.
Raw usage events are scheduled for deletion after 90 days. Resolved technical incidents are scheduled for deletion after 180 days. Open incidents may remain longer while a recurring problem is still being investigated.
Cookies, verification tools, and ad technology
LitterMeNot uses limited cookies for protected internal sessions and may use verification tools on public forms to reduce automated abuse. If advertising is enabled later, Google and other ad partners may use cookies, local storage, web beacons, IP addresses, device information, coarse location, and page context to serve, measure, limit, and improve ads where allowed by law.
Third parties, including Google, may place and read cookies on a visitor's browser or use web beacons or IP addresses as part of ad serving and measurement. Google explains how it uses information from sites and apps that use its services on its partner-sites information page.
Ad personalization and consent choices
If personalized ads are enabled for visitors in the EEA, the UK, or Switzerland, consent must be gathered through a Google-certified consent management platform before those ads are served. Visitors can control or clear cookies in browser settings and use Google's ad settings to manage ad personalization.
Non-personalized ads may still use limited technical data, such as device type, approximate location, page context, and basic measurement information when allowed by law.
Retention, access, and follow-up
Reports and submissions may be kept long enough to support moderation, map quality, contributor history, abuse review, legal compliance, and legitimate follow-up. If you need to ask about something you submitted, use the contact page with enough detail to identify the request.