Security

We treat security as a design constraint from the first architectural decision, not a layer added before launch. Every system we design accounts for authentication, authorization, data protection, and failure modes as structural requirements.

Our own systems and the client platforms we build use encryption in transit (TLS) and, where applicable, encryption at rest, with network segmentation and least-privilege access controls governing who can reach what.

We run dependency and vulnerability scanning as part of our development workflow, and we design access controls, input validation, and audit logging into the applications we build rather than retrofitting them.

We collect and retain only the data necessary to operate our website and deliver client work, and we apply the access controls and retention practices described in our Privacy Policy to the information we hold.

If you believe you've discovered a security vulnerability affecting Archigor's website or systems, we want to know. Please report it to [email protected] with enough detail to reproduce the issue. We will acknowledge your report and keep you informed as we investigate, and we ask that you give us a reasonable opportunity to address any issue before public disclosure.

Security requirements for client work, including any compliance frameworks relevant to a client's industry (such as healthcare or financial data handling), are scoped and documented as part of the engagement's statement of work rather than assumed by default.