Skip to content
Privacy

Privacypolicy

What personal data ArchiMass uses, why we use it, and the controls available to you.

Last updated17 October 2026
Applies toWebsite, Arena and workspace

1. Who is responsible

ArchiMass is a product by FSI Atlas. The final contracting legal entity and registered contact details will be inserted here before launch. That entity will act as the data controller for the website and customer accounts unless a contract states otherwise.

2. Data we collect

  • Account and contact data: name, email, phone, country, date of birth if supplied, profession, organisation, role, address, language and time zone. When you choose Google or LinkedIn sign-in, ArchiMass requires the name and verified email address returned by that provider to create or identify your account. We do not receive the provider password or request permission to publish to the provider account. Passwords created directly with ArchiMass are stored as non-reversible hashes; email-verification tokens are stored only as short-lived hashes.
  • Workspace content: prompts, project inputs, site data, uploaded files, geometry, outputs, edits, feedback and publication choices.
  • Billing data: plan, token usage, invoices and limited payment references. Full card data should remain with the payment provider.
  • Technical and usage data: device, browser, IP address, session, security events, feature usage, diagnostics and cookie choices.
  • Public content: Arena profiles, project descriptions, images and metadata you choose to publish.

3. Why we use data

We use data to create and secure accounts, provide generation and analysis services, save and publish projects, process payments, respond to requests, prevent abuse, comply with law, and improve reliability. Depending on location, our legal bases may include performance of a contract, legitimate interests, legal obligations and consent.

We may use aggregated or de-identified operational information to measure performance and improve the service where it cannot reasonably identify you. We do not sell personal data.

4. AI processing

When you ask ArchiMass to generate, evaluate or modify a design, the service processes your prompt, project parameters, geometry, files and relevant context to produce the requested result. This service processing is different from training a general model for future users.

5. On-demand GPU migration and processing

If you choose Boost with Cloud GPU, ArchiMass may securely copy the project data and workspace state needed to resume your work—including geometry, project assets, materials, settings, active view and recoverable unsaved changes—to an isolated cloud-compute environment. Migration may take additional time while the project is saved, the environment is prepared and the transferred state is verified.

Your browser cookies and personal browser data are never transferred to the GPU machine. ArchiMass does not copy local or session cookies, saved passwords, browser history, unrelated local-storage data, provider credentials or refresh tokens. The clean GPU environment is authenticated using a short-lived, single-use token limited to the relevant account, project and migration.

If a GPU connection is lost because of internet, electricity or device interruption, ArchiMass may create an immediate recovery checkpoint, retain the isolated session for the reconnection period shown in-product and create a final Auto Backup before shutdown. The recovery version may include the latest project geometry, assets, settings, active view and workspace state and will be associated with the user's project account. Recovery versions are retained under the project's documented recovery and deletion controls.

The local project session should remain available until the cloud copy has loaded and passed verification. Temporary GPU-session data is isolated from other users and is scheduled for deletion after successful synchronisation and shutdown, subject to documented backup, security and legal-retention requirements. Cloud-compute providers and processing locations will be identified in our subprocessor information before the service is made generally available.

5. Sharing, subprocessors and international processing

We may share data with contracted providers supporting hosting, storage, authentication, payments, communications, analytics, support, AI processing and on-demand GPU sessions; with professional advisers; during a corporate transaction; or when law requires it. Providers must be assessed for security, confidentiality, retention, deletion, incident notification and any independent use of customer data. Access should be limited to the service they provide.

Provider categoryPurpose
Cloud hosting and storageApplication hosting, databases, project files and backups
Identity providersGoogle or LinkedIn sign-in using the required name and verified email address
Authentication and paymentsLogin, session security, checkout and invoicing
AI and computeGeneration, analysis, model inference and isolated on-demand GPU workspaces
Email, monitoring and supportTransactional messages, diagnostics, security and customer support
Analytics, experience and campaign measurementConsent-gated Google Analytics, Microsoft Clarity, Meta Pixel and LinkedIn Insight measurement

Final contracted provider names, locations and transfer mechanisms will be inserted before launch. Where data crosses borders, we will use an appropriate transfer mechanism where required.

6. Retention

We keep account and project data while an account is active and for a limited period afterwards for recovery, security, disputes, tax and legal requirements. Retention periods will be documented before launch. Public Arena material may remain visible until removed. Backups expire on their normal rotation.

7. Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability or objection, and may withdraw consent without affecting earlier lawful processing. My Account provides profile editing, export, session management, marketing choices and account deletion. You may also email hello@archimass.ai. We will verify requests and respond within applicable deadlines.

8. Security, children and changes

Production safeguards are intended to include least-privilege access, separated environments, modern password hashing, secure sessions, rate limits, encryption in transit, encrypted storage where supported, logging, backups and incident response. Every claim must be validated against the deployed service; ArchiMass does not currently claim SOC 2 or ISO 27001 certification. No service is risk-free.

ArchiMass is intended for adults and authorised professional or education users; it is not directed to children below the age permitted to consent in their location. Material changes will be dated and, where required, notified in-product or by email. Security concerns may be reported to hello@archimass.ai.