Privacy policy

Yeam LLC, a Texas limited liability company based in Houston, Texas (“Yeam”, “we”), runs yeam.ai, the free worklist, the public demos and the Yeam app at app.yeam.ai. This policy says what we collect through them, why, who else handles it, and what you can ask us to do with it.

Information about you, as a visitor or an account holder, is covered by this policy.

Claim data your organization imports into the Yeam app is different. We handle it for your organization, as its service provider, under our agreement with it, and under a business associate agreement (BAA) whenever it is protected health information. Where that agreement and this policy differ about claim data, the agreement controls. The security page explains what the app keeps and what it never stores.

• Visits to yeam.ai. Vercel Web Analytics counts page views, the referring site, approximate country, and browser and device type. It sets no cookies and does not follow you across other sites. Your theme choice is saved in your own browser.
• The free worklist. Your export is read in your browser and is not sent to us. If you ask for a drafted letter, that one row’s payer, codes, billed amount, claim number and days left to file are sent to our app and to Google’s Gemini API to write it, and are not kept. Usage events record the shape of a run (a sample or your own file, a size range, the outcome), never its contents.
• Public demos. A document you upload to a demo is read in memory to draft a letter and is not stored, and neither is the letter. Demos are not covered by a BAA, so do not upload real patient information to them.
• When you contact us. The contact form sends us your name, email and claim volume by email. If you write to info@yeam.ai or call 747-388-6386, we keep the conversation.
• App accounts. Your name, email and a password, which we store only as a salted hash, or the name and email Google shares when you sign in with Google. A session cookie keeps you signed in. We also keep what you enter about your practice (such as its name, NPI and address, used to sign letters) and a record of the denials worked, which is what paid plans are billed on.
• Payments. Stripe collects card details on its own pages. We receive your subscription status and billing contact, never the card number.

• To run the site, the worklist, the demos and the app, and to keep them secure.
• To answer you, set up a pilot, and send account and billing email.
• To bill paid plans.
• To see which pages and features are used, in aggregate, so we know what to fix.
• To meet legal obligations.

We do not sell personal information, we do not use it for advertising, and we do not train models on your claim data. Letters are drafted with Google’s Gemini API on its paid tier, under terms that stop Google from using prompts and responses to improve its products.

We use these service providers, each only for the job listed:

• Vercel: hosting for this site and the app, and site analytics.
• Supabase: the app’s database.
• Google: Gemini for drafting letters, and Google sign-in if you choose it.
• TypeSafe: checking codes against a payer’s history, from payers, codes, claim outcomes and amounts, with no patient identifiers.
• Resend: account email and contact-form delivery.
• Stripe: payments.
• Purelymail: our own mailbox at info@yeam.ai.

We also share information when the law requires it, to protect our rights or someone’s safety, or with a buyer if Yeam is sold or merged, who would be bound by this policy.

Account information stays while your account is open. Contact messages stay as long as the conversation is useful. Claim data is kept for as long as your organization’s agreement says, and returned or deleted at its end as the BAA requires. When you close an account, ask us to delete what is left and we will, except records we must keep by law, such as invoices.

You can ask to see, correct or delete the personal information we hold about you, or to stop receiving email that is not about your account. Write to info@yeam.ai and we will answer within 30 days. If your information came to us inside your organization’s claim data, we will pass the request to your organization, which decides on it.

The app’s database is encrypted in transit and at rest, and patient identifiers are refused at import. The security page has the detail. No system is perfectly secure; if we learn of a breach that affects your information, we will tell you and, where it involves protected health information, follow the BAA.

Yeam is software for businesses. It is not meant for children and we do not knowingly collect information from anyone under 16.

When this policy changes we update the date at the top. If a change matters to how we use information you already gave us, we will email account holders before it takes effect.

Yeam LLC, Houston, Texas. info@yeam.ai · 747-388-6386