- Home
- Privacy policy
Privacy policy
This policy explains what personal data LeedFox processes, why, how long we keep it and what rights you have.
Who we are
LeedFox is operated by Vision Lab Agency s.r.o., company ID 19495935, VAT ID CZ19495935, Na Folimance 2155/15, 120 00 Praha 2, Czech Republic, registered in the Commercial Register kept by the Municipal Court in Prague, section C, file 387532 ("we"). The LeedFox app runs at app.leedfox.com.
For anything about personal data, write to privacy@leedfox.com.
Our two roles
- Controller. We decide how data is used for visitors of this website, for people who send us the demo form, and for customers and users for billing, payments, support, security and analytics of the app.
- Processor. Our customers store their own enquiries and contacts in the LeedFox CRM. For that data the customer is the controller and we process it only on the customer's instructions, under a data processing agreement.
Website visitors and demo requests
When you send the demo form, we receive your name, e-mail, phone number and company name. We use them to reply to your enquiry, arrange a demo and remind you of the meeting; we contact you by e-mail or phone.
The legal basis is taking steps at your request before entering into a contract (Article 6(1)(b) GDPR).
Customers and payments
For customers who order LeedFox, we process the name, e-mail and phone number of users, the company's billing details (name, company ID, VAT ID, address), the payment history and the record of consent to the recurring payment (date, time, IP address, payment parameters).
The legal basis is, for billing details and the details of the person who orders the subscription, performance of the contract (Article 6(1)(b) GDPR), for the data of account users our legitimate interest in providing the service to the customer (Article 6(1)(f) GDPR), and for tax and accounting documents compliance with a legal obligation (Article 6(1)(c) GDPR). Providing the data needed for the order and invoicing is a contractual and statutory requirement; without it the service cannot be ordered.
We may send customers news about LeedFox and our similar services by e-mail (Section 7(3) of Act No. 480/2004 Coll.) on the basis of our legitimate interest (Article 6(1)(f) GDPR). You can refuse these messages already at registration by leaving the relevant box unticked, and at any time later through the link in every e-mail or at privacy@leedfox.com. You can object to commercial communications at any time; after that we will not send them to you.
Support, security and the AI assistant
When you write to us or call us about support, a complaint or a request for a custom service, we process the content of the request, attachments and technical data that you send us in order to handle the request. The legal basis is performance of the contract and our legitimate interest in proper support (Article 6(1)(b) and (f) GDPR).
We process security logs, change history and application error logs on the basis of our legitimate interest in the security and operation of the service (Article 6(1)(f) GDPR).
We do not store the texts of conversations with the AI assistant. We store only the history of the last 50 steps of the assistant (the type of step, the tool used and the status), without the texts of queries and answers, so that the user can see what the assistant did in the app (legitimate interest, Article 6(1)(f) GDPR). The AI provider may temporarily retain inputs and outputs for the period set out in its data processing agreement, in particular for security and abuse prevention. The AI assistant and other AI features do not make decisions based solely on automated processing within the meaning of Article 22 GDPR; the user confirms every action.
You can object to processing based on legitimate interest at any time at privacy@leedfox.com.
Product analytics in the app
In the app at app.leedfox.com we use the product analytics tool PostHog (data stored in the EU) only if you allow it in the cookie banner. It records how users use the app (pages viewed and clicks, session recording, answers in surveys) so that we can improve the app. Without your consent the PostHog script is not loaded at all. The legal basis is your consent (Article 6(1)(a) GDPR and Section 89(3) of Act No. 127/2005 Coll.), which you can withdraw at any time in the user menu of the app. We record aggregate operational events without personal data even without consent.
Enquiries and contacts in the LeedFox CRM
Customers use LeedFox to receive enquiries, store contacts and send e-mails. We process this data only to provide the service to the customer. If you are an enquiry or contact of a business that uses LeedFox, that business is responsible for your data. Please contact it first. You can also write to us and we will pass your request on.
Data from Meta (Facebook and Instagram)
A customer can connect their Facebook Page and ad account to LeedFox. After that we:
- receive lead form submissions from that customer's Facebook and Instagram Lead Ads,
- read information about the customer's Page, ad account, campaigns, pixel or dataset, and ad performance,
- on the customer's instruction, change the customer's ads: pause and resume campaigns, ad sets and ads, and change their budgets,
- on the customer's instruction, send the outcomes of the customer's enquiries (for example a booked meeting or a closed deal) back to the customer's own Meta dataset through the Conversions API, and build Custom Audiences from them in the customer's ad account. E-mail addresses and phone numbers in this data are hashed (SHA-256) before they leave LeedFox; with them we send the Meta lead ID and the stage of the enquiry.
We use this data only to put the enquiries into that customer's CRM, to show the customer how their ads perform, to apply the ad changes the customer asks for, and to send the customer's CRM outcomes back to the customer's own Meta ad account. We do not sell data from Meta. We do not use it for advertising profiling. We do not share it with anyone except the processors listed below. If a user asks the AI assistant to work with this data, we pass the necessary part to the AI provider Anthropic, PBC only to handle that request; the provider does not use it to train models.
The customer can disconnect at any time in LeedFox settings, or in Facebook under Settings, Business Integrations. When the customer removes LeedFox on Facebook, Facebook notifies us and we delete the stored user access tokens automatically. We delete the Page access tokens for Lead Ads within 30 days of a data deletion request at the latest. How to ask for deletion of the data is described on the data deletion page.
Data from Google (Google Calendar, Google Meet and Google Ads)
A user can connect their Google account to LeedFox. Depending on what the user connects, we:
- Google Calendar: read only the busy and free times of the user's calendar, never the titles or content of events, so that a lead cannot book a meeting at a time when the user is busy,
- Google Calendar and Google Meet: create, move and delete the meeting events that LeedFox books in the user's own calendar, with a Google Meet link when the user has no meeting link of their own,
- Google Ads: read the customer's ad accounts, campaigns and ad performance, create the conversion actions LeedFox needs, and on the customer's instruction send the outcomes of the customer's enquiries back to the customer's own Google Ads account. E-mail addresses and phone numbers in this data are hashed (SHA-256) before they leave LeedFox; with them we send the Google click ID, the IP address and browser of the visit, and the stage of the enquiry,
- read the e-mail address of the Google account, to show which account is connected.
We use data from Google only to provide these features to that user. We do not sell it, we do not use it for advertising or advertising profiling, and we do not use it to train AI models. Nobody at LeedFox reads it, unless the user asks us for help, it is needed for security, or the law requires it. We do not share it with anyone except the processors listed below. If a user asks the AI assistant to work with this data, we pass the necessary part to the AI provider Anthropic, PBC only to handle that request; the provider does not use it to train models. We do not make data from Google available to other AI tools connected through MCP.
LeedFox's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The user can disconnect Google at any time in LeedFox, or in their Google account under Security, Third-party apps and services. When the user disconnects in LeedFox, we delete the stored access tokens and revoke the access at Google, unless the same Google account still serves Google Ads in LeedFox.
We store the data about events and conversions that LeedFox creates or uses from the Google account as part of the customer's CRM and delete it together with the customer's data; we do not store calendar availability information. We store access tokens encrypted and delete them on disconnection.
Data from Microsoft (Outlook and Microsoft 365)
A user can connect their Microsoft work or personal account to LeedFox. Depending on what the user connects, we:
- Outlook calendar: read the busy times of the user's calendar and create, move and delete the meeting events that LeedFox books, with a Microsoft Teams link for a work account,
- Outlook mail: read new e-mails in the user's mailbox, so that messages from the user's leads and contacts appear in LeedFox, and send the e-mails the user writes in LeedFox from the user's own mailbox,
- read the name and e-mail address of the account, to show which account is connected.
We use data from Microsoft only to provide these features to that user. We do not sell it, we do not use it for advertising and we do not use it to train AI models. We do not share it with anyone except the processors listed below. If a user asks the AI assistant to work with this data, we pass the necessary part to the AI provider Anthropic, PBC only to handle that request; the provider does not use it to train models. We store e-mails read from the mailbox as part of the customer's CRM and delete them together with the customer's data. We store access tokens encrypted. The user can disconnect at any time in LeedFox; we then delete the stored access tokens. The user can also remove LeedFox in their Microsoft account under Privacy, Apps and services.
Data from Zoom
A user can connect their Zoom account to LeedFox, so that LeedFox creates a Zoom meeting for each booking made on the user's booking page. We then:
- read the Zoom user ID and the e-mail address of the account, to show which account is connected,
- create, move and delete the Zoom meetings that LeedFox books, and read the list of the user's meetings only to find the ones LeedFox created,
- store the access tokens (encrypted), the Zoom user ID, the e-mail address and, on each booking, the ID and join link of its Zoom meeting.
We do not record meetings or read their content, and we do not store the user's other meetings. We use data from Zoom only to provide this feature to that user. We do not sell it, we do not use it for advertising and we do not use it to train AI models. We keep it while the Zoom account is connected. When the user disconnects Zoom in LeedFox, we delete the access tokens, the Zoom user ID and the e-mail address. When the user removes LeedFox in the Zoom App Marketplace, Zoom notifies us and we also delete the meeting IDs and join links from the bookings. A booking deleted in LeedFox takes its Zoom meeting along. You can exercise your rights over this data as described under Your rights.
Processors we use
- Database and sign-in: Supabase, Inc., EU region (Frankfurt am Main, Germany).
- Website and app hosting: Vercel Inc. (USA).
- File storage: Cloudflare, Inc. (USA), Cloudflare R2, data stored in the EU jurisdiction.
- E-mail sending: Amazon Web Services (Amazon SES); processing region according to the service settings, with a possible transfer outside the EEA.
- E-mail sending through SMTP: Websupport s.r.o. (Slovakia).
- Application error monitoring: Functional Software, Inc. (Sentry, USA).
- Product analytics in the app at app.leedfox.com: PostHog, Inc. (USA), data stored in the EU, only with your consent.
- Issuing invoices: Fakturoid s.r.o. (Czech Republic).
- AI assistant, AI texts and the page generator: Anthropic, PBC (USA). It processes data from the CRM (enquiries, contacts, notes, ad performance) only when the user asks it to, and only within the scope of the user's permissions. It does not use the data to train models.
- AI images: Google (Gemini API, paid service only; Google does not use inputs or outputs to improve its products).
- Address search: Google (Google Maps Platform, Places API).
- Electronic signing of contracts: Zoho (Zoho Sign), EU data centre.
Card payments
Card payments are processed by GoPay s.r.o., company ID 26046768, Planá 67, 370 01 České Budějovice, as an independent controller under its own privacy policy. Card details are stored solely by GoPay; we receive only a payment identifier, the result of the payment and the last four digits of the card.
Services connected on the customer's instruction
If a customer or user connects Meta, Google (Calendar, Meet, Ads), Microsoft, Zoom, Fathom (transcripts and summaries of calls from the user's own Fathom account) or Telegram (notifications to the user's own Telegram account), we pass on or receive data on their instruction. These providers are not our processors; they are independent controllers, and the processing is governed by their terms and the customer's agreement with them.
Transfers of data outside the EU
Some processors (Anthropic, Vercel, Sentry, Amazon Web Services, Google, Supabase, Cloudflare, PostHog, Zoho) are companies established outside the EU or have access to data from countries outside the EU, even though we store the data in the EU. Transfers to our processors take place on the basis of a European Commission adequacy decision (the EU-US Data Privacy Framework) for recipients certified under it, and otherwise on the basis of standard contractual clauses approved by the European Commission (Decision 2021/914) supplemented by additional measures (Articles 45 and 46 GDPR). If a customer connects the Meta, Microsoft or Zoom integrations, we pass data on their instruction to these providers as independent controllers under their terms, and they may process it in the USA. On request we will provide you with a copy of the relevant safeguards at privacy@leedfox.com.
How long we keep data
- Enquiries and contacts in the CRM: while the customer's account is active. After the contract ends or after a request to delete the account, you have 30 days to export (the account is read-only), and on the 31st day we delete the data.
- Data from the website demo form: up to 24 months.
- Data of account users (name, e-mail, phone, role): for the duration of the account; we delete it together with the account data under the previous point, or within 30 days after the user is removed.
- Tax documents (invoices, credit notes) and the data in them: 10 years from the end of the tax period in which the supply was made (Section 35 of Act No. 235/2004 Coll.). Other accounting records of payments: 5 years from the end of the accounting period (Section 31 of Act No. 563/1991 Coll.).
- Record of consent to the recurring payment: for the duration of the subscription and 12 months after the last payment.
- Communication with support and requests for custom services: for the duration of the account; we delete it together with the account. We keep complaints and refund requests for 3 years after they are resolved.
- Change history in the account (audit log): 90 days. Security logs (sign-ins, IP address, browser): 12 months.
- History of the AI assistant's steps (without texts): the last 50 steps.
- PostHog product analytics: up to 12 months; when consent is withdrawn, no further data is collected. We store the consent choice in a cookie for 12 months.
- Backups: data deleted from the app disappears from backups within 90 days at the latest.
Your rights
Under the GDPR you have the right to access your data, to have it corrected or erased, to restrict its processing, to data portability, to object to processing, and to withdraw consent at any time. Write to privacy@leedfox.com.
You can also file a complaint with the Czech data protection authority, Úřad pro ochranu osobních údajů, uoou.gov.cz, or with the supervisory authority of the country where you live or work.
Cookies
The website leedfox.com uses only necessary storage. It saves your choice of light or dark theme and your language in your browser's local storage (localStorage). We do not use advertising trackers or analytics cookies on the website.
The app at app.leedfox.com uses necessary cookies for sign-in and security. It starts PostHog analytics (the section Product analytics in the app) only after your consent in the cookie banner. We store your choice in the cookie lf_analytics_consent for 12 months; you can change it at any time in the user menu of the app.
Data processing agreement (DPA)
The data processing agreement under Article 28 GDPR is an integral part of the terms of service and is concluded with each customer by registering an account or ordering the service. The full text is at leedfox.com/cs/zpracovatelska-smlouva/. It covers the purpose of processing, security, further processors, help with data subject requests, personal data breach notification and deletion of data at the end of the service. The customer gives a general authorisation for the engagement of further processors. We inform you by e-mail at least 30 days in advance of the addition or replacement of a further processor; on serious grounds you may object to the change and terminate the contract.
Changes
We may update this policy. The effective date at the top always shows the current version. See also our terms of service.