FUNNELVOICE

Privacy policy.

Understand how your data is used and how to exercise your rights.

1. Who uses your information?

This policy covers funnelvoice.app, its member area at app.funnelvoice.app, the FunnelVoice order process including paiement.funnelvoice.app, and FunnelVoice support.

Dimitri Zegrar, sole trader, SIRET 844 316 224 00014, 31 avenue Georges Clemenceau, 34690 Fabrègues, France, is the controller for processing relating to visitors, customers, accounts and support requests. For privacy questions, contact support@funnelvoice.app or write to that postal address.

A member’s collection of leads for their own business has a different context, explained in section 8.

2. What information is used, and why?

Information comes from you, your use of the service, our checkout, and services you connect. Your email and information necessary for purchase and authentication are required to provide access. Fields marked as required in a form are needed to handle the request; other fields are optional.

Complete payment-card numbers are handled by the payment provider and are not stored in the FunnelVoice application database. Do not include passwords, login codes, API keys or sensitive information in support messages.

Paid access is enabled or disabled by checking payment and refund information. You may ask support for a human review if an error occurs. We do not use your projects or messages to build an advertising profile. A purchase or support enquiry does not automatically subscribe you to a newsletter.

3. Who receives information?

The operator and authorised support personnel access information needed for their work. The following providers are involved according to the feature used:

  • Cloudflare: website and application hosting, database and technical protection.
  • Resend: sending login codes and transactional notifications; recipient addresses, email content and delivery information.
  • Google Workspace: receiving and managing correspondence in our business mailbox.
  • Systeme.io: operations on the account you connect; information about orders placed through the previous Systeme.io checkout, where applicable.
  • Stripe: card payments, refunds and fraud prevention; Stripe also has independent duties as a payment provider.
  • ChatGPT / OpenAI, when you use the connector: information in tool requests and results returned to your conversation, within your permissions.

Connector tools can read your projects and authorised connected-account resources to answer your requests. Connecting ChatGPT does not systematically transfer your entire workspace. Any voice interaction is handled by the conversation service you use; FunnelVoice does not receive an audio recording through its connector. Your ChatGPT account’s rules and settings apply to information sent there.

Messages submitted through integrated support are stored in FunnelVoice and may be included in email notifications. Direct email replies reach support but are not automatically copied into the member-area conversation.

Authorised authorities may receive information when required by law. We do not sell your personal information.

4. Where is information processed?

Our providers operate international infrastructure. Information may be processed outside the European Economic Area, including in the United States. We do not promise exclusively European hosting.

Cloudflare’s and Resend’s contractual documents provide European standard contractual clauses for transfers requiring them, and use of the EU–US Data Privacy Framework when its conditions apply. Google also provides transfer mechanisms in its data-processing agreement. Payment services and third-party accounts you use describe their own processing in their notices.

You can consult these documents or ask support for details and a copy of safeguards applicable to your information. Confidential details may be redacted without preventing you from understanding the safeguards:

5. How long is information kept?

The following criteria distinguish account operation, handling a request, and evidential duties. They do not mean that a refund or logout immediately erases all information.

  • Account, projects and preferences: during the contractual relationship and use of the workspace. Lifetime access requires keeping the information that recognises your account and entitlement. On account closure or an erasure request, relevant information is reviewed to delete what is no longer needed and identify any remaining retention duties.
  • Orders and supporting documents: evidence necessary for the contract and acquired rights is kept while they are performed and then, where justified for evidence, for the applicable legal limitation period. Accounting documents subject to a ten-year retention duty follow that period from the end of the financial year concerned; this does not extend to every project or message.
  • Support: while the request and its follow-up are being handled, including a refund or dispute. Subsequent retention is limited to material needed to evidence commitments, handle a dispute or meet a legal duty, for the applicable period.
  • Operations and incidents: operation references help verify execution, avoid duplicates and resolve errors. Incident-related information remains necessary until resolution and, where disputed, to preserve relevant evidence.
  • Codes and sessions: a login code is valid for ten minutes and a browser session for seven days. Connector authorisation codes expire after five minutes, transactions and access tokens after fifteen minutes; renewal permissions are limited to thirty days. Scheduled cleanup removes expired authentication records and the relevant temporary counters.

A refund removes the purchase-linked access entitlement but does not automatically delete projects or the customer record. Moving an item to the workspace trash allows restoration and is not permanent erasure. To request deletion, use the contact in section 7. We explain what was deleted and the reasons for any necessary retention. Technical copies and providers’ independent processing also follow their own constraints and duties.

6. Cookies and browser storage

FunnelVoice uses these mechanisms for features you request:

The FunnelVoice public website does not include behavioural advertising. Private partner attribution is described below. Secure payment uses Stripe; its session, security and fraud-prevention mechanisms follow that service’s operation and notice. Orders placed through the previous Systeme.io checkout also involve that provider’s mechanisms and notice. Websites you open through links have their own rules.

You can clear cookies and site storage in your browser settings. Blocking essential cookies may prevent login or payment. Accepting the terms of sale is not consent to advertising trackers.

Private partner programme

When a visitor opens a partner link containing the ref parameter, FunnelVoice carries that reference only through internal links during the current visit so it can be associated with a possible order. No affiliate cookie or local storage is created. If the visit ends or the visitor later returns without the partner link, attribution is lost.

Clicks are counted as nonunique aggregates. Temporary IP digests limit abuse and are cleaned up during subsequent requests. Order attribution determines and documents partner commissions. Partners see their own amounts, dates and pseudonymous references, never buyer identities or email addresses. Commission and payout records follow the relevant contractual/accounting retention criteria in section 5.

The requested private statistics access uses a necessary __Host-fvp_… session cookie lasting up to seven days. This cookie only keeps the partner statistics view signed in after the private code is entered; it is not used to attribute sales.

7. Your rights and how to exercise them

Depending on your situation, rights include access, correction, erasure, restriction, portability and objection. You may withdraw consent without affecting earlier processing.

Email support@funnelvoice.app with your request and the email concerned. Proportionate identity checks may be requested where identity is uncertain. We normally respond within one month, informing you within that time if a permitted extension is needed. Restrictions to a right are explained.

You may complain to the French authority, the CNIL, without contacting support first.

8. Information collected by members

A member creating a form for their leads or customers determines the collection’s purposes, requested fields, recipients and retention appropriate to their activity. The member must inform people and have a legal basis. FunnelVoice performs the entrusted operations on their behalf as a processor.

Depending on the form selected, contact details, messages, questionnaire answers and reviews may be stored in the member’s inbox. A public review requires the permission requested in the form and approval before display. The member must inform people about this publication.

For a form relayed to Systeme.io, configured fields are received, encrypted and sent to the member’s account. After delivery is verified, the relay’s encrypted content is erased. Technical references and duplicate-prevention digests remain. If delivery is blocked, content remains pending resolution or a deletion instruction; it is not automatically erased like a successful submission. Deleting relay information does not itself delete a contact already saved in Systeme.io.

To exercise rights over information collected through a member’s page, contact that page’s controller. If you contact FunnelVoice, we identify and assist the relevant controller without sharing your information with another member. Leads’ information is not reused for FunnelVoice marketing.

9. Protection and policy changes

Measures include HTTPS connections, owner-based access controls, encryption of Systeme.io keys and lead-relay content, and protected sessions and tokens. These measures do not constitute an absolute security guarantee.

This policy is updated when processing changes. Its date and version appear on this page. Where a change requires specific information or your consent, we provide it under the applicable rules.