Powered by Believia

Privacy policy

Your information, and your patients’.

What this website collects, how we handle patient information when we work for a practice, and how patient consent works for billing, scheduling and virtual assistant services.

Last updated September 28, 2026

01

We never sell data

Not yours, not your patients’. We use information only to do the work you asked for.

02

A BAA comes first

We sign a Business Associate Agreement before we see a single patient record.

03

Consent stays with your practice

Patients consent at your front desk, in your EHR. Never through this website.

Part one · This website

What we collect

When you request a consultation. We receive what you type into the form: your name, role, work email and phone number, how and when you prefer to be contacted, your practice’s name, state, specialty, size, systems and current billing setup, the services and challenges you select, and any message you add.

When you browse. We count page views with Vercel Web Analytics. It does not use cookies and does not follow you across other websites. Our hosting provider also keeps standard server logs, such as IP address and browser type, for security and troubleshooting.

In your browser. The site stores two small settings on your device, not cookies: whether you turned the site sound on, and whether you have already seen the opening animation during this visit.

Please don’t send patient information here.

The consultation form, email, WhatsApp and Instagram are not the place for protected health information (PHI). Tell us about your practice, not about patients. If patient information reaches us this way, we delete it and ask you to use a secure channel agreed at onboarding.

How we use it

To reply to your request, arrange the consultation and prepare for it. We do not sell or rent your information, and we do not add you to marketing lists without asking.

Who else can see it

The people at FizzTech who handle your request, and the providers that run this website and our communication tools, such as Vercel for hosting and analytics. They process it on our behalf. We may also disclose information when the law requires it.

How long we keep it

Only as long as we need it to follow up with you. You can ask us to delete it sooner.

Your choices

Ask us what we hold about you, and ask us to correct or delete it. Email info@fizztechconsultancy.com or message us on Instagram at @FizzTechConsultancy. We reply within one business day.

Part two · Patient information

Our role: a business associate to your practice

When a practice hires us for billing, coding, credentialing, denial and A/R work, scheduling, medical scribing or a virtual assistant, the practice is the HIPAA covered entity and we are its business associate. Before we see any patient information, we sign a Business Associate Agreement (BAA) with the practice. It sets out what we may do with the information, how we protect it, and what happens to it when the work ends.

We use patient information only for the work the practice has hired us to do, and only as the BAA and HIPAA allow. We do not sell it, use it for our own marketing, or combine it across practices.

Calls, texts and emails to patients

Our scheduling and virtual assistant teams contact patients on behalf of their practice. We only contact patients whose practice has collected their contact details and their consent to be reached that way, and we keep a record of that consent.

Care and billing only

Reminders, confirmations, insurance details and referral follow-up. Never marketing.

Clearly from your practice

Texts and voice messages are short and say which practice they come from.

Easy to stop

Reply STOP, tell the caller, or ask the practice. We honor it promptly and tell the practice.

Nothing sensitive

No diagnoses, test results or other clinical details in texts or voicemails.

How consent is collected

Consent is collected by the practice, inside its own systems, as part of patient intake. We do not collect patient consent through this website.

  1. 01

    Notice at intake

    The practice gives each patient its Notice of Privacy Practices and asks them to acknowledge it.

  2. 02

    Consent signed

    The patient signs the consent and, where needed, the HIPAA authorization at the practice.

  3. 03

    Kept in the EHR

    The signed copy stays in the patient’s record in the practice’s own system.

  4. 04

    We work within it

    Our team checks the record before contacting a patient or sharing anything beyond billing.

Patient consent & authorization formPDF for client practices. Covers communication preferences and a HIPAA authorization.
Available soon

Until it is published, practices can request a copy from info@fizztechconsultancy.com.

How we protect patient information

  • HIPAA-trained team
  • Signed BAAs
  • Role-based access
  • Work stays in your systems
  • Breach notice to your practice
  • Return or destroy at exit

Access is limited to the people working on your account, through accounts in your EHR, practice management system and payer portals that your practice can switch off. We do not keep copies on personal devices or in personal email. If we discover a breach involving your patients’ information, we notify your practice as the BAA and HIPAA require. When the work ends, access is removed and information is returned or destroyed as the BAA sets out.

Patients’ rights

Patients’ rights to see, copy, correct or restrict their health information are exercised through their practice, which holds the record. If a patient contacts us directly, we pass the request to their practice right away and help the practice answer it.

Other details

Other websites

Links to WhatsApp, Instagram and our group companies take you to sites with their own privacy policies.

Changes to this policy

If we change how we handle information, we will update this page and the date at the top.

Questions about privacy or consent?

Email info@fizztechconsultancy.com, or bring them to a free consultation. We will walk you through the BAA and how we work with patient data.