Privacy, on tape.

Recappi is operated by Yinan Long as an individual sole operator. Service domain: recordmeet.ing. We act as the data controller for the data described in this policy.

Contact for any privacy matter: privacy@recordmeet.ing.

This policy covers:

• The Recappi web application at recordmeet.ing.
• The companion macOS app.
• The Recappi Windows Store app.
• The @recappi/sdk audio-capture SDK as bundled into our apps.

It does not cover third parties you choose to interact with through our service (for example, Stripe's hosted billing portal, which is governed by Stripe's own privacy policy).

We collect the following categories of personal data.

// account data

OAuth claims returned by Google or GitHub when you sign in: stable user id, email address, display name, and avatar URL. Captured via Better Auth on first sign-in.

// audio recordings

16-bit PCM WAV files you upload via the app or the SDK. Sample rate and channel count are read from the WAV header. We also store recording size, creation timestamp, and any title you assign. We do not automatically capture ambient audio at any time — see §05 below.

// transcripts & metadata

Text returned by Google Gemini or Xiaomi Mimo, detected language, timestamped segments, optional xAI word timing used to align those segments, and total duration in milliseconds. Stored in Cloudflare D1.

// usage & billing

Current plan tier, storage used (bytes), transcribed minutes, and the period start / end. Paid plans additionally store a Stripe customer id and subscription id. We never see or store your payment-card details; those go directly to Stripe.

// operational logs

Cloudflare-side request logs (IP address, User-Agent, request timestamp, request path) used for security and debugging. Retained per Cloudflare's defaults (~7 days). No business-side analytics SDK is loaded.

Each category is used only for the purpose stated below, and only on the lawful basis stated below (GDPR Art. 6).

Our desktop apps use the operating system's microphone capability only while you have actively pressed Record. There is no background listening, no wake-word, and no auto-launch capture.

The capture SDK produces a single 16-bit PCM WAV file per recording session, held locally on your device until you upload it.

Local file behaviour: on the Windows Store app, the local WAV file is kept on disk indefinitely after upload — you can delete it manually from your file system at any time. We do not read, modify, or remove those local files after upload.

We do not stream audio to a server during recording; the upload happens after you stop the recording.

When you ask us to transcribe a recording, we send it to the selected primary provider: Google's paid Gemini API at generativelanguage.googleapis.com or Xiaomi's MiMo API at token-plan-sgp.xiaomimimo.com.

When xAI timing alignment or live Grok speech-to-text is configured, we also send the relevant audio to xAI's API to request word-level timestamps or streaming transcript events. The batch timing pass is optional and non-fatal: if it is unavailable, Recappi keeps the primary-provider transcript and uses its own timestamps.

• Per Google's Gemini API terms for paid use, Google does not use your inputs to train models.
• xAI states that API inputs and outputs are not used for training without explicit permission. Recappi does not grant that permission.
• xAI's standard API retention is 30 days for abuse and misuse auditing unless a stricter enterprise data-retention setting is enabled for the account.
• Files uploaded to Gemini's Files API are retained by Google for up to 48 hours, after which Google deletes them.
• We send only the audio and service prompts needed to produce the transcript, live transcript, or word timing. We do not include your account email, account id, or any other identifying metadata in requests to Google, Xiaomi, or xAI.
• We do not generate voiceprints or perform speaker identification across recordings. Speaker labels (for example, "Speaker 1," "Speaker 2") are inferred per recording by the model and are not linked across recordings or users.

We share the data described above only with the third-party processors listed here, and only for the purposes stated.

We will update this list before adding any new sub-processor that handles personal data.

If you are located outside the United States, the data you submit to Recappi will be transferred to and processed in the United States and other countries where our sub-processors operate.

We rely on the EU-US Data Privacy Framework (and the UK and Swiss extensions) where the recipient is certified, and on the European Commission's Standard Contractual Clauses (2021) otherwise. Each vendor named in §07 maintains its own certifications, linked from the table.

• In transit: all data is transmitted over HTTPS with TLS 1.2 or higher.
• At rest: Cloudflare R2 and D1 encrypt data at rest by default.

Recording deletion is immediate and hard. When you click Delete on a recording, the R2 object and all related D1 rows are removed in the same request. There is no recoverable trash.

Account deletion is by email request to privacy@recordmeet.ing. We process within 30 days. On account deletion, we hard-delete all your recordings, transcripts, jobs, usage records, and account record. We retain billing records (Stripe references and invoice metadata) for 7 years where required by tax law.

// GDPR rights (EU / UK / EEA residents)

You have the rights of access, rectification, erasure, portability, restriction, objection, and to withdraw consent at any time. You also have the right to lodge a complaint with your supervisory authority.

// CCPA / CPRA rights (California residents)

You have the right to know, delete, correct, limit use of sensitive personal information, opt out of sale or sharing, and the right to non-discrimination. We do not sell or share Personal Information as those terms are defined under the CCPA, and we have not done so in the prior 12 months.

To exercise any right, email privacy@recordmeet.ing. We respond within 30 days (GDPR) or 45 days (CCPA).

Recappi is not directed to children under 16 (the GDPR-K threshold). We do not knowingly collect personal information from children under 16. If we learn that we have, we will delete it. Parents or guardians may contact privacy@recordmeet.ing.

We use only essential cookies for authenticated sessions — the Better Auth session cookie. We do not load analytics, advertising, or third-party tracking cookies. Browser local storage is used only for client-side state needed by the app (for example, the last-viewed recording).

We bump the revision number in the page header and post the diff at the bottom of the page when we make changes. For changes that materially affect your rights, we will email registered users at the address on file.

For any privacy request — questions, deletion, access, or complaints — email privacy@recordmeet.ing. We will respond as fast as we reasonably can.