Legal and trust center
This hub collects the current public legal, privacy, accessibility and AI-transparency boundaries for AVC. It deliberately distinguishes what is implemented from what remains a production-launch blocker.
Explore the trust surfaces
- Privacy — processing boundaries, rights, recipients and current data-protection blockers.
- Cookies — current tracking state and the consent boundary before non-essential technologies are enabled.
- Terms — public-alpha usage terms and the boundary before commercial customer contracting.
- Accessibility — current engineering target, verification limits and feedback blocker.
- AI Transparency — AI interaction disclosure, human ownership and use-case-specific compliance limits.
Privacy
The public privacy notice describes the current marketing origin, protected login handoff, technical request/security data, infrastructure processing, data-subject rights and known contact, retention and international-transfer limitations.
Cookies and tracking
The current public source does not intentionally include analytics pixels or marketing trackers. Non-essential tracking remains disabled until an appropriate consent mechanism is implemented where required.
Terms
The current terms govern the public-alpha informational and protected-access surfaces. They are explicitly not customer sales, subscription, checkout or service-level terms.
Accessibility
AVC uses WCAG AA-oriented engineering principles for the public experience, with automated checks and semantic interaction patterns. The current statement does not claim independent certification or complete statutory conformity across every AVC application.
AI transparency
AVC discloses its AI-native nature, preserves human ownership and defines the boundary for direct AI interaction, generated content, model limitations and use-case-specific compliance.
Security
The public origin publishes a security.txt endpoint and the platform exposes a source-backed security surface. Security reporting is separate from the missing general privacy/contact channel and must not be treated as a substitute for it.
Machine-readable compliance state
AVC publishes the current public legal surfaces, explicit non-claims and production blockers as JSON so release checks can fail closed when the public compliance state drifts from the human-readable notices.
What is still missing
- Verified legal-entity or trading-entity identification for commercial operation.
- Verified CVR where applicable.
- Verified public physical business address where required.
- A verified public contact email and dedicated privacy/accessibility contact path.
- Provider retention periods mapped to the deployed processing paths.
- International-transfer inventory and applicable safeguards for the deployed providers.
- Commercial customer, pricing, payment, subscription and cancellation terms before paid checkout.
- Consent controls before non-essential tracking is enabled where consent is required.
- Use-case-specific AI Act classification and verification before production approval.