This translation was prepared with machine assistance. The German version is authoritative. German original

Privacy notice

As of: 26 October 2026

These notices describe data processing in the current voizt web app. Some features are still local demos. There is also a server-based text community: when you publish a post while signed in, other authorized members can see it according to your chosen visibility. Private text messages start with a request; a conversation continues only after acceptance.

Controller and contact

The controller is iMild LLC, 2648 International Blvd Ste 285, Oakland, California 94601-1580, United States. Privacy requests: s@voizt.com.

Data we process

• Email accounts: Email address, a password hash protected with scrypt, and technical session data. The password itself is not stored. To verify the address, we store its verification status and temporarily store only the hash of a single-use verification token with a limited lifetime.
• Continue with Apple: The email address verified by Apple, including an Apple relay address, and a stable Apple account ID. voizt does not request or store your name, Apple password, or Apple access or refresh tokens.
• Account content: Learning progress, settings and profile information are associated with your account so they can be synchronized between devices.
• Community: When you publish text posts or comments while signed in, we process the text, account association, visibility and timestamps so other authorized members can see them. Likes, saved posts and follow relationships are also stored with your account. Text messages and message requests are associated with the respective accounts; after a request is accepted, both participants can see the conversation history. Reports record the reason and the relevant content or accounts for the intended review. Document sharing is restricted to accepted one-to-one chats.
• Teacher appointments: If your account has a verified email address and email delivery is configured, appointment requests and status changes generate a short notification containing the appointment time, duration and the other person’s name. Personal booking notes are not included in this email. The notification also appears in the signed-in app.
• Support requests: When you contact us through the app while signed in, we store the category, message, receipt time and any response with your account. Owners and operators can read these requests. Replies appear in your app; no support email is sent. Deleting the account removes its support requests from the active database.
• Optional discovery source: If you optionally tell us during setup how you found voizt.com, that answer is stored with your learning progress. The protected admin overview shows only totals by answer category, without links to individual accounts. “Prefer not to say” is not analyzed. Without an account, the answer stays on your device.
• Technical data: Sign-in flows and security events are stored with the provider, event type and time. The app does not log email addresses, Apple account IDs or IP addresses in these records. IP addresses may be processed in memory for short rate limits. Infrastructure providers may keep their own connection logs.

Self-hosted text translation

After your explicit consent, your text is processed over HTTPS on the existing voizt server in Ashburn, Virginia, USA. Argos Translate translates German, English and Turkish without an external translation API; Zeabur and Tencent Cloud remain the hosting providers. The translation process uses only a private local connection. Input and output are needed in memory during processing; the application creates no content cache, text logs or permanent translation file for them. This does not promise immediate physical erasure of all memory areas. To limit abuse, pseudonymous quota identifiers and request and character counters are stored, without translation texts. Usage-related quota counters are retained for at most 35 usage days. While the service is running, cleanup occurs hourly, removing them from the active database within 36 days. After an interruption, cleanup runs before startup. Existing backups are not altered by this cleanup; the backup retention described below applies to them.

Only if you also enable history will up to 20 translations remain in device storage and, where applicable, in synchronized learning progress. Saved favorites remain until you remove them. Older backups may contain previously saved content; the backup retention described below applies to it as well. Dictation on your device keyboard and speech output are also subject to your device provider’s settings and privacy terms. Please do not enter confidential data for translation.

Microphone, device and local storage

When you start a speaking exercise, the browser may open the microphone with your permission. In this app, the recording is created only temporarily on your device and is not uploaded to voizt. Speech output uses your device’s speech feature. Learning progress and settings are also stored in the browser; signed-in accounts synchronize them with the voizt server. Unacknowledged text messages and location messages explicitly confirmed for sending are queued in IndexedDB on your device with a stable identifier tied to the account, then retransmitted when the connection returns. Signing out pauses sending; the local copy stays tied to the original account until acknowledgement or account deletion. It is not sent under another account. The service uses a necessary HttpOnly session cookie. The necessary “voizt_ui_locale” cookie stores your chosen interface language for up to one year; the language also appears in the URL and, where applicable, in your synchronized settings. The language choice is not used for advertising or tracking. There are no advertising or analytics cookies or scripts.

Purposes and legal bases

We use account data to provide your account, sign you in and store your learning progress. The optional discovery-source answer helps us understand how users find voizt.com; internally it is shown only as totals by answer category. Security events protect against abuse. Where the GDPR applies, necessary account and synchronization processing is based on performance of a contract, and security processing on our legitimate interest in a secure service. Optional microphone access starts only after your device/browser permission.

Documents, locations and optional calls

A selected document is stored with its filename, file type, checksum and message association only after “Send document”. New large files are kept in protected file storage; older small attachments may still be in the voizt database. Only the two authorized conversation participants can retrieve it through the chat. Supported formats are PDF, TXT, DOCX, XLSX, PPTX, images (PNG, JPEG, WebP), video (MP4, WebM) and audio (M4A, MP3, WAV, OGG, WebM), by default up to 2 GB per file, depending on the displayed server limit and available media storage. New uploads use acknowledged chunks; to resume an interrupted upload, select the same file again. Unsent uploads can be removed under “Manage pending uploads” in the app. Voice messages are recorded only after you explicitly start recording and grant microphone permission, and transferred only after “Send voice message”. Recording previews stay on the device until sending. Granting location access alone does not send a message: the displayed coordinates are stored and shared as a text message only after your separate confirmation.

If calls are configured on the server, the other person receives an incoming-call display in the open app and can accept or decline. The microphone and, if applicable, camera are used only after you start or accept a call and grant device permission. Audio and video travel over WebRTC between participants’ devices and, where applicable, the configured relay service; voizt does not record calls. Connection signaling temporarily processes connection descriptions and network addresses. These signals are removed when the call ends or the server checks for expiration; call type, conversation association, status and times remain as history. Background calls and push call notifications are currently unsupported.

Recipients and storage location

When you sign in with Apple, your browser communicates with Apple and our server verifies the sign-in code with Apple. Apple receives the request and connection data needed for sign-in; Apple describes the feature in its Sign in with Apple documentation.

voizt is hosted through Zeabur on a Tencent Cloud server in Ashburn, Virginia, USA. Account data and learning progress are stored on the voizt volume in the United States. Zeabur and the infrastructure provider may process data as needed for operation, security and storage. This may involve transferring data from the country where you are located. Provider information: Zeabur privacy policy and Tencent Cloud data processing terms.

We do not sell your personal data or use it for cross-context behavioral advertising. We operate no newsletters, advertising tracking or analytics tools.

Images and videos in posts

An image or video is transferred and associated with a post only after “Publish post”. The original post’s visibility, blocking and removal also apply to the media. Public posts are visible to signed-in community members; “Contacts only” requires an accepted chat. Files are stored without automatic conversion; your device determines which video and image formats it can play.

Post views

The app reports a post view when at least half of the post header has been visible for at least one second. Each signed-in account is counted once per post; your own views do not count. We store the account association, post and first viewing time. Other members see only the total. This does not count unique natural persons and is not tamper-proof evidence. Your own view data is included in your account export and removed upon confirmed account deletion.

Personal daily vocabulary training

For daily training, we store your chosen language pair, difficulty guidance, topic, daily goal and time zone, together with daily lists, replacement reasons and exercise results with timestamps. Your text input and dialogue answers are compared locally with sample answers; only the result, use of hints and relevant exercise are stored and synchronized with your account. No answers are sent to an AI service and no microphone recordings are made for this. Optional read-aloud uses an available device/browser voice. Without sign-in, the learning plan stays in the browser. With sign-in, it belongs only to your account. You can export it from the training view; the server-side learning plan is also in the account export and is removed from the active database upon confirmed account deletion. A guest learning plan is not automatically associated with an account. There are no new automatic reminders or external background services.

Retention and erasure

Account data and synchronized content remain stored while your account exists. You can request/export a data copy through “Privacy & Security” or start account deletion in the app. Alternatively, send a request to s@voizt.com . After deletion is confirmed, we remove the active account and related app data unless a statutory retention obligation applies. Backups may remain until their regular removal; no fixed maximum retention period is currently set for these copies. Sessions expire after seven days, and pending sign-in flows after ten minutes.

Your privacy rights

Depending on where you live and the applicable law, you may request access, rectification, erasure, restriction, data portability or object to processing. Send requests to s@voizt.com; we may require reasonable identity verification. California users, where the CCPA/CPRA applies to them and iMild LLC, may also request information about the categories and uses of their data, or request erasure or rectification. We do not sell personal data. Requests may be submitted by email. Where applicable, you may also contact your data protection supervisory authority.

Data security

The connection uses HTTPS. Passwords are stored as scrypt hashes and session tokens are stored in hashed form; sessions are protected by HttpOnly cookies. No transmission or storage system can guarantee absolute security.

Changes and contact

If the app or its data processing changes significantly, we update these notices. Questions and requests: s@voizt.com.