Privacy policy

Information we process

Account information includes your name, email address, profile photo, account identifiers and sign-in/session information supplied through Clerk and your chosen Google, Facebook or Microsoft sign-in provider. Acharya does not receive your social-provider password.

When you use teaching features, information may include classroom audio, transcripts, topics, subjects, grade levels, notes, teaching reports, document uploads, chat messages and vector embeddings derived from notes and feedback. Support requests include the information you send by email. Network and authentication providers may process IP addresses, device/browser information and operational security logs.

Recording and classroom participants

Microphone access is used when you start a recording or voice feature. On supported Android builds, recording can continue with the screen locked or the app in the background, with Android's foreground-service notification and microphone indicators. You can stop recording in the app; operating-system interruptions may also stop it.

Audio can contain voices and personal information about students or other people who do not have Acharya accounts. Obtain required school permissions and participant or guardian consent before recording or uploading classroom material. Avoid student names and unnecessary sensitive information. Adult-only accounts do not remove these responsibilities.

Mobile processing, local storage and sync

The Android app uses your configured speech service, including Gnani, for transcription and your selected reasoning provider, such as OpenAI, Google Gemini or Anthropic, for reports or chat. Relevant audio, transcript, document or message content is transmitted when needed for the feature you choose. Your own API key does not make a provider request local-only.

Downloaded EmbeddingGemma inference creates embeddings on your device without an inference API request. Model downloads require internet access. Reports, source chunks and vectors are stored locally. When automatic cloud sync is enabled, notes, teaching feedback, class details and their embeddings are uploaded to Acharya's Neon database. Sync defaults to On for new accounts, can be turned Off in Profile settings, and queues uploads during connectivity failures. Turning Off does not delete existing cloud copies.

The mobile report-sync endpoint does not upload your raw recordings, raw transcripts or provider API keys. Separate speech/AI requests still transmit their required inputs to the selected provider. Saved API keys are encrypted using device secure storage, associated with your account on that device, and retained across sign-out and ordinary updates. Local SQLite content is app-private; it is not protected by full database encryption. The downloaded model is stored on the device.

Website features are different

The website uses Clerk for account access and Neon for stored application content. Existing web recording, notes verification and voice-coach features may send content through website server endpoints to Google Gemini, Sarvam and Vapi or the providers configured for those features. Documents and derived chunks may be stored for retrieval. These web features do not have the Android app's local-only storage or direct user-key behavior merely because they share the Acharya name.

The website uses essential sign-in cookies and browser storage/service-worker caching for its functionality. Browser storage can retain cached content until cleared. Acharya does not use advertising cookies or optional analytics/crash-reporting SDKs. Hosting, authentication and AI providers can still generate operational logs needed to provide and secure their services.

Purposes and recipients

We process information to provide account access, recording/transcription, teaching reports, notes verification, retrieval/chat, user-requested synchronization, support and service security. Content you deliberately publish through community features is visible to its intended audience; do not post confidential classroom information.

Recipients include Clerk (authentication), Google/Facebook/Microsoft (when selected for sign-in), Neon (cloud storage), our website hosting infrastructure, and the speech/AI/voice providers required by the feature you use. We may disclose information when legally required or necessary to investigate abuse or protect users. Providers may process data outside your country; their terms and settings govern their own retention and processing.

No advertising, sale or operator model training

Acharya does not display ads, sell personal information, share information for targeted advertising, or use classroom content to train its own AI models. We do not deploy optional analytics or crash-reporting SDKs. These statements do not mean the app never transmits data: account, cloud and user-requested AI processing still require service providers.

Third-party AI providers have their own data-use policies and account settings. We cannot promise that every provider/account configuration has identical retention or training exclusions. Review your selected provider's terms before sending classroom content.

Retention, deletion and your choices

Account information and stored teaching content are retained while needed to provide your account/features, until you delete them or request deletion, subject to legal/security requirements. Locally retained content remains on the device until removed through the app or device controls. Signing out is not deletion. Revoking a provider key or removing Facebook access is also separate from deleting Acharya data.

Use Profile → Account → Delete account in the Android app. Confirmed deletion begins immediately; successful completion removes the account and associated active Acharya cloud data and clears account-specific local data/keys on that device. Network or provider errors can prevent completion; follow the displayed error or contact us. Deleting only a Clerk identity through another interface should not be assumed to clear every Acharya record.

You may also request account deletion, selected-data deletion, access or correction by emailing our privacy contact. We verify account ownership before acting and communicate progress or any necessary retention exceptions. No password, API key, payment information or verification code is required in an email request. Provider backups/security logs may follow separate retention schedules, and disconnected devices cannot be remotely wiped by an email request. Contact us about applicable backup schedules and provider-held copies; we do not promise instantaneous erasure from all backups.

Security and changes

We use authenticated access, ownership checks, encrypted network transport for service requests and device secure storage for mobile API keys. No system can guarantee absolute confidentiality or security; protect your device and do not upload material you are not authorized to share. If you believe data has been exposed or a child's information has been included without permission, contact us.

We will update this page when practices change and show the revision date. Material changes may require additional notice or consent. For privacy questions and requests, contact Gaurav Chaudhary at githublobsters1997@gmail.com.