Privacy
This translation is for your convenience. The German version is the legally binding one.
In short: the website and the web app area work for you without an account (accounts exist only for speech therapists in the practice portal), without cookies and without trackers, and what you type there stays in your browser. Data only reaches our server if a speech-language therapist works with you through the professionals portal and you explicitly connect your app, and never more than you share. Every data flow is listed below with its purpose and legal basis.
Who is responsible?
The controller under the GDPR is Philipp Winkler, Burghof 1
24939 Flensburg, email: hallo@sagbar.app. For data protection questions, write to this address.
For data that a practice exchanges with its patients through the professionals portal, the practice is the controller. We then process it only on the practice's behalf (see the section Connecting a practice and the app).
Overview
This overview names every data flow. The sections below explain them in more detail.
- Visiting the website: connection data in server logs (Art. 6(1)(f) GDPR).
- Web app area (diary, courage ladder, thought check, settings): only local in your browser, nothing goes to us.
- Professionals portal: account of the professional (Art. 6(1)(b) and (f) GDPR).
- Connecting the app to a practice: health-related data, only with your explicit consent per area (Art. 9(2)(a) and Art. 6(1)(a) GDPR).
- Premium and payments: through the App Store, Google Play, RevenueCat and Stripe, payment data lives only there (Art. 6(1)(b) GDPR).
- Access log: security and proof (Art. 6(1)(f) GDPR).
- Error reports to our own GlitchTip: without personal or health data (Art. 6(1)(f) GDPR).
- Anonymous question about the AI conversation partner: only a counter, no personal data.
- Usage metrics of the apps (only if you switch them on): pseudonymous weekly counters, with explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR).
Hosting and recipients
The website, the portal and the database are run by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Deutschland. The servers are located in Rechenzentrum Nürnberg, Deutschland. Where required, a data processing agreement under Art. 28 GDPR is in place with the provider.
There are no other recipients: we do not pass data to advertising or analytics services and we do not sell data. The domain is resolved at Cloudflare through DNS only (no proxy): page views, content and accounts do not pass through Cloudflare, whose name servers only see the DNS request for the domain name. We ourselves do not transfer personal data to countries outside the EU.
Server logs
When you open a page, the server processes technically necessary connection data: IP address, date and time, requested address, status code, amount of data transferred and the browser identifier (user agent). This is needed to deliver the page, find errors and fend off abuse.
The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation). Logs are rotated by size: their volume is capped at 30 MB (3 x 10 MB), older entries are overwritten. There is no fixed period in days. They are not combined with other data and not used for statistics or advertising.
Cookies and browser storage
The public website and the web app area set no cookies. If you use the diary, courage ladder or thought check, your browser stores these entries locally in its database (IndexedDB) on your device, and settings and the note that you already answered the AI conversation partner question in local storage (localStorage). Installing it as an app also puts pages for offline use in the browser cache. None of this is sent to Sagbar. You can export entries or remove them under "Delete all data".
This storage only serves the service you asked for and is technically necessary (section 25(2) no. 2 TDDDG), so you do not need to give consent and there is no cookie banner.
Only the professionals portal sets cookies, and only for signing in: a short-lived cookie during the two-step sign-in (10 minutes) and afterwards an encrypted sign-in cookie (HttpOnly, only over an encrypted connection, 7 days at most, invalid after 12 hours without activity). Both are technically necessary, there are no advertising or analytics cookies. The chosen language is part of the address path (for example /de or /en) and is not stored anywhere.
Web app area and microphone
The exercises and the area under /app run in your browser. What you enter or select there, including ratings, diary and situations, stays on your device and is neither stored nor sent to us. The server only delivers the pages and the exercise texts.
For exercises with delayed auditory feedback (DAF) your browser asks for the microphone. The microphone is only used for that exercise, the sound is not recorded and not sent. Voice recordings never leave your device. If you decline the microphone, all other exercises keep working.
As long as you only practise locally, Sagbar processes no health data about you, because it never reaches us.
Professionals portal (account)
Professionals who use the portal create an account. For that we process: email address, password (as a hash only), role in the practice, language, name and country of the practice, the secret for two-factor sign-in (encrypted) and recovery codes (as hashes only). In addition there are the sign-in sessions with time and browser identifier (user agent), so that you can see and end them, and counters for failed attempts.
The purpose is to provide the portal and secure sign-in (two-factor is mandatory). The legal basis is Art. 6(1)(b) GDPR (usage contract) and (f) (security). We keep the data as long as the account exists. On request we delete the account, write to hallo@sagbar.app. Sessions end after 7 days at the latest. The portal currently sends no emails.
Connecting a practice and the app (health-related data)
This section only applies if you connect your Sagbar app (phone or watch) to a practice. Without a connection none of this data goes to us. The connection starts with an invitation code from the practice and you confirm it in the app. The practice gives you a nickname, we do not need your real name.
This is data about your health under Art. 9 GDPR. We only process it with your explicit consent under Art. 9(2)(a) and Art. 6(1)(a) GDPR. You give it separately per area: check-ins, situation logs and done-status of exercises. By default nothing is shared. Without consent for an area, the server rejects uploads of that area.
What is stored: the exercise list the practice made for you (title, note, schedule), for each area you share your entries (check-ins with rating, tension, avoidance, technique used and note; situation logs with situation, fear, avoidance and note; done-status), invitation codes and device tokens (as hashes only), device, platform and app version, and your consents with time, text version and language. Free text, nickname and notes are additionally encrypted in the database. Voice recordings are not transferred.
The practice that supports you is the controller of this data. We are its processor under Art. 28 GDPR (template of the agreement: AVV page). We process it only to provide synchronisation and to show the practice its data in the portal. The professional sees only what you shared. We do not use it for our own purposes.
At any time in the app you can: withdraw a consent (the area is blocked at once, on request we delete the existing data of the area immediately, otherwise after 30 days), export all your data, end the connection and delete all data. The practice can also end the connection.
Retention: deleted entries also disappear from synchronisation after 30 days. We delete ended connections after 90 days (you can export until then). Connections unused for 12 months are ended and deleted 90 days later. Invitations that were never redeemed are deleted after 30 days.
Children and young people: the connection is set up through the practice. The practice makes sure that the necessary consents are in place under the applicable rules, for children from the parents or guardians.
Premium and payments
Premium (history and patterns over weeks, programs, PDF report, sync) is paid, and so is the practice license. You pay through the App Store or Google Play (purchases are handled and evaluated by RevenueCat, Inc., USA) or on the web through Stripe Payments Europe, Ltd., Ireland. Payment data (card, bank account, name, address, email for the receipt) is collected and stored only by these providers, not by us. Both are our processors under Art. 28 GDPR. For the USA, standard contractual clauses or the EU-US Data Privacy Framework apply.
We only receive: a random identifier of your connection (not your name), which product, until when it runs, through which channel it was bought and the customer identifier at Stripe. Of the providers' payment messages we keep only these fields for 30 days, then we delete them. The legal basis is Art. 6(1)(b) GDPR (contract); the providers keep invoice data for the statutory periods.
If a practice has a license, your connected app has Premium for as long as the connection lasts. The practice sees none of your payment data.
Access log
For each connection we keep a log of who did what and when: pairing, consent given or withdrawn, export, ending, deleting, and on the practice side viewing, creating and publishing exercise lists. It contains only identifiers, an action, the time and a hash of the truncated IP address, never content, nicknames or free text. The hash is deleted after 90 days, the entry after 12 months.
The purpose is security and proof that only authorised people had access (Art. 32 GDPR). The legal basis is Art. 6(1)(f) GDPR. You get the log of your connection in the export.
Usage metrics of the apps (optional, pseudonymous)
If you switch on sharing of usage metrics in a Sagbar app (default: off), the app sends one row of counters per week to our server: practice days of the week, courage tasks of the week, means of your check-ins of the week (self-rating and tension before and after), operating system, app version, the calendar week (no day, no time of day) and, if you came to us through a practice QR code, a practice link or a search engine, the channel (practice code or "seo"), which is counted along with them. The channel is stored only on your device at the first open and is not sent to anyone else. The practice code is a random code, not the name of the practice, and neither you nor the practice can be recognised through it. There are no texts, no content of entries, no names, no account, device or advertising ID and no recordings.
The self-rating and the tension may be health data within the meaning of Art. 9 GDPR. We therefore process them only with your explicit consent (Art. 9(2)(a) GDPR, alongside Art. 6(1)(a) GDPR). You give it by switching on sharing in the app and can withdraw it there at any time, the app then sends nothing.
This data is pseudonymous, not anonymous. A random install key assigns the rows to one install, so nothing is counted twice. Through its hash the same install can be recognised for up to 8 weeks: the app renews the key every 8 weeks and the server refuses older keys. Only the hash is stored (an HMAC with a secret server key). We do not combine the rows with any other data, including connections to a practice. The rows themselves hold neither an IP address nor a time of day.
Sending creates server logs like any request (IP address, time), kept as long as stated in the section "Server logs". We do not write values of the report to the logs. In the portal we only see weekly totals and means of closed weeks, and only where at least 5 installs stand behind them. The rows are deleted after 13 months. Because we cannot assign the rows to a person, we do not delete them individually after a withdrawal, they disappear when the retention period ends.
Error reports
When an error occurs on the server, we send an error report to our own GlitchTip, which runs on our server in the EU, not to a third party. The report contains only identifiers and the kind of error, never content, nicknames, notes, email addresses or health data. They are filtered before sending. No such tools are built into the browser or the apps.
The legal basis is Art. 6(1)(f) GDPR (legitimate interest in finding and fixing errors).
No trackers, no ads, fonts
There are no analytics tools, no advertising networks, no social media plugins and no embedded videos or maps. The site loads nothing from other providers' servers. The fonts are on our own server.
Anonymous question about the AI conversation partner
On the role-play page we ask whether a planned AI conversation partner would help you. Your answer (yes, maybe or no) only raises a counter per calendar week. We store no IP address, no identifier and no text for it. Your browser remembers locally that you answered, so that we do not ask again. This is not a cookie and is never sent.
Community
A community with its own accounts, messages and emails is technically prepared but not switched on. While it is off, no data arises. Before it starts we will extend this statement with purpose, legal basis and retention periods and obtain the necessary consents.
Optional account and sync
Exception to the statements above (no account, no cookies, nothing leaves your device): you can create an account to sync your entries between devices. It is voluntary. Without an account and without syncing switched on everything stays local in your browser. When you sign in Sagbar sets two cookies: one holds the sign-in (encrypted, HttpOnly, HTTPS only, up to 14 days idle or 60 days), the other is the session for protection against forged requests (CSRF) on the account pages. Before signing in there is none. Both are technically necessary for the service you asked for. To sign in you give your e-mail address and we send you a link (valid 15 minutes, usable once). There is no password. The address is stored encrypted in the database, the link only as a check value.
The mail is sent by our service provider Resend (Resend, Inc., USA) on behalf of Sagbar. Address and link pass through its servers. A data processing agreement under Art. 28 GDPR and standard contractual clauses are required and still to be reviewed. The legal basis for account and sign-in is Art. 6(1)(b) GDPR.
Only what you explicitly switch on per area is synced: diary (check-ins), situation logs, finished exercises, my list. Diary and situation logs can be health data under Art. 9 GDPR. The legal basis is your explicit consent (Art. 9(2)(a), Art. 6(1)(a) GDPR). You can withdraw it per area at any time, then we delete the data of that area on the server at once. Notes and texts are stored encrypted in the database.
Voice recordings never leave your device, there is neither a field nor an interface for them. You delete the account and its data yourself at any time on the "Account" page (Art. 17), where you also find the export (Art. 15, 20). Access to the account is logged without content (action, time, truncated and hashed IP address, 90 days, entry 12 months). Retention: an account without a sign-in is deleted after 12 months, we send a warning mail 30 days before. Deleted entries disappear completely after 30 days.
Links to other sites
Articles link to sources of other providers. With a click you leave Sagbar, from then on the privacy notice of the other site applies.
Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR). You can withdraw a given consent at any time with effect for the future (Art. 7(3) GDPR), in the app as easily as you gave it. Write to hallo@sagbar.app. For data for which a practice is the controller, we pass your request on to the practice or help it to answer. The rows of the optional usage metrics can only be assigned to a person to a limited extent (see above).
You can also complain to a data protection supervisory authority, for example Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein (ULD), Holstenstraße 98, 24103 Kiel.
Changes
When Sagbar changes, we update this statement before the change goes live. The date above shows the current version.