Cookie Policy
Last updated: 21 September 2026
This Cookie Policy explains how Lavoop.com uses cookies and similar technologies, why they are used, and how you can manage your choices.
For this policy, “Lavoop”, “we” and “us” mean Modelhive Limited, whose registered address is Flat 18, Eyot House, London, England, SE16 4BN.
Where you are located and which laws apply
Lavoop.com initially offers its services to users in the United Kingdom and the European Economic Area. Depending on where you are located, different privacy and cookie laws may apply.
Our use of cookies and similar technologies is designed to comply with the Privacy and Electronic Communications (EC Directive) Regulations 2003, SI 2003/2426, the UK GDPR and the EU General Data Protection Regulation.
If you access Lavoop.com from the EEA, EU data-protection law may apply where Lavoop offers services to you or monitors your behaviour in the EEA.
EU representative: Antonia La Verghetta, appointed as Lavoop’s representative in the European Union, can be contacted at privacy@lavoop.com.
Lavoop intends to expand its services to users in the United States and Asia. Before doing so, we will review and, where necessary, adapt our cookie practices, privacy notices, consent mechanisms and user-choice controls to comply with the laws applicable in each relevant jurisdiction. This policy may therefore be updated as Lavoop expands internationally.
What are cookies and similar technologies?
Cookies are small text files stored on your browser or device. They allow a website to remember information between visits. Lavoop.com also uses limited browser local storage, which performs a similar function but stores information locally on your device rather than in a cookie.
Some technologies are necessary for Lavoop.com to provide services you have requested, including signing in and maintaining your session. Other technologies, such as analytics tools, are used only with your consent, in accordance with regulation 6 of the Privacy and Electronic Communications (EC Directive) Regulations 2003, SI 2003/2426 (“PECR”).1
How Lavoop uses cookies and local storage
| Name | Type | Provider | Purpose | Duration | Category |
|---|---|---|---|---|---|
LavoopAuthToken |
Cookie | Lavoop | Maintains your authenticated session and keeps you signed in | Until your browser session ends | Strictly necessary |
lv_consent |
Cookie | Lavoop | Records your analytics consent choice so that we do not ask you repeatedly | Six months | Strictly necessary |
lavoopLastVisit_<userId> |
Local storage | Lavoop | Records when you last visited, so that Lavoop can show you which jobs are new since your previous visit | Until you clear your browser data | Strictly necessary functionality |
lavoopLastAuthMethod |
Local storage | Lavoop | Remembers your last sign-in method so that it can be offered as a shortcut | Until you clear your browser data | Strictly necessary functionality |
_ga, _ga_<container-id> |
Cookies | Google Analytics | Distinguishes visitors and sessions and measures use of Lavoop | Up to two years | Analytics; consent required |
The Lavoop cookies and local-storage items are not shared with third parties. The two local-storage items stay in your browser and are never sent to Lavoop’s servers.
Google Analytics cookies are set only if you select “Accept” for Analytics. If you do not make a choice, or select “Reject”, those cookies are not set.
Why lavoopLastVisit_<userId> is used
Lavoop uses lavoopLastVisit_<userId> to improve the
job-search experience for signed-in users. It records the time of the
user’s previous visit so that Lavoop can distinguish jobs that were
already available at that visit from jobs that have become available
since.
This prevents users from unnecessarily spending time reviewing the same available jobs on every visit and allows them to focus more efficiently on jobs that are new since their previous visit. The feature is therefore directly connected to the job-search functionality requested by the user.
The item:
- is stored only in the user’s browser local storage;
- is not transmitted to Lavoop;
- is read only in the user’s browser, by the Lavoop page itself;
- is not used for advertising, profiling or cross-site tracking;
- does not identify or track the user across unrelated websites; and
- remains until the user clears the relevant browser data.
Lavoop treats this item as strictly necessary functionality because it supports the core job-search experience by enabling the user to see which jobs are new since their previous visit and avoid reviewing the same jobs repeatedly. Under PECR, storage or access may be used without consent where it is strictly necessary to provide a service requested by the user. Lavoop does not use this item for any secondary purpose.
Google Analytics
If you accept Analytics, Lavoop uses Google Analytics 4 to understand how users interact with its public pages and to improve the service. This may include information about:
- pages visited;
- approximate source of the visit, such as a search engine or referral link;
- scrolling and button interactions;
- campaign information included in links;
- browser and device type; and
- approximate location derived from an IP address.
Google Analytics 4 does not log or store IP addresses; Google uses the IP address only to derive an approximate location.
Before an event is sent to Google Analytics, Lavoop removes job IDs, company names and match scores wherever they might otherwise appear. Those details remain in Lavoop’s own systems and are not sent to Google Analytics.
Google Analytics is not requested or loaded before you provide consent. Lavoop’s consent signals default to “denied”. Accepting Analytics enables only the analytics signal; the advertising signals always stay “denied”, because Lavoop runs no advertising.
Google Analytics is provided by Google. Google may process analytics data outside the United Kingdom, including in the United States.
For transfers from the EEA, Lavoop relies on the EU–U.S. Data Privacy Framework.
For transfers from the United Kingdom, Lavoop relies on the UK Extension to the EU–U.S. Data Privacy Framework.
Google’s privacy information is available at https://policies.google.com/privacy.
Lavoop’s own usage data
Separately from Google Analytics, Lavoop records basic product-usage information in its own systems, such as the screen being viewed, a button pressed or a search returning no results.
This information is used to identify and fix product problems and improve Lavoop. It is not used to create advertising profiles and is not shared outside Lavoop.
This processing does not set an additional cookie or local-storage
item. When a user is signed in, the relevant records may be associated
with the user’s account through LavoopAuthToken, which is
required to operate the authenticated service. When a user is signed
out, no identifier is attached to these records and they are reviewed
only in aggregate.
Managing your choices
You can accept or reject Analytics at any time using the Cookie settings link available on Lavoop.com. Changing your choice takes effect on your next page view.
Rejecting Analytics, or not making a choice, does not prevent Lavoop.com from operating. The strictly necessary cookies and local-storage functionality continue to operate.
You can also delete cookies and local-storage items through your browser settings. Deleting them may sign you out, remove your saved sign-in shortcut or cause Lavoop.com to lose track of which jobs are new since your previous visit.
Global Privacy Control and Do Not Track
If your browser sends a Global Privacy Control or Do Not Track signal, Lavoop honours that signal automatically. In that event:
- Google Analytics is not loaded;
- Lavoop’s own usage recording is stopped; and
- the cookie banner is not displayed.
Contact
If you have questions about this Cookie Policy, contact us at privacy@lavoop.com.
Operator: Modelhive Limited
Registered address: Flat 18, Eyot House, London, England, SE16 4BN
You may also complain to the UK Information Commissioner’s Office if you are concerned about how Lavoop has handled your personal data.
For EEA users, you may complain to the data-protection supervisory authority in your habitual residence, place of work or the place of the alleged infringement.
References
- Privacy and Electronic Communications (EC Directive) Regulations 2003, SI 2003/2426, reg 6. ↩