Privacy policy

What you give us at registration: first name, last name, country, phone number, 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.

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.

• 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.

We ask for a phone number so we can reach you about your account and verify ownership during support; we do not use it for advertising.

We do not sell personal data. We use a small set of providers that process it on our instructions:

• Supabase — authentication, database and file storage for your account and models.
• Vercel — hosting and delivery of the web application.
• Railway — hosting of the modelling engine that authors your IFC files.
• Anthropic — the AI model behind the agent. Your prompts and the model context needed to answer them are sent there for processing, and are not used to train its models.
• 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, transfers rely on the European Commission’s Standard Contractual Clauses or an adequacy decision.

• Account data: for as long as the account exists, then deleted within 30 days of closure.
• Projects, models and chat history: until you delete them, or until the account is closed.
• 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].