Draft pending legal review. This text is not final and may change before it takes effect.
This policy explains which cookies Vecta 360 uses on its website and platform, what they are for and how they can be managed, in accordance with Article 22.2 of Spanish Law 34/2002 on information society services and electronic commerce (LSSI-CE) and with data protection legislation.
1. What cookies are
A cookie is a small file that a website stores in the browser to remember information between pages or visits. Cookies may be first-party, if set by the site being visited, or third-party, if set by another entity; and session cookies, if deleted when the browser is closed, or persistent cookies, if they remain for a set period.
2. Types of cookies used by Vecta 360
Vecta 360 uses only first-party cookies, except for those Stripe may set on payment pages. It does not use advertising cookies or third-party analytics cookies. Its cookies fall into the following groups:
- Technical and strictly necessary: they allow users to sign in, stay signed in and use the basic features of the service. Without them, the service cannot work.
- Preference: they remember options chosen by the user, such as language, light or dark theme, or whether the sidebar is open.
- Analytics or statistics: they allow unique views of virtual tours and their multimedia content to be counted.
3. Consent
Under Article 22.2 LSSI-CE, technical cookies and cookies strictly necessary to provide a service expressly requested by the user do not require consent.
Cookies that are not exempt will only be set with the user's consent, which the user may give, refuse or withdraw at any time through [MECANISMO DE CONSENTIMIENTO DE COOKIES].
The vecta_vid cookie is an analytics cookie. It is not necessary for the service to work, contains only a random identifier, is not disclosed to third parties and is not used for advertising or profiling.
4. Cookies used
The table below lists the cookies used by Vecta 360. In the name of the session cookie, [ref] is the technical identifier of the database project.
sb-[ref]-auth-token
Keeps the user signed in (authentication through Supabase).
First party (Vecta 360)
About 400 days
Technical, strictly necessary
NEXT_LOCALE
Remembers the chosen language.
First party (Vecta 360)
Session
Technical, preference
locale-session
Records that the session's language has already been loaded.
First party (Vecta 360)
Session
Technical, preference
theme
Remembers whether the light or dark theme has been chosen.
First party (Vecta 360)
Persistent
Preference
sidebar_state
Remembers whether the application sidebar is open or closed.
First party (Vecta 360)
7 days
Preference
vecta_signup
Temporary flag created after a new account's first sign-in to record the sign-up.
First party (Vecta 360)
A few minutes
Technical
vecta_vid
Random visitor identifier used to count unique views of virtual tours and their multimedia content.
First party (Vecta 360)
1 year
Analytics (statistics)
Stripe cookies
Operation of payments and fraud prevention on payment pages.
Stripe (third party)
As set out in Stripe's cookie policy
Payment and fraud prevention, according to Stripe
5. Third-party cookies
On payment pages, Stripe may set its own cookies to provide the payment service and prevent fraud. Stripe is responsible for those cookies, which are described in its own cookie policy.
When Google Calendar is connected, authorisation takes place on Google pages, which are subject to Google's policies.
6. How to manage or delete cookies
In addition to the options described in section 3, cookies can be blocked or deleted in the browser settings. How to do this depends on each browser and is explained in its help section.
If technical cookies are blocked, it is not possible to sign in or use the platform normally. If preference cookies are blocked, the options chosen will not be remembered.
