The German and English versions are intended to provide the same information. Mandatory local language and consumer protection rights remain unaffected.
PRIVACY
Privacy policy.
1. Controller
Marvin Kemper – Kemper Publishing & Merchandise
Email: datenschutz@jaysay.it
Service provider
We have not appointed a data protection officer because there is no legal obligation to do so (Article 37 GDPR, section 38 BDSG). For any data protection questions, contact us at the address above.
2. Key points
- Your recordings and text are processed only for speech recognition and editing. We do not store these dictations on our servers or write them to any logs. The exception is text you expressly attach to a report about an AI result (section 9).
- With a JaySay account, cloud dictations go first to JaySay on our server in Germany and from there to our AI service providers in the USA for processing (DeepInfra, with Groq as a replacement). For offline dictation, JaySay sends no recordings or text to servers. The subscription app does not use your own provider keys.
- Text already in the input field is sent only if you enable “Send text in field”.
- Your history is stored only on your device. Your dictionary and learned corrections are stored there and may be sent for text editing during cloud dictation.
- No advertising networks and no tracking across other apps or websites. We keep our own operational and offer statistics without dictation content (section 7). When your quota is used up, a local notice tells you.
3. Cloud dictation
Data: your voice recording, recognised text, live text from your phone's offline recognition if enabled to assist text editing, the result, selected style, dictionary terms and learned corrections. Language is detected automatically during cloud dictation.
Purpose and legal basis: providing the dictation feature, Article 6(1)(b) GDPR (contract). If a dictation contains health data or other special categories of data about you, the legal basis is your explicit consent, which you give in the app when enabling the accessibility service (Article 9(2)(a) GDPR). Information about other people that appears in your dictation is processed only transiently for that dictation (Article 6(1)(f) GDPR; legitimate interest in producing the text you requested). Detecting the active input field and inserting text through Android's accessibility service are strictly necessary for this service (section 25(2), no. 2 TDDDG).
Retention: on our server, only in memory for the duration of the request. DeepInfra and Groq process dictations only to answer the request, do not store them afterwards and do not use them to train AI models. Zero Data Retention is enabled for our Groq account. DeepInfra's terms allow storage only in narrow exceptions: to resolve a support case with our written consent (deleted no later than 30 days afterwards), and where required by law or necessary to prevent fraud, security incidents or abuse. Both keep content-free usage data such as the number, time and duration of requests.
Recipients: Hetzner Online GmbH (Falkenstein data centre, Germany) as hosting provider; Deep Infra Inc. (USA) and, as a replacement, Groq (contracting party for European customers: Groq UK Limited, United Kingdom; processing in the USA) for speech recognition and editing. If a response is slow, faulty or implausible, JaySay may send a second request; both providers may then receive the same data. All service providers process the data on our behalf under data processing agreements (Article 28 GDPR). Transfers outside the EU are covered by EU Standard Contractual Clauses (Article 46(2)(c) GDPR). You can obtain a copy of these safeguards from our privacy contact.
Please note: JaySay does not use voice recordings to recognise you by your voice. Dictations may nevertheless contain health data, political or religious information and similarly sensitive details about you or others. For information about you, the app asks for your explicit consent; you can withdraw it at any time by signing out and dictating offline. Only dictate sensitive information about other people or professional secrets if you are entitled to do so; offline dictation, which sends nothing to servers, is well suited for this.
4. Sending text in the field and command mode (optional)
With your consent, JaySay also sends text already in the input field during cloud dictation: up to 1,000 characters before and 1,000 characters after your writing position. With command mode enabled, up to 4,000 characters from the field, including the selection, are sent even during normal dictation. With a JaySay account, this text goes to our server in Germany, then to DeepInfra or Groq as a fallback for text editing. Offline dictation sends no field text. This may include personal data, such as a message you are replying to.
The legal basis is your consent (Article 6(1)(a) GDPR, section 25(1) TDDDG); for special categories of data about you, additionally your explicit consent under section 3 (Article 9(2)(a) GDPR). You can withdraw it at any time in the settings; this takes effect from the next request. Recipients and retention as in section 3.
5. Data on your device
History (1, 7 or 30 days, default 7 days), dictionary, learned corrections and settings are stored only on your device. The app protects these data through encrypted storage. History cleanup runs on access, at app startup and as a scheduled background task; Android may delay it, for example after a force stop.
Recordings are temporarily saved in private app storage so you can recover them after an error. The app does not additionally encrypt the audio files. They are cleaned up after successful insertion or discarding; after an error they may remain for recovery. You can delete local data in the app or by uninstalling it.
Offline dictations are processed by your device's speech recognition; no data is sent to us. With live text, your device's offline recognition writes into the text field during recording. During cloud dictation, this text may be sent to us and the AI service providers in section 3 to assist text editing; we do not store it on the server.
6. Account and sign-in
You can sign in with email and password, Google or a passkey. We ask only for your email address at registration, not your first or last name. The verification link in the email is valid for 7 days. Until verification, AI editing is limited to 200 words in total; this limit does not reset every week. Offline dictation on supported devices is independent of this limit.
Data: email address, a name value technically generated from it in the sign-in service, your Google identifier when signing in with Google, and technical sign-in data. Passwords are stored as hashes in the sign-in service. For passkeys, the sign-in service receives only the public key and technical sign-in information; the private key remains on your device or in the passkey manager you use for your devices. JaySay does not receive it. You can also link a Google account to your JaySay account later.
Purpose and legal basis: account management, Article 6(1)(b) GDPR; protection against abuse, Article 6(1)(f) GDPR.
Recipients: our own sign-in service on our server at Hetzner Online GmbH (Falkenstein, Germany). We send confirmation links and emails for setting or resetting a password from our domain jaysay.it via mailbox.org (Heinlein Hosting GmbH, Berlin) as processor. The email service processes your email address, the message content and technical delivery data. When you sign in with Google, Google is an independent controller for that sign-in; the responsible company depends on the Google terms applicable to your account.
Retention: account data until account deletion. The sign-in service keeps an internal, continuous change log. After deletion, older entries about your account, such as your email address and the times of sign-ins or changes, may remain in it for technical reasons. They are blocked from sign-in and used only for the security and troubleshooting of the sign-in service (Article 6(1)(f) GDPR). We do not keep copies of the emails we send; the email service stores technical delivery data according to its own retention periods.
Account deletion: after you sign in again, your account is blocked. We delete the associated login in the sign-in service, including password and passkey credentials, then the account data on our server: sign-in mappings, account word and usage counters, purchase mappings and stored purchase tokens, reported AI results, feedback and account invitation data. Direct account links in remaining subscription, early-adopter and promotion records are removed. This does not establish that the remaining dates, plans and statuses are anonymous. A referral may retain the other participant's identifier. If the sign-in service is unavailable or has not completed deletion, the account remains blocked and deletion stays pending; the app shows an error. Server maintenance can retry pending deletions. This does not delete your Google account or local data on your phone. You must cancel a Google Play subscription separately.
For 5 minutes, a sign-in identifier that is not stored in plain text remains so that a still-valid session does not immediately recreate the deleted account. Purchase records and usage and offer data no longer linked to your account are handled as described in section 7. We keep encrypted database backups for 14 days; until then they may contain older states of already deleted data. Automatic cleanup runs hourly, backups run daily.
7. Subscription, purchase and quota
Payment and subscription management take place through Google Play; Google is independently responsible for them. We receive a purchase token, subscription status and term, and link them to your account through a pseudonymous identifier. For the word quota, we store only figures per dictation (words, seconds, time and status), not content.
Legal basis: Article 6(1)(b) GDPR; after account deletion, Article 6(1)(f) GDPR (preventing multiple use, chargebacks and unjustified claims).
Retention: Technical length counters per dictation 24 hours, request metadata 90 days, quota counters until 90 days after the end of their period. On account deletion, account-related counters are deleted; totals of quota periods still running remain without an account link until 90 days after they end. For purchases, a pseudonymous token hash, period and status remain after account deletion until the end of the third calendar year after the year of deletion (deletion in 2026: cleanup from 1 January 2030). This period follows the standard limitation period (sections 195 and 199 BGB), so that we can check chargebacks, refund questions and reuse of an already used purchase.
7.1 Operational and offer records
Daily counts cover successful, failed and cancelled requests, broad duration groups and speech-recognition retries, without dictation content, account ID or IP address. They are used for capacity and reliability planning (Article 6(1)(f) GDPR) and are deleted after 90 days. Small groups are not shown separately in reports.
We store subscription events (plan, billing period, status, timestamps, conversion from a trial, cancellation), early-adopter places and promotion-code redemptions to allocate services and offers correctly (Article 6(1)(b) GDPR) and to evaluate our offer without dictation content, for example how many trials become paid subscriptions (Article 6(1)(f) GDPR). Our hosting provider receives these records. We delete subscription events 24 months after they are recorded. On account deletion, we remove the account link; promotion redemptions without an account link are deleted 24 months after redemption. An occupied early-adopter place then remains only as a place number with timestamps, without any account or purchase link, so that it is not allocated again.
Invitations store a code hash and an encrypted copy of your code for display in the app, the participating account identifiers, status, timestamps, purchase links and reward data. Code check attempts are counted to prevent abuse. The purpose is the requested invitation and reward (Article 6(1)(b) GDPR), with abuse prevention additionally under (f). The inviter may infer a qualifying payment from the reward status, but receives no dictation content. On account deletion, we remove the deleting person's identifier and purchase links; a reward the inviter has already earned but not yet received is kept. If only the inviter remains, completed invitations are deleted 24 months after redemption; if no one remains, immediately.
7.2 Google Cloud Pub/Sub
Google Cloud Pub/Sub delivers technical Google Play subscription events to our server. These include the purchase token, package name, event type and time, but no dictations. Purpose and legal basis: keeping the subscription status up to date, Article 6(1)(b) GDPR. Google Play is an independent controller for the purchase. Pub/Sub is operated for us by Google Cloud (Google Cloud EMEA Limited, Ireland) as processor under the Google Cloud data processing addendum. Google retains messages that have not been retrieved for no more than 7 days. Google may also process data in the USA; the basis is the adequacy decision for the EU-US Data Privacy Framework and the Standard Contractual Clauses in the Google Cloud agreement.
7.3 Local quota notices
When your quota is used up, the app shows a local Android notification: JaySay then continues to dictate offline and, depending on your plan, a tap opens the plans. So that the notice does not appear repeatedly, the app stores an account identifier and the quota period on your device. No push service is used and nothing is sent to us (Article 6(1)(b) and (f) GDPR, section 25(2), no. 2 TDDDG). You can turn these notifications off in Android settings under “Account and plans”.
8. Server logs
Our server processes technically necessary connection data, including your IP address. We keep no access log of individual requests. Technical operational and error logs serve operation, troubleshooting and abuse prevention (Article 6(1)(f) GDPR); dictation content is not recorded in them. These logs are deleted automatically after no more than 30 days. To limit excessive requests, we use hashed account and IP identifiers in memory only. Recipient: Hetzner Online GmbH (Falkenstein, Germany) as processor.
9. Reporting AI results and feedback
You can report inappropriate AI results in the app. We store the request identifier, reason and your note; text is stored only if you explicitly tick the option. Purpose: improvement and compliance with Google Play policies (Article 6(1)(f) or (a) GDPR). Deletion after 90 days.
Through “Send feedback”, you can send us a bug report or idea while signed in. We store your message, app version and device model. Only if you tick “Attach diagnostic data” do we also send technical events from recent dictations (timings, error codes and code locations), never the dictated text. The app keeps these events only in memory; after a crash, they are saved once on the device so you can send them afterwards. Purpose: finding and fixing errors (Article 6(1)(b) or (f) GDPR). Deletion after 90 days or with your account.
10. Email support
If you contact us, we process your address, message and attachments to handle the request (Article 6(1)(b) GDPR for contractual enquiries; otherwise (f): handling and documenting correspondence). Mailbox provider: mailbox.org (Heinlein Hosting GmbH, Berlin) as processor. We delete support emails no later than two years after the request is resolved. Business correspondence and accounting records that we are legally required to keep are stored separately for the statutory period (Article 6(1)(c) GDPR).
11. This website
The website is served from our server at Hetzner Online GmbH (Falkenstein, Germany). This generates technically necessary connection data (IP address, time and requested page), Article 6(1)(f) GDPR; we keep no access log for this. We use no advertising or analytics cookies and embed no external fonts. Referral links contain the referral code in the URL path. The page validates it locally in your browser without an account request. Only when you follow the installation link is a valid code passed to Google Play as an install referrer to attribute the requested invitation (Article 6(1)(b) GDPR). The page is excluded from search indexing and suppresses transmission of its address as a referrer.
12. Crash reports
If you have allowed diagnostic data sharing in Android, Google receives aggregated crash reports that we can view in the Play Console. They contain no dictation content.
13. Your rights
Within the limits of the law, you have the right of access, rectification, erasure, restriction, data portability and objection (Articles 15–21 GDPR), and the right to withdraw consent for the future; this does not affect the lawfulness of earlier processing. You can delete your account and download a copy of your account data in the app profile. You can request full information about all data stored about you from our privacy contact. The Delete account page also explains how to request deletion by email. For other requests, simply email datenschutz@jaysay.it.
You can lodge a complaint with a supervisory authority, for example the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia, who is responsible for us. You may also complain to a competent authority where you live, work or believe an infringement occurred. We normally answer rights requests within one month. You may object to processing based on legitimate interests for reasons relating to your particular situation, and to direct marketing at any time. We explain any legally permitted extension within the first month.
14. Automated checks and human review
AI transcribes speech and edits authorised text; it does not assess your creditworthiness or personality. Quota, purchase, promotion and security checks run automatically and may restrict features or offers, for example when your quota is used up. They implement the agreed plan terms (Article 22(2)(a) GDPR). If you believe a decision is wrong, write to our support: we review it personally, you can state your point of view and contest the decision.
15. Additional information for users in the United States
Categories of personal information: account data (email address, sign-in identifiers), dictation content during cloud dictation, processed only transiently (section 3), purchase and subscription data (section 7), technical connection data (section 8) and support messages (section 10). Recipients and retention periods are described in those sections. Data is processed in Germany and, for AI processing, in the USA.
We do not sell personal information and do not share it for cross-context behavioural advertising. We do not disclose personal information to third parties for their direct marketing purposes (California Civil Code § 1798.83). We do not allow third parties to collect personal information about your online activities over time and across websites through our app or website. As we do not track you, our handling does not change in response to Do Not Track or Global Privacy Control signals.
JaySay does not create voiceprints or other biometric identifiers and does not use your voice to identify you; audio is used only to convert your speech to text. If you buy a subscription in the United States, we use your account email address to send the renewal reminders described in our US terms, and we keep proof of your consent to automatic renewal (plan, price shown, time) under the pseudonymous identifier Google Play receives with your purchase for three years, or while your account exists until one year after your subscription ends if that is later. California law requires this proof (Business and Professions Code § 17602), so it remains after you delete your account. JaySay is not directed to children, and accounts are only for adults (18+). We do not knowingly collect personal information from children under 13 and delete it if we learn of it.
You can download and delete your account data in the app. For access, correction or deletion requests, email our privacy contact. We answer such requests from users in every state, even where state privacy laws do not apply to us because of their thresholds. We post changes to this policy with a new date and tell you about material changes in the app or by email before they take effect.
How we handle health information you may dictate is described in our consumer health data privacy policy. Additional contract terms: terms for the United States.
Last updated: 10 October 2026