Third-Party Integration Terms

C2A · 1BY0 SOLUTIONS · Last updated: September 2026

Lawyer review recommended before production. Your obligations to Meta, Google, WhatsApp and carriers still apply.

1. Scope

C2A can connect to third-party platforms (for example Meta / Facebook Lead Ads, RCS providers, and future Google Ads, WhatsApp API, or portal integrations). When you enable an integration, you authorise C2A to exchange data with that provider as needed to deliver the feature.

2. Your responsibilities

You must have lawful rights to connect Pages, numbers, WABAs, or ad accounts you authorize.
You must comply with each provider’s platform terms, advertising policies, and messaging rules.
You are responsible for consent language on Lead Ads and campaigns — see Consent Notice.
You must not use integrations for spam, phishing, or unlawful content.

3. Meta / Facebook

OAuth scopes are limited to what you approve. Lead data is stored in your C2A tenant. Callback: https://c2a.app/api/integrations/meta/callback. You may disconnect anytime in-app. Meta’s availability and policy changes are outside our control.

4. RCS & messaging providers

CTA/DLR webhooks and delivery reports depend on your messaging provider. We process payloads to create or update leads and statuses. Provider outages may delay or prevent lead ingest.

5. WhatsApp / Business API

Where WhatsApp-related features are offered (live or upcoming), additional disclosures apply — see WhatsApp / API usage disclosures.

6. Data shared with providers

Typically: tokens, Page/form IDs, lead field values returned by the provider, and delivery metadata. We do not sell this data. See Data Processing terms and Privacy Policy.

7. No endorsement

References to third-party brands do not imply partnership beyond technical integration.

8. Contact

support@c2a.app