Cookie Policy
This Cookie Policy explains how Veyra Apps uses cookies and similar technologies, what they do, who provides them and how visitors can control their preferences.
Who is responsible for this website?
The website operator and data controller for the activities described in this policy is:
- Legal name
- [[LEGAL NAME OF THE CONTROLLER]]
- Trading name
- Veyra Apps
- Business address
- [[PUBLIC BUSINESS OR PROFESSIONAL ADDRESS]]
- Country of establishment
- Spain
- Contact email
- hello@veyraapps.com
- Website
- veyraapps.com
Replace the legal-name and public-address placeholders with the same verified details used in the Legal Notice and Privacy Policy.
What are cookies and similar technologies?
Cookies are small files or pieces of information that a website may store on, or read from, a visitor’s device. They can support essential functions, remember choices, measure how a website is used or enable services supplied by another organisation.
Similar technologies may include local storage, session storage, pixels, tags, software-development-kit identifiers or other mechanisms that store or access information on a device. References to cookies in this policy also include those technologies where appropriate.
First-party and third-party technologies
First-party cookies
First-party cookies are set from the Veyra Apps website domain or by systems operated for Veyra. They may support security, consent choices, forms, sessions and other website functions.
Third-party cookies
Third-party cookies or similar technologies are set or accessed by another provider whose service is included on the website, such as an analytics, video, payment, security or embedded-content provider.
The exact provider, purpose and duration of every active technology will be listed in the inventory below after the production website has been scanned and configured.
How technologies are grouped
Strictly necessary
Always activeTechnologies required to transmit communications, provide functionality explicitly requested by the visitor, protect the website or remember consent choices.
Preferences and functionality
Optional where requiredTechnologies that remember optional settings or enable enhanced functionality that is not strictly required for the basic website experience.
Statistics and analytics
Consent controlledTechnologies used to understand traffic, navigation, performance and aggregated usage patterns. They are treated as optional unless a documented legal exemption applies.
Marketing and profiling
Consent requiredTechnologies used to personalise advertising, measure campaigns, build audiences or track activity across websites or services.
Cookies and similar technologies currently used
The final inventory must reflect the production website after WordPress, WooCommerce, login, caching, security, analytics, embedded content and the consent-management platform have been configured.
Replace the placeholder rows below with the verified inventory generated from the final production scan. Remove categories that are not used.
Strictly necessary technologies
Core operation, security, consent and requested functions.
| Name | Provider | Purpose | Duration | Storage type |
|---|---|---|---|---|
| [[COOKIE OR STORAGE KEY]] | [[PROVIDER AND DOMAIN]] | [[VERIFIED PURPOSE]] | [[SESSION OR EXPIRY]] | [[HTTP COOKIE / LOCAL STORAGE / OTHER]] |
Preferences and functionality
List active optional functionality or state that this category is not used.
| Name | Provider | Purpose | Duration | Consent category |
|---|---|---|---|---|
| [[COOKIE NAME OR “NOT CURRENTLY USED”]] | [[PROVIDER]] | [[PURPOSE]] | [[DURATION]] | Preferences |
Statistics and analytics
List the final analytics configuration after consent blocking has been tested.
| Name | Provider | Purpose | Duration | Consent category |
|---|---|---|---|---|
| [[COOKIE NAME OR “NOT CURRENTLY ACTIVE”]] | [[ANALYTICS PROVIDER]] | [[VERIFIED ANALYTICS PURPOSE]] | [[DURATION]] | Statistics |
Marketing and profiling
List advertising technologies or confirm that this category is not active.
| Name | Provider | Purpose | Duration | Consent category |
|---|---|---|---|---|
| [[COOKIE NAME OR “NOT CURRENTLY USED”]] | [[MARKETING PROVIDER]] | [[VERIFIED PURPOSE]] | [[DURATION]] | Marketing |
How permission is obtained
Strictly necessary technologies may be used where they are required to provide a function explicitly requested by the visitor or to support the transmission, security and essential operation of the service.
Where consent is required, optional technologies are blocked until the visitor makes an informed choice. The consent interface should provide clear options to accept, reject or configure optional categories without making rejection more difficult than acceptance.
Consent applies only to the categories and providers selected by the visitor and may be withdrawn or changed at any time through the cookie-preferences control.
Manage or withdraw cookie consent
Cookie preference centre
Use the website’s cookie-preferences control to review optional categories, change an earlier choice or withdraw consent.
Withdrawing consent does not affect processing that was lawful before the preference was changed.
[[INSERT COMPLIANZ “MANAGE CONSENT” BUTTON, LINK OR SHORTCODE HERE]]
Replace this placeholder after Complianz is configured and confirm that the control reopens the live preference centre.
Delete or restrict stored information through your browser
Most browsers allow users to review, delete or block cookies and site storage. Browser controls operate separately from the website’s consent tool and may affect strictly necessary functionality if all storage is disabled.
External providers and international processing
Third-party providers may process information under their own privacy terms and may operate from countries outside the European Economic Area. The inventory will identify the relevant providers and should be read together with the Privacy Policy.
Insert links to the privacy and cookie information of each active third party and confirm the applicable international-transfer safeguards: [[THIRD-PARTY PROVIDERS, POLICY LINKS AND TRANSFER DETAILS]].
Cookie duration and consent records
Each cookie or storage item remains active for the period shown in the verified inventory. Session technologies normally expire when the browsing session ends, while persistent technologies remain until their expiry date or earlier deletion.
The website may retain a record of the visitor’s consent choices for the period needed to remember the preference and demonstrate that consent was managed correctly.
Replace with the actual consent-record and preference-retention period configured in Complianz: [[CONSENT RECORD RETENTION PERIOD AND COOKIE PREFERENCE EXPIRY]].
Changes to this Cookie Policy
This policy may be updated when cookies, providers, embedded services, analytics, advertising technologies or applicable requirements change.
The current version will remain available on this page with its effective date and last-updated date. A new consent choice may be requested where a change materially affects optional technologies or their purposes.
Questions about cookies or privacy
Questions about this Cookie Policy or the use of technologies on the website may be sent to:
- Email: hello@veyraapps.com
- Controller: [[LEGAL NAME OF THE CONTROLLER]]
- Address: [[PUBLIC BUSINESS OR PROFESSIONAL ADDRESS]]
Continue through the legal hub
Review optional technologies whenever you need to.
The live preference centre will remain accessible after the consent-management platform has been configured for production.