Is Agenzo AI HIPAA compliant?
No. As of November 1, 2026, Agenzo AI does not claim HIPAA compliance and does not currently offer a Business Associate Agreement (BAA). Early-access workflows must not receive, store, or transmit protected health information (PHI).
This page states what the current public website, demo, and early-access workflows can—and cannot—be used for.
Current product status
The marketing website and early-access forms are live. The interactive workspace is a browser-only demonstration that uses sample data and creates no account. Any live pilot must be separately reviewed and configured with the medspa before activation.
Supported early-access scope
The intended scope is routine business information such as public services, opening hours, location, general availability, and non-clinical booking or callback requests. The final workflow and escalation rules must be reviewed before a pilot.
Information that is not supported
Do not submit patient names with treatment context, symptoms, diagnoses, treatment history, insurance information, adverse reactions, prescriptions, clinical photographs, or emergency information through the public website, demo, or an early-access workflow.
BAA and HIPAA scope
Workflows requiring Agenzo AI or its vendors to receive, store, or transmit PHI are not supported at this stage. Whether information is PHI depends on its context; medspas should review their proposed workflow with qualified privacy and legal advisers. See the U.S. HHS guidance on business associates.
Public forms and demo data
Public contact and early-access forms are processed through our website hosting provider. The interactive demo stores its configuration in the visitor's browser local storage and does not send those demo answers to an Agenzo AI account. Do not enter patient or medical information in either channel.
Security measures on this website
The site uses HTTPS and response headers that restrict framing, content types, browser permissions, and referrer data. We also use data-minimizing public forms, spam protection, and clear no-PHI instructions. No internet service can guarantee absolute security.
Before a production healthcare workflow
A production workflow that could involve protected health information requires a separate technical architecture review, vendor review, access-control plan, retention and deletion rules, incident procedures, and appropriate contracts before activation.
Questions
For a data-handling question about a proposed workflow, email support@agenzo.app. Do not include patient information in your message.