FlockNo

Privacy Policy

Last updated: August 18, 2026 · Applies to FlockNo 1.0.39 and later.

Plain-language summary: FlockNo does not require an account, does not run analytics, and does not collect your browsing history. It processes supported real-estate pages to provide surveillance context. Some limited data is sent to public data providers to make the feature work, and feedback is transmitted only when you choose to send it.

1. Purpose

FlockNo's single purpose is to show documented surveillance-device context on supported residential real-estate websites while you shop for homes. It is designed to work without creating an account or tracking your browsing across the web.

2. Chrome permissions & site access

FlockNo requests only the Chrome capabilities and website access needed for its single purpose. It does not request access to every website, your browser history, cookies, downloads, microphone, camera, or unrelated browser capabilities.

Permission / access	Why it is required	Why narrower access will not work
storage	Stores FlockNo preferences, bounded local feature state and short-lived session state used to keep the interface consistent while you browse.	These preferences must persist independently of a property website's own storage and, where appropriate, across page navigation.
Supported property-search domains	Allows FlockNo's packaged content script to recognize relevant map/listing context and add the surveillance and Privacy Report interface on supported services.	FlockNo must interact with the page being viewed to place its interface in context. Access is restricted to specifically supported domains rather than `<all_urls>`.
Published surveillance-data endpoints	Retrieves public surveillance records needed to show nearby known devices and source context.	The underlying records are hosted by external data providers, requiring HTTPS access to those specific services.
OpenStreetMap services	Supports bounded geographic queries for relevant open records and map-tile requests for FlockNo's contextual mini-map.	The information is supplied by OpenStreetMap infrastructure and is not available solely from the property-search page.
FlockNo feedback endpoint	Sends a report only after the user explicitly submits FlockNo's feedback form.	A remote endpoint delivers feedback without embedding a private email address or email-service credentials in publicly inspectable extension code.

FlockNo does not use remotely hosted executable code. Extension logic is packaged with the installed extension; remote endpoints return data or accept user-initiated feedback.

3. What FlockNo does not collect

No FlockNo account, sign-up, profile, or identity is required.
No browsing history is collected. FlockNo's extension code runs only on the supported real-estate sites listed in its Chrome manifest and does nothing on unrelated websites.
No analytics SDK, telemetry service, tracking pixel, advertising identifier, or behavioral advertising system is used.
FlockNo does not sell personal data or browsing activity.

4. Information processed locally on your device

To provide its features, FlockNo processes the following information locally in your browser:

The current supported real-estate page's visible map area, selected listing, and approximate coordinates, used to place surveillance markers and calculate a property Privacy Score.
Your FlockNo settings, such as whether the surveillance layer is enabled and which privacy filter is selected, stored in chrome.storage.local.
A small local engagement counter containing feature-use counts and timestamps. It is used only to decide whether to display a one-time, dismissible support prompt and does not store page content.
Per-tab selection state, such as the currently selected camera or listing, stored in chrome.storage.session and cleared by Chrome when the browser session ends.

Except for the limited network activity described below, this information remains on your device.

5. Network requests used to provide FlockNo

FlockNo retrieves published surveillance information and map imagery over HTTPS from third-party data providers. Those providers may receive ordinary network metadata, such as your IP address, as part of handling the request. FlockNo does not add an account identifier, advertising identifier, or FlockNo tracking cookie to these requests.

Provider / endpoint	What FlockNo sends	Purpose
FlockHopper public dataset `data.dontgetflocked.com`	No information about you or your search; FlockNo downloads a published data file.	Retrieve documented ALPR locations.
OpenStreetMap Overpass `overpass-api.de` / `overpass.kumi.systems`	The numeric geographic bounding box for the map area currently visible on a supported site. FlockNo does not send the listing address, your identity, or a FlockNo account ID.	Retrieve current OpenStreetMap surveillance records for the visible area.
Electronic Frontier Foundation Atlas of Surveillance `atlasofsurveillance.org`	No information about you; FlockNo downloads published surveillance-program data.	Retrieve documented agency ALPR program information.
OpenStreetMap tile service `tile.openstreetmap.org`	Standard map-tile requests generated by the mini-map displayed inside FlockNo.	Display map imagery in FlockNo's side panel.

6. Feedback you choose to send

FlockNo includes an optional, user-initiated feedback form. Nothing is submitted until you choose Send feedback.

Your report contains the message and feedback category you provide. If Include diagnostics is enabled, the report may also include the FlockNo version, the current supported site and page URL, the selected camera or listing identifier, and source-load status. You can turn diagnostics off before sending. FlockNo's feedback payload does not include a street address or map coordinates.

Who processes feedback

Feedback is sent over HTTPS to FlockNo's feedback endpoint at flockno-feedback.flockno.workers.dev, which is hosted by Cloudflare. The endpoint uses Resend to deliver the report by email to the FlockNo developer. Cloudflare and Resend therefore process feedback data as service providers for this limited purpose. Their own privacy and security practices also apply to their services.

Feedback is used only to operate, troubleshoot, secure, and improve FlockNo. It is not sold and is not used for advertising or cross-site profiling.

7. Retention

Surveillance data cached by the extension is kept in memory with short time-to-live limits and bounded cache size, and is discarded when the extension service worker or browser session no longer retains it.
Local settings and the engagement counter remain until you clear extension storage or uninstall FlockNo.
User-submitted feedback may remain in the developer's email system for as long as reasonably necessary to investigate the report, provide support, maintain security, and improve FlockNo.

8. Your choices

You can turn the FlockNo surveillance layer off using the extension's controls.
You can disable or uninstall FlockNo through Chrome at any time. Uninstalling removes extension-local storage maintained by Chrome.
You can turn off Include diagnostics before sending feedback if you do not want the current supported page URL or other optional diagnostics included.
You can simply choose not to send feedback.

9. Changes to this policy

This policy may be updated when FlockNo's functionality, data handling, or service providers change. The current version will be posted at this URL with an updated date. Material changes to data handling will also be reflected in the extension's Chrome Web Store disclosures as required.

10. Contact

For privacy questions, support, bug reports, feature suggestions, or surveillance-data corrections, use the Send feedback feature built into FlockNo. Reports are delivered privately to the developer without publishing a personal email address inside the extension or on this website.

FlockNo is independently developed and is not affiliated with, endorsed by, or produced by Zillow, Redfin, Homes.com, Realtor.com, Flock Safety, OpenStreetMap, the Electronic Frontier Foundation, Cloudflare, or Resend.