Privacy
Policy
/ As of 27 October 2026
This is a translation. The German version is legally binding.
01Controller
The controller is schema bau GbR. Its address is in the legal notice. Email: info@moddl.site
This policy describes which personal data we process when you use moddl with or without an account, and which rights you have.
02Hosting and operation
moddl is hosted with Hetzner Online GmbH, Gunzenhausen, on a server in its data centre in Nuremberg (Germany). Storage, logs, usage analysis and format conversion are provided by Google Cloud EMEA Limited, Dublin (Ireland), in data centres in the EU (currently Belgium and Germany). Sign-in is excepted. It is processed in the USA (section 7). Hetzner and Google are our processors under Art. 28 GDPR. Access by Google LLC in the USA to the data held by Google cannot be ruled out. The adequacy decision on the EU-US Data Privacy Framework applies to it, supplemented by the EU standard contractual clauses. We serve fonts and other parts of the website from our own servers.
The legal basis is our legitimate interest in secure and available operation (Art. 6(1)(f) GDPR).
03Server and access logs
For every request our server processes technical data, in particular IP address, time, requested address, status code and browser identifier. We do not keep a log of each individual request. We log operational and error messages of the server. We additionally log accesses by accounts to stored models with time, kind of access and technical identifiers, without model contents. We use the logs for operation, troubleshooting, security and defence against abuse. They are kept in the EU.
We delete server logs after 30 days at the latest and access logs after 180 days at the latest. We keep individual entries longer only as long as they are needed to investigate a specific security incident.
The legal basis is Art. 6(1)(f) GDPR.
Heartbeat of the open tab. If you have opened a workbench without an account or connected an AI agent without an account, every open tab of the application sends a request to our server every 30 seconds, less often in background tabs. It contains a random identifier of the tab and the cookies present.
If you have connected an AI agent, we hold in the server's memory the hash of the agent secret, the associated workbench and the time of the last report of each tab. If no tab reports for 3 minutes, we no longer accept calls from the agent. This protects you against misuse of an agent access when the application is no longer open. Each heartbeat renews the link cookie, so that the agent stays connected even after the browser restarts.
We delete these entries when you disconnect, but no later than 12 hours after the last report. We keep revoked agent accesses for the same period, so that they cannot be used again.
The legal basis for holding your workbench is Art. 6(1)(b) GDPR. For checking the agent connection it is our legitimate interest in secure operation (Art. 6(1)(f) GDPR). Access to and storage in the browser are permitted without consent under § 25(2) no. 2 TDDDG.
04Usage analysis
To improve moddl, we analyse how the tools are used and where errors occur. In particular we record the functions called with an approximate time (rounded to the hour in the analysis; the logging service records receipt to the second), duration and result, error codes and counts, technical features of uploaded files (such as IFC version, authoring software, order of magnitude), and, when an AI is connected, the name and version of the connected program.
For this we record no IP addresses, no file names, no model contents (such as names, addresses, property values, details of author or organisation in the file header) and no texts that you or a connected AI enter (such as search terms, values or scripts). The entries of a session are first linked by a pseudonymous identifier. We technically remove the assignment of this identifier to your session regularly, after two months at the latest. We delete the entries after two months at the latest.
We do not use the analysis for advertising and do not build profiles of people. Recipients are only our processors (section 11). The legal basis is our legitimate interest in a working and better tool (Art. 6(1)(f) GDPR). You can object (section 12). Without an account we can assign entries only if you give us the details needed for it (Art. 11 GDPR).
05Cookies and browser storage
We use only cookies that are technically necessary for the service you request. No consent is needed for them (§ 25(2) no. 2 TDDDG).
| Purpose | When set | Maximum duration |
|---|---|---|
| Keeping your workbench apart from that of other visitors | When you open the application | End of the browser session |
| Staying signed in | After sign-in | 30 days |
| Protecting the sign-in process with Google | During sign-in with Google | 1 hour |
| Linking an AI agent without an account to this browser. Holds one hash of its secret per connected AI agent and cannot be read by scripts on the page (HttpOnly) | Only when you connect an AI agent without an account. Every heartbeat of the open tab renews it | 30 days |
| Chosen language | When you choose a language or switch from a language version of the website to the application | 1 year |
The application also keeps operating settings in your browser storage, such as sort orders and views. If an account has already been used in this browser, it remembers this so that the consent page for an AI agent can show a notice about it. This marker contains no details of your person or your account, only the value “1”. This information stays on your device.
We do not use cookies or similar techniques for analytics or advertising and do not embed third-party tracking services.
06Working without an account
Without an account you work on a sample model or an empty project. You cannot upload your own files without an account. Your workbench is held on the server only temporarily and discarded at the latest 24 hours after the last tab of the application was closed, possibly sooner. You can download it as an IFC file beforehand.
The legal basis is providing the function you use (Art. 6(1)(b) GDPR).
07Account, models and project rooms
Account. An account is voluntary and required to upload your own models. We process your email address, an account identifier, sign-in times and the profile details you give (such as name, company, position, phone number). We do not store your password in plain text. We send you emails that are necessary for the account, such as to confirm the address, to reset the password, on security questions and on material changes to the service or the terms.
Sign-in with Google. Google sends us your email address and an identifier of your Google account. We use them only to sign you in and to assign your account. The use of information we receive through Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Google’s privacy policy applies to Google’s sign-in page.
Sign-in service. Sign-in is processed by Google Cloud Identity Platform (Firebase Authentication) with email address, account identifier and sign-in times. This service runs in data centres in the USA. The provider is Google Cloud EMEA Limited, the subprocessor is Google LLC. The adequacy decision on the EU-US Data Privacy Framework and the EU standard contractual clauses apply. Our server makes the requests to this service. Your browser does not connect to Google in doing so. Only if you choose “Sign in with Google” do we redirect you to Google’s sign-in page.
Models and workbenches. With an account we store your IFC files, their edit states and details of the workbench (such as name, project number, address of the construction project) in the EU so that you can find them again later. To convert older IFC formats we hold files briefly and delete them after 7 days at the latest. Deleted data remains technically recoverable for up to 30 days and is then removed for good. We use model contents only to provide the functions you call. If models contain personal data of third parties, we process it as a processor under the data processing agreement.
Project rooms. If the owner of a project room invites someone by email, we store that address, even if the person has no account, and send them an invitation naming the room and the person inviting. We record when members were invited, joined and last opened the room. Owners and editors see the member list. Open invitations expire after 60 days at the latest. The address is deleted when the person is removed, leaves the room, or the room or the owner’s account is deleted. The legal basis for the data of invited people is the legitimate interest in working together on the project (Art. 6(1)(f) GDPR).
Agent access and last visits. For each model in your account we store when you last opened it, to show you the notice “Since your last visit: N revisions by an agent”. For each agent access we store its scope (only the open model or the whole account), its target (the model the agent is working on) and when it was last used.
Storage period. We keep account data and workbenches until you delete them or the account. You can do this in the account at any time. We may delete accounts that have not been used for 24 months, with all their contents, after notifying you by email beforehand. If the contract ends for another reason, we delete the account with all its contents 90 days after the end of the contract at the latest. After deletion only logs (section 3) remain until their period expires, and the proof under section 14.
Unless stated otherwise, the legal basis is providing the account (Art. 6(1)(b) GDPR).
08Connecting an AI
If you connect an AI assistant to moddl, the provider you choose receives the answers from your model, including any details about people they contain. The provider processes this data under its own responsibility according to its privacy policy. You grant the permission yourself and, with an account, can revoke it at any time.
We do not receive the history of your conversation, only the calls the AI makes to moddl (such as search terms, values and scripts). We process these like your own operation. The legal basis is providing the function you use (Art. 6(1)(b) GDPR).
09Notification about the beta launch
You can sign up to be informed by email. For this we store your email address, the times of sign-up and confirmation, and the version of the consent text. We add your address only after you confirm through a link in our email (double opt-in). We delete unconfirmed sign-ups after 30 days at the latest. To protect against automated sign-ups we use a check without cookies and without embedding third parties.
The legal basis is your consent (Art. 6(1)(a) GDPR). We use the address only for the purposes the consent text names and delete it when they are fulfilled or you withdraw. You can withdraw at any time without formality, by email or through the link in every message. The lawfulness of the processing so far remains unaffected. We keep the proof of consent until three years after the end of the year in which the consent ends.
10Contact form, email and notices under the DSA
When you write to us, we process your details (such as name, email address, message) to deal with your request. We use your IP address only briefly to defend against abuse. The legal basis is Art. 6(1)(b) GDPR if your request concerns a contract, otherwise our legitimate interest in answering (Art. 6(1)(f) GDPR). We delete your message when your request is settled, unless statutory retention duties apply.
We process notices of illegal content (Art. 16 DSA) with location, reasons and your confirmation (Art. 6(1)(c) GDPR in conjunction with Art. 16 DSA), and name and email address only if you give them (Art. 6(1)(f) GDPR). We delete notices when they are settled, as a rule 12 months after our decision at the latest.
Email dispatch and mailbox are provided by Spaceship, Inc., Phoenix (USA), with the Spacemail service (section 11).
11Recipients and transfers to third countries
We use the following processors:
- Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (operation of the server), data centre in Nuremberg (Germany).
- Google Cloud EMEA Limited, Dublin (storage, logs, analysis, format conversion) in the EU, with possible access by Google LLC, USA. Basis: adequacy decision on the EU-US Data Privacy Framework and standard contractual clauses.
- Google Cloud EMEA Limited, Dublin, with subprocessor Google LLC (sign-in, section 7): processing in the USA. Basis as above.
- Spaceship, Inc., 4600 East Washington Street, Suite 300, Phoenix, AZ 85034, USA (email dispatch and mailbox). Basis: EU standard contractual clauses (Art. 46(2)(c) GDPR).
You can obtain a copy of the standard contractual clauses on request at the address in section 1. We pass data on to other parties only if we are legally obliged to, if it is necessary to establish, exercise or defend legal claims, or if the operation of moddl passes to a legal successor (Art. 6(1)(c) or (f) GDPR respectively).
12Your right to object (Art. 21 GDPR)
Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation. We then no longer process the data, unless we demonstrate compelling legitimate grounds that override your interests, or the processing serves to establish, exercise or defend legal claims. An informal objection to info@moddl.site is enough.
13Your further rights
You have the right of access, rectification, erasure, restriction of processing and data portability (Art. 15 to 20 GDPR), and the right to withdraw consent at any time with effect for the future. An informal request to the address in section 1 is enough. There is no automated decision-making including profiling (Art. 22 GDPR).
You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), for example the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg, Lautenschlagerstraße 20, 70173 Stuttgart.
14Proof of acceptance of the terms of use
When you accept the terms of use, we store a proof with the details needed for it, such as version, time, language and kind of acceptance. We keep it beyond the deletion of your account or workbench, until the regular limitation period has run, that is three years after the end of the year in which the contract ends (sections 195, 199 BGB). The legal basis is our legitimate interest in being able to prove the acceptance (Art. 6(1)(f) GDPR).
15Changes
We update this policy when moddl or the law changes. The version published here at the time applies.