Claim Lane
Trust & data handling
Last reviewed: June 2026
Claim Lane is built around the assumption that the less identifying information the system handles, the safer the user is. The architecture is designed to do useful work with the smallest possible amount of personal data.
Identifier minimization
Users are instructed to remove personal identifiers — name, date of birth, member ID, address, provider names where unnecessary — before pasting denial language into the free Record Check. Claim Lane does not require those fields to perform classification or to identify the next useful step.
The free Record Check is the classification surface: a user pastes redacted denial language and Claim Lane returns the pattern and the next written question to ask. No call is placed. For Record Calls in limited testing, the invited user supplies the minimum case fields required to place the call (insurer, phone number, questions to ask, and optional identifiers the call needs). The system stores only what is needed to place the call, generate the artifact, deliver it, and support access recovery.
The system does not request, store, or transmit clinical record attachments. Where a written record is recommended, the user is the one in possession of that record.
Vendors & data handling
Claim Lane uses third-party services to deliver the product. The current posture, accurate as of the date above, is:
- Voice (Retell): Business Associate Agreement in place as of May 8, 2026.
- Written delivery: artifacts are delivered by email and designed for the user to send through certified mail, member portal, or other channel they choose. No outbound fax transport is used.
- LLM inference (OpenAI): used only on input the user has been instructed to redact. Claim Lane uses OpenAI's API services for developers — not consumer chat products — and does not intentionally send clinical record attachments to LLM providers. OpenAI's business/API data-use policy applies.
- Email (Resend): transactional only — receipts, packet delivery, account messages.
- Payments (Stripe): card data is handled by Stripe directly; Claim Lane does not see or store full card numbers.
Vendor posture is reviewed before any new workflow that would expand the scope of data sent to that vendor is enabled in production. The list above describes the current posture as of the date at the top of this page; specific vendor-side certifications and configurations are not represented here unless we have confirmed and dated them.
Claim Lane is aware of the FTC Health Breach Notification Rule and monitors developments that may affect health-adjacent consumer services. We are not a HIPAA covered entity and do not represent ourselves as one.
Record Call artifact or refund — limited testing
This section applies only to invited limited-testing users with access to Record Call. A Record Call is not considered delivered unless a usable artifact is delivered: a recording, a transcript, a structured summary, a result page, and a delivery path to reach you. If Claim Lane cannot deliver a usable artifact, the payment is refunded. A captured-and-delivered refusal or non-answer — proof of what the carrier, provider, regulator, pharmacy, or advocacy line said when asked — can itself be the artifact.
Future coordination features
Some features that would run multiple channel touches in parallel — for example, placing a carrier call and a provider call at the same time — are in development. These are not yet live for production cases. When they are available, they will be gated behind the same consent and disclosure requirements as the limited-testing Record Call workflow.
Experimental and coordination features are tested only on synthetic or non-production case fixtures unless explicitly enabled. Production user case data is not used in experimental workflows unless the workflow has first passed a separate production-data review.
What Claim Lane is not
Claim Lane is not a law firm, medical service, insurance agency, or public-adjusting agency. It is not affiliated with, endorsed by, or sponsored by any health insurance carrier. It does not provide legal, medical, insurance-adjusting, or public-adjusting advice. It does not guarantee that any specific outcome will result from any specific filing. The product is administrative record-building, not legal action. Recordings capture whatever the carrier, provider, regulator, pharmacy, or advocacy line says on the line, including voices and any identifiers spoken aloud; Claim Lane does not promise full removal of identifiers from the audio file.
Reporting a concern
Security or privacy concerns: support@lane.claims.
If a denial pattern was misclassified, that is also useful signal — same address.
This page describes current architecture and vendor posture as of the date above. It will be revised as the product evolves. See also Privacy Policy and Terms.
Result links are signed and expire for security. If your link expires, email support@lane.claims with your case ID or checkout email for a fresh one.
Artifact emails and result pages may contain sensitive information. Do not forward artifact emails or share result links publicly — anyone with the link can view what it contains.