プライバシーポリシー
Sadisa が何を集め、なぜ集め、ほかに誰が扱い、あなたが何を求められるか。耐えるためではなく、読むために書きました。
Who is responsible
System Error MM GmbH, Lehrter Straße 49, 10557 Berlin, represented by Moses Mawila, is the controller for the purposes of the GDPR. Contact: support@sadisa.app.
There is no statutory Data Protection Officer; the company is below the threshold that requires one.
This website
This site sets no cookies, runs no analytics, embeds no third-party fonts and loads nothing from another domain. The only JavaScript on it switches between light and dark. Your visit is not recorded beyond the server log kept by the hosting provider for security and operation.
That is why there is no cookie banner: there is nothing to consent to.
What the app collects, and why
| Data | Why | Legal basis |
|---|---|---|
| Your onboarding answers | To set up how the assistant talks to you | Art. 6(1)(b) — performing the contract |
| Your conversations with Sadi | They are the product; the assistant remembers them so you don't have to | Art. 6(1)(b) |
| Calendar events and tasks | To see what's coming and to put things in on your behalf | Art. 6(1)(b) |
| Your device's time zone | So reminders arrive at the right hour, and travel does not shift your day | Art. 6(1)(b) |
| A device token and, if you allow notifications, a push token | To identify your app and reach you first | Art. 6(1)(b) |
| Photos and documents you attach, only if you say yes when asked | Sadi reads them to answer you; they are stored encrypted on our server in the EU and deleted automatically about 24 hours after Sadi has read them | Art. 9(2)(a) — your explicit consent |
| Voice notes you record | Sent to our own service to be turned into text; the transcript becomes part of your conversation | Art. 6(1)(b) |
| Health information, only if you say yes when asked | Only what you choose to have remembered | Art. 9(2)(a) — your explicit consent |
Sadi asks before writing anything about your health into its memory, and you can decline and carry on talking. Saying yes is the health consent named in the table above; you can withdraw it at any time, which stops further storage and removes what was stored. The same applies to the attachments consent: withdrawing it stops further attachments, and Sadi asks again before the next one. The conversation itself is kept like any other conversation, and you can delete it.
There is no advertising, no profiling for advertising, no sale of data and no automated decision-making with legal effect.
Google Calendar and Google Tasks
If you connect a Google account, Sadisa requests exactly two permissions:
calendar.events— to read and write events in your calendarstasks— to read and write your tasks
From your Google account, it does not request access to your email, your files, your contacts, your photos or your location, and it cannot reach them.
Sadisa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data obtained through those APIs is used only to provide the assistant's features to you, is not sold, is not used for advertising, and is not used by us to train any model. What the model provider does with what passes through it is in the next section.
You can disconnect at any time from your Google account permissions page, which revokes access immediately.
Who else processes it
Requesty Ltd. (United Kingdom, covered by the EU adequacy decision) routes model requests through its EU endpoint; inference is supplied by Google (Vertex AI) in data centres inside the EU. On our account, request logging is switched off, and the API key may call only a closed list of EU-hosted models — a request for any other model is refused by the router, which we tested. We have asked Requesty to confirm in writing that nothing sent through the account is retained or used to train models. That answer has not arrived; we will correct this page when it does.
Other processors: Google Ireland Ltd. (calendar and tasks, only what you connect), the hosting provider that runs your assistant, and the push notification service that delivers a notification to your device. Each acts under a data processing agreement and only on our instructions.
How long it is kept
Your assistant keeps your conversations and its memory for as long as you have an account, because losing them is the failure the product exists to prevent. Server logs are kept by the hosting provider under its own retention period. When you close your account, everything associated with it is deleted.
Your rights
Under the GDPR you can ask for a copy of your data (Art. 15), correction (Art. 16), deletion (Art. 17), restriction (Art. 18), portability (Art. 20), and you can object to processing (Art. 21). Where processing rests on consent, you can withdraw it at any time without affecting what happened before.
In the app you can do both. Settings, Privacy, Export gives you your persona and your memories as JSON and Markdown, directly readable; conversations are not included. Settings, Privacy, History deletes one conversation or all of them. Deleting your account is Settings, Account, Delete account, and it is permanent: it revokes the credential that grants access to your connected accounts, stops your assistant, and deletes your profile, your conversations and its memory of you. The credential is revoked first, so there is no window in which you believe you are gone while access to your calendar is still live. If any step fails, you are told which one rather than being told it worked. Write to us if you would rather we did it.
Write to support@sadisa.app and you will get an answer within one month.
You can also complain to a supervisory authority. The one responsible for us is the Berliner Beauftragte für Datenschutz und Informationsfreiheit.