General information
This document has been prepared in Polish and English. In the event of any discrepancy between the language versions, the Polish version shall prevail, unless mandatory law provides otherwise.
This Policy describes cookies and similar technologies used at contentdeliver.app. The controller is Adam Płotkowski; contact: [email protected].
Cookies are small pieces of information stored on a device. Similar technologies include localStorage, pixels and identifiers used to measure events.
Categories and consent
Necessary technologies operate without consent because they are required for security, sessions, login, recording cookie choices, forms and functions explicitly requested by the User.
Analytics technologies, including Google Analytics 4, operate only after analytics consent. Marketing technologies, including Google Ads, Meta Pixel and the LinkedIn Insight Tag, operate only after marketing consent.
The banner provides equivalent options to “Accept all”, “Reject optional” and “Customise”. Consent is not a condition of registration and is separate from acceptance of the Terms.
Preferences may be changed through the “Cookie settings” link or preference centre. Withdrawal does not affect the lawfulness of prior use.
Google Consent Mode sets analytics_storage, ad_storage, ad_user_data and ad_personalization to denied by default and updates the status after the User’s choice.
First-party technologies
Symfony/PHP session cookie – maintains session and login; necessary; up to 14 days depending on session settings.
REMEMBERME – keeps the User logged in; necessary; 14 days.
__Host-… cookie – temporary CSRF form-protection token; necessary; generally until form submission or session end.
cdp_cookie_consent – stores version, identifier, selected categories and decision time; necessary; 180 days. Evidence may be retained in the database for up to 24 months after withdrawal, change or replacement.
localStorage cd_fired_* – prevents repeated browser delivery of the same marketing event; it is not used to build a profile and is used only with the relevant tracking function.
Google Analytics 4
GA4 helps analyse visits, traffic sources and funnel stages. It may use _ga (usually up to 2 years) and _gid (usually up to 24 hours), depending on current Google configuration.
Events may include page views, registration-page visit, completed registration, trial start, checkout and subscription start. We do not send email, name, tax number, form content or Materials to GA4.
GA4 loads only after a valid identifier is activated and analytics consent is obtained.
Google Ads
Google Ads is used for conversion measurement and remarketing. It may use gcl* cookies for a period set by Google, typically up to 90 days.
Conversions may include completed registration, trial start and paid subscription start. For a subscription, value, currency and a pseudonymous transaction identifier may be sent.
Google Ads operates only after marketing consent. Click identifiers gclid, wbraid and gbraid are not currently stored by ContentDeliver.
Meta Pixel
Meta Pixel is used to measure advertising effectiveness, remarketing and audience creation. It may set the _fbp cookie, usually for up to 3 months.
Events may include PageView, ViewContent for the registration page, CompleteRegistration, StartTrial, InitiateCheckout and Subscribe. Only measurement parameters such as Plan, currency and value are sent, without Material content.
Meta Pixel operates only after marketing consent. ContentDeliver has not currently implemented Meta Conversions API and fbclid/fbc are not stored in the application.
LinkedIn Insight Tag
The LinkedIn Insight Tag is used for campaign analysis, remarketing and measurement of registrations, trials and subscriptions. LinkedIn may set cookies on its domains, including li_* or bcookie, for periods stated in its policy.
The Tag operates only after marketing consent. ContentDeliver has not currently implemented LinkedIn Conversions API or storage of li_fat_id.
Necessary external processes
Stripe may use its own cookies on the hosted payment page for security and transaction processing. They are used on Stripe domains after the User starts checkout.
Meta may use c_user, xs or similar cookies during OAuth login and Facebook or Instagram connection. The process is initiated by the User and takes place on Meta domains.
Cloudflare may use cookies necessary for security, WAF, traffic management and abuse prevention. Their names and duration depend on enabled Cloudflare features.
Inactive tools
Google Tag Manager, TikTok Pixel, TikTok Events API, Meta Conversions API and LinkedIn Conversions API are not currently active. This Policy and the consent mechanism will be updated before activation.
Managing cookies
The User may change preferences in the settings centre, delete cookies in the browser or restrict them. Deleting necessary cookies may prevent login or form operation.
After withdrawal, the application stops activating further optional scripts and deletes first-party cookies where possible. Some third-party cookies may need to be removed in browser or provider settings.