Information we use
Account and profile information
Trila uses your phone number to create and secure your account and your display name and profile information to identify you to Groups you join.
Contacts you choose to check
When you ask Trila to find contacts who already use the app, approved contact details are used for that request. Raw device contact payloads are not stored.
Locations you choose to share
You may share a current, manually picked, or previously stored starting point with a specific Group. Trila does not request background location access or continuously track your movement.
Group and decision information
Trila stores Group membership, Invite Links, readiness, recommendations, estimated travel times, Place Polls, votes, and the Final Place so the Group can complete its plan.
Security and service information
Trila processes authentication sessions, one-time verification attempts, operation identifiers, timestamps, and limited technical information needed to secure and operate the service.
Why we use it
- Authenticate your account and keep sessions secure.
- Create Groups and connect active Participants.
- Use only the starting point each Participant shares for that Group.
- Find real places and compare estimated driving times.
- Run the Place Poll and preserve the Group's Final Place.
- Prevent abuse, investigate failures, and protect the service.
How information is shared
Other Participants can see your identity, role, readiness, and the source of the location you shared. Candidate-place views are designed not to reveal Participant origins or exact coordinates.
Trila may send the minimum information needed to map, place-search, routing, infrastructure, authentication-delivery, and support providers. These providers process information for Trila under their applicable service terms.
Trila does not describe your Shared Location as public information and does not sell it.
Protection and retention
Phone numbers and stored or Shared Locations are encrypted in durable storage. OTP codes, session tokens, Invite Link tokens, and phone lookup values are stored as protected hashes rather than raw values.
OTP codes expire after five minutes. Sessions, Invite Links, and locations are removed or invalidated when their relevant lifecycle ends, such as session revocation, Invite Link expiry, location replacement, Participant removal, Group expiry, or account deletion.
No system can guarantee absolute security. Trila limits access and keeps sensitive values out of logs, screenshots, public pages, and client bundles.
Your choices
- Choose whether and which starting point to share with a Group.
- Deny contacts or foreground-location permission and use available alternatives.
- Update or remove a Shared Location while the Group workflow allows it.
- Leave a Group when you no longer want to participate.
- Request deletion of your account and associated personal data.
Contact
Questions or privacy requests can be sent to support@trila.social. Never include an OTP, session token, Invite Link, or exact private location in an email.