Crosstalk Partners privacy
Privacy built around booked sessions.
Crosstalk Partners is an 18+ English-Spanish language exchange marketplace. This page explains the operational data needed for profiles, availability, booking, video rooms, attendance, reliability, feedback, reporting, blocking, and support.
What Crosstalk Partners collects
- Account details such as your name, username, email address, authentication settings, and login/session metadata.
- Crosstalk Partners profile details such as your display name, photo, languages, comprehension level (or your self-reported hours of input), interests, timezone, general location, bio, and conversation preferences.
- Marketplace workflow data such as availability rules, exceptions, booking requests, confirmed sessions, cancellations, reminders, feedback, partner connections, blocks, reports, and moderation decisions.
Video and attendance
- Confirmed sessions use a video provider so participants can join a booked room. Crosstalk Partners stores the provider room id, room URL, participant access timing, and limited webhook events needed to classify attendance.
- Crosstalk Partners does not intentionally store full Daily webhook payloads. Attendance event summaries are limited to operational fields such as provider event id, event type, timestamp, participant identifier, and duration fields used by reliability logic.
- Crosstalk Partners does not provide user-facing recording controls in the MVP. Do not record another participant without their consent.
How data is used
- To help English and Spanish learners find compatible adult partners, request specific time slots, join sessions, and rebook when both people want to meet again.
- To calculate reliability and attendance signals while preserving an UNKNOWN status when provider data is missing, so webhook delivery failures are not treated as automatic no-shows.
- To support safety workflows including blocking, reporting, admin review, suspension, banning, and restoration.
Support, security, and retention
- Crosstalk Partners may use operational logs and error monitoring to diagnose failures. Secrets, raw tokens, API keys, and sensitive account credentials are not intended to be stored in monitoring payloads.
- Support requests should include the minimum detail needed to investigate the issue. Do not send payment details, government identity documents, or private credentials.
- The closed alpha is still evolving. Data may be corrected or removed when needed for safety, abuse prevention, legal compliance, or account support.