Privacy Policy

Who we are

The Pixel Manager Connection Service is operated by Wolf & Bär GmbH (Switzerland), the maker of Pixel Manager for WooCommerce ("the plugin"), published under the SweetCode brand. Contact: aleksandar@sweetcode.com.

What this service does

The connection service lets a shop manager connect their own Google or Meta account once and then configure their tracking assets (for example a Google Ads conversion action, a Google Analytics 4 data stream, or a Meta pixel and Conversions API) from inside the plugin, without copy-pasting IDs and tokens. Use of the service is optional; the plugin's manual configuration fields work without it.

Data we store

• Site enrollment: the shop's URL and a hashed per-site access token.
• Connection credentials: the OAuth refresh token (Google) or access token (Meta) granted by the shop manager, stored encrypted (AES-256-GCM) on our servers. These tokens never reach the shop's own server and are never shown to anyone.
• Account identifiers: the email address of the connected Google or Meta account and the identifiers of the assets selected during setup (for example account, property, pixel, or conversion action IDs).
• Operational logs: technical request logs (timestamps, request identifiers, error codes, latency) retained for up to 90 days, and a minimal per-site audit trail of connection events. Logs never contain tokens or credentials.

How we use data

Exclusively to provide the setup functionality described above: authenticating with the provider on the shop manager's behalf, listing and creating the tracking assets they choose, and returning the resulting configuration identifiers to their own WordPress site. We do not sell data, do not use it for advertising of our own, and do not share it with third parties beyond the provider (Google or Meta) the shop manager chose to connect.

How we protect your data

• Encryption in transit: all connections use HTTPS/TLS, between the plugin and this service as well as between this service and Google or Meta.
• Encryption at rest: OAuth tokens are encrypted with AES-256-GCM before they are stored. The encryption keys are kept separately from the database as deployment secrets, are versioned, and can be rotated. The underlying database is additionally encrypted at rest (AES-256) by our infrastructure provider.
• Access control and isolation: stored tokens are never exposed through any interface. Each shop authenticates with its own site-specific credential, which we retain only as a cryptographic hash and verify using a constant-time comparison. Connections are isolated per site: no shop can ever access another shop's connection.
• Data minimization: we store only what the setup feature needs, namely the token, the connected account's email address, and the identifiers of the selected assets. Short-lived access tokens expire automatically.
• Log hygiene: operational logs never contain tokens or credentials and are deleted after at most 90 days.
• Compromise response: if we ever suspect a compromise, we can rotate the encryption keys and revoke all stored grants directly with the provider.

Google API Services — Limited Use disclosure

Pixel Manager's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Meta Platform data

When a shop manager connects a Meta account, we access only the business assets needed for setup (ad accounts, pixels/datasets and their Conversions API tokens) and store them as described above, solely to configure the shop's own tracking.

Data deletion

Disconnecting inside the plugin (or uninstalling it) revokes the connection with the provider and permanently deletes the stored credentials and account identifiers. Idle connections are revoked and purged automatically. You can also request deletion at any time — see data deletion instructions.

Where data is processed

The service runs on Cloudflare infrastructure with data stored in the European region.

Changes

We will update this page when the service changes in a way that affects the data described here. Material changes are announced in the plugin's release notes.