Legal

Privacy Policy

Last updated: November 2, 2026

This policy describes how SpeedFunnel handles information, including information processed through Meta integrations. Please read it together with any privacy notice provided by the business whose form or workspace you use.

1. Operator and scope

SpeedFunnel SpA operates SpeedFunnel and SpeedOps. Its address is Andrés de Alcázar 356, Of. 603, Edificio Alcázar, Rancagua, Región de O'Higgins, Chile. Contact: thomas@speedfunnel.io. This Privacy Policy explains how SpeedFunnel SpA ("we," "us," or "our") handles personal information when you visit speedfunnel.io or use SpeedFunnel or SpeedOps. In this policy, each is a "Service" and both are the "Services."

When a business uses SpeedFunnel to collect information about its customers or prospects, that business decides why the information is collected and is responsible for its notices and instructions. For SpeedOps, the business requests processing of message content to provide analysis for its use. SpeedFunnel SpA processes information to provide the applicable Service and as described in this policy and the business's configuration.

2. Information we collect

Account and workspace information: name, email address, authentication identifiers, workspace and team settings, and records of actions taken in the Service.

Lead and form information: information a person submits to a business through a form or connected advertising lead form, which may include name, email address, telephone number, answers to form questions, appointment details, and related timestamps. The business using the Service determines which questions to ask.

Integration and message information: when a workspace administrator connects a third-party service, we process information needed to operate that connection. For Meta this can include Facebook Page and form identifiers and names, Meta lead identifiers and lead details, webhook events, and access credentials. For Google Calendar and Twilio it may include calendar, event, call, and provider account information. SpeedOps may receive complete message content for processing and produce analysis from it; full message content is deleted after processing, while analysis is retained as described in Section 7.

Device and usage information: browser and device details, IP address, request and diagnostic logs, and information needed to protect, operate, and troubleshoot the Service. Public forms may receive page URL, referrer, and campaign attribution parameters. If a workspace enables Meta Conversions API (CAPI) events, the event and matching information sent to Meta may include the event name and time, an optional conversion value and currency, an event-source page URL, SHA-256-hashed email, first and last names, phone number, country, and internal lead identifier, and—when available—client IP address, user-agent, and fbp/fbc browser identifiers. These fields vary by event and available information; further details appear in Section 6.

Support communications: information you choose to include when you contact us.

3. How we use information

We use information to provide and maintain the Services; authenticate users and administer accounts and workspaces; receive and route leads; support calls and appointments; process SpeedOps message content to generate requested analysis and task summaries; provide integrations and reporting; secure the Services and investigate errors or abuse; respond to support requests; and comply with legal obligations.

We do not use Meta Lead Ads information for purposes unrelated to providing the requested lead-management features. We do not sell personal information. We do not use information collected through the Service to build advertising profiles for our own unrelated advertising.

4. When information is shared

We share information with the workspace and its authorized users that control the relevant account or lead. We use service providers to host, secure, and operate the Service, and share only information needed for their work under appropriate contractual or other safeguards.

SpeedFunnel uses Amazon Web Services (AWS) for infrastructure: Amazon CloudFront and Amplify for website delivery, Elastic Beanstalk for API and worker hosting, and Amazon RDS, Cognito, SQS, and Secrets Manager for database, authentication, queues, and secrets. Depending on workspace settings, SpeedFunnel connects to Meta for Lead Ads, Pixel, and CAPI; Google Calendar; and Twilio for calls. SpeedOps uses AWS Lambda, API Gateway, DynamoDB, EventBridge, and Secrets Manager; Meta WhatsApp Cloud API for the administrator channel; Z-API for tenant WhatsApp chat retrieval and delivery; and Anthropic Claude API for message analysis (currently configured with the Claude Haiku 5.5 model). Some SpeedFunnel charges are made by Marketing Show LLC in the United States. Where Marketing Show LLC processes a charge, it may receive information needed to identify and record that transaction; its own privacy notice governs its handling of information it receives. The technical and integration providers named here receive information needed for their services and process it under their own privacy terms. Meta Pixel or CAPI may send event, attribution, and lead-matching information to Meta; the CAPI fields and conditional identifiers are described in Section 6.

We may disclose information when reasonably necessary to comply with law, respond to valid legal process, protect people or the Service, or establish or defend legal claims. If our business or assets are reorganized or transferred, information may be transferred subject to applicable privacy requirements.

5. Meta Platform data

When a workspace administrator connects a Meta Page or Lead Ads source, SpeedFunnel uses the granted access to identify the selected Page and receive or retrieve lead details so the workspace can manage those leads. For SpeedOps, Meta's WhatsApp Cloud API is used for the administrator messaging channel; tenant WhatsApp chat messages are retrieved and delivered through Z-API, as described in Section 4. We store the resulting lead and operational records for the workspace and protect integration credentials using access controls. We do not sell Meta data, use it to determine eligibility for credit, housing, employment, or insurance, or transfer it to data brokers.

The workspace administrator can disconnect an integration in the Service. Disconnecting stops future use of that connection but does not by itself erase lead records already created in the workspace. You can also revoke the app's access in your Meta account settings. For deletion requests, see Section 8.

6. Cookies, storage, and embedded forms

The Service may use cookies or browser storage for functions such as remembering language or interface preferences, maintaining authentication, and protecting the application. Public forms may receive a sanitized landing-page URL and query parameters, the referrer URL, and the Meta browser identifiers in the host page's _fbp and _fbc cookies when present and valid. When a business configures a Meta Pixel for an embedded SpeedFunnel form, the embed enables Pixel tracking by default if the host page does not provide a consent signal. The host can opt out by setting window.S2L_META_PIXEL_CONSENT to false before the embed runs, or by sending the embed an explicit denial through the consent-change event. In that default-enabled state, the embed can load Meta's Pixel and send PageView and configured standard or custom events to Meta. The host-page signal is a technical setting; it does not itself determine whether tracking is lawful or constitute consent. SpeedFunnel remains responsible for its own disclosures and legal obligations, and the business embedding the form may have separate obligations for its page and visitors. When a workspace enables CAPI events, each event sent to Meta may include its name and time, optional conversion value and currency, and the event-source page URL. Matching fields may include SHA-256-hashed email, first and last names, phone number, country, and internal lead identifier; client IP address, user-agent, and fbp/fbc browser identifiers are included when available. The exact fields vary by event and available data.

7. Retention and security

In SpeedFunnel, leads that have not resulted in a purchase are retained for 36 months from the date of the last contact. For SpeedOps conversation content, complete messages are deleted after processing; only the resulting analysis is retained. SpeedOps may also retain account, security, and operational information needed to provide and secure the Service. Other account and operational information is retained as needed to provide and secure the Services and meet applicable legal obligations.

We use technical and organizational safeguards designed to protect information. No method of transmission or storage is completely secure, and we cannot promise absolute security.

8. Your choices and deletion requests

Depending on where you live and your relationship with the workspace, you may have rights to request access to, correction of, deletion of, or a copy of your personal information, or to object to or restrict certain processing. If your information was submitted to a business using SpeedFunnel, contact that business first; it controls the information and can instruct us to act. We will assist the workspace as appropriate.

To ask us to delete or otherwise handle information associated with a SpeedFunnel or SpeedOps account, email thomas@speedfunnel.io with the subject "Privacy or data deletion request." Identify the account or workspace and the data involved; do not send passwords or access tokens. We may ask for information needed to verify your request. On a deletion request, we anonymize the relevant personal data rather than retain it in identifiable form. You may also revoke Meta permissions from your Meta account settings. Revoking app access does not itself delete records already held by the business using the Service.

9. Chilean law, international processing, and children

SpeedFunnel SpA is based in Chile, and the Services are operated subject to applicable Chilean law. Information may be processed outside Chile by the providers described in Section 4. The location of processing depends on the Service and provider configuration.

The Services are intended for businesses and are not directed to children. We do not knowingly seek to collect personal information directly from children in violation of applicable law. Contact us if you believe a child has provided information through a Service.

10. Changes and contact

We may update this policy as the Service or applicable requirements change. We will post the current version on this page and update the date below. Material changes will be communicated through the Service or another appropriate channel where required.

Questions or privacy requests: thomas@speedfunnel.io. This contact is also available for requests concerning Meta Platform data processed through SpeedFunnel.