Current facts, responsible use and clearly separated roadmap direction.

Invited users sign in to an authorised personal workspace. The current product provides two project origins, preserves project and workflow state, generates structured planning and assessment documents, and supports eligible individual Markdown downloads.

Public self-registration is not currently offered. Requesting access does not create an account or guarantee an invitation.

Authentication gates the current application. Saved projects, workflow state and generated documents are associated with the authorised workspace, and eligible downloads require authenticated access.

This description is not a security certification or proof that every possible authorisation condition has been formally audited.

The current product organises user-provided project information through structured new-project and existing-project workflows. It does not currently present the application as a repository, credential, private-source-code, regulated-data or raw Production-log intake system.

Use the minimum non-sensitive context required for planning and assessment.

Planning, assessment, roadmap and developer-handoff documents depend on the completeness and quality of the saved project information. They remain drafts for human review.

Readiness, confidence, evidence strength, risk, assumptions, missing information and recommended next actions are advisory. They do not independently prove technical, security, legal, financial or Production readiness.

The Product Updates form submits an email address and explicit consent to begin Brevo double opt-in. A subscription becomes active only after the recipient confirms it by email.

The marketing website does not use a local subscriber database for this flow. Subscribing does not request or grant application access.

The current product does not autonomously inspect repositories, execute code, repair software, run user-project tests or builds, create pull requests, deploy projects or certify technical, security, legal, financial or Production readiness.

Repository-aware work, execution, independent verification, Tested Preview and launch orchestration are described only through their approved development and roadmap states.

Airchor does not currently claim SOC 2 or ISO certification, blanket GDPR compliance, a security audit, penetration testing, vulnerability scanning, specific encryption guarantees, complete data-residency coverage, backup or disaster-recovery commitments, incident-response times, uptime, enterprise security, or formal retention and deletion periods.

Affirmative security-control, provider, retention, deletion and transfer statements require separate evidence and approval.

The current marketing website does not establish live repository, provider or deployment orchestration. Visitors should keep credentials, repositories, provider accounts, domains and Production systems under their own authorised control.

Customer ownership and provider neutrality are product principles whose individual integrations are governed through the roadmap.

Airchor publishes interim legal and operator information while the operating structure remains unresolved. Complete entity, controller and contractual details will be added only after they are established and approved.