Privacy Policy

Scope and identity

This policy applies to Bailey Enterprises, AUDIA-related services, TraceLayer/Visibility Engine surfaces, client systems, prototypes, dashboards, forms, and support interactions operated by Audia Systems LLC, DBA Bailey Enterprises.

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, name, organization, role, email address, phone number, and scheduling information where submitted.
• Account data, login identifiers, preferences, permissions, and authentication records where accounts are provided.
• Project data, uploaded files, documents, notes, requirements, prompts, outputs, research materials, operational records, and service history.
• Technical logs, device/browser information, IP address, timestamps, diagnostic data, API activity, security events, analytics, cookies, local storage, and session storage.
• Email communications, support requests, bug reports, privacy requests, security reports, and BAA/DPA requests.

Health, research, prototype, and sensitive data

Some prototypes or client services may involve health, research, clinical, educational, operational, or other sensitive workflows. Do not submit Protected Health Information, regulated clinical data, or highly sensitive data through general website forms unless a written agreement and appropriate workflow have been established.

A Business Associate Agreement may be available for eligible HIPAA-regulated clients and workflows. BAA may be available for eligible HIPAA-regulated clients before Protected Health Information is processed, transmitted, stored, or accessed through eligible services. We do not claim HIPAA compliance for every website, prototype, dashboard, or service by default.

How information is used

• Responding to inquiries, scheduling, support, project intake, and service delivery.
• Operating, improving, debugging, protecting, and documenting websites, applications, APIs, dashboards, prototypes, and client systems.
• Maintaining service records, billing records where applicable, legal/compliance records, security logs, and business communications.
• Developing internal knowledge, documentation, automation, and infrastructure while respecting contractual, confidentiality, and privacy obligations.

Storage, protection, retention, and deletion

Information may be stored in website databases, project systems, client workspaces, email systems, logs, backups, local development environments, and approved service providers where applicable.

Reasonable administrative, technical, and organizational safeguards are used, including access control, least privilege, backups where applicable, logging/monitoring where applicable, and encryption where supported by the relevant system.

Retention depends on the type of data, client relationship, legal obligations, security needs, and operational requirements. Deletion or export requests may be submitted through the contact or support routes, subject to legal, security, backup, and contractual limits.

Sharing and service providers

Information may be shared with service providers, infrastructure providers, payment/scheduling/email tools, professional advisors, or client-authorized systems as needed to operate services. Information may also be disclosed where required by law, to protect rights/security, or as part of a business transfer.

We do not sell personal information as a standalone business model. Additional privacy disclosures may be provided when a specific service, client relationship, jurisdiction, or written agreement requires them.