Privacy policy

What you give us at registration: first name, last name, email address, and a password — stored only as a salted hash, never in readable form. We also record the date and time you accepted these terms and this policy, and, if you ticked that box, the date and time you asked for the newsletter.

What you create in the product: your projects, IFC models and their revisions, the chat messages you exchange with the agent, and the log of operations the agent performed on your models.

What is generated by using it: sign-in events, usage counters and credit movements, and ordinary server logs (IP address, user agent, timestamps) kept for security and debugging.

If you sign in with Google, we receive the email address and basic profile of that Google account instead of a password.

What other members see: when you belong to a project, your email address, display name and role are visible to the other members of that project, whatever their role.

• To provide the Service you asked for — hosting your models, running the AI agent, showing your revisions (performance of a contract).
• To bill you and honour your plan or credit balance (performance of a contract; legal obligation for invoices and tax records).
• To keep the Service secure, prevent abuse and enforce quotas (legitimate interests).
• To reach you about your account — service notices, security alerts, password recovery (performance of a contract). Marketing mail, if any, only with your consent.

The newsletter is the only mail that needs your consent, and it is the only thing that box does: leaving it unticked has no effect on your account, and asking us to stop afterwards costs you nothing else.

We do not sell personal data. We use a small set of providers, listed below with what each one does for us. They process it on our instructions — with one exception, stated in its own item: OpenRouter passes each AI request on to a further model provider that we do not choose and whose handling of that request we do not control.

• Supabase — authentication, the database for your account, projects and models, and the account emails we send (confirmation, password recovery).
• Cloudflare (R2) — storage of the IFC files you upload and the geometry derived from them, in Cloudflare’s EU jurisdiction.
• Vercel — hosting and delivery of the web application.
• Railway — hosting of the modelling engine that authors your IFC files.
• OpenRouter — the gateway through which the agent reaches an AI model. Your prompts and the model context needed to answer them are sent to OpenRouter, which forwards each request on to a third-party model provider that it selects. We do not pick that provider request by request, and we do not enable the OpenRouter setting that would forbid those providers from retaining what is sent to them, including for training; what a provider may do with a request is governed by its own terms and by OpenRouter’s.
• Stripe — payment processing. Card details are handled by Stripe and never reach our servers.

Data may be processed outside your country, including in the United States, by the providers listed above. Where personal data leaves the EEA or the UK to reach one of those providers, transfers rely on the European Commission’s Standard Contractual Clauses or an adequacy decision.

The model providers OpenRouter routes to are not on that list. OpenRouter picks one when the request is made, so which company processes a given prompt, and in which country, is not fixed in advance, and this policy names no transfer safeguard for that onward step.

• Account data: for as long as the account exists. To have your account deleted, write to [privacy@your-domain] from the address you signed up with; we delete it within 30 days of your request and confirm when it is done.
• Projects, models and chat history: until you delete them, or until your account is deleted. Projects you share with others and do not own stay with their owners; your name is removed from what you created in them.
• Billing records: as long as tax and accounting law requires (typically 7–10 years).
• Server logs: a rolling window, typically 30–90 days.

Subject to the conditions in applicable law (in the EEA and UK, the GDPR) you may request access to your personal data, correction of what is inaccurate, deletion, restriction of or objection to processing, and a portable copy of what you provided. You may withdraw a consent at any time without affecting processing already carried out.

Write to [privacy@your-domain]. You also have the right to complain to your local supervisory authority.

Access to your projects is enforced at the database level by row-level security tied to project membership, not only by the application. Traffic is encrypted in transit, passwords are hashed, and files are stored in access-controlled buckets. No system is perfectly secure; if a breach affects your data and the law requires it, we will notify you and the competent authority.

We set only what the Service needs to work: the cookies that keep you signed in, and a browser-local preference for the light or dark theme. No advertising or cross-site tracking cookies are used.

The Service is not directed at children and we do not knowingly collect their data. If you believe a child has registered, contact us and we will remove the account.

The “last updated” date above marks the current version; we will notify account holders of material changes. For anything in this policy, write to [privacy@your-domain].