Policy on cookies and similar technologies
This policy explains how Pruvee uses cookies and similar technologies, including the browser's local storage (localStorage). For information about the general processing of personal data, see the Privacy policy.
Last updated: 11 October 2026 · version 2026-10-11
1.Who manages these technologies
The data controller is Andrea Bertolino.
For any question about cookies or similar technologies you can write to info@pruvee.com.
2.What Pruvee uses
Pruvee does not use its own cookies for advertising, profiling or browsing-analysis purposes.
The platform uses some browser web storage of the browser, in particular localStorage, to store on the device the information needed to keep the session active and remember some interface preferences, as well as sessionStorage and localStorage for the internal, aggregated measurement of visits described below.
Web storage is not an HTTP cookie: the data is kept locally by the browser and is not automatically attached to every HTTP request. However, the rules applying to technologies that store or access information on a user's device may also cover tools of this kind. That is why we describe them in this policy alongside cookies.
3.Data stored in localStorage
| Name | Technology | Purpose | Duration |
|---|---|---|---|
| social.auth.token | localStorage | Holds the session token needed to keep you signed in to your account while using the platform. | Until sign-out, removal by the application, or manual clearing of the site's data. |
| social.auth.user | localStorage | Keeps locally the essential data needed to rebuild the account interface: account identifier, email address, username and role. | Until sign-out, removal by the application, or manual clearing of the site's data. |
| pruvee.homeNavOrder | localStorage | Stores the custom order of navigation items chosen by the user. | Until manually cleared or until the site's data is removed. |
| pruvee:sid | sessionStorage | Random identifier of the visit, used to count page views and time spent in aggregated form. It is not a cookie and does not follow the user across other sites. | Until the browser tab is closed. |
| pruvee:first-touch | localStorage | Remembers the channel the first visit came from (for example TikTok, YouTube or a search engine) and its date, to know in aggregated form how many sign-ups come from each channel. It contains no personal identifiers. | 30 days from the first visit, or until the site data is manually deleted. |
The data stored in localStorage is not used to:
- track browsing on other sites;
- build advertising profiles;
- show personalised advertising;
- sell or transfer data to marketing companies or data brokers.
The session token is used by the application to make the requests to Pruvee's services that are needed while you use an account.
4.Why there's no cookie banner
Under the current implementation, Pruvee uses only technical tools needed to:
- authenticate the user;
- keep the session active;
- display the interface correctly;
- remember a browsing preference chosen by the user;
- measure visits and the channel they come from in aggregated form, on Pruvee's own systems only, without third-party tools.
Tools that are purely technical and necessary to deliver the service may be used without the user's prior consent, subject to the obligation to provide clear information.
For this reason, as things stand, Pruvee does not show a banner asking for cookie consent.
Pruvee currently does not use:
- Google Analytics;
- Google Tag Manager for tracking purposes;
- Meta Pixel;
- social network pixels;
- advertising tools;
- third-party behavioural analytics tools;
- advertising profiling systems.
Internal statistics on platform usage are processed on the systems used by Pruvee and are described in the Privacy policy.
If Pruvee introduces non-essential tools, or tools requiring consent, in future, this policy will be updated and consent will be requested before they are activated, where applicable law requires it.
5.Signing in with Google or Apple
Pruvee offers the option to sign in or sign up with Google or with Apple.
The Google Sign-In and Sign in with Apple components are not loaded when you open the sign-in or sign-up pages. Each one is activated only when you choose to use the corresponding button, “Continue with Google” or “Continue with Apple”.
Before that interaction, Pruvee loads neither component and, for this feature, your browser makes no requests to Google's or Apple's servers.
When you choose to use Google Sign-In:
- your browser may communicate with Google's servers;
- Google may use cookies or similar technologies needed for its own service to work;
- Google may receive technical information about the authentication request;
- Google processes the data as an independent controller under its own policy.
For more information see Google's privacy policy.
When you choose to use Sign in with Apple:
- your browser may communicate with Apple's servers;
- Apple may use cookies or similar technologies needed for its own service to work;
- Apple may receive technical information about the authentication request;
- Apple processes the data as an independent controller under its own policy.
For more information see Apple's privacy policy.
Pruvee does not control the cookies and technologies used directly by Google or Apple. Should either provider change how its component works or introduce further tools not needed for authentication, Pruvee will reassess the configuration and update this policy.
6.Typefaces and external resources
The typefaces used by Pruvee's interface are hosted on the systems used by Pruvee and delivered together with the application's pages.
Your browser therefore does not need to contact Google Fonts or other external networks to display the interface's typefaces.
For typefaces, Pruvee uses no third-party cookies or advertising tracking tools.
7.How to clear the stored data
You can remove the locally stored data in several ways.
Sign out
Signing out of the platform removes the session data used by the application, including the authentication token, as the application is designed to do.
Browser settings
You can clear localStorage and the other data stored by Pruvee through your browser settings, usually in the section covering:
- privacy;
- cookie;
- site data;
- site storage;
- browsing data.
The steps vary depending on the browser and device you use.
After the local data is cleared:
- you will have to sign in again;
- some interface preferences may be reset;
- your account and the data held on Pruvee's servers will not be deleted automatically.
Clearing your browser data is not the same as deleting your account. To delete your account or the data held by Pruvee, use the features available on the platform or write to info@pruvee.com.
8.Security
The data stored in your browser is accessible to the site's pages according to the security rules of the browser and of Pruvee's web origin.
Do not share your device with unauthorised people, and keep your browser and operating system up to date. If you suspect your account has been compromised, sign out, change your password and contact us at info@pruvee.com.
Pruvee applies technical and organisational measures to protect your account and communications, but no computer system can be considered entirely free of risk.
9.Changes to this policy
We may update this policy to reflect:
- technical changes to the platform;
- cookies being introduced or removed;
- new similar technologies being introduced;
- changes to the providers used;
- changes to applicable law.
The updated version will be published on this page with its date and version.
If tools requiring consent are introduced, Pruvee will update its preference management system and request consent before activating them, where the law requires it.
10.Contact
For questions about this policy you can write to info@pruvee.com.