T
Log inStart for free

Privacy Policy

Last updated: 13 October 2026.

Product terms for Tekarius as it ships today. This is not legal advice. Governing law, a payment provider, and a contact email will be named when we start charging.

Read this Policy together with our Terms.

This Policy describes how Tekarius handles personal data when you use the landing site and the browser editor. We process that data to run the product: sign-in, your projects, and the account plan.

We do not sell your email or your models. We are not a licensed professional practice; this Policy is about the software, not a client-architect engagement.

What we collect

Personal data is information that identifies you. We may collect:

  • Google account identity (name, email, subject id) via Playder auth when you sign in.
  • Project files: the building JSON and metadata (name, revision), stored on our project service and keyed to your account. The building document is your work; it is not a profile form.
  • Account plan (Free / Starter / Pro / Pro AI / Studio), status and period dates on that same service — not inside the JSON.
  • Technical data needed to operate the site (for example IP, browser, error logs) from hosting and the apps.
  • Theme and language in the browser (localStorage). That is not the source of truth for projects.

How we collect it

You give us identity by signing in with Google. You give us projects by creating and saving in the editor. The device stores theme and language locally. We do not run a separate email-and-password form in the editor. We do not buy lists of architects from data brokers.

How we use it

We use this data only to operate Tekarius:

  • Authenticate you and keep the session.
  • Store, open and autosave your projects.
  • Enforce the account plan (for example a project cap on create).
  • Keep the site and editor running (security, debugging, abuse).
  • Understand aggregate usage (which features are used) without putting your house in a marketing pack.

When we share it

We share data with the processors that make the product work: Google (sign-in and, if you opt in, 3D tiles), Playder (auth), our hosting and project database. When card payments ship, the payment provider will see billing identity, not the building JSON. We may disclose data if the law requires it. We do not sell personal data or project files.

On your device

Theme and language use localStorage so the site looks the same next visit. Google’s sign-in may set its own cookies. We do not currently show a cookie banner; turning off cookies or storage may break sign-in or preferences. Project JSON is not stored as a second source of truth in IndexedDB when you are signed in — the server copy is.

Other services

Google, Playder, hosting, and later a payment provider have their own privacy policies. Optional Google 3D tiles are loaded in the viewport under Google’s terms; we do not treat that imagery as yours or as a survey. Links on the landing site to the editor or docs may send you to another Tekarius origin.

Your rights

Depending on where you live, you may have rights to access, correct, delete or export personal data, or to object to some processing. There is no self-serve data-download portal yet. You can export IFC/PDF from the editor on plans that include export, and you can ask through the product. We will not discriminate against you for asking. We do not make automated decisions that legally reject you as a person (a project-cap 402 is the plan talking, not a credit score).

Where it is processed

Auth, hosting and the project database may process data outside the country you are in. By using the Service you understand that. We will name regions more precisely when we publish a production contact and charge cards.

Security

We use standard hosting and access controls (signed-in requests, account-scoped projects). No system is perfectly safe. You are responsible for the Google account you use. If we learn of a breach that affects you, we will notify you as the law requires.

Retention

Projects stay until you delete them or we close the account. Account and billing rows stay as long as the account exists, and for a reasonable time after if we need them for security or legal records. Theme and language stay on the device until you clear site data.

Changes

We may update this Policy. The date at the top is the version that applies. We will post the new text here. Continued use after a change means you accept it.

Contact

Questions or requests about this Policy: use the account you signed in with, inside the product. We will publish a contact email when we start charging. We do not yet have a dedicated data-protection officer or EU/UK representative on file.