Cookie Policy

1. This Cookie Policy describes how cookies and similar technologies are used on the AnyServ.eu online platform. It applies to users visiting the Platform from different countries; how the consent banner is shown and which consents are required may depend on your location and applicable law.
2. The Platform is operated by Mateusz Bobrowski, trading as AnyServ. For matters relating to cookies and privacy settings, you can contact the Controller at contact@anyserv.eu.

1. Cookies are small text files stored on your device when you use a website. Similar technologies may include local storage, device identifiers, pixel tags, measurement scripts, consent signals, and other technical means used to store information on or access information from your device.
2. In this Policy, the term “cookies” may also cover similar technologies where they perform a comparable technical or measurement function.

Cookies and similar technologies may be used to:

• ensure the Platform works properly,
• remember privacy settings and user preferences,
• maintain security, prevent abuse, and preserve service integrity,
• carry out statistical and analytics measurements,
• display advertising and measure campaign effectiveness,
• support external features, integrations, and embedded content.

Not all purposes listed above are necessarily active at the same time. The scope of technologies used may change as the Platform evolves.

The Platform may use the following categories of cookies and similar technologies:

1. a) Strictly necessary — required for proper operation, security, core functions, remembering consent settings, and Platform stability. Where the law provides an exception for strictly necessary cookies, they may not require consent, but they should still be disclosed to users.
2. b) Functional — used to remember preferences such as interface settings, language, selected tool options, or other personalization. In many jurisdictions, including the EU, this category may require consent if it is not strictly necessary to provide a service explicitly requested by the user.
3. c) Analytics — used to measure traffic, analyse use of the Platform, assess performance, and improve features and content. In the EU and EEA, such technologies generally require prior consent unless a legal exception applies.
4. d) Advertising and marketing — used to display ads, limit how often they are shown, measure campaigns, link information with advertising services, and personalize ads. This category generally requires prior consent in the EU and EEA.
5. e) Third-party and embedded — some Platform features may rely on third-party services such as embedded materials, external APIs, maps, multimedia, widgets, or other components. Those services may set their own cookies or similar identifiers under their own privacy policies.

1. For users in the EU and EEA, strictly necessary cookies may rely on technical necessity and exceptions under electronic privacy rules. Functional, analytics, advertising, or other non-essential cookies generally require prior user consent.
2. Consent should be freely given, specific, informed, and unambiguous. Users should be able to choose purposes separately and withdraw consent as easily as they gave it.

On your first visit you may see a cookie banner or consent interface that lets you:

• accept all relevant categories,
• reject all non-essential categories,
• choose consents in detail, by purpose.

The Platform should not load non-essential cookies before appropriate consent is obtained where the law requires it.

You may change your cookie settings or withdraw consent at any time using the mechanism available on the Platform, where it is active for your location and configuration.

If the Platform uses Google services related to advertising, analytics, or measurement, it may use Google Consent Mode v2 to pass consent signals to Google services according to your choices.

Under Google Consent Mode v2, the following consent parameters may be used in particular:

• ad_storage,
• analytics_storage,
• ad_user_data,
• ad_personalization.

Depending on your choices, these signals may affect whether certain Google tags store or read cookies and whether data may be used for ad measurement or personalization. Without consent, Google services may operate in a limited or modeled mode, as offered by Google.

In connection with cookies and similar technologies, information such as the following may be processed:

• browser or device identifier,
• IP address,
• activity on the site,
• referral source information,
• consent settings,
• session information,
• data on ad effectiveness or analytics tool activity.

The scope of data depends on which technologies are active at a given time and which consents you have given.

1. Cookies may be session-based or persistent. Session cookies are removed when you close your browser; persistent cookies remain on your device for a set period or until you delete them.
2. Retention depends on the purpose of the technology, the provider, and the current Platform configuration. Consent settings and related identifiers may be stored for as long as needed to remember your choice and demonstrate compliance, where such demonstration is required.

Where required by law, the Controller may store information about consents given, refused, or withdrawn to demonstrate compliance with applicable rules. Such records may include, among other things, the date and time of the decision, the categories selected, the version of the consent message, and a technical identifier linked to the user’s decision.

1. Regardless of settings available on the Platform, you can manage cookies in your browser, including deleting existing cookies, blocking new ones, or limiting selected technologies.
2. Restricting certain cookies may affect how some Platform features work.

The Platform may use third-party services that set or read their own cookies and similar identifiers, in particular providers of advertising, analytics, embedded content, security, API integrations, and other services supporting the Platform.

Detailed rules for processing data by those parties are set out in their own privacy and cookie policies. For how the Controller processes personal data, see the Privacy Policy.

1. This Cookie Policy may be updated due to legal changes, technological changes, changes in tools used on the Platform, or changes to the consent management mechanism.
2. An updated version is published on the Platform together with the update date.

For questions about cookies, consents, privacy settings, or this Cookie Policy, contact the Controller at: contact@anyserv.eu.