High-level terms Archetern.dev applies to custom software, web properties, and long-term operations. A full Statement of Work or MSA is provided before kickoff; this page is the non-binding overview clients see up front.
archetern.dev is a commercial engineering property within the broader Archetern family, together with archetern.com, archetern.cloud, and archetern.io. Domains may host different roles (public presence, cloud edge, R&D identity), but represent one engineering and brand continuum unless a signed contract states otherwise for a specific deliverable.
We process personal data only on documented instructions, apply data minimisation, support access / rectification / erasure requests, maintain processing records where required, and default to EU-friendly hosting when you do not specify otherwise. Sub-processors are disclosed before they touch production data. Data Processing Agreements (DPA) are available for B2B engagements.
Production code is version-controlled, reviewed for correctness and security hotspots, and structured for testability. We document public APIs, error handling, and deployment steps so your team or ours can operate the system without guesswork. Technical debt is tracked; critical paths are not “magic folders” on a single laptop.
Inputs are validated and encoded on output; authentication flows use industry-standard primitives; secrets never belong in the repository. We favour least-privilege access, CSRF protection on state-changing operations, secure session configuration, and TLS in transit. Dependencies are updated on a defined cadence; known CVEs in our stack are patched urgently.
Where we implement auth, we recommend strong factors (passkeys / WebAuthn, session-bound MFA) and monitoring of anomalous sessions. We help configure mail and DNS records (SPF, DKIM, DMARC) for outbound domain trust and can harden admin URLs, rate limits, and alerts on credential stuffing patterns. We do not guarantee zero incidents; we design for detection, containment, and audit trails.
Unless a contract states otherwise, you own the deliverables you paid for after cleared invoices. Third-party licenses (fonts, libraries, SaaS) remain under their respective terms. Acceptance is based on agreed acceptance criteria and defect SLAs in the SOW — not informal chat.
Last updated: May 2026. For the binding text, request the full agreement from contact@archetern.dev.