Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Pyze is a United States based mobile app and growth analytics and engagement platform. It tracks in app events, builds user segments, and powers push notifications and in app messaging. Pyze relies on mobile device identifiers and, on the web, a first party cookie, so it processes personal data that links activity to a user across sessions and devices for analytics and marketing purposes.
Pyze is a mobile app and growth analytics and engagement platform based in the United States. It helps product and marketing teams understand how people use an app or website and then act on that understanding. Pyze tracks in app events, builds user segments and powers push notifications and in app messaging. In short, it combines measurement with direct engagement aimed at individual users.
Pyze processes personal data such as event records, user and device identifiers and segment membership. On mobile it relies on device and advertising identifiers, and on the web it sets a first party cookie to recognise a returning visitor. These identifiers can link activity to the same person across sessions and sometimes across devices. Because they store and read information on the user device, they fall within the ePrivacy rules and they support profiling under the GDPR.
Under the GDPR, the app or website operator is normally the controller and Pyze acts as a processor for the analytics and messaging carried out on your behalf. The analytics identifiers and the web cookie are not strictly necessary to deliver the service, so under article 5(3) of the ePrivacy Directive they require consent before being stored or read. Engagement messaging that targets individuals based on their behaviour also relies on consent and must respect the right to object.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Consent should be collected before any identifier is set or read and before behavioural messaging begins. On mobile this usually means a clear permission prompt for analytics and advertising identifiers, and on the web a compliant consent banner for the cookie. The consent must be freely given, specific, informed and easy to withdraw. Keep the user able to opt out of push notifications and in app messaging at any time and record how consent was obtained.
Because Pyze is based in the United States, using it involves transferring personal data outside the European Economic Area. These transfers can rely on the EU US Data Privacy Framework where Pyze is certified, or on the EU Standard Contractual Clauses combined with a transfer impact assessment. Since the data includes persistent identifiers and behavioural profiles, the assessment should consider how easily individuals could be singled out and what safeguards reduce that risk.
In practice, gate Pyze behind consent on both mobile and web and connect it to your consent management platform. Describe the analytics, the profiling and the messaging clearly in your privacy policy. Sign a data processing agreement with Pyze, set a sensible retention period for event data and identifiers, and limit access to segments. Carry out a data protection impact assessment where profiling is significant and review it as your use of the platform grows.
Websites using Pyze must obtain user consent under GDPR regulations.
DPIA considerations
Pyze combines analytics with engagement messaging and builds user segments from mobile device identifiers and cookies, which supports profiling. A data protection impact assessment is advisable, especially where push notifications and in app messaging target individuals. Assess the lawful basis, the scope of profiling, retention of event data, and transfers of identifiers to the United States.
Sample consent text
We use Pyze to understand how our app and website are used and to send relevant messages. With your consent, Pyze processes device identifiers and sets a first party cookie to measure activity and to power push notifications and in app messaging. You can refuse or withdraw consent at any time.
Third-party domains contacted
pyze.comapi.pyze.comcdn.pyze.compush.pyze.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| pyze_uid | first party | persistent, up to 1 year | Identifies a returning user so web events can be linked across sessions |
| pyze_session | first party | session | Maintains the analytics session on the web |
| pyze_seg | first party | persistent, up to 6 months | Stores segment membership used for engagement messaging |
Pyze collects user analytics data — you legally need a consent banner. Try FlowConsent free.
On the web Pyze sets a first party cookie to recognise a returning visitor and to tie events to a user. On mobile it relies on device and advertising identifiers rather than cookies. Because none of these are strictly necessary, they require consent before being stored or read.
Yes. The analytics identifiers and the web cookie need consent under article 5(3) of the ePrivacy Directive, and the related profiling needs a lawful basis under the GDPR. Engagement messaging that targets people by behaviour also relies on consent. You should obtain it before any tracking or messaging begins.
The most appropriate basis is consent under article 6(1)(a) of the GDPR, paired with ePrivacy consent for the identifiers and cookie. Because Pyze supports profiling and behavioural messaging, consent is generally safer than legitimate interests. Record the chosen basis in your records of processing.
Yes. Pyze is based in the United States, so identifiers and event data can be transferred there. These transfers should rely on the EU US Data Privacy Framework or on the EU Standard Contractual Clauses with a transfer impact assessment. The persistence of the identifiers makes the assessment important.
A data protection impact assessment is advisable where Pyze drives significant profiling or targeted messaging. The assessment should look at the scope of the profiles, the lawful basis, retention of event data and the transfer to the United States. It helps you show that the processing is proportionate.
Gate Pyze behind consent on both mobile and web and connect it to your consent management platform. Describe the analytics, profiling and messaging in your privacy policy, and let users opt out of notifications easily. Sign a data processing agreement, set a retention period and limit who can access segments.
Some analytics tools store data in the European Union or avoid persistent identifiers, which reduces transfer and profiling risk. Others separate measurement from messaging so you can keep analytics lighter. The right choice depends on whether you need engagement features and where you want data stored.
List the Pyze web cookie with its purpose and duration and explain the mobile device and advertising identifiers. State that data is used for analytics, profiling and engagement messaging and that it may be transferred to the United States. Keep the policy aligned with what your consent tools actually control.