This Cookie Policy applies where Triggerize Studio uses cookies, local storage and similar browser technologies in connection with users in the European Economic Area, the United Kingdom or other jurisdictions with comparable cookie and privacy requirements.
1. Who we are
WorldEmp Holding B.V. is the holder of all rights in and to Triggerize Studio. Triggerize is the operating trade name and execution entity under WorldEmp Holding B.V., and Triggerize Studio is the application to which this Cookie Policy relates.
In this Cookie Policy, “Triggerize”, “we”, “us” and “our” refer to Triggerize acting as the operating instance under WorldEmp Holding B.V. for the provision of Triggerize Studio, unless the context specifically requires reference to WorldEmp Holding B.V. as the rights holder.
For questions about cookies, privacy or data protection, contact us at info@triggerize.nl.
2. What we use
Triggerize Studio keeps its use of cookies, local storage and similar browser technologies deliberately limited.
We distinguish between:
- Strictly necessary technologies: required for security, authentication or the basic operation of the service. These do not require consent, where permitted by applicable law.
- Functional technologies: used to remember preferences or provide functionality requested by the user.
- Analytics technologies: used to understand how Triggerize Studio is used and improve the service. Where consent is required, these technologies are activated only after you provide consent.
Depending on the features you use, Triggerize Studio may use the following:
| Technology | Purpose | Category | Typical retention |
|---|---|---|---|
| Session cookie | Keeps you signed in securely | Strictly necessary | Session or authentication expiry |
| Trusted-device token | Remembers a device you have approved for multi-factor authentication | Strictly necessary / security | Up to 30 days |
| Theme preference | Remembers interface preferences such as light or dark mode | Functional | Until changed or cleared |
| Consent choice | Stores your cookie and privacy preferences | Strictly necessary | Up to 12 months |
| Local application storage | Temporarily stores application information to improve responsiveness and user experience | Functional | Until cleared or no longer required |
| Analytics technologies, if enabled | Helps us understand aggregate product usage and improve Triggerize Studio | Optional, consent required where applicable | Depends on the relevant provider and configuration selected by Triggerize Studio |
Where analytics technologies are configured so that they have no or only limited impact on privacy, they may be treated as limited analytics technologies where permitted by applicable law.
The exact cookies, local storage and similar browser technologies used may change as Triggerize Studio develops. We periodically review these technologies and update this policy where necessary.
3. Strictly necessary technologies
Some cookies, local storage and similar browser technologies are required for Triggerize Studio to operate securely.
These may be used to:
- authenticate users;
- maintain secure sessions;
- protect accounts against unauthorised access;
- remember trusted devices;
- store your cookie preferences;
Because these technologies are necessary to provide the service or maintain its security, they may be used without consent, where permitted by applicable law.
Disabling them through your browser may prevent parts of Triggerize Studio from functioning correctly.
4. Optional technologies
Optional cookies, local storage and similar browser technologies are not activated where consent is legally required unless you choose to allow them.
These technologies may be used for purposes such as:
- measuring how the platform is used;
- understanding which features are most useful;
- identifying technical or usability issues;
- improving the Triggerize Studio user experience.
We do not require you to accept optional cookies in order to access essential Triggerize Studio functionality.
5. Your consent
Where consent is required, we ask for your choice before activating optional cookies, local storage and similar browser technologies.
You may choose to accept or reject optional technologies, and you can change that choice later where cookie settings are available.
Rejecting optional cookies, local storage or similar browser technologies does not disable the strictly necessary technologies required to operate and secure Triggerize Studio.
Consent is requested in a manner intended to be freely given, specific, informed and unambiguous. Where optional technologies are presented, accepting and rejecting them should be equally accessible.
You can withdraw or change your consent at any time through the cookie settings provided by Triggerize Studio where available. Withdrawing consent does not affect the lawfulness of processing that occurred before consent was withdrawn.
6. Managing cookies and browser storage
You can manage available cookie and browser storage preferences through the cookie settings provided by Triggerize Studio.
You can also delete or block cookies and browser storage through your browser settings, but browser controls may not affect all technologies used within Triggerize Studio.
Please note that deleting your stored consent preference may cause the cookie banner or consent request to appear again.
Blocking strictly necessary cookies may prevent you from signing in or using certain parts of Triggerize Studio.
7. Third-party services
Some Triggerize Studio functionality relies on third-party service providers.
Where these providers use cookies, local storage or similar browser technologies through Triggerize Studio, Triggerize manages the classification and use of those technologies as the operating instance under WorldEmp Holding B.V., according to their purpose and applicable privacy requirements.
Optional third-party cookies, local storage or similar browser technologies that require consent will not be activated until the required consent has been provided.
Third-party services may also process information according to their own privacy and cookie policies when you interact directly with their services.
Triggerize Studio does not use optional third-party tracking, advertising or profiling technologies unless these are disclosed and, where required, activated only after valid consent has been obtained.
8. Personal data
Some cookies, local storage and similar browser technologies may involve the processing of personal data, such as account identifiers, device information or usage information.
More information about how personal data is processed in connection with Triggerize Studio, including legal bases, service providers, retention periods and your rights, is available in our Privacy Policy.
Where cookies, local storage or similar browser technologies process personal data, the applicable legal basis is described in the Privacy Policy, such as necessity for the service, legal obligation or consent, depending on the purpose and category of technology.
Where personal data is processed on behalf of customers in connection with Triggerize Studio, Triggerize acts as the operating instance under WorldEmp Holding B.V. and additional terms may apply under our Data Processing Agreement (DPA).
9. Changes to this Cookie Policy
We may update this Cookie Policy when:
- we introduce or remove technologies;
- our service providers change;
- Triggerize Studio functionality changes;
- applicable privacy or cookie requirements change.
Material changes will be communicated through the platform, the cookie interface, by email or through another appropriate method where required by applicable law.
The “Last updated” date at the top of this policy indicates when this version was most recently revised.
10. Contact
Triggerize
A trade name of WorldEmp Holding B.V.
The Netherlands
For questions about cookies, privacy or data protection:
info@triggerize.nl
For more information about how Triggerize processes personal data in connection with Triggerize Studio, please refer to our Privacy Policy.
This Cookie Policy should be read together with our Privacy Policy and, where applicable, our Data Processing Agreement (DPA).