> For the complete documentation index, see [llms.txt](https://docs.nearby.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearby.finance/protocol-layers/proof-of-location-location-layer/geolocation-privacy.md). # Geolocation Privacy ### Introduction Location data reveals far more than physical position. Over time, location history can expose: * Daily routines * Places of residence * Work locations * Social relationships * Travel patterns * Personal interests For this reason, geolocation is among the most sensitive categories of personal information. The Proof of Location Layer was designed to minimize the collection, exposure and transmission of location data wherever possible. ### Privacy by Default Privacy is not an optional feature within Nearby. It is a foundational design principle. Users are not required to disclose precise coordinates in order to prove geographic eligibility or physical presence. Instead, they generate cryptographic proofs that reveal only the information necessary for verification. ### Selective Disclosure The protocol supports selective disclosure. Users may choose to reveal only the specific claim required by an application. Examples include: * Presence within a city * Attendance at an event * Eligibility for a local reward * Membership within a geographic region The underlying coordinates remain private. ### Data Minimization Traditional systems often collect more information than necessary. Nearby follows a different approach. The protocol seeks to minimize: * Data collection * Data storage * Data transmission * Third-party access Only proof artifacts are shared when verification is required. ### Local Processing Sensitive location data remains under user control. Location validation and proof generation occur directly on user devices whenever possible. This reduces dependence on centralized infrastructure and limits unnecessary exposure of personal information. ### Protection Against Surveillance Many location systems rely on centralized databases capable of building detailed behavioral profiles. The Proof of Location Layer is designed to reduce this risk. By replacing raw location disclosure with cryptographic verification, the protocol minimizes the creation of centralized location records. ### Privacy Without Sacrificing Utility Privacy and functionality are often treated as competing goals. zkGeolocation demonstrates that both can coexist. Users gain access to location-based services while maintaining control over their geographic information. The result is a privacy-first model for digital coordination in the physical world. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nearby.finance/protocol-layers/proof-of-location-location-layer/geolocation-privacy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.