Privacy Policy
Your presence. Your coordinates. Your ownership.
What We Collect
Depending on how you use Rheole, information may include:
Account details
Anonymized profile hashes
Spatial coordinates
Community node records
Registered local events
Decentralized mesh headers
Search queries
Hardware identifiers
Platform event logs
Why We Collect Information
Information helps us provide:
Relevant community mapping
Bespoke local discovery
Event calendar validation
Intelligent routing vectors
Decentralized node status
Abuse & sybil detection
Spatial engine improvements
Continuous security audits
Location Information
Location is an important part of the Rheole experience. Proximity processing powers local discovery, node matches, and traffic calculations.
Users maintain full granularity control. GPS coordinates are converted immediately on-device into geohash coordinates, keeping literal lat/long locations out of central storage servers.
Messages & Communications
Private communication is routed peer-to-peer across decentralized relays. The payload is encrypted using hardware-backed enclaves and automatically decays from all temporary node nodes within 24 hours of session inactivity.
Your Control
We believe you should remain sovereign over your physical presence. You have the right to request access to records, edit profile hashes, flush cached data, or request permanent deletion of database tags by contacting:
privacy@rheole.comData Sharing Principles
Rheole does not sell or lease personal information. Period. Spatial logs are cached client-side and only shared with infrastructure relays required to transmit messages or map traffic clusters.