MED1A Back
印Legal

Privacy policy

This is a translation of our German privacy policy. If the two differ, the German version applies.

The essentials in brief

1. Controller

Philipp Theuer · MED1A
Schiffbrückstr. 6, 24937 Flensburg
Email: post@med1a.online · Phone: +49 152 23559065

2. Hosting and server log files

This website is hosted by Hostinger International Ltd., 61 Lordou Vironos Street, 6023 Larnaca, Cyprus, and delivered via the host’s content delivery network (CDN). When you access it, the server processes technically necessary data that your browser transmits automatically: IP address, date and time, the page or file requested, referrer URL, browser and operating system. The server needs this data to deliver the website and to protect it against attacks.

The legal basis is our legitimate interest in secure and stable operation (Art. 6(1)(f) GDPR). We do not analyse the log files and do not combine them with other data. How long they are kept is determined by Hostinger. Hostinger does not state a fixed period, either in its documentation or when we asked its support (November 2026); according to its privacy policy, Hostinger keeps data for as long as is necessary to provide its services and to comply with its legal obligations. We have a data processing agreement with the host under Art. 28 GDPR.

3. Contact forms and email

On the contact page you can book a call, request a website review or describe a project. In doing so, we process the details you enter: name, email address and, depending on the form, preferred date, the address of your website, the focus areas you want, service areas, budget and your message. The details are sent to us by email via our server.

We use the data solely to answer your enquiry and, where applicable, to handle an offer or an order. The legal basis is Art. 6(1)(b) GDPR (steps taken at your request prior to entering into a contract) and our legitimate interest in answering enquiries (Art. 6(1)(f) GDPR). We delete the enquiry once it has been dealt with, unless statutory retention obligations (for example under commercial and tax law) require longer storage.

If you request a website review, we visit the website you name and examine it. In doing so, we only process publicly accessible content.

To protect against spam, the server stores a pseudonymised hash of your IP address with the times of your enquiries in order to reject more than ten enquiries per hour. After one hour an enquiry no longer counts; the server deletes older entries with the next enquiry made via one of the forms (Art. 6(1)(f) GDPR).

If you email us directly, we process your email address and the content of your message for the same purposes and under the same rules.

4. Storage in your browser

Some features store data exclusively locally in your browser (local storage). This data is not transmitted to us:

This storage is strictly necessary for the features you have requested (§ 25(2) no. 2 TDDDG, the German Telecommunications Digital Services Data Protection Act).

5. Client area

For ongoing projects, we provide our clients with a password-protected client area. There you can see drafts, approve or comment on them, download or upload files, send us messages and request new jobs. Only we can set up accounts, by invitation (also through our AI tool, see section 6).

What data we process

Name, email address and password (stored only as a salted one-way hash, never in plain text); your company; if you wish, your title (Ms/Mr) and surname for the greeting in emails; whether we address you informally or formally (German “du” or “Sie”) and whether we write to you in German or English; the content you create in the client area (comments, messages, approvals, job requests); files you upload; and the times of sign-ins and actions. To protect against misuse, we also log a truncated, pseudonymised hash of your IP address.

Purpose and legal basis

We use the data to carry out the project with you (Art. 6(1)(b) GDPR). The log of sign-ins and actions is kept for system security (Art. 6(1)(f) GDPR).

Cookie

The client area sets a technically necessary session cookie (med1a_sid). It is set as soon as you open the client area, protects the sign-in against forged requests and then keeps you signed in. It contains only a random identifier and lasts until you close your browser. Signing out ends your session immediately; after 12 hours without activity it becomes invalid. No consent is required for this (§ 25(2) no. 2 TDDDG).

Storage period

We store project data for the duration of the project and afterwards to the extent that statutory retention periods require it (for example, eight years for invoices). We delete accounts on request, and at the latest twelve months after the end of the project. The security log is deleted automatically after 90 days. Invitation links expire after seven days, password reset links after one hour.

Passkeys

Instead of a password, you can sign in with a passkey (Face ID, Touch ID, Windows Hello or a password manager). For this, we store only the public key and its ID, a device name, technical details of the passkey (algorithm, signature counter, transport, the authenticator’s model ID) and when it was created and last used. Biometric data never leaves your device and does not reach us. You can delete passkeys in your account at any time (Art. 6(1)(b) GDPR).

Messages, approvals and calendar

If you edit a message, we also store the earlier version so that it remains clear what was written when. It remains visible in the project and is deleted with the project. If you approve a draft or a website, we store as evidence your name, the date and time, the version and a checksum of the approved file. In your account you can set up a calendar subscription: it generates a secret address from which your calendar app retrieves the deadlines and appointments of your projects. Anyone who knows this address can see these appointments; you can revoke it in your account at any time. Your calendar provider (for example Google, Apple or Microsoft) retrieves the address and stores the appointments according to its own rules. If an appointment contains a link to a video meeting (for example Microsoft Teams or Zoom), the provider’s privacy policy applies when you join (Art. 6(1)(b) GDPR).

Voice messages

Instead of typing, you can send us a voice message in the client area (the “Voice” button in Messages, up to five minutes). The first time, your browser asks whether it may use the microphone. Recording only happens while the recording is running; you can listen to it and discard it before sending. Only “Send” passes it to us. We sometimes send you voice messages the same way; everything below applies to them too.

What we store: the recording as an audio file, its length, the date and time, the name of the person who sent it, the project and the automatically created text. The file is kept by our host (section 2) outside the publicly accessible part of the server, under a random file name. Only signed-in people who may see the messages of this project can listen to it: you, other accounts of your company for this project, and us.

Automatic transcript: So that the message can be read quickly and found again later, our server sends the recording to Mistral AI (Mistral AI SAS, Paris, France) after it has been sent and receives the text back. Only the audio file and the language we write to each other in (German or English) are sent: no name, no email address and not your IP address; the request comes from our server. The text appears below the recording marked “Transcribed automatically” and may contain errors. We can correct it; it is then marked “corrected” and the automatic version stays visible. Before sending you can untick “Transcribe automatically”; the recording then goes to no service at all. We do not analyse voices to identify people and do not create voice profiles.

Notification: As with every message, the other side receives an email with the transcribed text but without the audio file. If the text is not ready yet, the email says that it will follow.

Storage period: We delete the recording automatically after 30 days. The text stays in the project as a message and is deleted like the rest of the project data (see “Storage period” above). A deleted recording may remain in our backups for up to eight weeks. If you would like a recording deleted sooner, just send us a message.

Provider and contract: Mistral AI processes the recording on our behalf; we have a data processing agreement with Mistral AI under Art. 28 GDPR. Under its terms, Mistral AI is itself responsible for the automated abuse monitoring of its interfaces and may store requests for that purpose under its own rules. If Mistral AI transfers data to countries outside the EU, its terms allow this only to countries with an adequate level of data protection or with appropriate safeguards such as the European Commission’s standard contractual clauses.

Legal basis: carrying out your project (Art. 6(1)(b) GDPR). Voice messages are optional; you can always write instead.

Review bench

When we build a website for you, you review it in the client area on desktop, tablet and phone. For each comment, we additionally store the page address, the device type, the window size, the version of the website and a short text excerpt of the clicked element together with its position, so that we can find the spot again. In addition, your browser creates a small image of the commented section when you comment. It shows only the preview of the website we are building for you, not the rest of your screen, and records how the spot looked in this version. That way it remains clear what was meant, even after a new version. The image is stored with the comment in the client area and is deleted with the comment or the project. We also store when you first opened a version and on which devices and pages you viewed it at full size; this shows us what has already been reviewed, and devices you have viewed are ticked off in the checklist. For reviewing on your own phone, the client area generates a review link: it is valid only for this one approval and for seven days, we hold only a hash of it, and your browser remembers the link only for the open tab (session storage). The script for this is contained only in the preview version of your website, never in the finished one (Art. 6(1)(b) GDPR).

Questionnaires via link

For a project, we may send you a questionnaire. You open it without signing in via a secret link that opens only this questionnaire and is valid for 90 days. We save your answers as you go, the name you enter under “Completed by” and when the questionnaire was first opened, last saved and submitted. Until it is next saved successfully, your browser keeps a copy of your entries in local storage. To protect against misuse, the server uses a truncated, salted hash of your IP address, which it deletes after about one day. When you submit the questionnaire, we are notified with your name, and an entry appears in the project history. The answers are deleted with the project, or earlier if we delete the questionnaire (Art. 6(1)(b) GDPR).

Hosting and email

The database and files are stored with our host (see section 2), outside the publicly accessible area of the server. When there are new drafts, messages or status changes, we send you an email to the address on file; emails are sent via the host’s mail server.

Accepting offers online

When we send you an offer in the client area, you can view and download it, decline it, ask a question about it or accept it with binding effect. We see when and by whom the offer was first opened and when and by whom it was accepted or declined, and, if you decline, the reason you give.

When you accept an offer, we store an acceptance record: your name, email address and account number, your role, your company with its client number, address and VAT number, the wording of the two statements you confirmed, how you confirmed (for example by holding the button or with the keyboard), the interface language, the project and the client area, the date and time (UTC), your IP address together with the technical address details of the connection (the sender address seen by the server and, if present, the Forwarded, X-Forwarded-For, X-Real-IP and CF-Connecting-IP headers, and whether the address came directly or through a proxy), your browser’s user-agent string and a short form of it (such as “Chrome · macOS”), how and when you signed in (for example with a password, a passkey or an invitation link), the number, title, version, language, page count, file name and size, sending date, validity, price and terms of the offer, our details as the provider, and a SHA-256 fingerprint of the exact offer file you accepted. We also store the time stamp data, the versions of the certificate and when the related emails were sent. Downloads of the offer and the certificate are logged like other actions in the client area (see above).

Each record contains the fingerprint of the previous one, so later changes would be detectable. We have the record’s fingerprint time-stamped with a qualified time stamp by a qualified trust service provider, Sectigo (Europe) SL, Spain. The provider receives only this fingerprint, from which the record cannot be reconstructed. We send the offer and the certificate of acceptance to you and to us by email.

We process this data to be able to prove that and how the contract was concluded (legitimate interests, Art. 6(1)(f) GDPR) and, where you yourself are our contracting party, to perform the contract (Art. 6(1)(b) GDPR). The offer and the acceptance are also business correspondence that we must retain under German tax law (Art. 6(1)(c) GDPR in conjunction with § 147 AO, the German Fiscal Code).

We keep the record until the end of the sixth calendar year after acceptance. Until then the client area locks it against changes and deletion; afterwards it deletes it automatically. It may remain in our backups for up to eight weeks after that. We keep the certificate in our email inbox as business correspondence for the same period. You may object to processing based on legitimate interests (Art. 21 GDPR); we will then keep the record where we need it to establish, exercise or defend legal claims or are required by law to retain it.

The client area demo on this website works only with sample data in your browser (see section 4).

6. Access via AI tools

Philipp Theuer can connect an AI tool to the client area in order to summarise or evaluate project information or to prepare replies. The tool used for this is Claude by Anthropic. This happens only on his initiative and only within the scope of the permissions he has granted to the access concerned.

What data

For each request, the necessary project data is transmitted to Anthropic and processed there, for example project name and status, messages, comments (including the images from the review bench), approvals, files, and the names and email addresses of the people involved. When the tool works with the permissions for the agency area (see below), the details needed for this are added: the language and form of address of the people and whether they have set up their account yet, the details of a person to be invited and a personal note to them, offers with their file, price, deadline, company, address and VAT number, and the status of an offer up to acceptance (certificate number, name, role and email address of the person who accepted, and the time). Passwords, passkeys and access credentials are not included.

How access is limited

Access works via a key (token) or a sign-in with explicit confirmation in the client area. Each access grant has defined permissions, read-only by default, and an expiry date (no expiry only with explicit confirmation). It can be revoked at any time, and a master switch blocks all access at once. Each access is logged with the time, the access grant and the area retrieved; the log is deleted after 90 days.

If an access grant also has write permissions, the AI tool can, on Philipp’s instruction, write a comment or a message in the client area, change individual project details and create new clients (company, contact person, informal or formal address), projects and questionnaires; no email is sent when something is created. This appears there as an entry by MED1A and is also logged. We remain responsible for it.

Only Philipp’s own access can additionally be given permissions for work in the agency area, each one separately: changing client details (company name, contact person, form of address, language), uploading offers, sending them to you and withdrawing them, and adding and inviting people, optionally with a personal note. When an offer is sent, the people at your company who have an account get a notice in the client area and an email; when someone is invited, that person gets an email. The tool is instructed to show a preview and obtain Philipp’s consent before each such email. We receive an email about every invitation and every offer the tool sends, for invitations including the person’s name and email address and the personal note. We do not store the personal note in the client area; it only appears in these two emails. Each such action is recorded in the AI access log (time, access grant, type of action and the numbers of the client, project, offer or person, without content) and in the security log with a note that it was done via AI access; both are deleted after 90 days. Actions are limited per access grant (for example, at most ten invitations in 24 hours). Client access grants never get these permissions.

No access grant can manage passwords, passkeys, settings or backups. None can remove or block people, and none can delete anything.

Provider and transfer

The provider is Anthropic (Anthropic PBC, San Francisco, USA). Data may be transferred to the USA in the process. For client data, we use only Claude accounts under commercial terms for which Anthropic offers a data processing agreement under Art. 28 GDPR that incorporates the European Commission’s standard contractual clauses for transfers to third countries.

Legal basis

We use the tool to carry out your project (Art. 6(1)(b) GDPR) and on the basis of our legitimate interest in fast, careful project work (Art. 6(1)(f) GDPR). If you do not want data from your project to be processed via an AI tool, just let us know. We will then work on your project without AI access.

Your own AI access as a client

On request, we can enable your own AI access for you. You then connect an AI tool of your choice to your projects yourself under “Account”. This access can only read and can only see your own projects. The data then goes, on your initiative, to the provider you have chosen; you are responsible for this yourself. You can disconnect the access at any time under “Account”.

7. AI chat (website and client area)

On the website (the 問 “Chat” button) and in the client area (the “Chat” menu item and the 問 button at the bottom centre), you can ask an AI assistant questions. It runs only when you send it a question. The answers are generated by the language model Claude by Anthropic; they may contain errors and are not binding. Binding statements, prices and offers come only from us.

Assistant on the website

You do not need an account and do not give a name. When you send a question, our server sends it to Anthropic together with the previous messages of the same conversation (at most twelve), the language of the page and the public content of this website. The request comes from our server; your IP address is not transmitted to Anthropic. Please do not enter any personal or confidential data.

We store the text of your questions and of the answers with the time under a random conversation ID, without a name and without an IP address. This lets us understand what is being asked and improve the answers; only Philipp Theuer sees the conversations. Your browser keeps the current conversation and the ID in the session storage of the open tab so that the conversation is preserved as you continue scrolling; when you close the tab, it is gone from there. To protect against misuse (at most 20 questions in ten minutes and 80 per day), the server stores a hash of your IP address salted with a secret value and deletes it after about a day.

With “Delete conversation” in the window, you delete the conversation immediately on our server and in your browser. Otherwise we delete conversations automatically 90 days after the last message. They may remain in our backups for up to eight weeks after that, until they are routinely overwritten.

Assistant in the client area

In the client area, the assistant answers questions about your project and about using the client area. For this, Anthropic receives, along with your question and the previous messages of the conversation, the status of the project you currently have open, as you yourself see it in the client area: project name, phases and appointments, approvals with comments, job requests, the names of files (not the files themselves), the history, the latest messages in shortened form, and your name and company. Other projects and other clients are technically excluded. Passwords, passkeys and access credentials are not included.

We store questions and answers linked to your account and project; Philipp Theuer sees them so that he can follow up. If you choose “Send to Philipp”, your question ends up as a message in the project. We delete conversations automatically 90 days after the last message, or earlier together with the project; the same as above applies to backups. If you would like a conversation deleted sooner, a message to us is enough.

Provider and transfer

The provider is Anthropic (Anthropic PBC, San Francisco, USA), connected via the Anthropic API with MED1A’s own key. Data may be transferred to the USA in the process. We use the API under Anthropic’s commercial terms with a data processing agreement under Art. 28 GDPR that incorporates the European Commission’s standard contractual clauses for transfers to third countries. Under these terms, Anthropic does not use the content to train its models.

Legal basis

On the website: our legitimate interest in answering questions about our services quickly (Art. 6(1)(f) GDPR) and, if you enquire about working with us, steps taken at your request prior to entering into a contract (Art. 6(1)(b) GDPR). In the client area: carrying out your project (Art. 6(1)(b) GDPR). Storage in session storage is strictly necessary for the feature you have requested (§ 25(2) no. 2 TDDDG). You do not have to use the assistant; every way of reaching us also works without it.

8. Leaderboard in the game

At the end of the game “The Way of the Pixel”, you can voluntarily enter yourself on a public leaderboard. Visible there to all visitors are the name you enter, your score, your time and the date. Please use a nickname or just your first name for this, not your full name.

So that nobody floods the list with made-up results, each round of the game receives a unique, random ID when it starts, and the server remembers your IP address only as a truncated hash salted with a secret value. The address cannot be reconstructed from it; it serves solely to slow down too many entries in a short time. The game does not set a cookie.

The legal basis is your consent, given by making the entry (Art. 6(1)(a) GDPR), and, for protection against misuse, our legitimate interest in a fair list (Art. 6(1)(f) GDPR). We delete the IDs of game rounds after one day, the IP hash of an entry after 30 days and the entry itself after twelve months. If you would like your entry removed sooner, write to post@med1a.online with the name, score and approximate date.

9. Links to other websites

For some of the projects under “Selected work”, we link to our clients’ websites. The external website is only loaded once you click such a link. The respective provider is responsible for its data processing.

10. Encryption

This website is delivered exclusively in encrypted form via HTTPS. As a result, form entries are transmitted in encrypted form.

11. Your rights

At any time, you have the right of access to the data we store about you (Art. 15 GDPR) and the rights to rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). Where we process data on the basis of legitimate interests, you can object to the processing (Art. 21 GDPR). You can withdraw your consent at any time with effect for the future (Art. 7(3) GDPR), for example for your leaderboard entry. An informal message to post@med1a.online is sufficient.

You can also lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Independent Centre for Privacy Protection Schleswig-Holstein (Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein), Holstenstraße 98, 24103 Kiel.

Last updated: November 2026