Skip to content

Compliance

What we hold ourselves to, and how you can check.

HIPAA and the SHIELD Act are the floor. This page says what is built, what is in progress, and whom to email when something is not right.

Effective November 15, 2026. Questions: hello@trycarepair.com.

01HIPAA

CarePair Technologies LLC runs CarePair, and Cardinal Care Advisors LLC ("Cardinal"), a partner firm under common ownership, provides the Cardinal services. Cardinal handles protected health information as a business associate of the hospitals and skilled nursing facilities that refer patients for discharge planning, and signs a business associate agreement with each of them before any patient record is sent. A senior living community or care organization covered by HIPAA that uses CarePair to receive information about its residents can ask for one, and we sign it. We have business associate agreements in place with Amazon Web Services, which runs every part of the service that stores health information, and with Google Workspace, which carries our staff's email and calendar.

HIPAA is not a certification, and we do not claim one. These are the safeguards as built:

  • Encryption in transit (TLS 1.2 or better) and at rest (database and file bucket under AWS KMS), with per-document and per-record data keys on top for documents and sensitive fields.
  • Role- and row-level authorization on every server action: a family sees its own case, a community sees only what was sent to it, a hospital sees the cases it referred.
  • An append-only audit log of every read and write of health information: who, what, which fields, when, from where.
  • Two-step sign-in for every staff, community, and partner login; a 30-minute idle timeout for those sessions; a session list with revoke.
  • Minimum necessary by design: staged disclosure means financial details are collected only after a bed is offered and go to one community; physician forms pass through and are purged; face sheets from referring facilities are upload-only for the planner and deleted on a short clock; Social Security numbers, driver's licenses and photo IDs, card numbers, and account numbers are refused and never stored. Insurance and Medicare member numbers are accepted only in a family's own care binder, encrypted with their own key and shown as the last four digits, and only the family's care circle can open them.
  • No health information in email subjects or bodies, text messages, logs, or analytics.
  • Written policies (information security, access control, incident response, vendor management, retention, acceptable use, change management, continuity, risk, training) with named owners and review dates.

02New York SHIELD Act

The SHIELD Act requires reasonable administrative, technical, and physical safeguards for New York residents' private information and notification when it is breached. The safeguards above are ours. Our incident response policy sets the clock: contain first, write the first note within the hour, scope it from the audit log, then notify affected people in the most expedient time possible and the New York Attorney General, the Department of State, and the State Police as the Act requires, and the HHS Office for Civil Rights where HIPAA applies, each within the statutory deadline. A referring facility is told the same day. We keep a written record of every incident.

03SOC 2

SOC 2 is an auditor's report on our controls, not a self-declaration. We are building toward it: the ten policies are written, the controls they describe are the ones in the code and the AWS stack, and evidence collection follows. We expect a Type I report first and a Type II after the observation period. Until an auditor has signed, we say in progress, not certified. Hospital and enterprise partners can ask for our current control list and the evidence behind any item.

04Accessibility

We want everyone who cares for an older adult to be able to use CarePair, including people who use a screen reader, a keyboard alone, magnification, or voice control. Our target is WCAG 2.1 Level AA across the public site and the app: semantic structure, visible focus, sufficient contrast, labels on every control, one primary action per screen, and text that works at 200 percent zoom.

If you hit a barrier, email hello@trycarepair.com with the page and what happened. We reply within five business days, fix what we can quickly, and give you another way to do the task in the meantime.

05Electronic signatures

Agreements in CarePair are signed by ticking the stated consents, typing your name, and pressing the button. We record the exact text signed, the signer's name, the date and time, and the network address, and we show the record to both sides. A patient authorization can also be signed at the bedside through a one-time link, or on paper that Cardinal records with who signed and in what capacity. This satisfies the federal E-SIGN Act and New York's Electronic Signatures and Records Act. Paper copies are available on request, and consent to electronic records can be withdrawn as the Terms of Service describe.

06Reporting a security issue

If you find a vulnerability, email hello@trycarepair.com with enough detail to reproduce it. We acknowledge within two business days, keep you informed, and credit you if you want. We do not run a bug bounty. Please do not access other people's information, run automated scanning against the production service, or disclose the issue publicly before we have fixed it.

07Vendors that run the service

Every outside service that touches CarePair data, and what each one sees:

  • Amazon Web Services (hosting on App Runner, the database on RDS, file storage on S3, encryption keys in KMS, text messages through AWS End User Messaging once texting is on, secrets, logs): sees health information; covered by a business associate agreement; a single region in the United States (us-east-1).
  • Resend (transactional email): sees the recipient's address, the subject, and the body of each email. Our emails name the step and link to the app and never carry health details or the text of a message, which is why no business associate agreement is needed; we would get one before that rule changed.
  • Google Workspace (our staff's email, calendar, and files): sees whatever families and partners write to our team by email; covered by a business associate agreement. CarePair itself reads only the headers (to, from, subject, date) of staff mail that matches a community or provider, to log outreach; it never reads a body.
  • Cloudflare (DNS for trycarepair.com): sees domain name lookups only. The proxy is never enabled, so no application traffic passes through Cloudflare.
  • PostHog (product analytics): since October 29, 2026, page views and a few named steps on the public site only, sent through our own proxy without cookies, referrers, or IP addresses, with PostHog's IP discard setting on as well; no autocapture and no session replay. Signed-in pages and the server send nothing until PostHog has signed a business associate agreement, and we will update this page and the Privacy Policy before that changes. No health information, ever.
  • Apple Push Notification service and Google Firebase Cloud Messaging (notifications in the CarePair app for iPhone and Android, only for a phone that allowed them): see the phone's notification code and the short line shown under Updates, with a link into the app. Never a care summary, an answer, or a document.
  • Cal.com (booking for business calls on /book): sees the name, email, and chosen time of a business contact who books a call. Not used by families.
  • GitHub (source code and continuous integration): sees code and synthetic test data only, never real data.
  • Stripe (payments for Homeward, billed by Cardinal Care Advisors LLC): takes the card on its own checkout page, so no card data touches our servers. From us Stripe receives the paying family member's email address, an opaque reference, the product, and the billing company's name. The payer gives Stripe the name on the card, the card, and the billing address directly. No health details, no case data, no names from CarePair.

Related: Security · Privacy Policy · Terms of Service