Cookie Policy
Bwenieve Cookie Policy
1. Essential cookies
Bwenieve products use essential cookies for authentication (One Identity session) and, where applicable, anonymous attribution tracking. These cannot be disabled without losing core functionality.
2. Analytics
Analytics use privacy-safe techniques and do not rely on third-party advertising cookies.
3. Third-party content
Pages may contain links to third-party platforms, which may set their own cookies.
4. Managing cookies
You can control cookies through your browser settings. Disabling essential cookies may prevent you from signing in.
Bwenieve Link Cookie Addendum
1. Optional first-party campaign attribution
Bwenieve Link asks separately whether it may use first-party campaign attribution for its internal Growth Funnel reporting. If you allow it, Bwenieve Link stores a random attribution identifier and allow-listed campaign fields such as source, medium, campaign, content and term. Campaign attribution is optional and is independent from Meta advertising measurement.
The attribution choice is stored for up to 180 days. The first-party attribution cookie is stored for up to 30 days. If you deny or withdraw attribution consent, Bwenieve Link stops optional attribution in that browser and clears the current attribution cookie. If the choice expires, Bwenieve Link clears the expired choice and current attribution cookie, stops optional attribution, and asks again.
Withdrawal does not delete historical attribution sessions or touches already recorded on Bwenieve Link's servers. Those records have a 90-day cleanup boundary in the implementation, but automated deletion is not yet operational: the cleanup runner defaults to dry-run and requires separately reviewed scheduling and explicit apply-mode enablement. Until then, existing raw records may remain stored beyond 90 days. Authentication, checkout, subscriptions, and operational payment records are not deleted by changing this choice.
2. Optional Meta advertising measurement
On eligible acquisition and customer-conversion pages, you may independently allow the Meta Pixel. After you allow it, the Pixel may send:
- a PageView for an eligible page;
- CompleteRegistration once for a genuine account created during the current registration journey; and
- Purchase after an owned, server-verified, positive-value paid checkout has successfully activated or renewed a subscription.
A free trial is not a Purchase. An inconsistent positive-value paid checkout paired with a trial-status subscription is not sent. Purchase value and currency come from the verified canonical checkout. A checkout-specific event identifier suppresses repeat transmission in the same browser for up to 30 days; browser-only deduplication cannot guarantee suppression across cleared storage, browsers, or devices.
Meta may also receive browser and device information ordinarily associated with a Pixel request, including the eligible page URL, referrer, network information, device or browser characteristics, and Meta cookie information where present. Automatic event configuration is disabled. Bwenieve Link does not currently use Meta's Conversions API.
3. Separate choices, expiry, and withdrawal
Campaign attribution and Meta advertising measurement are separate optional choices. Choosing Allow or Decline for one does not choose for the other. Each choice expires after 180 days, when Bwenieve Link asks again. Legacy choices without a verifiable decision time are treated as expired.
Advertising events are eligible only when advertising consent was valid both when the event occurred and when it was transmitted. Conversions that occur before advertising consent, or while consent is denied or expired, are discarded and are not replayed after a later Allow, including through an old registration cookie or a later receipt revisit.
Withdrawing advertising consent stops future advertising events and clears pending registration evidence and Bwenieve Link's browser conversion-deduplication markers. It does not delete operational identity, checkout, payment, or subscription records. It also does not promise that an already-loaded third-party library makes no further network request while the page remains open, or that Meta-managed cookies already present in the browser are deleted by Bwenieve Link.
4. Browser and server storage
bw_link_attr_consent: the campaign-attribution choice, stored in first-party cookie and browser local storage for up to 180 days. A denied choice remains stored so Bwenieve Link can respect it. On expiry, the expired choice is cleared.bw_attr: the current first-party attribution identifier, stored as an HttpOnly cookie for up to 30 days after consent. Denial, withdrawal, or detected expiry of attribution consent clears it through the consent flow.bw_link_ad_consent: the advertising choice, stored in first-party cookie and browser local storage for up to 180 days. A denied choice remains stored so Bwenieve Link can respect it. On expiry, the expired choice is cleared.bw_link_meta_registration: eligible new-registration evidence, retained for no more than 24 hours and cleared after use or when advertising consent is absent, denied, withdrawn, or expired.bw_meta_sent_*: browser local-storage markers used to suppress duplicate conversion events for up to 30 days. These are cleared when advertising consent is absent, denied, withdrawn, or expired.bw_meta_page_*: browser session-storage markers used to suppress repeat PageView events during the current browser session.
Bwenieve Link stores raw campaign-attribution sessions and touches on its servers. Clearing browser attribution does not delete those historical server records. The separate retention cleanup described above is designed not to delete identity, checkout, payment, subscription, wallet, or other operational business records.
5. Excluded surfaces
Meta Pixel does not run on Bwenieve administrative pages, editor or preview pages, customer public Bio or Music pages, or other Bwenieve products.
6. International processing
Bwenieve's owner has confirmed that Meta Platforms Ireland Limited is the contracting entity for the Meta advertising dataset, that information received through the Meta Pixel may be processed primarily in Ireland and the United States, and that the applicable Meta Business Tools Terms and Data Processing Terms incorporate Standard Contractual Clauses where applicable. These account-specific facts have not been independently verified. The complete processing locations, onward transfers, safeguards and Meta retention terms also remain subject to independent review. Kenyan data-protection requirements require an applicable lawful transfer basis and appropriate safeguards or another permitted basis for transfers outside Kenya; this notice does not claim that account-specific compliance has been independently established. Meta advertising tracking remains disabled unless and until it is explicitly enabled in production configuration.
