Privacy Policy

The data controller for the processing described in this policy is:

Mohammad Soori
Senite AI
c/o COCENTER
Koppoldstr. 1
86551 Aichach
Germany

Senite AI provides the transcription, live translation, and related services described in this policy. Throughout this policy, “we” and “us” refers to the data controller named above. You can find the matching legal notice in our Impressum. For any privacy question, the fastest way to reach us is support@senite.app.

• Contract necessity — processing your uploaded audio, and generating transcripts/translations/summaries, is necessary to provide the service you requested.
• Legitimate interest — technical/rate-limiting data, and the hashed signup-bonus record described below, are processed to keep the service secure and free of abuse (e.g. repeated bonus claims); this interest is balanced against your privacy and limited to what's needed for that purpose.
• Consent — where a feature explicitly asks for your consent (e.g. optional processing steps), you can withdraw it at any time with future effect.

• Account data — the email address and profile info provided by your sign-in method.
• Content you upload — audio/video files you submit for transcription, and the transcripts, translations, and summaries generated from them.
• Live translation data — audio segments and text from real-time translation sessions you start.
• Recordings you make in the mobile app — voice recordings, and video you record with the camera, are captured on your device only when you start them, and are then submitted like any other file. The microphone and camera are never used in the background on their own: only a voice recording or live translation session that you started can keep using the microphone if you leave the app or lock your phone, and only until you stop it. Your device shows its own recording indicator (on Android, a persistent notification). Video recording does not continue in the background.
• Profile picture — if you add one, it is stored privately and served only to your signed-in account.
• Push notification data — if you allow notifications in the mobile app: a device push token, the platform (iOS or Android) and the app language you use, so we can tell you in that language when a file finishes. A notification contains the file name and the status. You can turn notifications off at any time in your device settings.
• Usage & billing data — credit balance, job history, and processing metadata (file duration, provider used, timestamps).
• Technical data — request metadata used for abuse prevention (rate limiting, bot/App Check verification). This is not tied to a long-lived profile beyond what's needed to enforce limits.
• Signup bonus record — a one-way cryptographic hash of your email (not the email itself), used only to prevent the same person from claiming the one-time signup credit bonus multiple times by deleting and recreating an account. See “How long we keep your data” below.

Solely to operate the service you asked for: turning your uploaded audio into transcripts, translations, and summaries; tracking credit usage so billing is accurate; keeping the service secure and reasonably free of abuse; and troubleshooting when something breaks. We do not sell your data, and we do not use your uploaded content to train AI models we operate.

Processing your files requires sending them to specialized service providers. Depending on which options are active for your job, that can include:

• Authentication & database provider — handles sign-in and stores job records and account data.
• Object storage provider — one storage backend is active at a time, used to store uploaded audio and generated results.
• Speech-to-text providers — used to transcribe uploaded audio into text.
• Language model provider — used for translation and summarization of transcripts, when you request those features.
• Real-time translation provider — used for live-translation sessions, and also to synthesize spoken audio when you enable Voice → Voice playback.
• Push notification services — deliver the notifications described above. They receive the device push token and the notification text (file name and status) and are operated by the app-distribution platform (Apple or Google) and our push-delivery provider.
• Payment processor — handles credit purchases; receives your email and payment details directly to process the charge. We never see or store your card number.

The specific vendors behind each category above may change over time as we adopt better or more suitable tools, so rather than list names that could quickly go out of date, we describe the categories of processing instead. Each provider processes data under its own privacy terms and may be located outside your country. We only send the minimum data each provider needs to perform its function. If you'd like the current list of providers for a specific purpose (e.g. a data-portability request), email us and we'll provide it.

Some of these providers are based outside the EU/EEA, which means using them involves an international transfer of your data. Where that's the case, the transfer relies on the provider's Standard Contractual Clauses or an equivalent safeguard recognized under GDPR Chapter V.

We use a small number of cookies necessary to operate the service. With your consent, given via the cookie banner, we also use optional analytics cookies to understand how the site is used. We do not use cookies for advertising or cross-site tracking.

• Keeping you signed in — a cookie that identifies your session so you don't have to log in on every page. Set when you log in, not readable by page scripts, and expires automatically after 14 days or when you sign out.
• Remembering your language preference — a cookie that stores the interface language you selected, so we don't reset it on every visit. Expires after 1 year.
• Security / bot-protection (Google reCAPTCHA) — set by Google when the app loads, used to distinguish real visitors from automated abuse before your requests reach our API. This is necessary to keep the service secure and isn't used by us for tracking. Google processes this as its own service; see Google's Privacy Policy for how it handles this data.
• Remembering your cookie choice — a cookie that records whether you accepted or declined analytics cookies in the banner below, so we don't ask again on every visit. Expires after 1 year.
• Analytics (optional — Google Analytics) — only set if you accept the analytics category in the cookie banner. Used to understand how visitors use the site (e.g. pages viewed) so we can improve it. Not set until you consent, and you can decline this category and continue using the service normally. Google processes this as its own service; see Google's Privacy Policy for how it handles this data.
• Analytics (optional — Microsoft Clarity) — only set if you accept the analytics category in the cookie banner. Used to understand how visitors use the site (e.g. navigation and session behavior) so we can improve it. Not set until you consent, and you can decline this category and continue using the service normally. Microsoft processes this as its own service; see Microsoft's Privacy Statement for how it handles this data.

The cookies above marked as necessary don't require consent under the German TTDSG or the EU ePrivacy rules — but we disclose them here for transparency. Analytics cookies are optional: they're only set if you actively accept them in the cookie banner, and declining them doesn't affect your ability to use the service.

Retention is configurable and enforced automatically by a background job. The current configuration is:

• Your original uploaded audio/video file (and any derived audio chunks or generated PDFs) is permanently deleted 90 days after the job completes.
• The transcript, translation, summary, and search text remain available for 365 days after the job completes (independent of when the original media is deleted above), after which they are cleared and the job is removed from search.
• Short-lived streaming copies of your audio, created only to hand a chunk to a speech-to-text provider, auto-expire within a couple of hours regardless of the settings above.
• The hashed signup-bonus record described above is kept indefinitely for fraud prevention — it cannot be reversed back into your email address without the server-side secret key.

Once a file is permanently purged, it is gone from our servers — including the transcript, translation, and summary text, not just the downloadable PDF/TXT copies. We do not keep a separate backup for you to recover later. If you want to keep a transcript, translation, or summary long-term, download or copy it before it expires. Self-service export of your full account data isn't built yet (see “Your rights” below) — until it is, this is the only way to keep a copy.

These numbers reflect the live configuration and update automatically if the retention policy changes.

You can permanently delete any finished job from the web app or the mobile app. This deletes the job record and its files in storage: the original audio/video, any derived chunks, and the generated transcript, translation, summary and documents. While the original file is still retained you can also download it again from the job page, through a short-lived link that only works for your signed-in account.

You can permanently delete your account from Settings at any time. Doing so immediately and irreversibly:

• Deletes outright — your account profile, profile picture, device push tokens, sign-in credentials, folders, job step logs, live translation transcript segments, and every audio/result file you uploaded or that was generated for you in storage.
• Anonymizes rather than deletes — your job and live-translation session records. We keep aggregate usage figures (processing time, provider used, token/credit counts, timestamps) because our internal cost and usage reporting is built from this data, but every identifying or content field — your file names, transcript text, translated text, error messages, and storage file paths — is stripped at the same time. What remains cannot be traced back to you once your account profile and sign-in credentials are gone.

There is no recovery grace period for the deletion itself; once you confirm, it cannot be undone.

Under GDPR (and similar laws elsewhere), you have the right to:

• Access — a copy of the personal data we hold about you.
• Rectification — correction of inaccurate or incomplete data.
• Erasure — deletion of your data. Self-service via Settings (see above); this immediately deletes your identity and content, and anonymizes the aggregate usage records we retain for reporting (see “Deleting your account” above).
• Restriction — limit how we process your data in certain circumstances.
• Objection — object to processing based on legitimate interest.
• Portability — receive your data in a portable format.
• Withdraw consent — at any time, where processing is based on consent, without affecting past processing.

To exercise any of these (other than self-service deletion), email support@senite.app and we'll handle it manually while self-service export is being built. You also have the right to lodge a complaint with a data protection supervisory authority — either in your country of residence, or in the country where the controller is based (see our Impressum for details).

All traffic to the service is encrypted in transit. Access to your account is protected by an industry-standard authentication provider, and API endpoints are protected against automated abuse with rate limiting and bot-detection checks. No method of transmission or storage is 100% secure, but we take reasonable, industry-standard steps to protect your data.

This service is not directed at, and should not be used by, anyone under 16 years old.

If this policy changes materially, we'll update the “Last updated” date above. Continued use of the service after a change means you accept the updated policy.

Questions about this policy or your data: support@senite.app