How ProArchitectOS handles project and account information.
This notice describes information ProArchitectOS processes when users access the platform, participate in workspaces or request pilot access.
Information we process and store
ProArchitectOS processes pilot enquiries (contact name, email, practice and project needs), account details such as name and email address, project membership and organisation details, and activity or audit records generated through use of the platform. Separately, the service stores and processes customer-controlled project content such as uploaded PDFs, DWGs, schedules, document metadata, transmittals, RFIs and markups to provide the authorised project workspace.
How information is used
Information is used to respond to pilot enquiries, authenticate users, provide access to authorised project workspaces, manage document revisions and transmittals, send project notifications, maintain the project audit record, and operate and improve the ProArchitectOS service.
Project files
Project content remains owned by the relevant customer and other applicable rights holders; uploading files does not transfer intellectual property ownership to ProArchitectOS. The service hosts and processes these files to provide authorised document-control and collaboration features. Files are subject to project membership, permissions and workflow visibility restrictions. Transactional notification emails link users back to ProArchitectOS instead of attaching project documents.
Who can access project information
Access depends on project membership, role and the document workflow. Work-in-progress information may have more restricted visibility than formally issued documents. Project Owners have additional governance controls within their project.
Service providers
ProArchitectOS uses third-party cloud service providers for application hosting, user authentication, project database operations, private document storage, backup operations and transactional notifications. Such providers may process information only as required to deliver and support those services, subject to applicable arrangements. Specific provider details may be supplied where required by law or through an appropriate confidential due-diligence process.
Data sharing and advertising
ProArchitectOS does not sell project files or account information to advertisers. Project information is shared through the access and distribution controls chosen within the relevant project workspace and with infrastructure providers required to operate the service.
Project closure, exports and retention
A Project Owner may place an active project into a read-only archived state. Subject to the applicable access arrangement, the Project Owner can request export packages for independent storage. These exports contain formally issued project information and other records the requesting owner is authorised to receive. Other organisations' private, unpublished working files and private communications are not automatically included. Original uploaded file formats, such as PDF and DWG, are retained in the downloadable packages where available; accompanying registers and metadata can be supplied as portable CSV or JSON files. The exported content can be stored and used independently of ProArchitectOS, without requiring a proprietary ProArchitectOS archive viewer or continuing platform subscription. Opening or editing files still requires software compatible with their normal formats.
Downloading an export does not itself delete information from ProArchitectOS. Project Owners may separately request removal of an archived project through the project management controls, after confirming that they have saved and checked the export packages. After a practice subscription expires or is cancelled, Project Owners ordinarily have a 60-day self-service exit period; suspended accounts and requests outside that period require administrator assistance. This period does not trigger automatic project deletion. Hosted, longer-term read-only retention may be arranged for a separately agreed fee and period; a quotation request does not create a paid subscription automatically.
Project records are otherwise kept while the relevant workspace is maintained, or as required by an applicable agreement or legal obligation. Removal from active storage and expiry of backup copies may occur at different times. ProArchitectOS will not claim that all backups are immediately erased when a project is deleted. Formal issue history may remain associated with a project when an individual membership ends, rather than being deleted with that user's access.
Pilot enquiry details are retained for follow-up and may be deleted following an applicable request.
Security
ProArchitectOS uses authenticated access, private project storage and project-level access controls. More information is available on the Security page.
Your choices and enquiries
Users can ask the Project Owner or ProArchitectOS administrator who invited them to correct project membership information or raise a privacy concern. Enquiries submitted through the public pilot form are sent to admin@proarchitectos.com. Existing project users may also contact their Project Owner or the administrator who issued their invitation.
Changes to this notice
This notice may be updated as ProArchitectOS develops, its infrastructure changes, or additional project workflows are introduced. The effective date above will be updated when material changes are published.