Privacy policy
TripPool is used by verified KdG Google accounts to organize shared travel for events. This policy explains which data is stored, why it is used, and how users can export or delete their account data.
Data we collect
- Your Google account identity data used for login, including name and email address.
- Profile settings, notification preference, account role, account status, and friend code.
- Events, travel groups, participants, routes, chat messages, reports, friendships, and notifications created while using the app.
- Operational timestamps such as creation, update, join, leave, read, and moderation times.
Why we use it
- To authenticate KdG users and keep the app limited to verified accounts.
- To let users create events, join travel groups, coordinate in chat, and receive in-app notifications.
- To support moderation, safety reports, event verification, and account restrictions when needed.
- To show personal travel statistics and improve coordination around shared travel.
Where data is stored
Application data is stored in the TripPool PostgreSQL database. Production secrets such as database credentials and API keys are stored in GitLab CI/CD variables and are not committed to the repository.
Who can access it
Normal users can access their own profile, chats, events, trips, friends, and notifications. Moderators and administrators can access moderation and verification screens needed for safety, report handling, event verification, and role or account management.
Your controls
- You can export your account data from the Settings page.
- You can delete your account from the Settings page. Account deletion removes the user account and related application data owned by or linked to that account.
- You can turn in-app notifications on or off from the Settings page.
Contact
For privacy questions, use the contact form on the TripPool landing page or contact the project team directly.