Privacy
How Traina uses marketplace data.
This privacy page summarizes the main data categories used to operate customer, trainer, and gym owner workflows.
Data Traina may use
- Account and profile data, such as name, email, role, public profile details, and customer readiness details.
- Booking data, such as trainer, approved gym context for the current customer beta, package, date, time, status, payment status, refunds, reviews, and reschedule records.
- Payment method summaries and booking payment status received through Stripe. Full card details are handled by Stripe, not stored directly by Traina.
- Phone verification data used to confirm customer phone readiness, including verification messages sent through Twilio or another configured provider.
- Essential cookie and browser storage data described on the cookies page.
- Support and contact data that users provide when asking for help.
How data is used
Traina uses marketplace data to operate accounts, show role-appropriate profiles and booking details, prepare booking quotes, support payment and refund status, handle readiness checks, provide support, and keep operational records.
Analytics status
Traina may use privacy-safe product analytics, such as PostHog product analytics, after a user has given analytics consent. Analytics are optional and are not required to use Traina. They help Traina understand page usage and customer beta funnel issues such as signup, onboarding, search, trainer profile views, booking request submission, payment page visits, session views, and support clicks.
Product analytics are not used for payment decisions, trainer approval decisions, or pricing. Traina does not intentionally collect card details, one-time codes, phone numbers, private notes, health information, support messages, raw booking IDs, Stripe IDs, payment method IDs, trainer/customer private IDs, or token-bearing URLs in analytics events.
Session replay, heatmaps, surveys, broad autocapture, and user identification are not enabled. Users can decline analytics or change their choice on the cookies page. WhatsApp beta feedback is separate from analytics, and support remains the route for operational help.
Service providers and role visibility
Traina uses external providers for services such as payment method handling and phone verification. Customers, trainers, and gym owners may see role-appropriate booking, profile, location, and status details needed to operate a session. Private customer data should remain limited to the flows that need it.
Deletion requests
Users can request account or data deletion through support. Customer accounts may also have in-account deletion controls when the product shows those controls. Deletion can be limited or delayed where active bookings, pending payments, refunds, disputes, reschedule requests, audit records, or required operational records still need to be kept. For more detail, read the account deletion page.
Related policies