Kolo
Privacy policy
This policy explains how Kolo processes information for its authenticated nearby-rider network for people aged 16 and over. Kolo is a prototype and is not an emergency service.
Information processed
- Account and security information such as email address, display name, identifiers, authentication provider, sessions, recovery and policy-acceptance events.
- Rider profile information such as ride type and characteristics, birth year used to enforce the 16+ rule, optional sex, interests, visibility, and messaging preferences.
- Fresh foreground location and accuracy. Ordinary discovery publishes a coarsened cell and banded distance, not an exact rider coordinate. Sparse cells are suppressed.
- Messages, broadcasts, events, blocks, reports, notification records, and optional push-notification installation information.
- If you explicitly confirm an SOS, one fresh exact incident location, accuracy, consent time, and limited-duration emergency event are shared with eligible nearby riders. This is not continuous or background tracking and does not contact emergency services.
- Technical and security records needed to operate, diagnose, and protect the service.
How information is used
Information is used for authentication, profile and visibility controls, privacy-bounded nearby discovery, rider communication, events and SOS display, blocking and reporting, notifications, abuse prevention, support, and service security.
Visibility and location choices
Profiles start hidden. Foreground publishing stops when you hide your profile, sign out, or leave the foreground. Sex is not published unless you opt in and cannot be used as a discovery filter. Ordinary rider results use approximately one-kilometre cells, rounded distance bands, freshness limits, and minimum cell occupancy.
Sharing and service providers
Public-safe profile and coarsened location fields are shared only with authenticated, eligible nearby riders under the visibility, freshness, occupancy, block, and messaging rules. An SOS exact location is shared only after the separate confirmation described above. Infrastructure, email, authentication, notification, map, and secure-storage providers process data only as needed to deliver the service.
Retention and security
The service keeps the latest location rather than a general location history. Account, profile, communication, event, safety, notification, and security records remain while needed for the service or a limited legal, fraud-prevention, safety, dispute, or backup purpose. Production traffic uses HTTPS and native sessions use platform secure storage. No system can guarantee absolute security.
Your choices
You can remain hidden, control profile disclosures and message audience, deny location or notification permission, opt out of push, resolve or cancel an SOS, block and report users, sign out, and request account deletion.
Contact
Email support@rolutec.com. See the Kolo account-deletion page.