We are ListenFox, a company registered in India. We act as the controller for your account details and a processor for the call data you connect. The short version: we do not sell your data, we do not use it to train models of our own, and you can have all of it deleted by asking.
1. What we hold
About you
- Name, email address and a hashed password (argon2id). We never see the password itself.
- Workspace membership and role, plan, credit balance and a ledger of what was spent on what.
- Session records: an opaque token, when it was created, and from which IP address and browser.
- A record of each version of our terms and policies you accepted, with the time, your email address, IP address and browser.
- A security audit log of sign-ins and of changes made in your workspaces, with who made them and from which IP address.
If you ask for a demo
- What you send on the form: your name, email address, company, phone number, team size, industry, where your calls are recorded and your message, plus the IP address it came from. We keep it until you ask us to delete it.
How you use the website and the app
- We use Microsoft Clarity to see how people use our website and the app: the pages you visit, where you click, tap and scroll, recorded as session replays and heatmaps, with your browser, device and approximate location (from your IP address). Clarity never records what you type into a form. In the app it doesn’t record your calls either: caller names and numbers, transcripts and findings are hidden from it in your browser, so they are never sent to Microsoft.
About your calls
- Call records from the sources you connect: caller and target numbers, time, duration, agent, and any revenue field your source provides.
- The recordings themselves, stored in our object storage so we can play them back to you.
- Transcripts, split by speaker, with timings.
- The answers extracted from each call, the findings built from them, and any questions you ask and their answers.
- Credentials for your sources, such as an API token or a Google sign-in grant, encrypted at rest.
- If you connect an online store, its orders and abandoned checkouts (see section 6).
Callers are not our customers and we have no relationship with them. You are responsible for being allowed to record and process their calls (see the terms, section 3).
2. Why we hold it
For each use, the legal basis under the GDPR and the UK GDPR is in brackets.
- To run the service: sync, transcribe, analyze, display and play back (our contract with you).
- To bill you and to tell you when credits are low (our contract with you, and the tax law we must follow).
- To keep the service secure: sign-in lockout, session checks and the audit log (our legitimate interest in a secure service).
- To improve the website and the product: our analytics tools show us where people get stuck (our legitimate interest, and your consent where the law requires it for cookies; see section 7).
- To answer a demo request (steps you asked us to take).
- To email you about your account. After you sign up, that includes a few emails with tips on getting started, which you can unsubscribe from (our legitimate interest). We do not send other marketing email.
We do not make decisions about you by automated means alone that have legal or similarly significant effects on you.
We do not sell personal data, we do not share it with advertisers, and we do not use your recordings, transcripts or findings to train machine-learning models of our own.
3. Who else processes it
The subprocessor list shows each kind of company that processes your data for us, what it receives and where it is. In short: Hetzner hosts everything in the EU; Cloudflare carries all traffic between your browser and us; speech-to-text providers transcribe the audio; an AI routing provider passes audio and transcript text to the AI model providers that transcribe and analyze it; Brevo sends our email; Microsoft Clarity shows us how the website and the app are used; and Stripe takes card payments. Several of these are in the US, so call audio and transcripts are processed outside the EU and India. Customers can ask us for the list with each provider named. Services you connect yourself, such as Slack, Telegram or Google, receive what you send them.
Speech-to-text and AI model providers receive a call’s audio or transcript in order to process it. Which ones handle a call depends on the effort level chosen in Settings:
- At Standard and Deep, and as Quick’s backup, audio goes to the EU region of our main speech-to-text provider, and we ask it to delete each transcript as soon as we have collected it.
- A second speech-to-text provider, in the US, reads a new account’s first sample calls and is a backup. We have opted out of its model improvement program.
- At Quick, audio goes through the AI routing provider to an AI model provider’s speech model, under that provider’s own retention terms.
- Analysis requests go through the AI routing provider with settings that allow only AI providers that don’t collect or train on the data and keep no copy of it (zero data retention). The exception is the Deep effort level, where it is offered: its AI provider may keep call data briefly to process it.
- Transcript text is sent for analysis only after any redaction the workspace has switched on.
Our Data Processing Agreement covers how we process call data for you and how transfers out of the EU and the UK are protected.
4. How long we keep it
- Call records, recordings, transcripts and findings: for as long as your workspace exists, so the evidence behind every finding stays playable. A workspace admin can set a shorter retention period in Settings, and older calls are then deleted automatically.
- Public share links you create expire on the date you set (30 days by default) and stop working as soon as you revoke them.
- Sessions: until you sign out or they expire.
- The credit ledger: for the life of the account, because it is the record of what you were charged.
- After an account is closed: everything is deleted straight away, except the invoices and payment records Stripe keeps for us because tax law requires them, and the record of which terms you accepted and our security audit log, which we keep as legal evidence. Any copy in a backup is deleted when that backup expires, within 6 months.
5. Deletion and your rights
Inside the product you can delete a call, a source and everything synced from it, every call from one caller’s number, a whole workspace, or your own account. You can also download a copy of everything in a workspace. Deleting a call removes its recording, transcript and findings. Deleting the account removes everything in section 1, except the records listed in section 4. You can also email us from the address on the account and say what you want removed; we confirm by email when it is done, within 30 days.
You can also ask us for a copy of what we hold about you, in a portable format; ask us to correct it, to restrict how we use it, or to delete it; object to a use of it; and withdraw a consent you gave. We answer within 30 days, and we don’t treat you differently for asking. The rights that apply to you depend on where you live:
- EU, EEA and UK: you may complain to your data-protection authority, such as the ICO in the UK.
- India: under the Digital Personal Data Protection Act, 2023, raise a grievance with us first at privacy@listenfox.com. If we don’t resolve it, you may complain to the Data Protection Board of India. You may also nominate someone to exercise your rights if you die or cannot act yourself.
- California and other US states: you may ask to know, correct or delete your personal information. We don’t sell it.
- Australia: you may complain to the Office of the Australian Information Commissioner if we don’t resolve your complaint.
If you are a caller on a business’s calls, that business decides how your call is used. Ask it first; if you write to us, we pass your request to it.
6. Online store data
If you connect a Shopify or WooCommerce store, we read data from it on your behalf, as your processor. The store’s customers are not our customers, and we have no relationship with them.
What we read
- Orders: the order number, date, status, total and currency, the items with their quantities and prices, and the customer’s phone number and email address. We don’t keep customer names.
- On Shopify, abandoned checkouts: when the checkout was started and whether it was completed, the total, the items, the customer’s phone number and email address, and the link Shopify uses to bring the customer back to their cart.
- The name of the payment method, such as “Cash on delivery”. Nothing else. We never receive card numbers or other payment details, and our access is read-only: we can’t change your orders, products, customers or prices.
Why we read it
Only to link orders and checkouts to calls in your own workspace, so you can see which calls led to sales and which carts were recovered. A call and an order are linked when the order was placed within 7 days after the call from the same phone number or email address, or when the order number was said on the call. We don’t use store data for anything else: we don’t sell it, we don’t use it to contact your customers, and we don’t use it to train AI models.
How we keep it
- Email addresses are stored as a one-way hash for matching, with a masked version (such as j•••@e•••.com) for display. Phone numbers are stored like the caller numbers we already hold.
- When you connect a store, we read its recent orders: the last 90 days from WooCommerce, or the last 60 days from Shopify. We keep its data for as long as the store stays connected.
- The access token for your store is encrypted at rest, like every other source credential.
Disconnecting and deletion
- When you disconnect a store in Settings, or uninstall our Shopify app, we stop reading from it and delete the orders, checkouts and call links we copied from it.
- Deleting your workspace or your account deletes its store data too.
- Your calls are not store data. They stay until you delete them, as described in section 5.
Requests from your customers
We honor Shopify’s mandatory privacy requests, which cover requests under the GDPR, the CCPA and similar laws:
- Customer data request (customers/data_request): when one of your customers asks your store for their data, we tell you what we hold about that customer from your store, so you can pass it on.
- Customer erasure (customers/redact): we delete that customer’s orders, checkouts and links to calls.
- Shop erasure (shop/redact): when Shopify asks us to erase a store’s data after the app is uninstalled, we delete everything we copied from that store.
We complete each request within 30 days. For a WooCommerce store, or any request that doesn’t come through Shopify, email privacy@listenfox.com from the address on your account and we handle it the same way.
7. Cookies
The product sets a few functional cookies: one keeps you signed in, and the others remember display preferences, such as light or dark theme.
The website and the app also run Microsoft Clarity (see section 1). Clarity sets its own cookies, _clck and _clsk, so that the pages you see in one visit are linked into one session, and it can set a Microsoft cookie that Microsoft uses for its own purposes, including advertising, under the Microsoft Privacy Statement. If you visit from the EEA, the UK or Switzerland, Clarity sets none of these cookies and records each page view on its own. Clarity keeps session replays for 30 days. You can opt out of Clarity at optout.aboutads.info (choose Microsoft), and it respects the Global Privacy Control setting in your browser. We run no advertising scripts of our own.
8. Security
- Everything travels over HTTPS.
- Passwords are hashed with argon2id; sessions are opaque random tokens in httpOnly cookies; requests that change anything carry a CSRF token.
- Source credentials are encrypted at rest. Every request for workspace data, from the app or an API key, checks workspace membership and role.
- Redaction removes card numbers, ID numbers, bank account numbers and spoken passwords from transcripts before they are stored. Card numbers are hidden by default; you switch the other categories on per workspace.
- If we discover a breach that affects you, we will tell you without undue delay and say what was involved.
More on the security page.
9. Contact
Privacy questions, data requests and deletion requests: privacy@listenfox.com, from the email on your account. Anything else: hello@listenfox.com. We email you at least 30 days before a material change to this policy and ask you to accept it in the app; small fixes just update this page and its date.