Privacy Policy

Data We May Collect

Depending on how you interact with the ecosystem, data may include contact forms, account data, project data, uploaded files, technical logs, analytics data, cookies or local storage, email communications, service records, support requests, privacy requests, security reports, billing or payment records where applicable, and client-service materials.

For research, health, clinical, accessibility, prototype, or workflow systems, data may include user-provided research notes, operational context, accessibility needs, service configuration, feedback, bug reports, test data, or health-related information submitted by a client or user. Do not submit Protected Health Information, emergencies, crisis information, or highly sensitive data through public forms unless a written agreement and approved workflow are in place.

How Data Is Used

• To respond to inquiries, support requests, project requests, privacy requests, security reports, DPA requests, and BAA requests.
• To operate, maintain, secure, debug, improve, and document websites, applications, dashboards, prototypes, APIs, automations, and client services.
• To provide contracted business, research, operational, accessibility, technology, or consulting services.
• To prevent fraud, abuse, unauthorized access, misuse, spam, scraping, credential attacks, malware, and other prohibited conduct.
• To comply with applicable law, contracts, tax, accounting, security, and recordkeeping obligations.

Storage, Protection, and Retention

Data is stored using practical administrative, technical, and organizational safeguards appropriate to the service context. These may include access control, least privilege, authentication, logging, backups where applicable, encryption where applicable, and provider-level security controls.

Retention depends on the relationship and data type. Contact and support records may be retained for operational continuity. Client project records may be retained according to the applicable agreement. Security logs may be retained for abuse prevention and diagnostics. Data that is no longer needed may be deleted, de-identified, archived, or retained where required by law or legitimate operational needs.

Sharing and Service Providers

Data may be shared with service providers that help operate hosting, email, analytics, security, backups, payment processing, client services, communications, and support workflows. Data may also be shared when required by law, to protect rights or safety, to investigate abuse, or with consent or direction from a client.

Client data is not sold as a standalone product. Aggregated, de-identified, or operational analytics may be used to understand performance, safety, reliability, and product quality.

Health, Research, and BAA Availability

Some services, prototypes, or client workflows may relate to health, research, clinical coordination, accessibility, or operational decision support. The public website and general forms are not a HIPAA-regulated intake channel by default.

Audia Systems LLC maintains a Business Associate Agreement template for eligible healthcare, research, clinical, and covered-entity clients. When a service relationship involves Protected Health Information or HIPAA-regulated workflows, a BAA may be executed before PHI is processed, transmitted, stored, or accessed through Audia Systems LLC services.

BAA available for eligible HIPAA-regulated workflows. This page does not claim HIPAA compliance for all services or public website features.

Access, Correction, Deletion, and Contact

You may request access, correction, export, deletion, or restriction of data where applicable by using the contact page, the support page, or email at [email protected]. Requests may require identity verification and may be limited by legal, security, backup, contractual, or operational obligations.

General business and support messages may be sent to [email protected]. Legal, privacy, security, DPA, and BAA requests should use [email protected] when email is appropriate.