CallFlowKitOpen the builder ↗
Privacy

Privacy, without the vague parts.

The builder and audit intake keep draft operating information on your device until you choose to export it. This policy also explains what happens if you email an audit request and what site providers may process.

Effective July 16, 2026

1. Builder and audit drafts stay in your browser

CallFlowKit does not require an account. Information entered into the interactive builder or audit intake is processed in your browser and saved in your browser's local storage. Exported JSON files are created on your device. We do not silently transmit those draft answers to a CallFlowKit application database.

Clearing site data in your browser can remove saved progress. Anyone with access to your device or browser profile may be able to view locally saved information, so avoid entering sensitive personal, payment, health, or authentication data.

2. Paid audit communications

If you choose to email a request pack to CallFlowKit, the contents and ordinary email metadata will be processed by the sender's and recipient's email providers. Submit only redacted operating material. Do not send caller personal information, recordings, patient or payment data, API keys, passwords, tokens, or production credentials.

Audit material may be used to confirm scope and perform the requested review. Sandbox or test access is used only after authorization. Retention and deletion arrangements for a paid engagement should be confirmed with the scope before work begins.

3. Payment processing

Paid audit checkout is hosted by Creem. Creem processes checkout details, payment method information, billing data, fraud signals, receipts, and transaction records under its own terms and privacy policy. CallFlowKit does not receive or store full payment-card numbers.

4. Technical data

When you request a page, hosting and security providers may process standard technical information such as IP address, browser and device type, requested URL, timestamps, referring page, and security signals. This information is used to deliver the site, maintain reliability, prevent abuse, and diagnose errors.

5. Google advertising services

CallFlowKit uses Google AdSense. Google and its partners may use cookies, local storage, device identifiers, IP addresses, and related data to provide, personalize, measure, and protect advertising, subject to your consent choices and applicable law. Google explains how it uses information from sites that use its services in its partner sites policy.

Where required, a consent message will let you accept, reject, or manage advertising choices. You can also review Google's advertising settings.

6. Cookies and browser controls

The builder relies on local storage to remember progress. Advertising and consent providers may use cookies or similar technologies. You can change consent selections when the site offers that control, and you can delete or block storage through your browser. Blocking storage may affect saved builder or audit-intake progress and advertising preferences.

7. Retention and sharing

CallFlowKit does not sell the contents of builder answers or paid audit materials. Technical and communication data is retained by service providers according to their settings and policies. It may be disclosed when required by law, to protect the service, or in connection with a business transfer.

8. Children and policy updates

CallFlowKit is a business operations tool and is not directed to children. This policy may change as the product or its providers change. Material revisions will be reflected by an updated effective date on this page.

9. Contact and customer support

For customer support, privacy questions, or paid-audit assistance, email audit@callflowkit.com.

© 2026 CallFlowKit
HomePrivacyTermsSupport: audit@callflowkit.com