Toothy asks a practice for access to its practice system, payer logins and every patient's insurance data, and its footer says "HIPAA-first. Built for real dental workflows." Yet the footer links to no privacy policy, terms or security page, and toothy.ai/privacy, /terms, /trust and /security all show "404 Oops! Page not found". The FAQ asks "How do you handle HIPAA and PHI?" but no answer appears in the page text. Lassie's homepage states that it signs HIPAA business associate agreements. When an office manager or practice owner checks Toothy before a demo, the first thing they look for is missing.
First action
Put the existing privacy policy, terms and BAA template live at /privacy, /terms and /security and link them in the footer.
How to measure it
Demo-to-close rate
- Now
- –
- Target
- +15%
- By
- 90 days
Steps
Collect the documents
Privacy policy, terms, BAA template and the subprocessor list.
Co-founder & CEO 1 day
Write the security page
PHI handling, access controls, audit trail, MFA, data location and retention, human QA, and the compliance roadmap.
Co-founder & CTO 2 days
Publish and link
Live routes for /privacy, /terms and /security, plus links in the header and footer.
Founding Lead Engineer 1 day
Answer the FAQ
"How do you handle HIPAA and PHI?" in plain words, linking to the page.
Co-founder & CEO 2 hours
Add a BAA request
Button on the security page and a line in the demo confirmation email.
CRO 1 day
Check every route
Make sure no linked page shows "Page not found" and that real 404s return a 404 status.
Founding Lead Engineer 2 hours
Track
Security-page visits before demos, and the demo-to-close rate.
CRO monthly
Why it works
Publish four pages this week and link them from every footer: a privacy policy, terms of service, and a /security (or /trust) page. The security page should cover how PHI is handled (access controls, audit trail, MFA for remote access, where data is stored, who sees it and how long it is kept), confirm that Toothy signs a BAA (with a request button), list subprocessors, and give the SOC 2 or HITRUST status the engineering team is already working toward. Answer the HIPAA FAQ in one paragraph that links to the page. Mention the BAA and security page in the demo confirmation email so the owner can send it to whoever handles compliance before the call.
Practices buying RCM help are trusting a vendor with patient data and their cash flow. A clear security page and an up-front BAA remove a late-stage objection. They also make Toothy look like the safer choice next to rivals who say "HIPAA compliant" in one line. Larger groups and DSOs often cannot start a vendor review without these pages.
Ready to use
ChecklistTrust page launch list
[ ] /privacy live and linked in the footer [ ] /terms live and linked in the footer [ ] /security: PHI handling, access controls, MFA, audit trail, data location and retention [ ] "We sign a BAA" with a request button [ ] Subprocessor list [ ] SOC 2 / HITRUST status with a target date [ ] HIPAA FAQ answer linking to /security [ ] Security page linked in the demo confirmation email [ ] Unknown routes return a real 404 status
Risks and how to handle them
Overstating certifications
Show SOC 2 or HITRUST as "in progress" with a date, never as done.
Pages copied from templates do not match practice
Have the CTO check every security claim against how the system works.
Evidence
- Your websitePolicy pages (checked twice on November 9, 2026): toothy.ai/privacy, /terms, /trust, /security, /pricing, /careers and /changelog all show "404" and "Oops! Page not found"; the footer says "HIPAA-first. Built for real dental workflows." but links to no privacy policy, terms, security page or BAA; toothy.ai/sitemap.xml also returns 404.Source
- Your websiteHomepage (checked November 9, 2026): hero "Stop letting insurance slow your revenue."; stats "80–240+ hours saved monthly" and "97%+ collection ratios"; results shown without practice names or time periods ("$119,172 AR reduction", a 97.2% collection ratio up from 50.8%, "Collections doubled"); a pricing section, "Simple pricing. Predictable ROI.", with "Unlimited Verification (per provider)" and "Usage-Based" plans and a Billing & Collections tab, no prices and "Get a quote" buttons; six FAQ questions, including "How do you handle HIPAA and PHI?" and "Will this replace my team?", with no answers in the page text; every call to action leads to "Book a demo".Source
- HiringFounding Lead Engineer (San Francisco, Chicago or remote US; $100K–$200K and 0.5–2% equity): "We automate backoffice operations for dental clinics using LLMs"; the role builds AI agents that call insurance payers, X12 270/271 and 837/277 EDI pipelines and RPA bots meant to scale to tens of thousands of clinics, and works toward SOC 2 or HITRUST; the listing says Toothy grew 30x during YC W25, plans to scale to 140k dental clinics, recently closed a seed round and has a team of 15 led by a CEO, CTO and CRO.Source
- Competitor researchLassie's homepage: AI that enrolls practices in EFT, reconciles payments and posts them to the PMS (98% of posting handled autonomously), works with existing systems, onboards in about 1–2 weeks (up to about 8 with paper checks), is paid on the work it does, and states that it signs HIPAA business associate agreements.Source