Know what runs your system.
Review deployment responsibilities, data handling and procurement materials for the system you are assessing.
What you receive during procurement.
Corporate identity
We provide corporate and tax details, identify the contracting signatory and include a service schedule when managed operation is agreed.
Scope and governance
The scope records assumptions, dependencies, acceptance criteria and the process for approving changes.
Architecture and controls
We document the architecture, operating responsibilities, data handling and access controls. Permissioned references or redacted samples are available where agreed.
Where each system runs.
| System | Source and access arrangement | Where it runs | Who operates it |
|---|---|---|---|
| StockTick | Approved financial reports, cited answers, calculations in application code | The client’s AWS environment | Managed operation confirmed in the case record |
| AuraOS | Configuration and access agreed per client; optional client-owned model keys | AURA-run infrastructure with per-client deployment and database isolation | AURA LOGIC LABS |
| SWS Community (AuraLibrary) | Administrator-approved membership, guest and member access, moderation | One shared backend across web, iOS, Android and administration | AURA LOGIC LABS hosting and maintenance |
Region, retention, subprocessors and responsibility are stated in each agreement.
Named controls and responsible AI.
Client-owned keys, PII removal and deterministic fallback are agreed per AuraOS system.
Purpose and boundaries
Define the decision the AI system supports and the limits on its actions.
Grounded sources
Keep source references so reviewers can trace outputs to approved material.
Evaluation before launch
Evaluate the system against agreed criteria before launch and assign monitoring responsibility.
Human accountability
Keep material decisions open to human review and agree the fallback when the system cannot proceed.
Data and access controls
Agree permitted data, access and retention before use, with a route for reporting incidents.
Continuity
Name the person responsible for fallback and changes after launch.
What each data processing agreement covers.
Roles and purpose
The applicable agreement covers the parties’ roles and the purpose of the processing.
Categories and retention
It covers data categories, permitted processing, security responsibilities and retention or deletion.
Transfers and third parties
It covers third parties, incident handling and transfer arrangements.
Client-controlled environment
A custom client system may run in a client-controlled environment or another agreed deployment.
Contracting entity
The website terms identify the website operator and contracting entity.
Accessibility statement.
Standard
We target WCAG 2.2 AA. We claim conformance only when testing has established it for a specific release.
Review
Reviews cover headings, keyboard access, focus, reading order, contrast, text alternatives, overflow and reduced motion.
Help
Email hello@auralogiclabs.com or contact us on WhatsApp. A human reply within six hours, any day.