Cookie Policy
1. About this Policy
This Cookie Policy explains how VIDA uses cookies and similar storage or access technologies on its website and related web service.
The term “cookies” is sometimes used broadly in this Policy for readability, but the technologies covered may also include browser session storage, local storage, IndexedDB, service-worker storage and other technologies that store information on or access information from a user's browser or device.
This Policy should be read together with VIDA's Privacy & Data Policy.
VIDA is operated by VIDA NETWORK LTD, incorporated in England and Wales, United Kingdom. VIDA Colombia primarily serves users in Colombia.
Operator details are provided in the Terms of Use and Privacy & Data Policy.
3. How VIDA currently uses browser storage
VIDA currently uses browser or device storage for purposes connected with operating the service.
These purposes may include:
- authenticating members and maintaining secure sessions;
- refreshing authentication where necessary;
- remembering the selected interface language;
- preserving incomplete signup information during onboarding;
- maintaining temporary navigation or Discover state;
- preserving appropriate draft or conversation state where implemented;
- supporting photo-upload or recovery checkpoints where implemented;
- operating Web Push on devices where the member has enabled it;
- storing device/browser information needed to prevent duplicate push displays;
- preserving technical selections made by the user; and
- maintaining security and service integrity.
VIDA does not currently intend to use browser storage for behavioural advertising or cross-site advertising tracking.
If that changes, VIDA must update this Policy and implement any additional notice, consent or control required by applicable law before introducing the relevant technology.
4. Authentication and security cookies
VIDA uses Supabase authentication infrastructure.
Supabase authentication may use first-party cookie-based session information to:
- identify an authenticated session;
- keep a member signed in where appropriate;
- securely refresh authentication;
- complete passwordless authentication flows;
- protect authenticated routes and account functions; and
- prevent unauthorized use of authenticated services.
The precise cookie names may depend on the Supabase project and authentication configuration.
Authentication and security storage is used only to the extent necessary for the relevant account, session and security purposes.
Blocking or deleting authentication cookies may sign the member out or prevent authenticated VIDA functionality from working correctly.
Where the applicable UK storage/access rules apply, storage that is strictly necessary to authenticate a user or securely provide a service requested by that user may be used without separate cookie consent.
5. Language preference
The vida_locale cookie remembers your selected language for up to one year. In the language menu, turn off ‘Remember my language’ to remove it and stop it being recreated. A separate vida_locale_disabled cookie stores only this objection for up to one year; it does not store your chosen language. Explicit /en and /es routes continue to work and authentication is unchanged. With remembering disabled, an address without a language prefix uses the site's default language. Turning remembering on stores your current language again. Clearing cookies also clears the objection, so you will need to set it again.
6. Onboarding and temporary session storage
During signup, VIDA may use browser session storage to preserve information entered during the multi-step onboarding process.
This can include temporary `signup_*` values corresponding to onboarding steps such as username, gender, Looking for, date of birth, city, height, weight, photo state and biography.
This temporary storage helps the member move between signup steps without unnecessarily losing information already entered.
Browser session storage is generally scoped to the applicable browser session and is separate from VIDA's server-side account records.
Onboarding information that is ultimately submitted to VIDA is processed in accordance with the Privacy & Data Policy and Personal Data Authorization.
Clearing browser storage during onboarding may cause unfinished signup information to be lost.
7. Functional browser storage
VIDA may use browser storage to preserve temporary interface or functional state.
Depending on the implemented feature, this may include information such as:
- Discover state;
- loaded results or navigation state;
- filters;
- scroll position;
- temporary conversation or draft state;
- upload checkpoints; and
- other short-term interface state intended to make navigation more reliable.
This information is used for VIDA functionality rather than cross-site advertising.
Some functional storage may qualify for an applicable exception from prior consent under UK rules where its sole purpose is to provide requested functionality or adapt VIDA's appearance or operation to the user's preference.
Where an applicable exception requires VIDA to provide a simple and free means of objecting, VIDA must provide that control before relying on the exception.
If particular functional storage does not qualify for an applicable exception, VIDA must obtain any consent required before using it.
8. IndexedDB and local browser databases
Some VIDA functions may use IndexedDB or another structured browser-storage mechanism.
Current or planned VIDA uses may include:
- temporary photo or upload checkpoint information;
- browser/device binding information for Web Push; and
- delivery identifiers used to reduce duplicate notification display.
Browser database information remains on the relevant browser/device unless it is separately transmitted to VIDA as part of the associated service.
Clearing browser site data may remove this information and may cause the corresponding browser feature to be reset or re-enrolled.
VIDA does not use IndexedDB as a hidden behavioural-advertising profile.
9. Web Push storage
Web Push enrollment is currently unavailable in VIDA. In-site Notifications remain available.
If Web Push is reintroduced, VIDA will request browser or operating-system notification permission only when the member chooses to enable it.
Where permission is granted, the browser may maintain a Push subscription containing information required to route notifications.
VIDA's Web Push implementation may also use browser-side storage or service-worker information for purposes such as:
- associating the browser with the appropriate VIDA account;
- maintaining a device/browser binding;
- preventing or reducing duplicate notification display;
- remembering recent delivery identifiers; and
- opening or focusing the appropriate VIDA destination after interaction with a notification.
The VIDA service worker is not intended to provide a general offline browsing cache and does not intercept ordinary VIDA page requests merely to create an offline copy of the service.
Disabling Web Push or clearing the relevant browser data may require the device to be enrolled again before push notifications can resume.
10. Analytics, advertising and tracking
At the drafting date of this Policy, VIDA has not intentionally integrated behavioural-advertising cookies, cross-site advertising trackers or advertising-profile technology into the service.
VIDA must not introduce non-exempt advertising or tracking technologies on a user's device before obtaining any consent required by applicable UK law.
Consent, where required, must involve a valid affirmative choice. Merely continuing to use VIDA is not sufficient where applicable law requires consent.
VIDA must not use preselected acceptance controls for technologies that require consent.
If VIDA later introduces analytics, measurement or similar technologies, VIDA must first determine whether the particular technology qualifies for an applicable legal exception or requires consent.
Where VIDA relies on a UK statistical-purpose exception for eligible privacy-preserving analytics, the information must be used only within the legal limits of that exception, users must receive clear information and a simple free means of objecting must be available.
Advertising purposes do not qualify for the UK statistical or appearance exceptions.
11. Third-party technologies
VIDA uses third-party infrastructure to operate parts of the service.
Current core technical providers include Supabase for authentication, database, storage and realtime infrastructure and Cloudflare Workers AI for eligible message translation.
The fact that VIDA uses a third-party provider does not necessarily mean that provider places a cookie or browser tracker on every VIDA visitor.
VIDA will identify third-party storage or access technologies where they are actually used on the user's device and where disclosure is required.
VIDA must review future payment, analytics, support, embedded-content or advertising providers before deployment to determine whether they introduce additional cookies, scripts, SDKs or browser/device storage.
A future provider must not be allowed to introduce non-essential tracking contrary to the choices and notices VIDA provides to users.
12. When consent is required
Under applicable UK rules, not every cookie or storage technology requires prior consent.
Depending on its exact purpose and implementation, an exception may apply where storage or access is used:
- solely to transmit a communication;
- because it is strictly necessary to provide an online service requested by the user;
- for qualifying statistical purposes;
- to adapt the appearance or functionality of a service to the user's preference; or
- for another applicable statutory exception.
The requirements of each exception must actually be satisfied.
Some exceptions, including qualifying statistical and appearance/functionality uses, require clear information and a simple, free means for the user to object.
If VIDA cannot rely on an applicable exception, VIDA will obtain any valid consent required before storing or accessing the relevant information.
Where consent is required, users must be able to withhold or later withdraw it without VIDA treating continued browsing as consent.
13. Users in Colombia
Cookies and similar technologies may collect or generate personal data from devices located in Colombia.
Where Colombian personal-data law applies, VIDA processes that information subject to the Privacy & Data Policy and the applicable authorization, transparency, security, rights and other data-protection requirements.
VIDA does not treat its status as a UK company as removing Colombian data-protection obligations that legally apply to processing carried out in relation to users or devices in Colombia.
The use of a browser-storage technology does not give VIDA permission to use personal data for purposes unrelated to those disclosed and lawfully authorized.
14. Your controls
Depending on the technology, users may be able to manage browser/device storage by:
- changing settings provided within VIDA;
- changing the selected VIDA language;
- revoking notification permission in the browser or operating system;
- clearing VIDA cookies or site data;
- clearing browser storage;
- blocking cookies through browser settings; or
- using any additional VIDA storage/consent controls introduced for technologies that require them.
Blocking all cookies may prevent login and other authenticated VIDA features from operating.
Clearing all site data may remove language preferences, unfinished onboarding state, temporary interface information and device-specific Web Push information.
Browser settings alone will not be treated as the only mechanism for an objection or consent where applicable law requires VIDA itself to provide an additional control.
15. Duration and storage review
Different browser-storage technologies remain for different periods.
Session-based information is generally removed when the relevant browser session ends, subject to browser behaviour.
Persistent cookies remain until their configured expiry, replacement or deletion.
Authentication-cookie duration may be connected to the applicable Supabase session and token configuration.
Push subscriptions may remain until disabled, expired, invalidated, removed or otherwise ended through the push/account lifecycle.
IndexedDB and similar persistent browser storage may remain until VIDA removes it through the feature lifecycle or the user/browser clears the relevant site data.
Before commercial launch and whenever VIDA materially changes its storage technologies, VIDA will review the actual technologies, purposes and configured durations so this Policy remains accurate.
VIDA will not intentionally retain device storage longer than reasonably necessary for its stated purpose.
16. Changes and contact
Version: cookies-v3 Effective date: 16 October 2026 Last updated: 16 October 2026
VIDA may update this Policy when browser technologies, service providers, legal requirements or VIDA functionality change.
If VIDA introduces a storage/access purpose that requires consent, VIDA will implement the required choice before that technology is activated for users who have not provided the required consent.
Questions about this Policy may be sent to:
Email: [email protected]
VIDA is operated by VIDA NETWORK LTD. Any storage controls required by applicable law must be in place before the relevant technology is used.
Visitor measurement
VIDA's first-party visit measurement uses no tracking cookies, persistent browser identifiers or third-party analytics SDK. The control “Exclude this browser from visit measurement” stores only the value 1 under vida:analytics-disabled in this browser's local storage. It contains no unique identifier and is used only to remember your objection until you remove it or clear site data. The preference applies to this browser; set it separately on other browsers. Clearing site data removes the preference. Do Not Track and Global Privacy Control are also honored. Login, language selection and navigation remain available when you object.