Effective July 6, 2026; updated November 2, 2026
Privacy Notice
This Notice explains how Charm ABA handles account information, operational data, approved real-record workflow data, and how our public website measures visits. PHI processing is limited to approved users, approved workflows, and covered vendor paths.
1. Who We Are
Charm ABA is operated by Indy Toy Lab LLC d/b/a Charm ABA. We provide software that helps authorized ABA and behavioral-health users create treatment-plan drafts for qualified clinician review.
2. Information We Process
- Account information, such as name, email, authentication state, organization, role, and provider contact details you enter.
- Operational metadata, such as plan IDs, user IDs, timestamps, processing status, audit events, payment/download status, and PHI-free support notes.
- Website and app activity data, recorded for each page you view: IP address, approximate location derived from the IP address, browser user agent, referring page, page path, a random visitor identifier stored in a first-party cookie, timestamps, and, when you are signed in, your account and app path. We use it for admin reporting, abuse prevention, testing, and account security.
- Uploaded source files, extracted text, generated drafts, final documents, and finalization answers, but only for approved workflows and subject to PHI controls when PHI mode applies.
- Payment and checkout metadata handled through our payment processor. We do not intentionally store payment card numbers in Charm ABA.
- Security, diagnostic, and log data designed to avoid PHI content and secrets.
3. PHI Workflow Controls
Do not upload PHI unless your account has been expressly approved for real-record workflow use and any required Business Associate Agreement or PHI terms are in place. In PHI mode, durable PHI artifacts are intended to be stored in the approved AWS S3 PHI storage path. Supabase is intended to hold authentication, ownership, status, audit, and opaque object-key metadata, not PHI content.
- Use the minimum necessary information for the approved treatment-plan workflow.
- Use one client packet per plan unless we approve a broader scope in writing.
- Do not send PHI through email, chat, screenshots, SMS, or ordinary support channels.
- We may restrict or suspend PHI processing if we suspect unauthorized use, system risk, vendor risk, legal risk, or a privacy/security incident.
4. How We Use Information
- To provide, operate, secure, monitor, and improve the Service.
- To authenticate users, enforce access controls, and prevent unauthorized use.
- To process uploaded materials into clinician-review drafts for the approved workflow.
- To provide payment, reporting, download, support, audit, incident-response, and compliance functions.
- To understand how visitors find and use our public website and content pages, and to improve them.
- To meet legal, contractual, security, and operational obligations.
5. Cookies, Analytics, And Website Measurement
- Our own visitor log. A first-party cookie named app_visitor_id holds a random identifier for up to one year so we can tell repeat visits apart. The log records the activity data described in section 2 on charmaba.com pages outside the /learn content pages, and only Charm ABA administrators can see it.
- Google Analytics 4. We use Google Analytics on our public pages only: the home page, the sign-up and sign-in pages, the Terms, Privacy, Business Associate Agreement, and legal pages, and the content pages at charmaba.com/learn. It is not loaded on the signed-in application, it is switched off whenever you move from a public page into the application, and it never receives uploaded files, plan content, PHI, your name, or your email address.
- What Google Analytics collects on those pages: the pages viewed, the referring site and any campaign tags in the link, approximate location, device, browser, and screen type, engagement such as time on page, scrolling, outbound link clicks, and file downloads, and a sign-up event when an account is created, without any account identifier. It sets first-party cookies named _ga and _ga_ followed by our property code, which last up to two years. Google Analytics does not log or store IP addresses.
- Google signals and ad personalization are turned off, and we do not use Google Analytics data for advertising. Google keeps event-level Analytics data for no longer than 14 months.
- Your choices. If your browser sends a Global Privacy Control signal, we do not load Google Analytics. You can also block cookies in your browser settings or install Google's Analytics opt-out browser add-on at tools.google.com/dlpage/gaoptout.
- Our hosting provider, Vercel, also measures aggregate page views and page performance with Vercel Web Analytics and Speed Insights, which do not use cookies.
6. Vendors And Subprocessors
We use vendors and infrastructure providers to operate the Service. For approved PHI workflows, we intend to use only approved vendor paths with appropriate HIPAA/BAA posture or to keep vendors outside the PHI boundary. Our current intended PHI architecture uses AWS for PHI artifact storage, Vercel for production application hosting, OpenAI API under the approved healthcare/ZDR posture for model processing, Supabase for non-PHI operational metadata, and Stripe for PHI-free payment metadata. Google provides Google Analytics for our public pages only; it sits outside the PHI boundary and receives no PHI.
7. OpenAI And AI Processing
For approved PHI workflows, Charm ABA is intended to route OpenAI API calls only through the approved organization/project and configured privacy posture. We do not intentionally use OpenAI web browsing, third-party tools, vector stores, Assistants/Threads, Code Interpreter, or direct file inputs for PHI unless separately approved.
8. Security
We use technical, administrative, and operational safeguards designed for the approved workflow, including access controls, audit events, object-key-only metadata posture, private storage, encryption where configured, and PHI-free support rules. No internet service can guarantee absolute security.
9. Retention And Deletion
We retain information for as long as needed to provide the Service, support the workflow, meet legal or contractual obligations, resolve disputes, preserve security evidence, enforce agreements, and maintain audit trails. PHI retention, return, deletion, or destruction may be subject to a Business Associate Agreement or customer agreement.
10. Customer And User Responsibilities
- Upload only information you are authorized to provide.
- Keep account credentials secure and use individual accounts only.
- Review generated output before use and do not rely on the Service as final clinical judgment.
- Do not include PHI in ordinary support messages.
- Notify us promptly if you suspect unauthorized access, misdirected data, or PHI in an uncovered channel.
11. Individual Rights And Covered Entity Requests
When we process PHI as a business associate, individual-rights requests should generally be handled through the covered entity or provider customer. We will support covered-entity requests as required by the applicable Business Associate Agreement and law.
12. Changes
We may update this Notice by posting a revised version. Material changes to approved PHI workflows may require additional customer notice, agreement, or approval depending on the applicable contract.