Skip to main content

Month-to-month · no contracts

Work with us

Legal Lead Flow Privacy Policy

Effective: November 17, 2026

What information Lead Flow handles, why, who it is shared with, and how it is protected. Lead Flow is the reporting tool Azokaa LLC, doing business as cruxdata, provides to its clients.

01 Who we are and what this covers

Lead Flow is provided by Azokaa LLC, doing business as cruxdata (“cruxdata”, “we”), at 23465 E Lolo Pass Rd, Rhododendron, OR 97049. Effective date: November 17, 2026. See also the Lead Flow Terms of Service.

This policy covers the Lead Flow app. Our website, cruxdata.io, has its own privacy policy.

Lead Flow handles two kinds of information, and our role differs for each:

  • Account information about the clinic staff and cruxdata staff who sign in. For this, cruxdata decides how the information is used.
  • Client data that a clinic connects or enters, which can include information about the clinic’s leads and patients. For this, cruxdata works on the clinic’s behalf and follows the clinic’s instructions and our agreements with it. If you are a patient or lead of a clinic, the clinic’s own privacy notice applies, and questions or requests about your information should go to the clinic first.

02 Information Lead Flow handles

Account information

  • Name, business email address, the clinic you work for, and your role.
  • Mobile phone number, if you use text message codes to sign in. It is held by our sign-in provider and used only to send those codes.
  • A sign-in identifier from our sign-in provider. Your password is held only by that provider; we never see or store it.

Client data from connected platforms

  • From the clinic’s CRM (such as GoHighLevel): contact records for leads, which may include name, phone number and email address; the CRM’s contact ID; when the contact was added; lead source and campaign; ad-click identifiers and tracking tags; which forms were submitted; appointment dates, status and calendar; pipeline stage; and, if the clinic uses one, the practitioner field.
  • From the clinic’s advertising accounts (Google Ads, Meta): campaign names, spend, clicks, leads and similar performance figures. These are totals, not information about individual people.

Information users enter

Revenue per campaign, spend on events and social media, average booking amounts, the list of practitioners, which practitioner is credited for a plan of care (recorded by contact ID, not by patient name), and notes such as invoice references.

Technical and security information

IP address, browser type, sign-in and sign-out times, and a record of actions taken in Lead Flow (who viewed, changed or exported what, and when). We record actions using IDs, not patients’ names or contact details.

03 How we use information

  • To show each clinic its own reports: where leads come from, how they move through each stage to a plan of care, and what each campaign costs and earns.
  • To create and manage accounts, verify sign-ins and apply each person’s role.
  • To keep Lead Flow secure: detect misuse, investigate problems and keep an audit record.
  • To support clinics and fix problems they report.
  • To meet legal obligations and our agreements with clinics.

We use the least information each feature needs. Screens used by cruxdata staff show CRM contact IDs, not patients’ names or contact details.

04 What we never do

  • We do not sell personal information, or share it for advertising.
  • We do not put advertising pixels or third-party analytics in Lead Flow.
  • We do not send patient information to advertising platforms, analytics tools, error-tracking services or artificial intelligence services.
  • We do not use any clinic’s data to train artificial intelligence models.
  • We do not use one clinic’s data for another clinic, or show one clinic another’s data.
  • We do not write to or change a clinic’s CRM or advertising accounts. Lead Flow’s access to them is read-only.

05 Who we share information with

We share information only with the service providers below, each limited to what it needs to do its job, plus the cases listed under the table.

Service providerWhat it does for Lead FlowWhat it receives
RenderHosts the app and its database in the United StatesAll Lead Flow data, stored encrypted, under a business associate agreement
Auth0 (Okta)Sign-in and two-step verification for staffStaff email address, sign-in identifier, password, and mobile number if text codes are used. No patient or lead information
TwilioDelivers text message sign-in codes, through Auth0Staff mobile number and the code
GoHighLevel, or the clinic’s CRM providerThe clinic’s own CRM, which Lead Flow reads fromLead Flow only reads; it sends nothing back except the request for data
Google Ads and MetaThe clinic’s own advertising accounts, which Lead Flow reads fromLead Flow only reads; it sends no patient information to them

We may also share information:

  • with the clinic’s own users, according to their roles;
  • when the law requires it, for example in response to a valid court order, after telling the clinic where we are allowed to;
  • to protect people’s safety, or Lead Flow’s security, where the law allows;
  • with a buyer or successor if our business is merged or sold, under the same protections and with notice to clinics.

06 Google and Meta data

Lead Flow’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use Google Ads data only to show the clinic its own advertising reports in Lead Flow. We do not transfer it to others except as needed to provide those reports or as the law requires, do not use it for advertising, and do not let people read it except with the clinic’s permission, for security, or as the law requires.

We use data from Meta under Meta’s Platform Terms, only to show the clinic its own advertising reports. A clinic can remove Lead Flow’s access at any time in its Google or Meta account settings.

07 Health information and HIPAA

Many of our clients are healthcare providers covered by HIPAA. When a clinic connects patient information to Lead Flow, cruxdata acts as the clinic’s business associate under a signed business associate agreement. We use and disclose that information only as the agreement allows: to provide Lead Flow to that clinic. We will report any breach of that information to the clinic as the agreement and the law require.

Patients who want to see, correct or get a copy of their records, or who have a privacy question, should contact their clinic. We will help the clinic respond.

08 How we protect information

  • Encryption: all connections use HTTPS, and stored data is encrypted. Especially sensitive fields, such as notes, have an extra layer of encryption tied to each clinic.
  • Separation between clinics: each clinic’s data is walled off inside the database itself, so one clinic’s users cannot reach another’s data.
  • Sign-in: every account uses two-step verification. Sessions end after a period of inactivity and on sign-out.
  • Access by role: each person can see and change only what their role allows, checked on our servers for every action.
  • Audit record: we record every view, change and export of client data, and every sign-in, sign-out and failed sign-in. Access keys for connected platforms are stored encrypted and never shown in the browser.

No system is perfectly secure. If a breach affects your information, we will notify the clinic, and where required the people affected, as the law and our agreements require.

09 How long we keep information

InformationHow long
Client dataWhile the clinic uses Lead Flow, then 30 days for the clinic to request an export, then deleted within 30 days
Lead and patient recordsWhile the clinic uses Lead Flow, then deleted on the same schedule as client data, unless a business associate agreement requires otherwise
Account informationWhile the account is active; removed within 30 days after the clinic leaves or the user is removed
Audit and security records6 years, or longer if the law requires
BackupsOverwritten on a rolling cycle of 30 days

Under a business associate agreement, we return or destroy patient information when the service ends, as that agreement requires.

10 Cookies

Lead Flow uses only the cookies it needs to work: one that keeps you signed in, and security cookies that protect your session and forms. We do not use analytics, advertising or tracking cookies in Lead Flow.

11 Your rights and choices

  • Clinic staff: you can ask to see, correct or delete your account information. Ask your clinic’s Lead Flow owner, or email us. Deleting your account ends your access.
  • Patients and leads: contact your clinic, which controls your information. If you contact us, we will pass your request to the clinic.
  • State privacy rights: depending on where you live, you may have rights to access, correct, delete or get a copy of your information, and to appeal our decision. Email privacy@cruxdata.io with “Privacy Request” in the subject. We may need to verify your identity, and we respond within the time the law requires (for example, 45 days under California law). We will not treat you differently for using these rights.
  • Text messages: reply STOP to stop sign-in texts, or HELP for help. You will then need another way to verify your sign-in.

12 Children

Lead Flow is for clinic staff and is not meant for children; we do not knowingly collect information from children who use it. A clinic’s records may include information about patients who are minors. We handle that information only on the clinic’s behalf, as described in Section 7.

13 Where information is stored

Lead Flow stores and processes information in the United States.

14 Changes to this policy

We will update the date at the top when this policy changes. For a material change, we will tell clinics by email or in Lead Flow before it takes effect.

15 Contact

Azokaa LLC, doing business as cruxdata. Mailing address: 23465 E Lolo Pass Rd, Rhododendron, OR 97049. Email: privacy@cruxdata.io or preston@cruxdata.io.