Last updated: September 2026. Bytek S.r.l., Italy.
Bytek Tag collects pseudonymized user data for advertising conversion tracking and identity resolution. All personal identifiers (email addresses, phone numbers) are hashed client-side using SHA-256 before any data is transmitted. No clear-text personal data is ever stored or transmitted to Bytek servers.
All hashing occurs exclusively in the user's browser using the Web Crypto API (SHA-256). Raw personal data exists in memory only during the milliseconds of normalization and hashing — it is never logged, stored, or transmitted. Bytek acts as a data processor under GDPR; the customer (website operator) is the data controller.
_bp: First-party cookie on the customer's domain (365 days, configurable). Contains anonymous visitor ID (UUID) and session ID. No PII._bp_s: First-party HttpOnly cookie set by the server (365 days). Contains only the anonymous visitor ID (UUID). Used to extend identity persistence beyond Safari ITP limits. Not accessible by JavaScript._bp: Browser storage on the customer's origin. Contains the full identity store: anonymous IDs, SHA-256 hashes (if captured), click IDs, first-touch data. Optional AES-GCM encryption available. Cleared on consent denial.Hashed identifiers are shared with advertising platforms (Google Ads, Meta, TikTok, etc.) only when the user has granted consent for the relevant category (marketing, analytics). Each platform receives data in its required format via server-side Conversion APIs (CAPI). Bytek does not sell or share data with third parties for purposes other than the customer's configured conversion tracking.
Additional data processing:
bp('consent', 'denied') immediately clears all stored data and stops tracking.For privacy inquiries, data deletion requests, or DPA agreements: privacy@bytek.ai