Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Keywee is a US content distribution and paid social optimisation platform used by publishers and brands to acquire readers and subscribers through Meta, Google and TikTok inventory.
Keywee is a content distribution and paid social optimisation platform used by publishers and brands to acquire new readers, leads and subscribers through paid placements on Meta, Google, TikTok and other paid social inventory. The platform combines a tracking pixel on the publisher domain with audience optimisation algorithms and integrations into the major ad networks.
Keywee sets cookies on the publisher domain, captures the IP address, user agent, page URL, content category, scroll depth, time on page and conversion events such as subscriptions or paywall transactions. The data are sent to Keywee and to the connected advertising platforms (Meta, Google, TikTok) for audience optimisation and conversion measurement.
Cookie storage falls under Article 5(3) of the ePrivacy Directive and requires prior consent. The downstream sync with Meta, Google and TikTok pixels triggers their own consent regimes, and the publisher acts as joint controller for the activation purpose.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Block the Keywee pixel and the connected ad network pixels until marketing or advertising consent is granted. Honour withdrawal by stopping the events. Use the consent mode of each ad network so that conversion modelling falls back to aggregate measurement.
Keywee is a US headquartered company with infrastructure in the US and Israel. Israel benefits from a GDPR adequacy decision, but US transfers require certification under the EU US Data Privacy Framework or Standard Contractual Clauses with a transfer impact assessment.
Sign a Data Processing Agreement, document Keywee and its ad network sub processors in your record of processing activities, run a DPIA, gate the pixel and the connected ad network pixels behind your CMP and offer a user level opt out from the audience syncing.
Websites using Keywee must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is required because Keywee combines content engagement profiling, paid social audience syncing with Meta and Google and US transfers, factors that exceed the EDPB criteria for high risk processing.
Sample consent text
I agree that Keywee reads and writes cookies on my device, follows my engagement with content distributed via paid social and shares my browsing identifiers with Keywee and the advertising platforms it integrates with, including transfers to the United States.
Third-party domains contacted
keywee.cocdn.keywee.copixel.keywee.coapi.keywee.coCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| kw_uid | http_cookie | 1 year | Persistent Keywee visitor identifier used to recognise the user across the publisher network |
| kw_session | http_cookie | session | Session level cookie used to deduplicate events during a single browsing session |
| kw_attr | http_cookie | 90 days | Attribution cookie linking a paid social click to the resulting subscription or conversion |
Keywee places tracking cookies for advertising — comply with GDPR using FlowConsent.
Keywee sets first or third party cookies on the publisher domain, including a persistent visitor identifier (kw_uid), a session cookie and short lived event cookies. Connected ad networks (Meta, Google, TikTok) also set their own cookies through the integration.
Yes. Storage and reading of advertising cookies and the cross site profiling that follows fall under Article 5(3) of the ePrivacy Directive and require prior consent.
Article 6(1)(a) GDPR (consent) is the only valid basis. Cross site profiling and audience syncing with paid social platforms are excluded from legitimate interest under EDPB guidance.
Yes. Keywee processes data in the United States and Israel, and shares data with Meta, Google and TikTok which operate from the United States. Use the EU US Data Privacy Framework or Standard Contractual Clauses with a transfer impact assessment.
Yes. Cross site profiling, audience syncing with paid social platforms and US transfers combined trigger Article 35 GDPR.
Block the Keywee pixel and the paid social pixels behind your CMP. Use consent mode for Meta, Google and TikTok. Sign a DPA. Document downstream sub processors. Allow user level opt out.
Native paid social campaigns managed directly via Meta Ads Manager, Google Ads or TikTok Ads remain subject to the same consent obligations but reduce the number of layers. Server side conversion APIs reduce the third party tracking footprint.
List Keywee as a processor with the categories of data, purposes (paid social optimisation, audience building, conversion measurement), retention, US and Israel transfer mechanisms and a direct opt out link.