Orygent Accessibility and Assistance Statement
1. Commitment
1.1 SMARTEDTECH SL designs the public pages and the Orygent application to be usable with keyboard navigation, visible focus, meaningful headings, text alternatives for images, labelled form controls, readable contrast and status information that does not rely on colour alone.
1.2 The Operator uses WCAG 2.2 level AA as its design and testing benchmark. This statement describes the current state; it is not a conformance certificate.
2. Current status
2.1 The Operator maintains an accessibility issue register for orygent.com listing the routes tested, the assistive technologies used, the known barriers and the planned remediation. The register is updated at each release that changes a tested journey.
2.2 Third-party components (payment checkout, authentication, support chat) are provided by their vendors; the Operator records their published accessibility statements in the register and routes barrier reports to the vendor where the barrier sits in the vendor's component.
2.3 Legal documents and acceptance controls are rendered as accessible text and native form controls. An inaccessible control is never the only way to read the terms, accept them or ask for help; support@orygent.com is always available as an alternative route.
3. Reporting a barrier
3.1 Report the page, the action you were attempting and the assistive technology you use to support@orygent.com. Do not include passwords, payment credentials or sensitive personal records in the message.
3.2 The Operator acknowledges within 2 business days, offers an accessible alternative for an essential function where one exists, and records the barrier in the register.
3.3 Nothing in this statement limits your rights under accessibility or consumer law.
4. Change control
4.1 A new release, theme, language or embedded provider triggers a re-check of the affected journeys before the registry version of this statement is updated.
4.2 Each version is archived with its date and content hash at the versioned archive route of this document.
Platform-specific terms
Enterprise AI operations
1. The customer appoints tenant administrators who manage users, authority levels and data classes within the tenant. Actions with legal, financial or employment effect require approval by a human with the configured authority before execution; the service does not execute them automatically.
2. Employee data processed in the tenant is processed under the customer's instructions as controller; the DPA (DAT-01) applies.
3. Outputs are recommendations and drafts; decisions are the customer's.
---
AI services: disclosure, limitations and human escalation
1. Disclosure. Where you interact with an AI system (chat, voice, agent, digital twin or generated content), the Operator tells you so at the start of the interaction and labels AI-generated or AI-manipulated content in accordance with Article 50 of Regulation (EU) 2024/1689. A voice or persona representing a real person is used only with that person's recorded permission.
2. Nature of outputs. AI outputs are generated from models and data that can be incomplete or wrong. They are information and assistance, not professional advice, and not a decision of the Operator. You remain responsible for decisions you take on the basis of an output. Where a decision has legal, financial, medical, educational or safety effect, the service routes it to a human reviewer or to you for decision, and the Operator does not make that decision automatically.
3. Human escalation. You may at any time request a human review of an AI interaction through support@orygent.com or the in-product escalation control; the Operator responds within 5 business days (consumer) or within the SLA (business).
4. Permitted use. You will not use AI features to impersonate a person without permission, to generate unlawful content, to circumvent safety controls, or to extract or reverse-engineer models. The Operator may suspend AI features for breach.
5. Recording and model use. Recordings, transcripts and uploads are used to provide the service to you. They are used to improve models only with your separate permission (purpose research_contribution), which you may withdraw at any time without affecting the service.
---