Privacy Policy
This draft summarizes data handling visible in the current application code. It needs confirmation and legal review before production use.
Draft for legal review. Operator identity, retention periods, deletion procedures, vendor terms, and some data flows require confirmation before this policy is finalized.
Information handled
Depending on the features used, TuitionSathi handles account identifiers and authentication data through Supabase Auth; profile and role details; student and tutor profile information such as names, contact details, subjects, location, and teaching preferences; saved tutor preferences stored in the browser; contact requests; and messages exchanged through the platform. Tutor profile images may be loaded from Supabase Storage. The precise fields can vary by feature.
Why information is used
The application uses this information to create and manage accounts and profiles, display and search tutor listings, connect students and tutors, handle contact requests and messages, provide account features, and administer and secure the service. If a visitor submits the public contact form, their name, email address, and message are sent by the server to the configured recipient using Resend. That form submission is not written to a contact table by the inspected API route.
Service providers and sharing
Supabase is used for authentication, database access, and tutor avatar storage. Resend processes email delivery for the contact form. When a PostHog project token is configured, the browser analytics client sends pageview events and explicit application events to the configured PostHog host (defaulting to the US ingestion host). The code disables autocapture, automatic pageviews/pageleaves, and session recording; explicit events include authentication journey events and selected application actions. User identification may use the Supabase user ID. Exact event coverage, processor locations, and provider retention settings should be confirmed. Information is also made available to other users where necessary for profile discovery, contact requests, or conversations.
Cookies and browser storage
Supabase’s browser/server authentication uses session cookies to maintain signed-in sessions and support authentication flows. The application also uses browser local storage for saved tutor IDs and session storage temporarily for sign-up role intent during authentication. PostHog may use browser storage or cookies when enabled; the exact identifiers depend on its configuration and should be confirmed. The code reviewed does not show an advertising cookie or consent banner.
Retention and deletion
Profiles, tutor/student records, contact requests, and messages are stored in Supabase. The inspected application code does not establish a general retention schedule or confirm that deleting an account removes all related records, backups, or provider-held data. Contact-form email retention depends on the configured mailbox and Resend settings. These periods and deletion procedures need confirmation. You can contact us to ask about access, correction, or deletion; applicable rights and processes depend on your location and law.
Your choices
You can choose what information to include in a profile or message, avoid submitting information that is not necessary, and clear browser storage or sign out to remove local session state from that browser. Clearing browser data does not itself delete server-side records. For account or privacy requests, contact us using the details below.
Privacy contact
Use tuitionsathi.support@gmail.com or the contact form. The legal entity/operator name, postal address, privacy contact role, and response process are not established in the inspected code and must be confirmed. This draft should be reviewed against applicable privacy requirements and the actual deployment configuration.