Privacy & data handling

What we collect and how we use it

Account and access

We collect the name, email address and credentials you provide when you create or use an account, together with workspace membership, preferences and AI-consent records. We use them to authenticate you, operate your account, enforce access controls and remember your choices.

Recordings and meeting content

When you choose to record, supported desktop apps capture microphone and computer audio; the iOS and Android apps capture microphone audio. We also collect meeting titles, dates, participant names, notes, tags and templates as you use the service. We use this content to provide transcripts, summaries, tasks, search and sharing you request. No recording bot joins your meeting.

Speaker features

Audio samples and derived voice representations help separate speakers and match speakers to profiles. Samples and profiles may remain available with your meetings until deleted. Assigning a speaker can update a profile for future matching; this is separate from training a general-purpose AI model.

Service and support records

We receive technical information such as IP addresses, app and device details, request times, errors and security events as you use Drushya. We use these records for security, troubleshooting and operating the service. We also retain information you send to support.

Billing

Where purchases are offered, Razorpay processes payments. Drushya receives payment identifiers, plan, payment status and subscription dates to manage access and billing support. Payment details you enter into the payment provider are handled by that provider.

Recordings and transcripts may contain personal information about you and other participants. Obtain any necessary participant permission before recording or sharing their information.

AI processing and named providers

Drushya uploads recordings to its servers and uses the providers below for the described operations. Audio can also be processed on Drushya's own infrastructure. Only providers needed for an operation receive its data. Processing may take place outside your country.

OpenAI

Meeting transcripts and relevant speaker names, titles, dates, time zones, duration and summary templates are sent to generate meeting titles, summaries and tasks. Provider information

Modal

Recorded audio, speaker samples, processing identifiers, language and speaker-count settings are processed by Drushya's transcription and speaker-processing software running on Modal infrastructure. Provider information

RunPod

Recorded audio, speaker samples and processing settings may be sent to Drushya's software running on RunPod when selected for audio processing, including fallback processing if Modal is delayed. Provider information

Cloudflare R2

Recording files, audio samples and intermediate processing results are stored and transferred through Cloudflare R2. Selected audio-processing providers receive time-limited access to the files needed for the requested operation. Provider information

Drushya does not use meeting content to train general-purpose AI models. Speaker matching uses the voice profiles described above. Provider processing is governed by applicable service and data-processing terms; operational and abuse-monitoring retention can still apply.

Your permission and choices

Before new AI sharing, the app explains the data, recipients and purposes and asks you to choose Allow AI processing or Not now. Permission covers this and future meetings under the displayed disclosure and is saved against your account. A changed disclosure requires renewed permission. Microphone permission is separate.

You can decline and continue viewing existing meetings. Open Account → Privacy to review or withdraw AI permission. Withdrawal blocks new sharing, including pending processing that has not yet been sent. It cannot recall data already transferred or undo completed processing. It does not itself delete your account or meetings.

Protection and other sharing

Drushya protects connections to its website and API using HTTPS with TLS 1.2 or TLS 1.3. Individual and Enterprise users can protect their accounts with two-factor authentication using Google Authenticator or Microsoft Authenticator.

We require service providers receiving personal data to provide the same or equal protection described in this policy, including confidentiality, appropriate security, processing limited to authorized service purposes and assistance with deletion, subject to applicable legal obligations. Provider service and data-processing terms govern these responsibilities.

Our hosting and email service providers support account storage, authentication, transactional messages and support. Authorized Drushya operators may access data for support and troubleshooting. If you share a meeting or contribute it to a shared workspace, the authorized recipients can access it. Organization administrators manage organization-controlled access. We may disclose information when legally required.

Retention and deletion

We retain account and meeting information to provide the service until it is deleted under the applicable account, meeting or organization policy. Recording and intermediate files may remain while processing, retry or cleanup is pending. Speaker samples and voice profiles can remain after transcription to support playback and speaker matching. We do not promise that every audio copy disappears immediately after transcription.

OpenAI requests are made with response storage disabled. Provider security, abuse-monitoring and legally required retention may still apply. Temporary audio-processing artifacts are cleaned up through background jobs; cleanup retries when a service is unavailable.

Delete individual meetings, use the app's account-deletion control where available, or contact support. Shared copies, organization records, necessary billing/deletion records and backups can have different retention. Withdrawal and deletion are separate choices.

Questions and privacy requests

For access, correction, deletion or questions about your information, email support@mydrushya.com. We verify account ownership before acting on requests. We update this policy when practices change and seek renewed AI permission when the disclosure changes.