Privacy Policy
Overview
PixelHubz ("PixelHubz", "we", "us") is a platform that lets advertising clients import leads and automatically forward them as conversion events to the ad platforms they connect — currently Meta, Google, and LinkedIn. This policy explains what we collect, why, and how it's handled.
There are two kinds of people this policy covers: account users (people who log in to PixelHubz to manage a client's leads and integrations) and leads (the end-customers whose contact details our account users import for conversion tracking).
Information we collect
Account data. Name, email address, and password (stored as a salted hash, never in plain text) for anyone who signs in to PixelHubz.
Lead data. Whatever an account user imports on a client's behalf — typically first and last name, email, phone number, and details about the marketing event (source, timestamp, and platform-specific fields like a Meta action_source or event URL). This comes from a CSV upload or a connected CRM, never collected by us directly.
Integration credentials. OAuth tokens or API credentials for each ad account a client connects (a Meta pixel, a Google Ads customer ID, a LinkedIn conversion ID, and similar). These are encrypted at rest and are never shown in full anywhere in the product.
How we use it
Lead data exists for one purpose: matching a client's leads to the ad platforms that likely influenced them. When a lead is dispatched, PixelHubz sends it to every ad account the client has enabled for that lead, following each platform's own requirements — for example, Meta's Conversions API requires personal fields like email and phone to be hashed (SHA-256) before they leave our servers.
We keep a record of each dispatch attempt (success, failure, and the platform's response) so a client can audit what was sent and troubleshoot failures. We don't use lead data for our own marketing, and we don't sell it.
Who we share it with
Lead data is shared only with the specific ad platforms a client has explicitly connected — Meta, Google, or LinkedIn — and only to the extent needed to record a conversion event. We don't share it with any other third party.
Data retention
Lead and dispatch records are kept for as long as the client's account is active, so they remain useful for reporting and troubleshooting. A client can request deletion of leads or their entire account at any time — see our data deletion instructions for how.
Security
Integration credentials are encrypted at rest. Access to a client's leads and integrations is scoped by role (Owner, Admin, Member) so only authorized users on that client's account can view or export them. All traffic to and from PixelHubz is encrypted in transit.
Your rights
If you're an account user, you can update or delete your own account from Settings at any time. If you're a lead — someone whose details were imported by a PixelHubz client — and you'd like your data removed, see the data deletion instructions page for how to request that.
Changes to this policy
If this policy changes materially, we'll update the date at the top of this page. Continued use of PixelHubz after a change means you accept the revised policy.
Contact
Questions about this policy or your data can be sent to privacy@pixelhubz.com.