Privacy Policy

Unwired Logic Ads Conversion Tracking

Last updated: 14 July 2026

This Privacy Policy explains how Unwired Logic K.K. ("Unwired Logic", "we", "us") handles information in connection with Unwired Logic Ads Conversion Tracking (the "Service"). It applies specifically to the Service and is separate from our general website privacy policy.

The Service is delivered as integrations (add-ons) for business platforms - such as Storeganise, Zendesk, Pipedrive, and respond.io - and uploads offline conversion events (for example, a lead or a completed sale/move-in) from a connected platform to the operator's own Google Ads and/or Meta (Facebook) advertising accounts, so the operator can measure the ad performance that drives their conversions. The Google account access described below is the same regardless of which platform the events come from.

Who this involves

• Operator - the business that enables the Service on a supported platform and connects its own Google Ads and/or Meta ad accounts.
• Visitors/customers - people who interact with the operator on its connected platform and become leads or customers.

Information we access and process

1. Google account data (via OAuth). When an operator connects Google Ads, we request the https://www.googleapis.com/auth/adwords scope. With the operator's consent we receive an OAuth refresh token and the list of Google Ads customer IDs accessible to that operator. We use this solely to identify the operator's chosen Google Ads account and to upload conversion events to it.

2. Meta account data. When an operator connects Meta, we store the Meta Pixel ID and Conversions API access token the operator provides, and use them only to send conversion events to the operator's Meta account.

3. Conversion and attribution data (processed on the operator's behalf). To build conversion events, the Service processes advertising-attribution data associated with the operator's leads/customers, such as ad click identifiers (e.g., Google gclid/gbraid/wbraid, Meta fbclid), UTM campaign parameters, landing-page URL, event type, timestamp, and conversion value. For Meta's Conversions API, contact identifiers (such as email and phone) are hashed (SHA-256) before transmission. For Google Ads, we upload click-based conversions keyed on the click identifier, not personal contact details.

How we use the information

We use the information only to:

• authenticate to the operator's connected Google Ads and Meta accounts, and
• upload offline conversion events to those accounts on the operator's behalf.

We do not use it for advertising to you, profiling, resale, credit assessment, or training machine-learning/AI models, and we do not access Google Ads data for any purpose other than the conversion uploads described above.

Google API Services User Data Policy (Limited Use)

The Service's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, Google user data is used only to provide and improve the conversion-upload feature, is not transferred to others except as necessary to provide that feature or as required by law, is not used for advertising, and is not read by humans except with the operator's consent, for security/debugging, or as required by law.

Storage and security

• OAuth refresh tokens, Meta access tokens, and other secrets are encrypted at rest with field-level encryption (AWS KMS) in addition to storage-level encryption, and are stored per operator.
• Data is hosted on Amazon Web Services (region: US East, N. Virginia) and transmitted over TLS.
• Access is restricted to the automated service and authorized Unwired Logic personnel for support, security, and debugging.

Sharing and sub-processors

We do not sell personal information. We share data only:

• with Google (Google Ads API) and Meta (Conversions API) to deliver the conversion uploads the operator requested;
• with Amazon Web Services, our hosting sub-processor; and
• where required by law.

Retention and deletion

We retain an operator's connected-account credentials and configuration for as long as the Service remains connected. When an operator disconnects the Service, uninstalls it, or requests deletion, we delete the associated OAuth refresh token, access tokens, and configuration. Operators may also revoke the Service's access to their Google account at any time at myaccount.google.com/permissions.

Your choices

• Disconnect or uninstall the Service from your platform's add-on/integration settings.
• Revoke Google access via your Google Account permissions page.
• Contact us to request access to, or deletion of, data we hold about your connection.

Children

The Service is a business tool and is not directed to children.

Changes

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.

Contact

Unwired Logic K.K.
2-2-15 Hamamatsucho, Minato-ku, Tokyo 105-0013, Japan
Email: support@unwiredlogic.com