Privacy summary

Account information includes your sign-in identity and email address, along with profile details you provide, such as your role and leadership context.

Practice information includes the situations you share, preparation answers, submitted responses, conversation history, AI-generated feedback and records of completed practice. We store this information to support preparation, saved reviews, progress and later practice.

If you use voice input, audio chunks are sent for transcription. The resulting text is added to your draft and can become part of your practice record when submitted.

The app also processes account access, organization membership and invitation information, and subscription and payment references when those features are used.

The current AI integration uses OpenAI. Relevant situation details, responses, conversation context and learner context are included in requests used to prepare practice, simulate interactions, provide coaching and generate feedback. Optional voice input sends audio to OpenAI for transcription.

Some AI requests enable provider-side storage of inputs and outputs. This draft does not establish provider retention periods or model-training terms; those details remain under review.

Supabase supports account authentication and application data storage. Google is used for sign-in, and Resend is used for account and approval emails.

When analytics is configured, the app uses PostHog for interaction events and error tracking. Signed-in analytics can include your account ID, name, email and subscription details. The integration also includes automatic interaction capture and session-recording configuration; input fields are configured to be masked in recordings. Which recording features are enabled depends on the deployed analytics settings.

Learner-facing requests use authentication and account-ownership checks. Administrative tools can read account, profile and subscription information to manage users and access approval. Backend services have elevated database access for application operations.

Practice information is processed by the services involved in the feature you use. Do not treat practice as an anonymous service or include information you are not permitted to share.

Organization features maintain membership and invitation records. Organization-level access to individual practice content requires further verification and is not established by this summary.

Practice history, feedback and progress records are persisted so they can be resumed or reviewed. Some unfinished preparation and conversation drafts are also kept in browser storage to recover interrupted work.

Signing out is not an account or practice-record deletion request. This draft does not specify a general retention period or promise immediate removal from application storage, backups, analytics or AI providers.

Retention schedules, backup handling and the scope of deletion across connected services remain under review.

To ask about your information, request a correction or request account or practice-data deletion, email micropilot.india@gmail.com. Tell us the email address associated with your account and what you are requesting. Do not include passwords or confidential workplace details.

The current Settings page does not provide self-service account deletion. Administrative account deletion exists, but it does not by itself verify removal from every connected service or backup. The handling, scope and timing of deletion requests remain under review.