How SafeS Pay Uses Meta Conversions API

Primary API Purpose

The integration sends server-side purchase conversion events for authorized ecommerce merchants after SafeS Pay verifies a real order or payment outcome.

• Send Purchase events through Meta Conversions API.
• Use merchant-authorized Pixel, Dataset, access token, and event configuration.
• Record response status, event IDs, retry attempts, and troubleshooting logs.
• Support attribution and reporting for merchant-owned stores and ad assets.

Data Categories

• Event name, event time, event ID, action source, and event source URL.
• Order ID, value, currency, item information, and purchase status.
• Browser and request context such as IP address and user agent where permitted.
• Meta identifiers such as fbclid, fbc, and fbp when available.
• Hashed customer identifiers, such as hashed email or phone, only where authorized and permitted.

Authorization and Scope

SafeS Pay sends events only for merchant assets that are configured or authorized by the merchant or an authorized operator. One merchant's token, Pixel, Dataset, or Business asset is not used for another merchant.

• Merchant settings are scoped to the relevant store and account.
• Sensitive tokens are masked or encrypted where configured.
• Internal access is limited to operations and support users with appropriate role permissions.

What We Do Not Do

• No Facebook ad campaign, ad set, ad, budget, creative, or audience creation.
• No public ad account management or anonymous third-party access.
• No sale or resale of Meta advertising account data.
• No fabricated, duplicated, or unverified purchase events.

Controls and Compliance

• Only payment-confirmed or otherwise verified orders are eligible for purchase event delivery.
• Event IDs and order IDs are used to support deduplication and audit review.
• Failed events can be retried or reviewed by authorized users.
• Data deletion requests can be submitted at https://safespay.app/data-deletion.

Review Summary

Recommended application wording: "SafeS Pay uses Meta Conversions API only to send confirmed ecommerce Purchase events for authorized merchant Pixels or Datasets. We do not create or manage campaigns, budgets, creatives, audiences, or public ad accounts."