THOLA · Find. Discover. Obtain.

Your people. Your goals. Your privacy.

Standalone beta notice · November 19, 2026

Support: jesse.c.williams3@gmail.com.

Google sign-in

THOLA asks Google for your account identifier, verified email, and basic profile name. These are used to sign you in, check the beta invitation list, and protect your records. THOLA does not request Gmail, contacts, or Google Calendar access. Authentication tokens are verified on the server; session cookies are secure and not readable by page scripts.

Email and password

Firebase Authentication manages email accounts, password hashing, email verification and password reset links. Passwords pass securely through THOLA to Firebase and are never saved in THOLA’s database or logs. A secure, HttpOnly session cookie expires after one hour; sign in again to continue. Firebase account status and password-reset revocation are checked before private data is returned. Email addresses must be verified and approved for this beta. Email login and Google login have separate profiles; they are not automatically merged.

Your app information

THOLA stores rides, group membership, RSVP choices, feedback, private riding settings, private personal calendar events, support requests, and optional beta participation information when you use them. Personal events and fitness settings are restricted to your account through application access controls. Names on attendance and feedback are hidden unless you explicitly share them. Feedback moderation reports explicitly share selected content with the operator.

Hosting and outside services

This standalone build is intended for Cloudflare Workers and D1. Hosting and Google process normal account/network information under their own policies. The app uses coarse server-error records and optional visit dates as described inside the app. Fonts may load from Google Fonts. Route weather sends five sampled coordinates and timing to Open-Meteo only when you explicitly request it. THOLA is not end-to-end encrypted.

People and event attendance

You may opt into Friend Finder from My Profile. Your saved first and last name become your searchable name for other signed-in members. City, state, birthdate, gender, disciplines, photo, goals, activity log and fitness remain private. Existing connections remain visible if you turn discovery off. Attendance counts remain visible to event viewers, but attendance names require mutual following and the attendee’s explicit Going visibility choice. Following never grants access to a private event. Your private profile details and email are not included in community discovery. You can unfollow to end mutual attendance visibility. Community settings and follow records are included in account export and removed with account deletion.

Failed password attempts

THOLA keeps a hashed email identifier, failed-attempt count and reset-required timestamp. After five failed password attempts, signing in requires a provider-confirmed password change after the lock time. Requesting a reset alone does not remove the requirement. Successful sign-in clears earlier failures. Passwords are never stored in these records. Your own policy record is included in account export and cleared with account deletion.

Retention and control

Use the signed-in Privacy & data controls page to export your app records or review deletion. Confirmed deletion removes the app's Google-user record and revokes its sessions, alongside your personal calendar, fitness, attendance, feedback, and owned events/groups. It does not delete your Google account. Owned ride/group deletion can affect other participants. Provider logs, backups, downloaded exports, and browser-local demo data are separate. Contact support for invitation removal and retained provider copies.

Beta limitations

Outside calendars are not connected. Conflict checks can have incomplete event times. Training warnings are planning heuristics, not safety guarantees. Sources and hazards require current organizer checks. Demo events are fictional. No external registration or payment is completed by an RSVP.