Privacy policy

Who handles information

The operator identified below is responsible for account, security and service-administration information. Where a team determines the purposes of personal information inside its models, that team remains responsible for those purposes; Archibara handles the content to provide the requested service.

Information and purposes

We handle sign-in identifiers, name, email, verification status, team membership and permissions; architecture models, snapshots, imports and exports; subscription identifiers, plan and payment status; and technical or security information such as IP address, browser information and access records. Support correspondence is used to respond to your enquiry.

We use this information to provide the service and fulfil agreements, maintain access and security, operate limits and billing, meet applicable legal duties and address support requests. Where applicable, the legal grounds are performance of a contract, legal obligations and legitimate interests in a secure, reliable service. Optional consent-based processing, if introduced, must be explained separately.

Providers, sharing and integrations

Auth0 supports sign-in, including sign-in with Google when you choose it. OVHcloud hosts the service in France. Cloudflare supports network delivery, security and email routing for our support address, and stores service backups in the European Union. When you use checkout, Paddle handles payment information under its own privacy notice; Archibara receives the identifiers and status needed to manage access, rather than card numbers or security codes.

Authorised team administrators and platform operators can access information needed for their roles. Enabled share links and integrations can disclose content to their recipients. MCP or AI tools you authorise may read or change data within their permissions; their providers' terms also apply. Provider processing may take place outside your country. Information about relevant processing locations and transfer arrangements can be requested from the operator.

Browser storage and security

The service uses session cookies and browser storage for sign-in and preferences such as language and appearance. Disabling necessary storage can prevent sign-in or correct operation. Authentication, payment and security providers may use their own technical cookies under their notices. Connections to the hosted service use HTTPS; access is controlled by account and team permissions.

Retention

Account and model information is retained while needed to provide the service or deal with your requests. Snapshot history is limited by the selected plan. Deletion and closure requests are assessed alongside legal retention duties, security needs, disputes and backup recovery cycles. An inactive Free space becoming read-only does not mean its data has been deleted. Contact us if you need the retention criteria for a particular category of information.

Your choices and rights

Use the available model export and access controls, or contact the operator to request access, correction, deletion or an applicable portable copy of personal information. Depending on the law that applies, you may also request restriction, object to processing, withdraw consent or complain to a competent data-protection authority. We may need proportionate information to verify a request. For payment data controlled by Paddle, use Paddle's privacy request channels.