Privacy Policy

Who we are

Bhaasa Nepal is the data controller for the personal data processed through the Service, unless otherwise stated. We are based in Kathmandu, Nepal, and our infrastructure and service providers are located in multiple countries, as described in Sharing your data with third parties below.

Contact information

Account information

You create a Bhaasa account either by signing in with Google, or by entering a work email and verifying a one-time code we send to it. In both cases, account creation and sign-in are handled by a trusted authentication provider — we never see or store a password. From your chosen sign-in method, we receive and store your name, email address, and (for Google sign-in) a profile picture, along with your plan, preferred language, and onboarding preferences you set in the app.

Video, audio, and caption content

When you upload a video, we store the video file, an automatically generated thumbnail, and any exported outputs (captioned video, .srt/.vtt subtitle files). We also store the transcript generated from your audio, any translations you request, the caption styling you choose, and related editing state (overlay text/images, caption position, playhead position) so your project can be reopened and continue exactly where you left it.

You are responsible for ensuring that any content you upload is lawful and that you have the necessary rights to share it with us and to have it processed by the third-party transcription and translation providers described below.

Payment information

When you upgrade to a paid plan, your payment is handled directly by our payment processors — your card number or wallet credentials are entered on their systems, not ours, and we never receive or store them. We do receive and store a record of the transaction itself: the plan purchased, the amount, the payment method used, the status, and a gateway reference ID, so we can show your billing history and send you a receipt.

Usage and technical information

We automatically collect technical data when you interact with the Service, including IP address, browser type, device information, and the pages and features you use. We also keep an internal, append-only record of your AI-minutes, translation-minutes, and storage usage against your plan's limits, so we can enforce fair usage and show you your remaining quota.

This information helps us ensure the security and reliability of the Service, diagnose problems, and prevent abuse.

Communications

If you contact us for support, we retain that correspondence, along with any information you volunteer in it, so we can respond and keep a record of the issue.

We use the data described above for the following specific purposes:

• Generating captions from your uploaded audio, using a speech-recognition engine we run ourselves for most languages, and, for a subset of languages, sending your audio to third-party AI models who transcribe it on our behalf.
• Translating your captions into another language, when you request it, by sending the caption text to a third-party AI model.
• Rendering and exporting your styled captions, and burning them into an output video file.
• Authenticating you and keeping your account, projects, and billing history in sync.
• Processing payments, maintaining your billing history, and emailing you a payment receipt.
• Providing customer support and responding to your inquiries.
• Enforcing your plan's usage limits (AI minutes, translation minutes, and storage).
• Improving service reliability, troubleshooting issues, and preventing abuse of the Service.
• Meeting legal obligations and enforcing our Terms and Conditions.

We keep this section deliberately specific, because "cookies and tracking" language is often used to cover far more than a site actually does. Here is exactly what Bhaasa uses today:

• Authentication cookies/local storage. Our authentication provider sets a session cookie/token so you stay signed in between visits. This is strictly necessary for the Service to function — without it, you would need to sign in again on every page.
• Theme preference.Your light/dark mode choice is stored in your browser's local storage, purely so the site remembers it.
• Locally cached media.Video and thumbnail files you've opened in the editor may be cached in your browser (via IndexedDB) so re-opening a project you've already viewed doesn't re-download it from our servers every time. This stays on your device.

We share personal data only with the specific service providers who need it to help us operate the Service (our "subprocessors"), and only to the extent necessary for their function. We do not sell your personal data to anyone.

• Authentication and database provider — handles sign-in (Google sign-in and email one-time-code verification) and stores your account, projects, captions, styles, and billing history.
• Cloud storage provider — stores your uploaded video files, generated thumbnails, and exported outputs.
• Third-party AI models — provide speech-to-text transcription for a subset of languages, and text translation of your captions when you request it.
• Payment processors — process paid plan purchases. Your card or wallet credentials are handled entirely by them; we never receive them.
• Email service provider — sends payment receipts and, occasionally, service announcements.

While your project is active

We keep your projects for as long as your account is active, subject to the storage window that applies to your plan:

• Free plan — projects are intended to be kept for 7 days after processing finishes, with temporary working files removed automatically after that.
• Creator plan — projects are intended to be kept for 90 days, with permanent storage available as an add-on.
• Studio plan — projects are kept permanently for as long as your subscription remains active.

These windows describe our storage policy and design intent for each plan, as published on our pricing page, rather than a guaranteed contractual retention period — we recommend exporting or downloading anything you want to keep long-term, regardless of your plan.

When you delete a project

When you delete a project yourself, we remove its video, thumbnail, and exported files from our storage immediately — this is a real deletion, not a move to a "trash" you can browse. Once deleted, a project's files cannot be accessed, previewed, or recovered again, by you or by us.

The project's record in our database is then kept for up to 30 days as an internal audit/undo grace period before it is permanently purged, but the Service itself never shows you a deleted project again and provides no way to restore it — the 30-day window exists purely for our own operational and abuse-prevention purposes, not as a user-facing recovery feature.

When you delete your account

Deleting your account (by contacting hello@bhaasa.io) deletes your projects the same way described above. We retain a record of your billing/usage history for as long as required for accounting, tax, and legal compliance purposes, even after your account and projects are gone — this record does not include your video or audio content.

We take reasonable technical and organizational measures to protect your data, including:

• Encrypting data in transit using HTTPS across our website, application, and API.
• Passwordless sign-in — we never handle or store a password for your account, since sign-in is delegated entirely to Google sign-in or one-time-code email verification.
• Never receiving or storing your payment card or wallet credentials — those are handled entirely by our payment processors.
• Storing your video files in access-controlled cloud storage, scoped per account, so one user's content isn't accessible to another.
• Limiting internal access to personal data to what is needed to operate and support the Service.

Depending on your jurisdiction, you may have the following rights in relation to your personal data:

• Access — request a copy of the personal data we hold about you.
• Rectification — ask us to correct inaccurate or incomplete data.
• Erasure — delete individual projects yourself at any time from the app, or request full account deletion by emailing us, as described in Data retention and deletion.
• Restriction — ask us to limit how we process your data in certain circumstances.
• Objection — object to processing based on our legitimate interests.
• Portability — request your data in a structured, commonly used format.