Privacy Policy
How the Gwyn Legacy ecosystem handles information across websites, applications, dashboards, prototypes, APIs, and client services.
Last Updated: May 8, 2026
Entity notice: Operated by Audia Systems LLC, DBA Bailey Enterprises, within the broader GLC / Gwyn Legacy ecosystem.
Information provided through this website, application, dashboard, prototype, or service is for general informational, operational, research, or business purposes only. It is not medical, legal, financial, emergency, or professional clinical advice unless separately agreed in a written contract.
Do not use this website, application, dashboard, form, or service for medical emergencies, safety emergencies, crisis situations, or urgent support needs. For emergencies, contact local emergency services or an appropriate licensed professional.
Scope
This Privacy Policy applies to public websites, applications, APIs, PWAs, dashboards, mobile experiences, prototypes, operational tools, and client services operated by Audia Systems LLC, DBA Bailey Enterprises, within the broader GLC / Gwyn Legacy ecosystem.
AUDIA, the Adaptive Unified Distributed Intelligence Architecture, is an intelligence architecture and platform ecosystem operated by Audia Systems LLC, DBA Bailey Enterprises.
Institute for Civil Memory is a nonprofit-oriented initiative within the GLC / Gwyn Legacy ecosystem. It is not currently filed as a separate nonprofit entity and is not currently soliciting or collecting donations.
Information We May Collect
- Contact form details, messages, email communications, and support requests.
- Account data, authentication records, organization details, preferences, and service records.
- Project data, uploaded files, documents, research materials, prototype inputs, client instructions, and workflow data submitted to services.
- Technical logs, device/browser data, IP-derived diagnostics, analytics events, cookies, local storage, session storage, and security logs.
- Health, research, clinical, or prototype data only where a user or client intentionally provides it for an eligible workflow.
How We Use Information
- Operate, secure, maintain, debug, and improve websites and services.
- Respond to contact, support, privacy, security, accessibility, BAA, and DPA requests.
- Deliver client services, prototypes, dashboards, research workflows, integrations, APIs, and operational automation.
- Maintain records, enforce terms, prevent abuse, monitor reliability, and satisfy legal or contractual obligations.
Storage, Protection, and Retention
Reasonable administrative, technical, and operational safeguards are used based on the sensitivity and context of the information. Safeguards may include access controls, least privilege, backups where applicable, monitoring/logging where applicable, and encryption in transit or at rest where supported by the service design.
Retention periods vary by service, contract, operational need, legal obligation, and backup cycle. Data may be deleted, anonymized, exported, or retained as required for security, dispute resolution, compliance, or service continuity.
Sharing and Service Providers
Information may be shared with infrastructure providers, hosting providers, analytics or security services, professional advisors, client-authorized integrations, or authorities where legally required. Data is not sold as a standalone product.
For eligible HIPAA-regulated clients, a Business Associate Agreement may be available before Protected Health Information is processed, transmitted, stored, or accessed.
Your Choices and Requests
You may request access, correction, deletion, export, restriction, or clarification using the Contact or Support page. Some requests may require identity verification or may be limited by legal, contractual, security, backup, or operational requirements.
Contact, support, privacy, accessibility, security, DPA, and BAA requests are routed through [email protected]. Do not include passwords, payment details, PHI, emergency information, or highly sensitive regulated data in general email unless a secure workflow has been established.