Privacy Policy

Summary

Minine Transcribe, also known as MinineSTT (“we”, “us”, the “app”), is a recording and transcription service published by Minine Inc, available as an iOS app, a web app at app.mininetranscribe.com and a desktop app. In the iOS app, recordings made with the on-device engine are stored locally. Audio or transcript content is sent to our services when you use the cloud features below:

• You choose a cloud transcription engine.
• You record or upload in the web or desktop app, which have no on-device engine (see §3.7).
• You use cross-device sync after signing in.
• You share a session into a team.
• You request cloud translation, an AI summary or an answer about a transcript.
• Where the meeting assistant is available to your account, you connect Zoom and ask the assistant to join and record a meeting.

In the web and desktop apps you can also turn on live captions and connect Google Calendar; both are optional and described in §3.7.

The iOS app uses Meta and AppsFlyer SDKs for marketing attribution and product analytics; the web and desktop apps do not include them. The iPhone download page on this website uses Meta Pixel and AppsFlyer measurement, as described in §3.6. This is separate from recording content: the app does not send audio or transcript text in those analytics events. Advertising identifier access is subject to your App Tracking Transparency choice. We do not use your recordings to train our own AI models. The current app does not display app-open ads; earlier versions included Google AdMob.

On-device recording

Using the on-device Apple Speech engine does not upload your recording or transcript to our service for transcription. Cloud translation, summaries, sync and team sharing are separate features that can send content off-device. App analytics can still operate as described in §3.4.

Who we are

Minine Inc is the data controller for MinineSTT. Our registered address is 18952 MacArthur Blvd, Irvine, CA 92612, United States. Our backend is hosted in Oregon, United States.

For privacy questions you can reach us at mian@minine.games, or use any of the channels listed in Contact.

Data we handle

The following describes the data used by the app, our backend and connected services.

3.1 On-device data

These records are stored in the app’s iOS sandbox. Content may be uploaded when you use the features described in §3.2; analytics data is described separately in §3.4.

3.2 Server-side data

The following exists on our backend in Oregon, United States only after you trigger it:

3.3 Device access

In the iOS app, recording uses microphone access and on-device speech recognition. Imported files are processed when you choose them. The iOS app does not request device location, contacts, calendars, health or motion access for these features. Device access in the web and desktop apps, including the optional Google Calendar connection, is described in §3.7.

We do not embed a separate crash-reporting service such as Sentry or Crashlytics. App and backend diagnostic logs may include operation status, errors, account identifiers or usage counts needed to operate and troubleshoot the service.

3.4 App analytics and tracking choices

Meta and AppsFlyer receive installation and app-session events, selected product interactions (such as sign-in, first recording, summary use and notification choices), and purchase/subscription events. Depending on the event, data can include an app account identifier, product identifier, transaction identifier, amount and currency, and device or advertising identifiers handled by the SDK. These events do not contain the recording or transcript text.

iOS asks whether you allow tracking through App Tracking Transparency. IDFA access requires authorization. You can change the choice in iOS Settings → Privacy & Security → Tracking. Declining tracking does not disable every analytics or attribution event: SDKs may still send permitted installation, usage and purchase information without an authorized IDFA.

3.5 Meeting assistant (Zoom)

The meeting assistant is available only when enabled for your account. It currently supports Zoom meetings. Connecting Zoom links your Minine account to a Zoom user identifier and stores encrypted OAuth access and refresh tokens on our backend. The connection uses Zoom account identification and an on-behalf meeting token; OAuth tokens are not returned to the iOS app or the web app.

When you request a meeting recording, the service processes the meeting URL or ID, passcode if provided, title, assistant display name, duration limit and operational status. After admission and recording permission from the host, it records meeting audio and can import that audio into your Minine records for transcription. Audio, transcript content and any requested translations or summaries then follow the cloud-processing rules in this policy.

Disconnecting in Minine revokes access and queues cleanup of the affected Zoom authorization and associated cloud meeting artifacts. Removing the app in Zoom triggers the same cleanup when Zoom’s signed deauthorization notice is received. Active recording or transcription work may need to stop or finish before cleanup can complete. This does not remotely erase offline copies on a device, exported files or copies you have shared elsewhere; remove those separately. It does not delete unrelated Minine recordings.

When the meeting assistant is disabled in an app build, the app does not poll the meeting assistant service. Use Zoom App Marketplace to remove the authorization if the in-app controls are unavailable, and contact us for help with related data.

3.6 This website

Apart from the iPhone download page described below, this website does not load advertising or analytics tracking scripts. It does not itself provide an account sign-in or a data-submission form, and does not set a login cookie; its “Sign in” link opens the separate web app described in §3.7. Language is selected through the page URL. The hosting service may process ordinary access logs. A support email link opens your email application; no message is sent unless you choose to send it.

The iPhone download page (mininetranscribe.com/iphone and its language versions) is where our ads link to. It loads Meta Pixel and AppsFlyer’s Smart Script so we can tell which ads bring visitors and app installs. Meta receives a page view and a tap on the App Store button. AppsFlyer builds the App Store link from the campaign parameters in the page address, such as utm tags and ad click identifiers, and keeps a browser identifier so an install that follows can be matched to the visit. Both services also receive the browser’s technical details, such as IP address, user agent and language, and can store identifiers in cookies or local storage. The page has no form and collects no account or recording data. Visitors whose device is set to a European time zone are asked first, and these scripts load only if they allow them; a browser Global Privacy Control signal is treated as a refusal. Without them, the App Store button still works and goes through a plain AppsFlyer link.

3.7 Web app and desktop app

The web app (app.mininetranscribe.com) and the desktop app use the same account and cloud library as the iOS app. They have no on-device transcription engine: recordings you make or files you upload there are stored in cloud audio storage and transcribed by a cloud transcription provider. Neither includes advertising or marketing analytics SDKs.

Recording asks your browser or operating system for microphone access and, if you choose to record a tab, window or your computer’s sound, for screen or system-audio capture. Only the audio is kept; any accompanying video is discarded immediately. The web app keeps your sign-in token and preferences in your browser’s local storage; signing out removes the token.

Live captions (Pro) stream the audio being recorded directly from your browser or desktop app to our cloud transcription provider, using a short-lived access token issued by our backend, and show the text as you speak. Turning captions off or pausing closes the stream.

Google Calendar is optional. If you connect it, we request read-only access to your calendar events (the calendar.events.readonly permission) and read the title, start and end time, meeting link and your response status of today’s remaining events, to show upcoming meetings, remind you to record them and suggest a title for the recording. Calendar data is read directly between your device and Google. The only calendar data that reaches our servers is the title of an event you choose to record, which becomes that recording’s title; it is stored with the recording like a title you type yourself, and you can rename it or delete the recording at any time. Calendar data is never sent to our transcription, translation or AI summary providers. In the web app the access token is kept in your browser’s local storage and expires after about an hour; the desktop app stores a refresh token on your computer, encrypted with your operating system’s credential protection. Disconnecting in Settings → Integrations deletes the stored token and revokes access; you can also remove access at myaccount.google.com/permissions.

Minine’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use calendar data for advertising, do not sell it, do not share it with AI providers, and do not use it to train AI or machine-learning models.

On Windows, the optional meeting detection in the desktop app reads Windows’ own record of which apps are using the microphone, to notice when a meeting app such as Zoom or Teams starts or ends a call. This check runs only on your computer and is not sent to us. You can turn it off in Settings → Desktop.

Web subscriptions are paid through Stripe on Stripe’s own checkout page. We receive the subscription status, plan and renewal date, and never receive your full card number.

Third parties

We use the service providers and categories below to provide the features described here and to measure app usage and marketing attribution. Recording content is not sold or supplied to the marketing analytics SDKs. The providers’ own privacy terms also apply to their processing.

Requests to cloud transcription, translation and AI summary providers go through our backend, except live captions, which stream from your device to the transcription provider with a short-lived token issued by our backend. We do not attach your Minine account identity to the audio or text sent for these processing requests; however, the content you submit can itself contain personal information. Provider retention and handling rules apply to the submitted content. Contact mian@minine.games for information about the providers handling your data and the applicable processing terms.

Retention

• On-device data stays until you delete it from the app or uninstall the app.
• Account record persists until you delete your account.
• Sessions, transcripts, translations on our servers persist until you delete them in the app, or until your account is deleted (whichever comes first).
• Cloud-stored audio is removed within 14 days of the corresponding session being deleted.
• Team data (membership, activity log) persists while you remain a member; leaving a team removes your membership row immediately.
• Backups of our cloud database roll over within 35 days; deleted records age out of those backups within that window.
• Job queue messages are transient (max 14 days) and contain only the references needed to process a transcription, not the audio itself.
• Google Calendar data is not stored on our servers, except an event title you choose to use as a recording title, which is kept and deleted with that recording. Calendar tokens on your device stay until you disconnect Calendar or Google revokes or expires them.

When you request account deletion (see §6), we delete server-side account content within 14 days, except where a minimum record must be retained for legal obligations. Apple processes in-app subscription payments and Stripe processes web subscription payments; payment records they keep follow their own retention rules. Our backend also holds subscription verification and entitlement information needed to provide the service. Backup and processor retention follow the applicable rules described in this policy.

Zoom authorization and associated cloud meeting data are handled through the revocation and queued cleanup process in §3.5. Offline device copies, exported files and copies shared elsewhere must be removed separately.

Your rights

Regardless of where you live, you can:

• Access your data — every transcript can be exported as text, SRT, bilingual SRT, or JSON from inside the app.
• Delete a session — this also removes the corresponding cloud audio and database record if sync is on.
• Delete your account — until the in-app self-service flow is shipped, send a request to mian@minine.games from the email tied to your account; we will action it within 14 days.
• Export your data — ask us at the same address; we will return a ZIP containing your account record, all sessions (JSON), and audio files.
• Object / restrict / correct — correct your displayed name in Settings → Account; for any other objection, write to us.
• Change tracking permission in iOS Settings → Privacy & Security → Tracking.
• Disconnect Zoom or remove the app in Zoom App Marketplace; contact us for related data requests (see §3.5).
• Disconnect Google Calendar in the web or desktop app under Settings → Integrations, or remove access at myaccount.google.com/permissions (see §3.7).
• Request information about the service providers that receive your personal information, including specific recipients where applicable, by contacting mian@minine.games.

We will respond to verifiable requests within statutory windows (typically 30 days under GDPR, 45 under CCPA). We do not charge for these.

If you live in a region with a supervisory authority (e.g. an EU Data Protection Authority), you also have the right to lodge a complaint with them directly. We’d appreciate the chance to fix things first — just write to mian@minine.games.

Regional notes

7.1 European Union / EEA / United Kingdom (GDPR / UK GDPR)

Our legal bases are: contract (we cannot give you sync, cloud transcription or teams without processing your audio and account data); legitimate interest (we need to operate, secure, and improve the service); and consent, where you affirmatively select a cloud feature. Data is processed in the United States, with our backend hosted in Oregon; we rely on Standard Contractual Clauses with our processors and our cloud infrastructure provider’s GDPR Data Processing Addendum for these international transfers.

7.2 California, USA (CCPA / CPRA)

The categories of personal information are described in §3. Marketing attribution involves sharing limited identifiers and app-event data with Meta and AppsFlyer as described in §3.4; we do not sell recording content. California residents may request access, deletion, correction and an opt-out of sale or sharing where applicable by contacting mian@minine.games. You can also change the app’s tracking permission in iOS Settings.

7.3 Mainland China (PIPL)

For users in mainland China, cloud features transfer data to and process it in the United States, and may send it onward to the service providers described in §4. Marketing attribution data is handled separately as described in §3.4. You can stop future recording-content uploads by choosing on-device features and disabling cloud features, and exercise your rights under PIPL by contacting mian@minine.games. Where separate consent is required for a transfer or other processing, that requirement applies.

7.4 Other jurisdictions

We aim to honour equivalent rights wherever you live. Reach out and we’ll do our best.

Children

MinineSTT is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal data from children. If you believe a child has used the app and submitted data, please contact us so we can remove it.

Security

App-to-backend traffic uses HTTPS/TLS. Cloud audio and database content use encryption at rest. Zoom OAuth access and refresh tokens use managed encryption with an account-specific encryption context. You can sign out of the app or revoke a Zoom connection. Cloud-processing API keys and confidential Zoom OAuth credentials are held on the backend, not in the iOS, web or desktop apps or this website; live captions receive only a short-lived token.

No system is perfectly secure. If you believe you’ve found a vulnerability, please reach out at mian@minine.games — we welcome responsible disclosure and will work with you on a fix.

Changes to this policy

When we change this policy, we update the “Effective” date at the top and bump the version number. Material changes (new vendors, new categories of data, new uses) will be surfaced in the app on next launch and described in the App Store release notes.

Contact

Privacy questions: mian@minine.games Account deletion / data export: mian@minine.games Security disclosure: mian@minine.games General support: support@minine.games