Contents
1. Who we are
Call Flow Studio is operated by Adam Volchko, a sole proprietor based at 10 Kings Lane, Cape May Court House, NJ 08210, United States. For the purposes of the EU/UK General Data Protection Regulation (GDPR), Adam Volchko is the data controller of personal information collected through this website and through use of the Call Flow Studio software.
This policy explains what personal information we collect, why we collect it, how we use it, and the rights you have over it.
2. Quick summary
We collect the minimum information needed to sell, license, and support a self-hosted product: your name and billing details when you buy through Paddle, the admin contact details given when the Software is set up, and basic technical details from the Software itself (PBX platform and version, hostname, a machine fingerprint, license key ID). We use self-hosted Umami analytics, which runs on our own server and sets no cookies. On this marketing site it also records session replays and click heatmaps, so we can see where the site confuses people. Anything you type into a form is masked before it leaves your browser. We never see your dial-plan content, call recordings, or end-user data. That all stays on your PBX. If you use the Software’s text to speech or transcription, what you type, or the recording you transcribe, goes from your PBX to the service you chose, under your own account, and never to us. We do not sell your information.
3. What we collect
Information you give us
- Purchase via Paddle: your name, business name, billing email, billing address, and country, as well as payment method details collected and processed by Paddle. Paddle shares with us the order metadata (order ID, product purchased, amount, currency, country, license key issued) but not your full payment-card information.
- Support requests: your name, email, and the contents of your message, along with any technical details you choose to include.
- Registration and activation: when the Software is installed and its first admin is set up, when an admin starts a trial, or when an admin enters an activation code, the Software sends us that admin’s email address, name and company, the date and version of the terms they accepted and, for activation, the activation code, along with the machine details described under “Information from the Software”. At installation it also sends the admin’s username, only so our welcome email can name it; we don’t keep it.
- Password reset: when someone uses “Forgot password”, the Software sends us that account’s email address and username, a one-time code, the server’s hostname, the machine fingerprint and the license key ID, so we can email the code. What we keep is described under Retention.
- New user email: when an admin adds a user, the Software sends us that user’s email address and username, the server’s hostname, a one-time link for choosing a password (it contains the address your admins use to open the Software), how many days the link works, the machine fingerprint and the license key ID, so we can email the link. What we keep is described under Retention.
- Two-step sign-in code: when someone who chose to get their two-step sign-in codes by email signs in, or turns that choice on, the Software sends us that account’s email address and username, a one-time code, how many minutes it works, the server’s hostname, the machine fingerprint and the license key ID, so we can email the code. What we keep is described under Retention.
- Feedback: if you answer the Software’s optional in-app feedback card, we receive your answers, the signed-in account’s email address so we can reply, how many times the card has asked, the account’s sign-in count, your license tier, status and key ID, and the machine details. If you tick “Anonymous” on the card, we receive only your answers: no email address, account, license or machine details, so we can’t reply. Our server still sees the internet address they come from, as it does for any request. If you answer the optional question asked when you uninstall, we receive your choice and anything you type, with the uninstall notice. You can skip both.
Information collected automatically
- Server access logs: IP address, request URL, HTTP method, response code, user-agent string, referer, and timestamp. Logs are kept for security, abuse prevention, and debugging.
- Analytics: page-view counts collected via our self-hosted Umami analytics. It records page paths, referrers, approximate country, browser, and device type. It sets no cookies, does not fingerprint you, and does not follow you to other websites.
- Session recording & heatmaps: on this marketing site only, Umami also records how visitors interact with a page: mouse movement, clicks, scrolling, window size, and the page content as it was displayed to you. We watch these replays, and the click heatmaps built from them, to find confusing layout and broken flows. Anything you type into a form field is masked in your browser before the recording is sent, so we never receive it. The Paddle checkout is never recorded, and neither is the transaction reference shown on the thank-you page. We do not record the Software running on your PBX.
Information from the Software
- License check: every night, and when someone signs in, the Software sends a hashed machine fingerprint, the server’s hostname, the PBX brand and version, the operating system, the PHP version, the Call Flow Studio version, the license key ID, what started the check, and on VitalPBX, FusionPBX and FS PBX the number of tenants or domains. These are the “machine details” referred to elsewhere in this policy. We use them to verify your license, tell you about updates, and understand which platform versions are in use. With each installation’s record we also keep the public IP address it registered from, looked up to an approximate country, region and city, and the address of its most recent check-in.
- Server list check: Call Flow Studio can also run on a server of its own and connect to your PBXs. That server list checks in at setup, at each sign-in, nightly, and when a PBX is added or removed. It sends a random ID it made for itself, the address it is opened at, the operating system, whether it was installed on Linux or in Docker, the PHP and Call Flow Studio versions, and how many PBXs it holds, but no PBX’s name or address. Each PBX whose license key is on the list also makes the License check above through the list, with the list’s ID added, so we can see which PBXs belong to which list.
- Updates: nightly if automatic updates are on, and whenever you run
cfs upgrade, the Software checks our server for a new release and downloads it if there is one. Installing or upgrading also downloads the release, and a PHP component some systems need, from us. A server list also checks for a newer list release when an admin opens it, at most every six hours, and each time its update command runs; that request carries only the list’s version. - License release: running
cfs release-licensesends the license key ID and the machine fingerprint, so the license can move to another PBX. - Uninstall notice: when you uninstall the Software, it sends us the machine details, so we know the PBX no longer runs it and stop sending trial reminders to it.
4. What we don’t collect
The Software runs on infrastructure you control. The following stays on your PBX and is never transmitted to us:
- Dial-plan content (extensions, queues, ring groups, IVR menus, time conditions, etc.).
- Caller IDs, called numbers, call detail records (CDR), or any call metadata.
- Call recordings or voicemail content.
- End-user names, phone numbers, or contact directories from your PBX.
- Live status such as registrations and queue state, which the Software reads locally to display it.
Text to speech. The Software can make voicemail greetings and system recordings from typed text, and transcribe a recording into text, using ElevenLabs or OpenAI. It does this only once your PBX has a key for one of them, saved by an admin in the Software or, on FreePBX 17, in FreePBX’s own System Recordings. When someone saves a key, turns text into speech, plays a voice sample or transcribes a recording, your PBX sends that service what the request needs (the key, the text and chosen voice, or the recording’s audio) directly, under your own account with them. Their privacy terms apply to it. None of it is sent to us. A key saved in the Software is stored encrypted on your PBX and is never sent to us either.
We also do not use advertising trackers, third-party advertising cookies, or social-media pixels.
5. How we use your information
- To deliver the Software and license keys you purchase.
- To verify license validity and serve software updates.
- To send you messages about your own license or installation, such as the welcome email, password-reset codes, two-step sign-in codes, new-user emails, trial expiry reminders and notices that an update is available.
- To respond to support requests and customer service inquiries.
- To detect, prevent, and investigate security incidents, fraud, and abuse.
- To comply with legal, accounting, and tax obligations.
- To improve compatibility with new and existing PBX platform versions, in aggregate.
6. Legal basis (GDPR)
If you are in the European Economic Area or United Kingdom, we rely on the following legal bases under the GDPR:
- Performance of a contract: to deliver the Software, issue license keys, and provide support to customers.
- Legitimate interests: to keep our website and Software secure, prevent abuse, and understand aggregate usage. We have weighed these interests against your privacy rights.
- Legal obligation: to retain transaction and tax records as required by applicable law.
9. Retention
- Server access logs: retained for 30 days, then deleted.
- Session recordings & heatmaps: retained for 30 days, then deleted.
- License & update-check telemetry: routine license-check records are retained for 90 days, then deleted automatically.
- Abuse-prevention records: when a password-reset, sign-in code or new-user message is sent from an installation, we record that it happened using a one-way hash of the recipient address, never the address itself, together with the server’s hostname. These are kept alongside the installation record for security and abuse investigation.
- Order & tax records: retained for at least seven (7) years to comply with U.S. tax and accounting requirements.
- Support correspondence: retained for two (2) years from the last interaction.
- Feedback answers: retained for two (2) years, then deleted.
10. Your rights
Depending on your jurisdiction, you may have the right to:
- Access the personal information we hold about you.
- Correct inaccurate information.
- Request deletion of your information (subject to our legal retention obligations).
- Receive a copy of your information in a portable format.
- Restrict or object to certain processing.
- Withdraw consent for processing that relies on consent.
- Lodge a complaint with your local data-protection authority.
To exercise any of these rights, email hello@callflowstudio.io. We will respond within 30 days. We may need to verify your identity before acting on your request.
11. California residents (CCPA/CPRA)
If you are a California resident, you have the right to know what categories of personal information we collect and the purposes for which we use it (see sections 3 and 5), to request deletion (subject to legal exceptions), to correct inaccurate information, and to be free from discrimination for exercising these rights.
We do not sell or share your personal information as those terms are defined under the CCPA/CPRA, and we have not done so in the preceding twelve (12) months.
12. Security
We protect your information using HTTPS for all traffic, access controls on our database, and operational separation between our marketing site and our customers’ PBX environments (which we never access). Payment-card data is handled exclusively by Paddle and never reaches our servers.
No system is perfectly secure. If we discover a security incident affecting your personal information, we will notify you and the appropriate authorities as required by applicable law.
13. International data transfers
Our infrastructure is located in the United States. If you are accessing the site or buying the Software from outside the United States, your information will be transferred to and processed in the United States. Where required, we rely on appropriate safeguards (such as the European Commission’s Standard Contractual Clauses) for transfers from the EEA, UK, or Switzerland.
Paddle operates its own global infrastructure and may process information in additional jurisdictions; refer to Paddle’s privacy policy for details on its transfer mechanisms.
14. Children
Call Flow Studio is a business product. We do not knowingly collect personal information from children under 16. If you believe a child has provided us with personal information, contact us and we will delete it.
15. Changes to this policy
We may update this policy from time to time. The “Last updated” date at the top reflects the most recent revision. Material changes will be communicated by email to active customers or by a prominent notice on this page.
16. Contact
For privacy questions, data-rights requests, or to update or delete your information, email hello@callflowstudio.io.
Postal address:
Adam Volchko
dba Call Flow Studio
10 Kings Lane
Cape May Court House, NJ 08210
United States