How Claimaro collects, uses, shares, and protects information — including Protected Health Information handled under HIPAA Business Associate Agreements.
Last updated: July 31, 2026
Quick read: Claimaro is built for HIPAA-regulated workloads and serves health plans and sharing ministries. We process PHI only under signed Business Associate Agreements and run on SOC 2 Type II-audited infrastructure. We don't sell personal data. You can request export or deletion of your data at any time.
Claimaro ("Claimaro," "we," "us," or "our") is a software platform operated by Nexopic, Inc. that provides claims administration, enrollment, member portal, payments, and CRM tools to self-funded health plans, healthcare sharing ministries, third-party administrators (TPAs), and similar organizations ("Customers"). Members and other end users of our Customers' platforms are referred to as "Members."
This Privacy Policy describes how we collect, use, share, and protect information through (a) our marketing website at claimaro.com, (b) the Claimaro application at app.claimaro.com, and (c) any related services (collectively, the "Services").
When a Customer uses Claimaro to administer benefits or process medical needs, we receive and process Protected Health Information ("PHI") on the Customer's behalf. This may include: name, date of birth, address, phone, email, government ID, dependent details, plan/group identifiers, eligibility, claims and Explanation of Benefits (EOBs), provider and procedure codes, payment instruments, and member communications.
We process PHI only as a Business Associate of the Customer (or its covered entity / health plan) under a signed Business Associate Agreement ("BAA"). The Customer is the data controller for Member PHI; we are the data processor.
We do not sell personal data. We share information only as follows:
Claimaro acts as a Business Associate to Customers that are HIPAA-covered entities or to other Business Associates. For PHI:
Claimaro maintains a control environment aligned to the SOC 2 trust services criteria: security, availability, confidentiality, and processing integrity. Controls include: encryption everywhere, secrets management, vendor risk reviews, change management, dependency vulnerability scanning, PII masking with audited reveal, and incident response procedures. We have not yet completed a formal SOC 2 audit; documentation of our controls is available to qualified Customers under NDA. See our Security page for detail.
We retain Customer Data and PHI for as long as the Customer's account is active and as required to provide the Services. On termination, we follow the deletion or return obligations set out in the Master Subscription Agreement and BAA — typically returning a complete data export and then deleting Customer Data within 30–90 days, except where retention is required by law (e.g., financial records). Aggregated, de-identified data may be retained indefinitely.
Customers and Members may exercise the following rights, subject to verification and applicable law (including HIPAA):
For Member PHI, requests should generally be directed to the Customer (the covered entity / plan) — but you can also email us at privacy@claimaro.com and we'll route as appropriate.
The marketing website uses essential cookies and privacy-respecting analytics. We do not use third-party advertising trackers or build cross-site profiles. You can disable cookies in your browser; some site features may not work correctly if you do.
The Services are not directed to children under 13, and we do not knowingly collect personal data directly from children. PHI of dependents covered under a plan is provided by the plan administrator or member-parent under the Customer's authority.
Claimaro's infrastructure is hosted in the United States. If you access the Services from outside the U.S., you understand that your information will be transferred to and processed in the U.S. We use contractual and technical safeguards consistent with applicable data protection laws.
We may update this Policy from time to time. Material changes will be communicated by email to account administrators or via an in-app notice at least 30 days before they take effect. The "Last updated" date at the top reflects the latest revision.
Questions about this Policy, BAA requests, or data subject requests: