Privacy policy
DRAFT FOR LEGAL REVIEW — controller identity, provider contracts, international transfers and retention schedule require confirmation before commercial launch.
1. Controller
The proposed controller is [FULL LEGAL NAME], [LEGAL STATUS], [POSTAL ADDRESS], [REGISTRATION DETAILS IF APPLICABLE]. Contact: [email protected]. Data protection officer, if appointed: [CONFIRM OR REMOVE]. Effective date: [TO COMPLETE].
2. Account and service data
The API stores an account identifier, email, password hash when password login is used, verification status, hashed verification/reset tokens, session records, usage counters and subscription/payment identifiers. Google sign-in, when configured, supplies a verified identity and email. We do not receive your Google password. Stripe handles card entry; Typavo does not collect full card details. Account data is required for authenticated recognition and allowance enforcement; browsing product information does not require an account.
3. Audio, text and local history
Audio and requested text processing pass through the Typavo API to OpenAI. The API does not deliberately retain audio files or transcript content in its application database or logs. It does retain usage and request metadata, including duration and an audio digest used for request accounting. This is not a claim that every infrastructure provider retains nothing. Desktop transcription history is stored locally as unencrypted text: someone with access to those files can read it. Audio saving is off by default for new installations; if you enable it, recordings are saved locally with Windows account protection for replay and re-transcription. Existing explicit preferences are preserved. Deleting an app does not necessarily remove its local data.
4. Browser demo and clipboard
Microphone access starts only after you request it. A sample stays in tab memory until you explicitly send it for transcription, discard it or leave. Sign-out clears the sample, result and in-memory credentials. Only the appearance preference is stored in browser localStorage; there are no advertising trackers or tracking cookies in this site package. Clipboard copy is explicit in the browser. Desktop paste uses the chosen field; copy and paste may interact with system clipboard services outside Typavo.
5. Purposes and proposed legal bases
Account delivery, recognition, cleanup and requested translation: GDPR Article 6(1)(b), performance of the service. Billing records required by law: Article 6(1)(c). Security, abuse prevention and handling claims: Article 6(1)(f), subject to a documented balancing assessment and your objection rights. Optional features must be explained at activation; microphone permission is not blanket consent for unrelated processing. We do not intentionally perform advertising profiling or decisions producing legal effects using your dictated content. Do not dictate sensitive or third-party data without an appropriate basis; special-category processing requires separate legal assessment before launch.
6. Recipients and locations
Service providers include OpenAI for speech/text processing, Render for API/database hosting, Resend for transactional mail, Cloudflare for website/download delivery and Stripe for billing. Google is involved only when you choose its sign-in service. The exact contracting entities, processor/independent-controller roles, agreements and any subprocessors must be recorded: [TO COMPLETE]. EU-only processing is not promised. Where data leaves the EEA, confirm the destination and applicable safeguards, such as adequacy or contractual clauses, and how to obtain them: [TO COMPLETE]. Provider regions must be checked in the actual accounts, not inferred from DNS.
7. Retention
Desktop history remains until you delete local entries or app data. Optional local recordings remain until deleted with the associated entry or local data. The browser sample lasts only for the current page session. Verification links expire after 24 hours, reset links after 30 minutes and refresh sessions after 30 days; expiration does not itself establish database deletion. Audio-request accounting metadata has a 30-day cleanup rule in the reviewed source; confirm operation after deployment. Account deletion, expired-token cleanup, usage/billing records, backups and infrastructure-log deletion schedules: [SPECIFY PERIODS AND JUSTIFICATION BEFORE LAUNCH]. OpenAI retention depends on the endpoint and account settings; a blanket zero-retention claim is not made.
8. Security and your rights
Connections use HTTPS with certificate validation. Passwords and link tokens are hashed; this does not make all stored content encrypted. Restrict access to your Windows account and devices. You may request access, rectification, erasure, restriction, portability or object where applicable, and withdraw consent for processing based on consent without affecting earlier lawfulness. Contact [email protected]; we may verify identity proportionately. You can complain to the Polish data protection authority (UODO) or another competent authority. Mandatory records may limit erasure. Removing local history and deleting a server account are separate operations.
9. Before approval
Complete controller identity, precise retention periods, contracts and transfer safeguards, support procedures and the special-category-data assessment. Ensure deployment matches this description and explain any material changes before they apply. This draft is not a certification of GDPR compliance.