# Doc: https://www.hipaatizer.com/docs/account > LLM view for https://www.hipaatizer.com/docs/account This file contains all documentation content in a single document following the llmstxt.org standard. ## Account ## Account Types in HIPAAtizer HIPAAtizer offers two types of accounts: **Covered Entity (CE)** and **Free Sandbox (Developer)**. Each is designed for different use cases and levels of compliance. --- ## Free Sandbox (Developer) Account The Free Sandbox account is intended for web developers and agencies who want to explore, test, or manage HIPAAtizer on behalf of their clients. - Not HIPAA-Compliant - No Business Associate Agreement (BAA) with HIPAAtizer - Suitable for experimenting, building, and testing forms - Can invite Covered Entity (CE) clients to use HIPAAtizer - Ideal for agencies managing multiple CE clients under their developer account - Can also invite other developers to collaborate A Developer account can later be converted into a Covered Entity account if needed for production use. --- ## Covered Entity (CE) Account The Covered Entity account is fully HIPAA-Compliant and designed for healthcare providers and organizations handling Protected Health Information (PHI). - Includes a signed Business Associate Agreement (BAA) with HIPAAtizer - Comes with a 30-day free trial - Can invite team members and assign them roles: - Security Officer - Assistant - Developer - Designed for production environments requiring PHI security and compliance --- ## Account Collaboration Overview | Account Type | Can Invite CE Clients? | Can Invite Developers? | HIPAA-Compliant? | |---------------------|-----------------------------|-------------------------|------------------| | Developer Account | Yes | Yes | No | | Covered Entity | No | Yes (team members) | Yes | --- Choose the account type based on your role and needs: - Select **Developer** if you are a web developer or agency building and managing forms for CE clients. - Select **Covered Entity** if you are directly handling PHI and need HIPAA compliance.