Privacy policy

Version privacy-policy-v4-2026-10, effective [[EFFECTIVE_DATE]]

Draft, not yet reviewed by counsel.

This policy explains what HealthPod Scribe does with your data, in plain words. It is written to satisfy the GDPR (we are a German company) and the LGPD (you are likely in Brazil) at the same time, so where the two differ we describe the stricter one.

1. Controller and contact

Controller[[LEGAL_ENTITY]], [[REGISTERED_ADDRESS]]
Data protection officer / encarregado[[DPO_CONTACT]]
Privacy contact[[PRIVACY_EMAIL]]
Supportscribe@dehaze.de

2. The short version

This is what we do today. If it changes, this policy changes with it, and where the change affects what you agreed to, we ask you to agree again (section 9).

3. What we process, why, and on what legal basis

3.1 Account and sign-in

DataWhyLegal basis
Email addressSign-in, security notices, deletion confirmationsGDPR Art. 6(1)(b) contract · LGPD Art. 7(V)
One-time sign-in codes (stored hashed, valid 10 minutes), with the app language you signed in fromPasswordless sign-in, and sending the code email in your languageGDPR Art. 6(1)(b) · LGPD Art. 7(V)
Session tokens (refresh tokens stored hashed, 90 days, rotating)Keeping you signed inGDPR Art. 6(1)(b) · LGPD Art. 7(V)
Content language, reading level, summary styleShowing generated text in your language, at the level and in the style you choose. The language the app itself is shown in stays on your deviceGDPR Art. 6(1)(b) · LGPD Art. 7(V)
Service region, set when your account is createdKeeping your data in the storage region your account belongs toGDPR Art. 6(1)(b) · LGPD Art. 7(V)
Consent history, for your account and per person, your own record included: for each consent its kind, granted or withdrawn, exact text version, a fingerprint of the exact wording shown, language, timestampProving that consent was given or withdrawn, as the law requiresGDPR Art. 6(1)(c), Art. 7(1) · LGPD Art. 8 §2
Account settings history: for each setting you change (content language, reading level, summary style, and each optional feature you turn on or off for your account): the new value and when you changed it. You can read this history in the app under Account. The AI-training switch is set per person, your own record included, and each change to it is kept in that person's historyShowing you what applied to your account at any time, and letting us answer "what was on when this was generated"GDPR Art. 6(1)(b) · LGPD Art. 7(V)

3.2 Your visits — health data

This is the core of the app, and all of it is special-category health data (GDPR Art. 9, LGPD Art. 11). We process it only on explicit consent (GDPR Art. 9(2)(a), LGPD Art. 11(I)): for your own visits, the consent you give during sign-up; for a person whose records you keep, the consent you give for them when you add them (section 3.11). Either can be withdrawn at any time.

DataWhere it comes from
Audio recordingsYour microphone, only while a recording is running
The moment you confirmed your doctor agreed, plus the version of the consent text shownThe Consent Gate, once per recording
Which person a visit and its recordings belong to, and that you made the recordingYou: a visit is yours unless you choose another person whose records you keep for it, or move it to them
Pause markers within a recordingYour pause/resume actions
Transcripts, with time-aligned segments and — when the engine provides it — speaker labelsAutomatic speech recognition on your audio
Your transcript corrections, with full revision history and who wrote each version (you or the engine)Your edits
Summaries, extracted medical terms (medications, dosages, symptoms, conditions, procedures, dates, doctors, institutions, follow-ups), to-dos and their due dates, suggested questionsAI processing of the transcript
Your questions in Ask and the answers, with references to transcript passagesYour use of the Ask feature
Your visit notes: typed note blocks (thoughts, questions, to-dos, headings) with full revision history and who wrote each version — including notes the AI writes during a recording (live notes, if you switch them on) and afterwards, verdicts on whether your prepared questions were answered, and AI-proposed notes, whether you confirmed or dismissed themYou, and AI processing of your recording; every AI-written note is labelled with its author
Visit details: date and time, appointment type, institution, doctor's name, your prep notesYou, and — where the transcript makes them clear — automatic pre-filling that your own edits override
Documents you attach (photos, PDFs)Your camera, photo library, or file picker
Visit location, only if you switch it on (off by default)Your device, as a recording starts (the fix can take a few seconds to arrive), not in the background
Technical processing data: durations, file sizes, processing state, error codes, per-call AI usage units, the app version that made the recordingThe processing pipeline

Recording length is capped at 120 minutes, and processing at 120 audio-minutes per day. Over-cap recordings are kept and processed later, not discarded.

3.3 Other people in your recordings

A recording contains your doctor's voice, name, and what they said, and sometimes other people present. That is their personal data, and we process it as part of providing the service to you. When you record the visit of a person whose records you keep, the recording is about them and is their health data, processed on the consent you gave for them (section 3.11); your own voice in it is part of that record.

3.4 Usage statistics — only if you allow it

Off by default. If you switch it on, the app and our servers send events only: which screen and which feature you used, and when, not the content of your recordings. The events say which screen or feature was used and when, whether an action succeeded or failed, which optional features are on, and, for an action about a person, only whether they are a person under 18 in your care or an adult who asked you; not the content of a recording, transcript, summary or note.

We also record operational measurements that contain no personal content and no user identifier — processing durations, error codes, queue depths, cost per stage — to keep the service running.

3.5 AI training — only if you allow it

Off by default, set for each person separately (your own record is one of them), and revocable at any time in the app. If a switch is on, then after a visit of that person is ready, the transcript text and the text of the visit notes (including notes the AI wrote) go through de-identification and only the redacted result is added to a training dataset kept in a store of its own, segregated from your visit data, and used to improve dehaze's AI models.

3.6 Notifications

If you allow notifications, we store a push token per device and send you a message when a visit finishes processing or fails, before a planned visit, and for to-dos that have a date. Message text is deliberately neutral ("You have an outstanding step from your visit") because lock screens are semi-public: it names neither what was said nor the person a visit belongs to. Legal basis: GDPR Art. 6(1)(a) consent (the OS permission) · LGPD Art. 7(I).

3.7 Visit location — only if you allow it

Off unless you turn it on in the app. While it is on, the app saves the coordinates of where you are as a recording starts (the fix can take a few seconds to arrive), attached to that visit, together with the time they were captured. Nothing between recordings: the app does not follow you around, and it does not ask for background location. The switch is yours and applies to every recording you start; when you record the visit of a person whose records you keep, the place is saved with their visit.

We treat this as health data rather than ordinary metadata, because the address of a clinic can reveal what you are being treated for even when nothing else does: an oncology practice, a psychiatric clinic. So it gets the same treatment as your recordings — explicit consent, off by default, deletable.

Legal basis: your consent (GDPR Art. 9(2)(a); LGPD Art. 11, I). You can withdraw it at any time.

Showing it on a map. When a visit's map is drawn, those coordinates go to the map service your phone uses: Apple Maps on iPhone, Google Maps on Android. Opening a location in a separate maps app is your own action, and hands the coordinates to whichever app you choose.

Removing it. You can remove the location from any visit without deleting the visit. Turning the switch off stops new captures immediately; it does not delete locations already saved, because a saved location is yours to keep or delete. You remove those yourself, one visit at a time, or by deleting the visit they belong to.

3.8 Device permissions

Microphone (recording), notifications (see above), camera and photo library (attaching documents), and location (only if you enable visit location). Each is requested at the moment it is first needed, not at startup, and each can be reviewed and revoked in the app or in your device settings.

3.9 Crash reports

If the app crashes, a crash report is sent to us through a crash-reporting service (named in the subprocessor list) so we can find and fix the fault. A crash report contains technical information about the crash: the stack trace, your device model, operating system version and app version. It contains no recording, no transcript, no summary, no email address and no user identifier: we cannot look up who a crash report belongs to, and we do not combine crash reports with the usage statistics above. Crash reports are kept for 90 days and then deleted; that period is set by the crash-reporting service, not by us. Legal basis: GDPR Art. 6(1)(f) legitimate interest in running a reliable service · LGPD Art. 7(IX). Our servers report errors the same way, from logs that do not contain health content.

3.10 Protecting sign-in and the service

To stop abuse, such as someone guessing sign-in codes or flooding our servers with requests, we count recent requests in short-lived counters. Depending on the request, a counter is keyed by the email address entered, by your account, or by your device's IP address. The counters contain nothing else, and each one ages out within an hour. Legal basis: GDPR Art. 6(1)(f) legitimate interest in keeping the service secure · LGPD Art. 7(IX).

3.11 People whose visit records you keep

This section applies if you keep the visit records of another person in your account: a person under 18 in your care, if you are their parent or legal guardian, or an adult who asked you to manage their visits. Each such person has a record of their own, separate from yours, and everything section 3.2 lists can be part of it.

DataWhyLegal basis
The name you give the person, such as a first name or "Dad"Telling the records apart in the appThe consent you give for them (GDPR Art. 6(1)(a) and, where the record is health data, Art. 9(2)(a) · LGPD Art. 11(I); for a person under 18, Art. 14 §1); for the name you choose, also the contract with you (GDPR Art. 6(1)(b) · LGPD Art. 7(V))
How you are related to them, if you choose to say, from a short list the app offersShown on the person's pageThe consent you give for them (GDPR Art. 6(1)(a) and, where the record is health data, Art. 9(2)(a) · LGPD Art. 11(I); for a person under 18, Art. 14 §1)
Your consent for them: which of the two statements you chose, its exact text version, a fingerprint of the wording shown, the language, when you confirmed it and when we received itProving the consent given for themGDPR Art. 6(1)(c), Art. 7(1) · LGPD Art. 8 §2
The AI-training switch for them, and each change to itUsing their de-identified text only if you switched it on (section 3.5)GDPR Art. 9(2)(a) · LGPD Art. 11(I)
Their visits, as section 3.2 listsThe service, for themExplicit consent given for them: GDPR Art. 9(2)(a) · LGPD Art. 11(I), and for a person under 18 LGPD Art. 14 §1

We do not ask for the person's date of birth, age, email address or any other detail about them. The person has no account: their record is part of yours, and you can rename them, change how you are related, or remove them, in the app or by writing to us. Removing a person deletes their record (section 5). If the adult cannot decide about their own health matters, write to us before adding them.

Their recordings take the same path as yours, including the steps outside Brazil that section 4 describes; the consent you give for them names those transfers.

The name and the relation appear on your account's screens and in what you share: a summary you share or a PDF you export of their visit carries their name. They are not sent to the AI services that write summaries and answers, not used in notification text, and not part of usage statistics or the training set.

4. Where your data is, and who touches it

At rest, your health data is stored in Brazil: the database, the audio and document storage, and the servers.

The exceptions you should know about:

  1. Speech-to-text runs in the European Union. Audio is sent to our speech-to-text provider's servers in the European Union for transcription and the text comes back; the provider is named in the subprocessor list. This is an international transfer of health data out of Brazil, and it is why the health-data consent names it (LGPD Art. 33(VIII), specific and highlighted consent). Brazil's data protection authority (ANPD) recognises the European Union as offering adequate protection (LGPD Art. 33(I); the ANPD's page), and under the provider's data-processing terms for our account the audio is processed only to deliver the transcription, not kept for its own purposes.
  2. AI processing runs on our AI provider's global service. Today that provider is Google Cloud; every provider is listed on our subprocessor page. That covers the summary, the extracted medical terms, to-dos, suggested questions, the answers in Ask, the notes Scribe writes during and after a recording, and, if you switched on AI training, the automatic process that removes identifying details. What is sent: the transcript and the text derived from it, your notes and questions, and during a recording the small slices of audio Scribe uses to write notes as you record. The global service gives no guarantee of the country a request is processed in: the provider processes each request in one of its locations worldwide (the provider's page), which can be outside Brazil, and returns the result, which we store in Brazil. The provider can keep a temporary copy of a request to answer faster, in the location that served it, and a record of a request to check that its service is not misused, each for a limited time; the provider states the periods on its own page (the provider's page). Under the data-processing terms our account runs under, neither is used to train its models. This is an international transfer of health data out of Brazil. The health-data consent names it in highlighted form (LGPD Art. 33(VIII)); our data-processing agreement with the provider includes the standard contractual clauses approved by the ANPD for transfers the LGPD restricts (LGPD Art. 33(II)(b)) and, for the GDPR, the standard contractual clauses adopted by the European Commission (GDPR Art. 46(2)(c)); the provider's locations include countries with and without an adequacy decision of the European Commission. You can read those clauses in the provider's published data-processing terms or ask us for a copy at [[PRIVACY_EMAIL]]. [[COUNSEL: confirm the Art. 33 mechanism for the global endpoint and whether the consent stays a basis or becomes information only — Q-48]]
  3. Notifications are delivered through the push service of your phone's platform (Google's on Android, Apple's on iPhone). The delivered message contains no health content beyond the neutral wording above.
  4. Crash reports go from the app to our crash-reporting service, which stores them on its own infrastructure outside Brazil (subprocessor list). They are content-free, as described in section 3.9.

Because we are a German company storing your data in Brazil, that storage is a transfer out of the European Union under the GDPR. It rests today on [[EU_BR_TRANSFER_BASIS]], and, independently, on the standard contractual clauses in our cloud provider's data-processing terms.

The full list of companies that process data on our behalf, what each does, and where, is in the subprocessor list. Summary: today one cloud provider, Google Cloud (hosting, storage, speech-to-text, the AI service, usage-event storage, crash reports, notifications), and one email provider, Mailjet (the emails that carry your sign-in codes); the subprocessor list says where each processes and links each provider's published terms. The app stores are not our processors.

Two map services sit outside that arrangement, and only if you turn visit location on: when a visit's map is drawn, the coordinates go to Apple Maps on iPhone or Google Maps on Android under those companies' own terms for their platform services, the same way a notification passes through Apple's or Google's delivery service. They receive the coordinates being shown, nothing else.

Under the data-processing terms our account runs under, our cloud provider does not use your data to train its models, and our email provider processes your email address only to deliver our email.

5. How long we keep things

DataKept
Recordings, transcripts, summaries, terms, to-dos, Ask history, documents, visit detailsUntil you delete them — we do not expire them for you
A person whose records you keep: their name, how you are related to them, your consent for them and everything in their recordUntil you remove the person or delete your account
Account data and consent historyUntil you delete your account (see below for what a deletion leaves behind)
Sign-in codes10 minutes, or until used
Session tokens90 days, rotating; revoked when you sign out or delete your account
BackupsRolling 30 days — deleted data disappears from backups within 30 days
Server logs30 days; in the environments that serve the published apps they do not contain recordings, transcripts, summaries or extracted terms. Our internal test environment, used only by our own testers with a separately labelled build, additionally logs the content detail of a failed processing step for fault investigation
Usage events (if enabled)24 months, linked only to a random id
Activity log — a content-free record of what happened in your account and who did it, you or Scribe ("you deleted this visit", "Scribe finished processing this recording"), not the content it touchedUntil you delete your account
Crash reports90 days
Training set contribution (if enabled)Until you withdraw or delete — removed within 30 days
Support emails you send us24 months after your request is closed

What an account deletion leaves behind. Deleting your account erases your data and the records of every person you keep records for. Three content-free records remain: (1) proof that the deletion happened, so we can show we honoured your request; (2) your consent history, including the consents and AI-training choices you made for the people whose records you kept (for each consent only its kind, whether it was granted or withdrawn, the language, the timestamp, and the text version with a fingerprint of the exact wording, which a grant always carries and a withdrawal carries only where a text was shown), kept so we can prove what was agreed if a legal claim is ever raised. It is stored under a cryptographic code derived from your email address with a secret key we hold; without that key it identifies nobody, and we can match it only against an email address its owner shows us; and (3) if you sent us a data request by email, the fact and dates of that request, kept the same way, so we can show we answered in time. None of the three contains any recording, transcript, name or email address. For up to an hour after a deletion, the short-lived security counters described in section 3.10 can also still exist before they age out; they then disappear on their own.

Removing a person leaves two of those kinds of record for that person's part: proof that the removal happened, and the consents and AI-training choices you made for them, stored the same way under the code derived from your email address. Neither contains the person's name.

6. Your rights

Under the GDPR (Art. 15–21) and LGPD (Art. 18) you may:

We do not make automated decisions with legal or similarly significant effects about you. The AI in the app produces text for you to read; it decides nothing about you.

7. Security

TLS in transit, encryption at rest, customer-managed encryption keys on the audio and document storage, and encrypted storage on your device. Every request that reads or changes a visit record is checked, in one access-control module, against the account that keeps the record of the person it belongs to. In the environments that serve the published apps, health content is excluded from logs by an allowlist, so transcripts do not reach our log lines; our internal test environment logs more, as §5 says. Signed download links are short-lived (15 minutes).

No system is perfectly secure. If a breach affects you, we notify you and the authorities as required (GDPR Art. 33/34, LGPD Art. 48).

8. Children

Accounts are for adults: you must be 18 or older to have one, and if we learn that an account belongs to someone under 18, we delete it. Where a parent or legal guardian keeps the visit records of a person under 18 in their care in their own account (section 3.11), that person has no account of their own; we process their health data on the consent the parent or guardian gives for them, in the person's best interest as the law requires, and we do not ask for their date of birth or age. The parent or guardian exercises the person's rights for them, as section 6 describes. If you believe someone under 18 holds an account, contact [[PRIVACY_EMAIL]].

9. Changes to this policy

We update this policy when the app changes. The version in effect is the one published at https://scribe.dehaze.de/inapp/privacy, and the top of the page names its version. Where a change affects something you agreed to, the app asks you to agree again before you continue.