Contact and communications
Name, email address, organization, message content, support requests, early-access requests, email communications, and service records submitted through forms or direct business communications.
Privacy Policy.
This policy explains how TraceLayer and related Audia Systems LLC services may handle information across websites, apps, dashboards, APIs, prototypes, and client services.
Last Updated: May 8, 2026
Operating identity
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.
General disclaimer
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.
Emergency disclaimer
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.
Data we may collect
Account and project data
Account identifiers, license state, workspace preferences, project metadata, site records, publishing queues, working copies, service configuration notes, and client-provided operational details.
Uploaded and generated files
Files, images, documents, exports, reports, backups, snapshots, previews, generated pages, logs, and other material that a user or client chooses to upload or generate through a service.
Technical data
IP address, device/browser information, timestamps, request paths, error events, security events, API activity, diagnostic logs, local storage state, cookies, session storage, and analytics or visibility reports where enabled.
Health, research, and prototype data
Some prototypes or client workflows may involve health, research, clinical, educational, disability, or sensitive operational contexts. Do not submit PHI or regulated sensitive data unless a written agreement and applicable controls are in place.
Cookies and local storage
The site and applications may use cookies, local storage, session storage, preference storage, license/session state, and security-related browser storage. See the Cookie Policy for more detail.
How data is used
Information may be used to operate websites, applications, APIs, PWAs, dashboards, mobile apps, prototypes, and client services; respond to contact and support requests; manage access; provide downloads; maintain security; improve product workflows; generate reports; troubleshoot errors; and document service activity.
TraceLayer may process client project data only as needed to provide requested services, support, implementation, diagnostics, audits, publishing workflows, data exports, or contractual deliverables.
BAA availability: a Business Associate Agreement may be available for eligible HIPAA-regulated clients before PHI is processed, transmitted, stored, or accessed through Audia Systems LLC services.
Sharing
Data may be shared with service providers, infrastructure providers, contractors, professional advisors, or authorities when needed to operate services, comply with law, protect rights and security, or fulfill a client relationship. Data is not sold as a standalone product.
Retention and deletion
Data is retained only as long as reasonably needed for operations, support, legal, security, backup, audit, contractual, or business purposes. Deletion/export requests may be sent through Contact or Support, subject to legal, security, backup, and contractual limits.
Protection and storage
Protection
Practical safeguards may include access control, least privilege, server-side handling of secrets, TLS where applicable, logging, backup practices, local-first workflows, review gates, and separation of public and private surfaces.
Storage locations
Data may be stored on local systems, self-hosted servers, cloud providers, email/support systems, project storage, backup locations, or client-designated infrastructure, depending on the service relationship.
Your choices
You may request access, correction, export, deletion, or restriction of certain information by using Contact or Support. Identity verification and contractual review may be required.