Privacy Policy
Last updated 11 October 2026
This policy explains how personal data is handled in the Inqui language-learning service — the inqui.ai website, the Inqui mobile apps, the teacher and administrator dashboard and the API behind them (together, the “Service”). It is information under Articles 13 and 14 of the General Data Protection Regulation (GDPR). Reading it, or using the Service, is not consent to research participation or to any other optional purpose; those are asked for separately. The rules for using the Service are in the Terms of Service; how AI is used is explained on the AI transparency page.
1. Who is responsible for your information
The Service is operated by Michal Macinka, a sole trader (OSVČ) registered in the Czech Trade Register, IČO 11824492, with a registered seat at Lhotka 198, 560 02 Česká Třebová, Czech Republic. For anything in this policy, write to [email protected]. No Data Protection Officer is appointed; that address reaches the person responsible.
If your school or institution gave you your account, that institution decides why your course and learning records are processed. It is the controller for those records and Inqui processes them on its documented instructions, as a processor under Article 28 GDPR. The institution’s own privacy notice covers its responsibilities and legal basis. Inqui is separately the controller for processing it decides on itself — running and securing the platform, accounts people create themselves, answering direct enquiries and meeting its own legal obligations.
Research is separate again. Each study names its own controller and research team in the participant information you receive before you decide whether to take part (Section 8).
2. What we process
Account and enrolment
E-mail address, display name, password (kept only as a one-way hash), interface language, the language you are learning and your native language, your organisation, group and course membership and your role, and the version and time at which you accepted the Terms of Service. Where you join through an institution, some of this reaches us from the institution rather than from you.
Year of birth — optional. The app asks for your year of birth (the year only, never a full date) during onboarding; you can choose “prefer not to say” and change or clear it at any time in your profile. We use it to make the Service more age-appropriate and for aggregate statistics about our users (for example age bands). It is not used to verify your age or restrict access, it is not shown to teachers or administrators of your institution, and it is not part of any research export — a study asks for age separately in its own questionnaire.
Learning content
The messages you send, recordings of your spoken turns and the text transcribed from them (recordings: see Section 3), the AI replies, questions you ask the native-language helper, activity goals and whether you reached them, corrections and feedback, per-turn error markers, saved vocabulary, flashcard and quiz answers and grammar notes.
Learning activity
Session dates and duration, number and length of turns, activity and course completion, points, streaks and badges, and estimated proficiency (CEFR) levels. For spoken practice we also keep speech-recognition timing and confidence metadata (for example speaking rate and pauses) — these describe how an utterance was produced, not who you are.
Conversation memory
Unless you switch it off, short notes that Inqui keeps between your conversations, separately for each language you learn: up to 5 interests, up to 5 things you find tricky and up to 8 topics you have already practised, each a short phrase (see Section 3). They never contain names, contact details or other sensitive information, are never created in research studies and are not shown to your teachers or institution.
Misuse screening
Your messages in a conversation are automatically screened for misuse (see Section 3). If a message is flagged, we keep an incident record: an excerpt of the message, a category, a severity and a short reason.
Usage and technical data
IP address (processed when you connect; see Section 7), app version, device model and operating system, and server logs needed to run the Service securely. The app also records our own usage events (for example which screen was opened, how long a section was used, connection quality and response times) linked to your account, so we can see whether features work and find bottlenecks. For every AI call we record technical metadata — model, number of tokens, latency and whether it succeeded — but not its content. We use no third-party analytics or advertising tools.
Mobile diagnostics and crash reports
The app keeps a technical event log — timestamps, screen names, error messages, network quality, device model, operating-system version, app version and a random device code — and uploads it to our servers so failures can be diagnosed. If the app crashes, a crash report with the same technical identifiers and a stack trace goes to Google Firebase Crashlytics, without your user ID. These logs never contain conversation content, passwords, tokens, e-mail addresses or URL query strings.
Notifications
If you allow notifications, a push token for your device, the time zone your device reports and the notifications we send you are stored. Besides reminders for research participants, Inqui sends:
- a gentle vocabulary review reminder — at most once a day, in the evening of your local time, and only when at least 10 of your words are waiting for review. It is on by default; switch it off in the app under Vocabulary → My words, in the review settings of the “To review today” card (“Gentle review reminder”);
- an inactivity reminder — at most one a day, when you practised in the last month but not in the last three days.
Nothing is sent during quiet hours (21:00–08:00 your local time), and participants in an active research study receive only the reminders their study describes. You can turn off all push notifications from Inqui at any time in your phone’s settings (the app shows the current state under Settings → Notifications).
Communications
What you send us by e-mail, a support message or the contact form on this website (name, e-mail address, role, organisation, message). The contact form does not store your IP address or browser details; the bot check described in Section 11 uses your IP address only transiently.
Research records
Only as described in Section 8 and in the information for the specific study.
You choose what you say in a conversation. Please avoid other people’s personal information and unnecessary sensitive details about yourself. A practice scenario — a doctor’s appointment, a job interview — works just as well with invented details.
3. AI features, voice and the providers we use
Conversation content is sent to AI providers — that is how the Service works. To generate replies, transcriptions, synthesised speech, feedback, error annotation, goal evaluation, CEFR estimates and translations, your conversation text, the relevant learning context (for example the activity, your level and your languages) and, for voice, your audio are sent to the AI providers listed below. Inqui is a service built on these providers, so using its conversation features means this transmission happens; it is part of the service you asked for and its legal basis is the contract (Article 6(1)(b) GDPR). There is no separate consent step for it. If you do not want your conversations processed this way, do not use the conversation features. We do not send your name, e-mail address or account details to the AI providers — only the content and context a reply needs (unless you write such details into the conversation yourself).
Voice. The app uses your microphone only when you start a voice activity and the operating system has granted permission. Your speech is transcribed to text by OpenAI (Whisper); we keep the transcript and its timing and confidence metadata, and — as described below — the recording itself. Hiding the transcript on screen does not stop it being produced or stored. Pronunciation of single words and example sentences uses your device’s own text-to-speech engine.
Misuse screening. The same AI that analyses your mistakes also checks each of your conversation messages for jailbreak attempts, requests for dangerous or illegal help, profanity, harassment and persistent off-topic misuse. A flag creates an incident record that we and, for institutional accounts, your institution’s administrators can review. A flag never leads to a sanction automatically; any decision about your account is taken by a person (see the Terms).
Voice recordings
We store recordings of your spoken turns. What they are used for and how long they are kept depends on how you use Inqui:
- Regular use of the app — on by default, you can switch it off. Recordings are stored to improve the Service and to train and improve our own models that detect speech errors (for example in pronunciation or grammar). You can switch this off at any time in the app under Settings → Privacy. Switching it off stops new recordings from being stored and deletes the recordings already kept for this purpose. Otherwise they are kept until you switch it off or delete your account.
- Research study participants. If you have joined a study and given your consent, the recordings of your spoken turns are always stored for the study’s research analysis (for example pauses and speaking rate) and kept for 5 years after the end of the study. Using them to train models as well needs your separate, optional consent in the study consent form, which you can withdraw at any time. Withdrawing from the study stops new recordings; the recordings made so far are deleted if you ask for it (the app asks when you withdraw) and at once if you delete your account. Details are in the study’s participant information and consent form (Section 8).
How recordings are protected. Each recording is encrypted (AES-256-GCM) before it is stored, and it is stored only on our main server in the EU (Germany). The regional servers in the USA and Singapore that speed up the connection store no recordings — they forward them to the EU. Recordings are never public and are not available to your teachers or your institution’s administrators; only the operator’s system administrators can access them. Deleting your account deletes all your recordings.
Training is ours, not the AI providers’. Training error-detection models on stored recordings is our own purpose as the operator of the Service, for which Inqui is the controller even if your institution gave you your account. It is not training by the AI providers: they process your audio and conversations only as our processors, to deliver the Service, and do not use them to train their own models.
Conversation memory
Inqui remembers a few things between your conversations — on by default, you can switch it off. After each conversation outside a research study, the AI provider (currently OpenAI, see the table below) receives your last messages from that conversation (up to 20, without the AI’s replies), how often each type of mistake came up in the feedback, the goals you worked on and the notes kept so far, and returns updated notes for that language: up to 5 interests, up to 5 things you find tricky and up to 8 topics you have already practised, each a short phrase. The AI is instructed never to note names, contact details, employer or school, age, health, religion, political opinions, sexual orientation, ethnic origin, finances or anything about other people, and any note that still looks like an e-mail address, web address, social-media handle or phone number is discarded before it is saved. In your later conversations outside a study, the notes are added to the AI’s instructions so it can come back to topics you enjoy and practise what you find difficult.
You can read the notes in the app under Settings → What Inqui remembers about me, delete them for one language (“Forget this language”) or all at once (“Forget everything”), and switch the memory off there; switching it off deletes the notes and no new ones are made. The memory is never created or used in research studies and is not part of any research export, it is not visible to your teachers or your institution, and it is deleted with your account.
Providers (processors) we use
| Provider | What it does | What it receives | Location and safeguard |
|---|---|---|---|
| OpenAI (OpenAI Ireland Ltd., Ireland; processing by OpenAI, L.L.C. / OpenAI OpCo, LLC, USA) — privacy | The default AI models: conversation replies, feedback and error annotation, misuse screening, goal evaluation, CEFR estimates, translation of course content, speech-to-text (Whisper), text-to-speech and real-time voice | Conversation text, learning context, audio of voice turns | USA — EU Standard Contractual Clauses (OpenAI is not certified under the Data Privacy Framework) |
| OpenRouter, Inc. (USA) — privacy | Access to alternative language models, only where an organisation or a feature is configured to use one | Conversation text, learning context | USA (and the model provider it routes to) — EU Standard Contractual Clauses |
| Perplexity AI, Inc. (USA) — privacy | Source and literature research in the dashboard’s research workspace, used by staff (teachers, administrators, researchers); never used for learner conversations | The query written by the staff member | USA — EU Standard Contractual Clauses |
| DeepL SE (Germany) — privacy | Machine translation of interface texts | Interface strings written by us — never your conversations | EU — no transfer |
| Google (Firebase: Google Ireland Ltd. / Google LLC) — privacy | Push notifications (Firebase Cloud Messaging) and crash reports (Crashlytics) | Device push token, notification text, random device code, device model, OS and app version, stack traces — no user ID | EU and USA — Data Privacy Framework (Google LLC is certified) and Standard Contractual Clauses |
| Cloudflare, Inc. (USA) — privacy | DNS, network proxy and attack protection for the website, dashboard and API, and the Turnstile bot check on the contact form | IP address and the encrypted traffic passing through its network, browser signals for the bot check | Global network incl. USA — Data Privacy Framework (Cloudflare is certified) and Standard Contractual Clauses |
| Contabo GmbH (Germany) — main servers — privacy | Hosting of our main servers and database, and of the nightly backups | All data stored in the Service (encrypted in transit), including voice recordings, which are encrypted before they are stored | Germany (EU) — no transfer |
| Contabo GmbH (Germany) — regional edge servers in the USA and Singapore — privacy | Regional servers without a database for users near those regions: they handle requests, call the AI providers and keep the state of an ongoing conversation in memory only (expires within an hour; never written to disk); they store no voice recordings and forward them to the main servers in the EU | Requests and conversation data of users routed there, transiently | USA and Singapore — EU Standard Contractual Clauses offered in Contabo’s data processing agreement for non-EU locations (Singapore has no adequacy decision) |
| Seznam.cz, a.s. (Czech Republic) — privacy | E-mail: one-time codes, password resets, invitations, contact-form confirmations and our mailboxes | E-mail address and message content | EU — no transfer |
The mobile app’s fonts are bundled in the app, so displaying text does not contact any font provider. Some learning fonts (e.g. textbook or handwriting styles) are downloaded on demand from our own servers (inqui.ai, delivered via Cloudflare); no request is made to Google or other font services. When you download the app, Apple (App Store) or Google (Google Play) process data under their own privacy policies as independent controllers.
Automated feedback and Article 22 GDPR
Corrections, error annotations, goal evaluations and estimated CEFR levels are produced automatically and can be wrong. They are learning aids: within Inqui they only steer which activities are suggested and how difficult they are. They do not produce grades or any other decision with legal or similarly significant effect on you, so they are not automated decision-making within the meaning of Article 22 GDPR. Our Terms prohibit institutions from using them for grading, admission or certification. If an institution nevertheless uses them in assessment, that is its decision and its notice must tell you so.
4. Why we process your data, and on what legal basis
Where your institution is the controller (Section 1), its own documented legal basis applies to course delivery. For the processing Inqui decides on, the bases are:
| Purpose | Legal basis |
|---|---|
| Providing the Service you asked for: your account, courses, conversations, sending conversation content to the AI providers in Section 3, feedback, progress, notifications you enabled, and necessary transactional e-mail (one-time codes, password resets, invitations) | Performance of a contract, or steps taken at your request before entering into one — Art. 6(1)(b) GDPR |
| Security, misuse screening, abuse prevention, rate limiting, fault diagnosis, crash reports, and our own usage and performance statistics to keep the Service working and improve it | Our legitimate interest in a secure, reliable and improving service — Art. 6(1)(f) GDPR. You can object (Section 9). |
| Storing recordings of your spoken turns to improve the Service and to train our own models that detect speech errors (regular use of the app, Section 3) | Our legitimate interest in improving the Service and its error detection — Art. 6(1)(f) GDPR, with your right to object: the switch in Settings → Privacy. Once you switch it off, no new recordings are stored and those kept for this purpose are deleted. |
| Conversation memory: keeping short notes on your interests, recurring difficulties and practised topics between conversations outside research studies, so later conversations can build on them (Section 3) | Our legitimate interest in offering continuous, personalised practice — Art. 6(1)(f) GDPR, with your right to object: the switch under Settings → What Inqui remembers about me. Switching it off deletes the notes and no new ones are made. |
| Your optional year of birth: an age-appropriate experience and aggregate statistics about our users | Our legitimate interest — Art. 6(1)(f) GDPR. Giving it is entirely voluntary; you can object at any time by clearing it in your profile, after which it is no longer used. |
| Answering the contact form, support messages and privacy requests | Steps at your request before a contract, our legitimate interest in answering you, or a legal obligation, depending on what you ask — Art. 6(1)(b), (f) or (c) GDPR |
| Keeping evidence of accepted terms and consents; records we are required to keep; lawful requests from authorities; reporting under the Digital Services Act | Legal obligation — Art. 6(1)(c) GDPR, and our legitimate interest in being able to prove compliance — Art. 6(1)(f) |
| Taking part in a research study, including storing your voice recordings for the research analysis and — only with your separate, optional consent — using them for model training | Your consent — Art. 6(1)(a), and Art. 9(2)(a) where special-category data is involved (Section 8) |
We do not run advertising, we do not sell personal data, and the apps contain no advertising or data-broker SDKs. If you do not provide what an account or a conversation feature needs, that part of the Service cannot work. Research data is always optional.
5. Who can access your information
- The operator and anyone acting on his instructions, limited to what their role requires.
- Your institution, if you have an institutional account. Authorised teachers and administrators can see your individual learning records — progress, session activity, mistakes, misuse incidents and, depending on their permissions, your conversations. These are personal records about you, not anonymous statistics. Ask your institution how it uses them. Voice recordings are not available to your institution.
- The providers in Section 3, each as a processor for the purpose shown, bound by a data processing agreement.
- The research team of a study you joined, under the separate arrangements in Section 8. Research access is not given to a teacher or administrator merely because they use Inqui.
- Authorities or courts, where disclosure is required by law or necessary to establish, exercise or defend legal claims.
6. Where your data is processed, and international transfers
Our database, main application servers and backups are in the European Union, hosted by Contabo GmbH in Germany; your account and learning data are stored only there. To keep spoken conversation responsive, users far from Europe are routed through regional edge servers in the United States and Singapore, also rented from Contabo GmbH: the app picks the fastest region automatically, and you can see and change it under Settings → Server region. An edge server has no database and keeps none of your data on disk, apart from technical server logs, which are rotated (Section 7). It handles your requests, calls the AI providers directly and keeps working data only in memory — mainly the state of an ongoing conversation, which expires within an hour. It reads from and writes to the database in the EU over an encrypted tunnel. Recordings of your spoken turns are forwarded to the EU and stored only there (Section 3).
Transfers outside the European Economic Area happen to the AI providers, to Cloudflare and Google, and — when you are served by an edge server — to the United States or Singapore. Even though only transient data is processed there, and by an EU hosting company, we treat this as a transfer. Singapore has no EU adequacy decision, and not every US provider is certified under the EU–US Data Privacy Framework, so each transfer relies on the safeguard shown in the table in Section 3: the Data Privacy Framework (Commission adequacy decision of 10 July 2023) where the recipient is certified, otherwise the EU Standard Contractual Clauses (Commission Decision (EU) 2021/914) — for the edge servers, those offered in Contabo’s data processing agreement for its non-EU locations — with supplementary measures such as encryption in transit, no data kept on the edge servers’ disks, short expiry times and not sending account identifiers to the AI providers. Write to [email protected] for a copy of the relevant safeguards.
Security
Traffic is encrypted in transit with TLS; traffic between our servers in different regions runs over an encrypted WireGuard tunnel. Passwords are stored only as a one-way hash (argon2). Access is restricted by role, API credentials are encrypted at rest, stored voice recordings are encrypted (AES-256-GCM) before they are stored and are accessible only to the operator’s system administrators, and authentication and other sensitive endpoints are rate limited. No system is perfectly secure and we cannot promise absolute security; if a breach affects you, we will tell you as the GDPR requires.
7. How long we keep your data
As a rule, your account and learning data — including all your conversations — are kept for as long as your account exists and are deleted when the account is deleted. You can delete your account at any time in the app (Profile → Settings → Delete account), via the account deletion page, or by writing to [email protected]. You can also ask us to delete specific conversations or other specific data without deleting your account.
| Record | How long |
|---|---|
| Account, profile (including the optional year of birth), conversations and turns, feedback and error markers, goal results, CEFR estimates, questionnaires, saved vocabulary and its review schedule, points and badges, enrolments, consent and terms-acceptance records, misuse incidents, notifications and push tokens, usage events | While your account exists; deleted when you delete it or ask us to |
| Conversation memory (notes on interests, recurring difficulties and practised topics, per language) | Until you delete the notes or switch the memory off in Settings → What Inqui remembers about me, or delete your account |
| Technical metadata of AI calls (model, tokens, latency) | Kept for statistics; the link to your account is removed when the account is deleted, the rest contains no content |
| Conversation state in server memory (in the EU or on an edge server) | 1 hour; on edge servers it is never written to disk |
| Result of a finished session, kept in memory so a repeated request gets the same answer | 24 hours |
| Voice recording pieces waiting to be transcribed | At most 10 minutes, then discarded |
| Recordings of your spoken turns — regular use (improving the Service, training error-detection models) | Until you switch storing off in Settings → Privacy (which deletes them) or delete your account |
| Recordings of your spoken turns — research study participants | 5 years after the end of the study; deleted earlier on request (for example when you withdraw from the study) or when you delete your account. Withdrawing only the optional training consent ends their use for training. |
| One-time registration codes / password-reset links | 5 minutes / 1 hour |
| IP-based rate-limit counters | About 15 minutes |
| Mobile diagnostic logs | 90 days; 14 days if not linked to an account; deleted at once when you delete your account |
| Crash reports (Firebase Crashlytics) | Per Google’s Crashlytics retention, currently 90 days |
| Contact-form submissions | 12 months, then deleted automatically |
| E-mails you send us | As long as needed to handle your request and show that we did, then deleted |
| Server logs | Rotated by size (at most 50 MB per service) and discarded whenever the service is updated — in practice days to a few weeks |
| Database audit trail (sign-ins with IP address, record of changes) | Sign-in and change records 180 days; copies of changed records 90 days. Your conversations, answers and other learning records are not copied into the audit trail; changes to your account and memberships are. |
| Database backups | Nightly backups on our EU server, each deleted after 14 days |
| Research records | Study-specific periods disclosed before you enrol; deleted with your account, or on request when or after you withdraw (Section 8) |
When your account is deleted, live data is erased immediately and permanently, including any research records — no copy is kept for research. Deleted data can remain in database backups until they rotate out, at most about 15 days later; we never restore a backup to bring deleted data back. Replacing your name with a participant code is pseudonymisation, not anonymisation — coded data is still personal data.
8. Research studies
Inqui supports research into AI-assisted language learning — conversation practice, learning outcomes, motivation and confidence in speaking another language. This includes doctoral research by Michal Macinka at the University of Hradec Králové, Faculty of Science, Department of Applied Informatics, Rokitanského 62, 500 03 Hradec Králové, Czech Republic, supported by Specific Research grant 2110/2025. The current study compares styles of AI feedback and their effect on speaking accuracy and fluency.
Installing or using Inqui does not enrol you in anything. Before any study data is collected you receive separate participant information — purpose, duration, what you would do, eligibility, risks, benefits, how your data is used and how to withdraw — and you give informed consent in the app. That consent is recorded against a specific version of the document; if the text changes materially you are asked again.
What a study may collect
Depending on the study: questionnaire responses about language-learning anxiety and motivation (for example AI-adapted FLCAS and IMI), short in-app check-in questions, background information such as age, gender, native languages and prior study, assessment and completion data, conversation transcripts, AI feedback and error annotations, speech-recognition timing and confidence metadata, and recordings of your spoken turns. The participant information states exactly which of these apply. In a study that uses speaking, the recordings of your spoken turns are stored — encrypted, in the EU, for 5 years after the end of the study — for the research analysis; using them for model training needs your separate, optional consent (Section 3).
Assignment
A study may assign you a feedback mode, an input mode or a sequence of activities. While it runs you may therefore be unable to switch between Coach and Partner mode or between typing and speaking. This is explained before you join.
Voluntariness
Taking part is voluntary and refusing has no effect on your grades, your relationship with your teachers, the teaching support you get, or any access you already have. Where a course offers a bonus for completing a session quota, not taking part does not reduce your ordinary grade — it only means you do not earn the bonus, and an equivalent alternative activity is available.
Pseudonymisation and publication
Research records are held under a participant code. The key linking that code to your identity is kept separately and is accessible only to the principal researcher. Exported data uses pseudonymous IDs and is scrubbed of contact details in free text. Published results report group-level statistics or material that does not identify anyone; an identifiable quotation would need your separate, specific agreement.
Leaving a study
You can withdraw at any time, without giving a reason, in the app or by writing to the study contact. No new research data is collected after that. Withdrawing does not delete your research records by itself: the app asks whether you also want the records collected so far (including recordings) deleted, and if you do, the researcher deletes them; you can also ask for this later by e-mail. Deleting your account deletes them immediately. Withdrawing consent does not make processing carried out beforehand unlawful. Data that has already been irreversibly anonymised cannot be traced back to you and therefore cannot be removed individually.
9. Your rights
Under the GDPR you may ask us to:
- Access — give you a copy of the personal data we hold about you
- Rectify — correct data that is wrong or incomplete
- Erase — delete your personal data, or specific parts of it such as individual conversations
- Restrict — pause processing while a dispute is resolved
- Port — hand over the data you provided in a machine-readable format
- Object — to processing based on our legitimate interests (Section 4)
- Withdraw consent — for anything based on your consent, without affecting what was lawful beforehand
Write to [email protected]. We answer within one month; if a request is complex enough to need the extension the GDPR allows, we will tell you within that month and explain why. We may ask for proportionate information to confirm it is really you. For records your institution controls you can also go to the institution — and if you are not sure who is responsible, ask us and we will tell you.
Deleting your account
In the app: Profile → Settings → Delete account. Deletion is immediate and permanent: your conversations and turns, voice recordings, conversation memory, feedback and error markers, goal results, questionnaire answers and scores, saved vocabulary, review schedule and word exposure, points, badges and streaks, CEFR estimates, course and study enrolments, consent records, push tokens, notifications, usage events, diagnostic logs and the account itself are all erased. The shared demo account used for app-store review cannot be deleted. Step-by-step instructions, including how to ask by e-mail without the app, are on the account deletion page.
Complaints
You may complain to the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, Pplk. Sochora 27, 170 00 Praha 7, uoou.gov.cz), or to the supervisory authority where you live, work, or believe the problem occurred.
10. Younger users
In the Czech Republic a person must be at least 15 to consent on their own to an information society service (Article 8 GDPR and Section 7 of Act No. 110/2019 Coll.); other countries set the threshold between 13 and 16. You may use Inqui on your own from 15; younger users may use it only with the consent of a parent or guardian or through a school or institution. Where an institution enrols minors, it is responsible for the legal basis and any parental authorisation its law requires before accounts are created. We do not knowingly let younger children create accounts on their own; if you believe this has happened, write to us and we will delete the account.
A study involving minors needs age-appropriate participant information, permission from a parent or guardian, the young person’s own assent and whatever institutional safeguards apply.
12. Changes to this policy
We update this policy when our practices change and show the date of the last update at the top. We tell you about material changes in the app or by e-mail before they take effect. An updated policy does not extend a research consent you gave earlier and does not create permission for a new optional purpose — those are always asked for separately.
13. Contact
Questions about this policy, or a request about your data: [email protected]
Michal Macinka, IČO 11824492, Lhotka 198, 560 02 Česká Třebová, Czech Republic
For a specific research study, use the contact given in that study’s participant information.
This policy is available in English and Czech.