Transparent access. Your own resources. Clear responsibilities.
This page describes confirmed ArchiCOS functions and operating principles. Detailed legal terms, retention periods and the provider list applicable to a service will be made available to the customer before the agreement is concluded.
Accounts, roles, project access and participant responsibilities.
Except for the public demo, workspace access requires an individual account. The ADMIN assigns participants to projects and grants roles and permissions. Each user is responsible for protecting their sign-in details and using shared information for the intended project purpose.
What information appears in ArchiCOS and who decides how it is used.
The system processes profile and contact data, project content, files, calendar and chat entries, the correspondence register, and technical information related to sign-in and security. Visibility depends on the organisation, project membership, account type and assigned permissions. In the organisational service model, the customer determines the purpose of project-data use and the operator processes it as needed to provide and protect the service.
Account protection, project separation and role-based access.
Access is limited at organisation, project-membership and detailed project-permission levels. Connections to the application are encrypted, passwords are not stored in plain text and credentials for external services are encrypted in the database. Changing a password ends active account sessions. Administrative and project-management accounts use two-factor authentication.
An agreement for customers whose project data is processed on their instructions.
Where the ArchiCOS operator processes data on behalf of a customer organisation, the DPA is an electronic annex to the service agreement. It is accepted by the customer or an authorised representative. A participant accepts participation rules and receives privacy information; accepting an invitation does not replace the DPA or grant authority to act for an organisation.
Information about language selection on this website.
The marketing website stores a manual language choice locally in the browser under archicos.language until the choice or site data is cleared. Initial language matching uses browser preferences, not IP geolocation. We have not added analytics or advertising pixels to this website. The application and chosen hosting require their own information about the technologies they use.
What stays in ArchiCOS and what remains with the selected provider.
The ADMIN chooses the destination, schedule and retention for backups available in the system. A project snapshot includes project data and files within its scope as well as the correspondence register. It does not contain full email messages or their attachment files, nor does it include the activity log, sessions or sign-in history. External-file retention depends on configuration and the selected provider’s terms.