Close-up of the sculptural concrete Arc, lit by warm natural light.

SECURITY & DATA

YOUR PROJECTS.
OUR RESPONSIBILITY.

YOUR PROJECTS.
OUR RESPONSIBILITY.

YOUR PROJECTS.
OUR RESPONSIBILITY.

Project information deserves thoughtful protection. Learn how Project Arc approaches data hosting, access, integrity, and responsible platform development.

01 / BUILT WITH CARE

The record behind
the built environment.

The record behind
the built environment.

The record behind
the built environment.

The drawings, decisions, and records behind a project deserve more than an afterthought.

A shared project record brings together information from people with different responsibilities. The right deployment discussion starts with what that information contains, who needs it, and the obligations attached to it.

02 / WHERE YOUR DATA LIVES

Clear answers.
Specific arrangements.

Clear answers.
Specific arrangements.

Clear answers.
Specific arrangements.

Hosting is more than a database location. Ask us to confirm the current arrangements for your proposed deployment before introducing confidential project information.

Production residency and service-provider details are pending verification. We do not currently make a Canadian-only data-residency promise.

01

Primary database & files

02

Authentication & application hosting

03

Backups & recovery

04

Logs, analytics & third-party processing

03 / ACCESS & PERMISSIONS

Shared information.
Clear boundaries.

Shared information.
Clear boundaries.

Shared information.
Clear boundaries.

Firm roles, project roles, and external collaboration are distinct access considerations. Current permission coverage and organization boundaries should be validated for the agreed deployment.

04 / DOCUMENT INTEGRITY

The original.
The revision.
The context.

The original.
The revision.
The context.

The original.
The revision.
The context.

Ask how the current platform handles original files, drawing revisions, annotations, exports, and retention. Original-document preservation and revision behavior require implementation verification before we make a specific public commitment.

05 / SECURITY IN PRACTICE

A concrete place to begin.

A concrete place to begin.

A concrete place to begin.

The website’s demo-request form uses HubSpot to manage enquiries. These checks apply to the website form; customer-workspace security and deployment arrangements require separate verification.

01

A dedicated enquiry form

Demo requests are sent to the configured HubSpot form, with mapped contact and enquiry fields.

02

Credentials stay out of the page

The demo form uses public form identifiers. No HubSpot private access token is placed in its client code.

03

A checked submission path

The form checks required details and reports a failed submission before confirming receipt.

04

A separate marketing choice

Requesting a demo asks us to respond to your enquiry. It does not subscribe you to unrelated marketing.

06 / OUR APPROACH TO TRUST

Trust is ongoing work.

Trust is ongoing work.

Trust is ongoing work.

Testing, review, and responsible development belong throughout a platform’s life. This page distinguishes verified website behavior from application controls and deployment arrangements that still require evidence.

No certification, independent audit, penetration-test result, uptime guarantee, or recovery commitment is asserted here.

QUESTIONS ABOUT SECURITY?

QUESTIONS ABOUT SECURITY?

QUESTIONS ABOUT SECURITY?

Tell us what your organization needs to evaluate.

© 2026 Project Arch Technologies Inc.

ONE PROJECT. EVERY PHASE. EVERYONE ALIGNED.

© 2026 Project Arch Technologies Inc.

ONE PROJECT. EVERY PHASE. EVERYONE ALIGNED.

© 2026 Project Arch Technologies Inc.

ONE PROJECT. EVERY PHASE. EVERYONE ALIGNED.