1. Scope
This policy applies to location records used to describe publicly documented roadside monitoring in PrivateRoute. It does not make every listed system equivalent, claim continuous operation, or treat an absence of records as proof that no monitoring exists.
2. Initial coverage region
The first release program focuses on Kentucky, Tennessee, Georgia, Alabama, and Florida. Coverage can differ by state, county, city, road, source category, and update cycle. PrivateRoute displays coverage confidence separately from documented exposure so a sparse dataset is not mistaken for a clear route.
3. Sources we may accept
- Official agency publications, maps, permits, inventories, meeting records, procurement documents, or open-data portals.
- Statutes, regulations, court records, and other authoritative public documents.
- Reputable reporting that identifies a location and explains its sourcing.
- Direct field observations or community leads that can be independently reviewed.
- Licensed or permissioned datasets whose terms allow the intended use.
4. Sources we reject or restrict
- Rumor, anonymous assertion, or a social post without corroborating evidence.
- Personal information about private individuals that is unnecessary to describe infrastructure.
- Illegally obtained material or content whose use would violate applicable terms or rights.
- Records that cannot be located with sufficient precision for responsible route comparison.
- Entries created to harass, mislead, target a person, or facilitate unlawful activity.
5. Record fields
A record may include a category, geographic coordinates, source reference, source date, last review date, jurisdiction, directional or road context, location precision, operational-status notes, and internal provenance identifiers. Unknown fields remain unknown; they are not silently inferred.
6. Evidence and confidence
PrivateRoute evaluates source authority, corroboration, age, location precision, and record consistency. A stronger confidence level means the available evidence better supports the displayed record; it does not guarantee that a device is present, active, legally authorized, or configured in a particular way at the time you travel.
7. Location precision and route matching
Source material may describe an exact point, an intersection, a road segment, or only a broader area. PrivateRoute should preserve that uncertainty and use a match radius appropriate to the stated precision. It should not display false coordinate precision or claim a route encounter where the evidence supports only proximity.
8. Duplicates and conflicts
Records that appear to describe the same location are reviewed for consolidation while retaining provenance. Conflicting sources are not resolved solely by majority count; authority, date, specificity, and documented context matter. Material unresolved conflicts should lower confidence or prevent publication.
9. Updates and integrity
Published datasets should be versioned, validated, and distributed with integrity checks so the app can reject malformed or unexpected data. Review dates describe when a record was assessed, not a promise that field conditions were inspected that day. Sources may be suspended or removed when they become unreliable or legally unavailable.
10. Corrections and removals
Anyone may report a possible error, duplicate, outdated record, privacy concern, or source-rights issue. Reports should identify the record or location, explain the requested change, and include supporting evidence when available. We assess the evidence, document the decision, and prioritize credible safety, privacy, and legal concerns.
We may correct, qualify, suppress, or remove a record while a report is reviewed. A removal request is not automatically granted when accurate public-interest information can lawfully remain, but unnecessary personal information and unsupported claims are not part of the product’s purpose.
11. Community submissions
A community report is a lead, not instant publication. It may be checked against authoritative sources, independent evidence, location context, and abuse signals. PrivateRoute should never reward volume in a way that encourages unsafe field verification, confrontation, trespass, or device interference.
12. Responsible use
The dataset exists to support informed, lawful route planning and public understanding. It must not be represented as exhaustive, real-time, government-certified, or a tool for evading lawful authorities. Users should obey traffic laws and never stop, trespass, or drive unsafely to verify a record.
13. Report a data issue
Email support@privaterouteapp.com with the location, the issue you found, and any public source that supports the correction. For privacy-specific concerns, email privacy@privaterouteapp.com.