Privacy Policy
Last updated: September 12, 2026
Draft for legal review: this page describes the current product behavior and is not a statement that legal counsel has reviewed or approved it.
Information We Collect
We collect information needed to provide and improve the neighborhood discovery service. The categories can include:
- Account information supplied through Replit authentication, such as a username or profile information
- Saved neighborhoods, comparisons, and filter preferences when you choose to save them
- Feedback or bug reports that you submit
- Operational request telemetry such as a timestamp, registered route template, method, status, response byte count, duration, rate-limit outcome, environment/release markers, and a pseudonymous identifier
Operational Telemetry and Retention
Operational telemetry is a first-party, local segmented NDJSON evidence sink used to understand route status, response volume, latency, rate-limit outcomes, and local writer health. It is best-effort evidence for one process or instance, not a fleet-wide or cross-instance record. Its configured retention target defaults to 30 days and is capped at 30 days. Retained evidence has an aggregate 10 MiB cap across segments, not a separate allowance per file; expired, malformed, and oldest-over-cap records are removed during startup, periodic, or write maintenance on a best-effort basis. Bounded temporary replacement files can exist during migration or maintenance and are reclaimed during recovery. Storage outages, lock contention, or process downtime can delay cleanup, so this local sink is not an absolute deletion guarantee.
The local queue is bounded. When storage is slow or unavailable, a record may remain queued, be dropped when the queue is full, or fail to write. These outcomes are counted in operational status but do not block a visitor response. Status reports expose counts and coverage only, not record payloads.
What Operational Telemetry Does Not Store
The telemetry record does not store raw query strings, request bodies, response bodies, headers, cookies, authorization values, or raw IP addresses. A transient transport peer or server-authenticated subject can be converted immediately to an HMAC pseudonym; the source value is not written to the evidence sink. Route values are registered templates or coarse unmatched buckets, not request URLs.
How We Use Information
We use collected information to provide saved features, operate and secure the Service, understand aggregate reliability and usage, improve recommendations, and respond to feedback or support requests. Operational telemetry is not used to create advertising profiles.
Third-Party Services
The Service may use Replit authentication, Open-Meteo weather data, Wikimedia Commons content, and configured AI or other data providers for requested features. Only information needed for the requested feature should be sent to a provider. Provider handling is governed by the provider's own terms and privacy information; do not submit sensitive information in an optional feature request.
We do not add third-party advertising trackers or Google Analytics as part of this telemetry. Essential session cookies may still be used for sign-in and saved features.
Security
We use reasonable technical and organizational safeguards for the Service, including encrypted transport where supported, restricted database access, bounded operational records, and omission of private request payloads from telemetry. No method of transmission or storage is guaranteed to be completely secure.
Your Choices and Questions
You can choose whether to sign in or save preferences. Use the feedback button to ask about information associated with your account or to raise a privacy question; requests are handled subject to applicable law and the information we can reasonably verify.
Cookies
We use essential cookies to maintain sessions and support requested preferences. We do not use third-party advertising cookies or add a new analytics provider through this policy.
Changes to This Policy
We may update this Privacy Policy by posting a revised version on this page and changing the Last updated date. Material changes will be communicated through the Service when reasonably practical.