Legal
Cookie policy
1. Purpose
This Policy explains how QRzen.io uses cookies and similar technologies on qrzen.io, its subdomains and other environments linked to the Service.
It should be read together with the Privacy Policy.
2. What cookies are
Cookies are small files or records that are stored on or read from the user's device when visiting a site.
They can be used to:
- Maintain a session.
- Remember preferences.
- Protect the Account.
- Measure usage.
- Attribute campaigns.
- Personalize content.
- Display advertising.
3. Similar technologies
In addition to cookies, we may use:
- Local storage.
- Session storage.
- Pixels.
- Tags.
- SDKs.
- Identifiers.
- Scripts.
- Web beacons.
- Limited fingerprints for security, where lawful.
- URL parameters.
- Server logs.
This Policy uses “cookies” as a general term where appropriate.
4. First-party and third-party cookies
First-party
These are set directly by QRzen.io or under our domains.
Third-party
These are set or read by external providers, such as analytics, advertising, payment, security or authentication services.
Third parties may use the information in accordance with their own policies, subject to the applicable consents and restrictions.
5. Session and persistent cookies
Session
These are normally deleted when closing the browser or ending the session.
Persistent
These remain for a set period or until the user deletes them.
The duration may change due to technical updates or provider settings.
6. Categories used
6.1. Strictly necessary cookies
These are necessary for the operation, security or requested service.
They may be used to:
- Log in.
- Maintain the session.
- Protect forms.
- Prevent fraud.
- Distribute traffic.
- Remember consent.
- Process a purchase.
- Store essential items.
- Protect against attacks.
- Maintain essential preferences.
They cannot be disabled through the panel when they are essential, although they can be blocked from the browser with possible effects on the Service.
6.2. Preference cookies
They allow us to remember:
- Language.
- Region.
- Appearance.
- Settings.
- Interface options.
- Non-essential preferences.
They may require consent depending on the jurisdiction.
6.3. Analytical cookies
They help us understand:
- Visits.
- Navigation.
- Performance.
- Conversions.
- Errors.
- Feature usage.
- Traffic sources.
We may use analytics services, including Google Analytics or equivalents.
Where necessary, they will only be activated with consent.
6.4. Advertising cookies
They may be used to:
- Measure campaigns.
- Attribute conversions.
- Build audiences.
- Personalize ads.
- Cap frequency.
- Analyze advertising performance.
We may work with platforms such as Google, Meta, TikTok, Microsoft or other providers.
They will be used in accordance with the available consent options and applicable law.
6.5. Functionality and integration cookies
They allow the use of external features, such as:
- Social login.
- Embedded content.
- Video.
- Maps.
- Payments.
- Integrations.
- External resources.
The provider may set its own cookies.
6.6. Security cookies
They are used to:
- Detect bots.
- Prevent abuse.
- Mitigate attacks.
- Verify traffic.
- Protect forms.
- Maintain the integrity of the Service.
Some are strictly necessary.
7. Tools and providers
Depending on the current configuration, QRzen.io may use:
- Analytics services.
- Advertising platforms.
- Social networks.
- Security providers.
- Authentication providers.
- Payment providers.
- Infrastructure and distribution.
- Measurement and diagnostic tools.
The specific list may evolve.
The cookie settings panel, when available, will show up-to-date information about active categories and providers.
8. Indicative cookie table
The following table describes cookies or identifiers that may be used. The name and duration may vary depending on the technical configuration.
The pages that open when a dynamic code is scanned also use a first-party visitor cookie, with a random identifier and a lifetime of 30 days, whose only purpose is to measure how many different browsers open the same code. It is first-party, is not shared, and is not used for advertising or to track the user across sites.
This table is descriptive and may be supplemented through the consent panel.
9. Consent
Where the law requires it, we will request consent before using non-necessary cookies.
The user will be able to:
- Accept all.
- Reject non-necessary ones.
- Configure categories.
- Withdraw consent.
We will not make general access conditional on accepting advertising cookies, unless a specific feature legitimately depends on a third party and an adequate explanation is provided.
10. Managing preferences
The user can change their choices through the “Cookie settings”, “Privacy preferences” link or button, or equivalent available on the site.
Withdrawing consent does not affect the lawfulness of prior processing.
Changes may take a short period to apply and do not automatically delete cookies already stored by third parties. These can be deleted from the browser.
11. Consent Mode and privacy signals
QRzen.io may use technical mechanisms that adjust the behavior of tags and services according to the user's preferences.
These mechanisms may send limited signals or cookieless data to:
- Maintain security.
- Model aggregated metrics.
- Verify consent status.
- Adapt the operation of providers.
They will be configured in accordance with the law and the options chosen.
12. Browser settings
Browsers allow you to block, delete or limit cookies.
The path depends on the browser and device.
Blocking all cookies may cause:
- Inability to log in.
- Loss of preferences.
- Form failures.
- Payment issues.
- Reduced security.
- Incomplete operation.
13. Cookies on Customer pages
Pages, forms or content created by Customers may incorporate additional resources or integrations.
The Customer will be responsible for:
- Determining which technologies it installs.
- Informing visitors.
- Obtaining consent.
- Configuring its tools correctly.
- Complying with applicable laws.
QRzen.io may provide technical mechanisms but does not guarantee that the Customer's configuration is legally sufficient.
14. QR codes and server logs
Simply scanning a dynamic code may generate technical logs even if the End User rejects cookies.
These logs may include IP, date, time, device and request, and may be necessary to:
- Resolve the redirect.
- Maintain security.
- Prevent fraud.
- Diagnose errors.
- Generate limited statistics.
When used for additional analytical or advertising purposes, the corresponding legal bases and consents will apply.
15. International transfers
Some providers may process information outside the user's country.
Where necessary, appropriate legal mechanisms will be applied, such as adequacy decisions or recognized contractual clauses.
Further information can be found in the Privacy Policy.
16. Provider updates
Cookies may change when:
- QRzen.io is updated.
- A feature is added.
- A provider changes.
- An integration is modified.
- Security measures are applied.
- Regulation changes.
We will update this Policy or the panel when necessary.
17. Changes to the Policy
We may modify this Policy to reflect the actual use of technologies, legal changes or new features.
The current version will indicate its update date.
Last updated: 20/10/2026