Privacy Policy

What we collect when you use Ciev.ai, why, and what control you have over it.

Effective 26 September 2026 · Published by Saasflux Technologies LLP

Ciev.ai ("Ciev.ai", "we", "us") is operated by Saasflux Technologies LLP, a limited liability partnership registered in India. This policy explains how we handle personal data and customer content across the Ciev.ai web app, API, MCP (Model Context Protocol) server, and the Ciev Recorder browser extension (together, the "Service").

Ciev.ai is a business tool: organizations use it to ingest recordings of their own meetings (engineering reviews, onboarding calls, technical interviews) and make the content searchable for their team and their coding agents. If your organization invited you as a member, your organization's admin controls your access and content — see "If you were added by an organization" below.

1. Data we collect

Account & organization data

Email address, and organization name/role, when you sign up or are invited to an organization.
Session and authentication data — we set a vmcp_session cookie after sign-in, and (for OAuth-based sign-in or connector flows) a short-lived vmcp_oauth_state cookie during the handshake. Both are functional, not tracking, cookies.
API keys you generate — we store only a salted hash, never the key itself, the same way we treat passwords.

Content you or your organization provide

Recordings you upload directly, or that your organization connects via OAuth to Zoom, Google Meet, or Microsoft Teams (only the recordings your org chooses to ingest — we don't crawl your entire account).
For interview-track customers, candidate interview recordings and any evaluation notes entered by the org's interviewers.

Data we derive from your content

To make a recording searchable, we generate and store:

A transcript (via automated speech-to-text) and speaker-attributed text chunks.
Extracted video frames, with on-screen text (OCR) and AI-generated captions/summaries of what's shown.
Semantic embeddings of the above, used for search.
For interview-track customers, an AI-generated coaching report and chat transcript grounded in the recording.

Usage & telemetry data

We log product usage at the organization and user level — logins, searches, ingestion volume, agent/MCP tool calls, and report generation — so we can operate the Service, debug problems, and understand what's actually useful. This is operational telemetry, not sold or shared for advertising.

Payment data

Billing is handled by Dodo Payments, our merchant of record. We never see or store your card details — Dodo shares back only what we need to manage your subscription (plan, status, invoice history).

2. How we use this data

To provide the Service: ingest, transcribe, index, and serve your organization's content back to authorized members and their connected agents.
To operate and secure the Service: authentication, abuse prevention, debugging, and the usage telemetry described above.
To communicate with you: transactional email (sign-up verification, invites, billing) sent via Amazon SES. We don't send marketing email without opt-in.
To bill your organization, via Dodo Payments, for paid tiers.

We do not sell personal data or customer content, and we do not use your recordings or transcripts to train any AI model outside of generating your organization's own search index and reports.

3. How AI/ML processing works

Transcription, OCR, and summarization are performed by third-party AI infrastructure we call on your organization's behalf — currently Amazon Web Services (Transcribe, Textract, and Bedrock-hosted foundation models). Your content is sent to these providers only to produce the outputs described above (transcript, captions, summaries) and is not used by us or, per AWS's own terms, by AWS to train their models.

Most Ciev.ai infrastructure — including your stored recordings, derived data, and database — is hosted in AWS's ap-south-1 (Mumbai) region. AI model inference on Bedrock currently runs in AWS's us-east-1 (N. Virginia) region, meaning content is transiently transmitted there for processing. See "International data transfers" below.

4. Connecting a coding agent (MCP)

Ciev.ai exposes an MCP server so you can connect a coding agent — Claude, Claude Code, Claude Desktop, or any other MCP-compatible client — directly to your organization's indexed meeting content. This connection is something you deliberately set up, using your own API key or an OAuth consent flow:

Once connected, the agent can retrieve content from your organization's Ciev.ai index (transcript excerpts, frame images, clips) in response to your prompts, scoped to whatever your account is authorized to see — the same access boundary as the web app.
We log that a tool was called, which tool, and whether it succeeded, for the telemetry described in §1 — we do not log the agent's own conversation or your prompts to it.
What the connected agent (e.g. Anthropic's Claude) does with the content it retrieves is governed by that provider's own terms and privacy policy, not this one — we recommend reviewing them before connecting.

5. The Ciev Recorder browser extension

Ciev Recorder is our Chrome extension for recording meetings you take part in. It only records when you tell it to: when you press Record (in the meeting, from its icon, or with its keyboard shortcut), or on a meeting site where you have turned on auto-record yourself.

What it reads. On supported meeting sites (Google Meet, Zoom, Microsoft Teams, Webex, Whereby, Jitsi) it runs a small script that detects when a call is active, so it can offer to record. While recording, it captures that call's audio (the other participants, plus what you send to the call, so your mute is respected) and its main video: the shared screen, or the active speaker. When you record any other tab from the icon or shortcut, it captures that tab and, if you allow it, your microphone. It does not read your browsing history, other tabs, keystrokes, or page content beyond what's needed to detect the call and its title.
Where recordings are kept. Recordings are written to the extension's private storage on your computer as they are made. They are saved to your Downloads folder only if you choose to, one at a time or with the "Save a copy to Downloads" setting.
What is sent to Ciev.ai. Nothing, unless you connect a Ciev.ai account. Once connected, recordings are uploaded to your organization's Ciev.ai workspace. Uploading happens in parts while the meeting is still being recorded (unless you turn automatic sending off), and the recording is then processed as described in §1–3. If you discard a recording, the parts already uploaded are deleted. The extension sends data only to Ciev.ai's own servers, and contains no advertising, analytics, or tracking code.
Sign-in. Connecting a Ciev.ai account creates an API key for your organization, stored only in the extension's local storage (we keep a salted hash, as with any API key). Disconnecting revokes it.
Retention on your computer. You can delete any recording from the extension at any time. Its own copy of a recording is removed automatically after the number of days set in its settings, but only once the recording is both in your Downloads folder and in Ciev.ai. Uninstalling the extension removes everything in its own storage; files you saved to Downloads are yours and stay.
Other participants. You are responsible for telling the people in a meeting that you are recording it, and for getting their consent where the law requires it.

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

6. Who we share data with

We share data only with the infrastructure and service providers ("subprocessors") needed to run Ciev.ai, and with parties you explicitly connect:

Provider	Purpose	Data involved
Amazon Web Services	Hosting, storage (S3/RDS), transcription, OCR, AI model inference, transactional email (SES)	All stored content and derived data
Dodo Payments	Billing, merchant of record	Billing contact, subscription/plan data — no card data reaches us
Zoom / Google / Microsoft	Fetching recordings your organization authorizes via OAuth	Recording metadata and file access, scoped to what you authorize
Anthropic (or another MCP client provider)	Only if you connect a coding agent, per §4	Content your agent retrieves, at your request
Glean	Only for organizations that opt in to the enterprise search push connector	Indexed content pushed into your org's Glean instance

We do not sell data to data brokers or advertisers, and we disclose personal data to government or legal authorities only when legally required to.

7. International data transfers

We're based in India and store your data primarily in AWS's Mumbai (ap-south-1) region. As noted in §3, AI model inference currently runs in AWS's us-east-1 (United States) region, so content is transiently processed there. If you or your organization are located outside India, using the Service necessarily involves transferring data to India (and, for inference, briefly to the United States). We rely on our subprocessors' own compliance frameworks (AWS, Dodo) for these transfers and will update this section if that architecture changes.

8. Data retention & deletion

We retain your organization's recordings and derived data for as long as your account or organization remains active, so historical meetings stay searchable.
An organization admin can delete individual sources from within the product at any time.
To close an account or request deletion of your organization's data entirely, email contact@ciev.ai — we'll confirm the scope and complete it within a reasonable time, subject to any legal retention obligations (e.g. billing records).
Backups may retain deleted data for a limited period after deletion before being purged in the normal backup rotation.

9. Security

All connections to the Service use TLS in transit.
API keys are stored as salted hashes, never in plaintext.
OAuth credentials for connected recording sources (Zoom, Google Meet, Microsoft Teams) are encrypted at the application layer before storage.
Access is scoped by organization at the application layer — one organization's members and API keys cannot read another organization's data.

No system is perfectly secure; if we become aware of a breach affecting your data, we'll notify affected organizations without undue delay.

10. Your rights

If you're located in India, you have rights under the Digital Personal Data Protection Act, 2023 as a Data Principal — including the right to access, correct, or erase your personal data, and to withdraw consent. If you're located in the EU/UK or elsewhere with similar data-protection law, we'll honor equivalent access, correction, deletion, and portability requests. Contact us at contact@ciev.ai to exercise any of these.

Note that if you're a member of an organization on Ciev.ai rather than the account holder, some requests (e.g. deleting a meeting recording) may need to go through your organization's admin, since they control that content — see below.

If you were added by an organization

Ciev.ai is provided to organizations, who act as the "controller" of the meeting content they choose to ingest — including any recordings that include you as a participant. We act as their processor. If you appear in a recording ingested by an organization you're not the admin of, please raise access or deletion requests with that organization first; we'll assist them in fulfilling it.

11. Cookies

We use only functional cookies — vmcp_session for authentication and vmcp_oauth_state during OAuth handshakes — plus a localStorage entry for your light/dark theme preference. We don't run third-party advertising or cross-site tracking cookies.

12. Children's privacy

Ciev.ai is a business tool and is not directed at, or knowingly used by, children under 18.

13. Changes to this policy

We'll update the "Effective" date above when this policy changes, and for material changes we'll notify organization admins by email.

14. Grievance Officer & contact

For privacy questions, data requests, or grievances under applicable Indian law:

Grievance Officer — Saasflux Technologies LLP
Email: contact@ciev.ai
Jurisdiction: Delhi, India