1. Operator
Doppi, Inc. operates Yato. Doppi, Inc., 1111B S Governors Ave, STE 37768, Dover, DE 19904, United States.
2. Data Yato uses
- Supabase account identifiers and the Google or email account data needed to authenticate paid access.
- Your display name, locale, timezone, subscription, fixed local time, schedule revision, and upcoming lesson state.
- For Guest, an encrypted email only while needed to send and operate the invitation, plus encrypted or one-way keyed booking, delivery, Lesson Door, return, and abuse-prevention capabilities.
- Lesson and Meet identifiers, timing, dedicated Lesson Door, teacher arrival, provider lifecycle, Calendar projection, duration, and deterministic eligibility decisions.
- For paid access, one bounded Markdown Learning State for each target language and one cross-language bounded Relationship for each learner.
- Short-lived operational metadata needed for authentication, security, reliability, rate limiting, and support.
Live audio and transcript excerpts may be processed temporarily to run and close the current conversation. Raw transcripts are not stored as Yato product memory, and Yato does not record a conversation by default.
3. Guest and paid memory
The first free five-minute Guest lesson and its one eligible return lesson are memoryless and create no Learning State, Relationship, or Dashboard history. The invitation email is the sole Guest entrance. Its protected Lesson Door capability permits the scheduled lesson and, after completion, one-tap booking of one offered return time using the same encrypted email. Paid twenty-minute lessons update the selected language's Learning State containing the current level, mistakes, words, goals, Can Do 80%, Current 20%, Teacher Comment, and Next Conversation. General rapport and Teaching Preferences stay in one learner Relationship.
4. Scheduling and Calendar output
Yato, not a Calendar provider, owns booking, recurrence, moves, skips, cancellation, capacity, and Meet access. Guest has no Calendar output and joins only through the invitation email. For paid schedules, Calendar links and downloadable ICS are optional read-only projections of Yato schedule state. A paid projection may show teacher identity, lesson time, recurrence, and Lesson Door, but not the actual Meet URL or learning state. Editing a Calendar copy does not change Yato.
5. How data is used
We use data to create Guest bookings, deliver and retry Guest invitations, hold capacity, create fixed schedules and dedicated Meets, render optional paid Calendar projections, run live lessons, continue the 80/20 learning loop, preserve the learner Relationship, show and change the current schedule, process subscriptions, prevent abuse, secure the service, diagnose failures, and respond to support requests. Yato must not invent progress when the source is missing or unclear.
6. Services
Yato uses services for authentication, database and private storage, email, meetings, AI generation, realtime speech, payments, hosting, and operational security. Those services process only the data needed for their role and apply their own terms and privacy policies.
7. Retention, security, and choices
Guest email plaintext is deleted after the short operational period described at booking. Yato keeps other product data while needed to provide and secure the service, subject to legal, fraud-prevention, backup, and dispute requirements. We use access controls and private storage, but no system is perfectly secure. You may stop using Yato or contact us to request access, correction, or deletion where applicable.
8. Contact and changes
Contact [email protected] with privacy questions. We may update this policy as the service changes and will post the new date here.