Cookie Policy

Cookies are small text files that a website asks your browser to store on your device. On each subsequent visit, the browser sends those files back to the website that created them, which allows it to recognise your browser and remember information between pages and between visits: a preference, a step already completed, a video already watched.

There are also equivalent technologies, such as the browser's local storage or identifiers calculated from technical characteristics of the device, which perform similar functions without being cookies in the strict sense. Where this policy refers to cookies, it includes those technologies whenever we use them.

alturys.dev uses cookies for two things: making the website work as you would expect and understanding, in aggregate, how it is used. We do not use advertising cookies, we do not integrate advertising networks and we do not sell or pass on your data to third parties for commercial purposes.

A cookie notice is shown on your first visit. Cookies that are not strictly necessary (identity, vsl-booking and vsl-who_we_are) are only set after you accept it; until then, the only cookie present is cookies-accepted, which stores your answer to the notice itself. There is no reject button: if you do not wish to accept, simply do not continue browsing, and no non-essential cookie will remain in your browser.

First-party cookies, set directly by alturys.dev, serve only the operation and statistics of the website. They are the responsibility of Guilherme André Cabral, a sole trader operating under the Alturys brand, identified in full in the Privacy Policy. Third-party cookies only reach your browser when you interact with content embedded from other platforms, such as YouTube videos or the booking calendar, and are described in the Third-party cookies section.

All cookies set by alturys.dev are valid for 400 days and are set with the SameSite=Lax attribute and, over https connections, with the Secure attribute. For the cookies-accepted, identity, vsl-booking and vsl-who_we_are cookies, that period is renewed on each visit; for the staff cookie, it runs from the moment of authentication. The table summarises them and the paragraphs that follow explain each one in detail.

cookies-accepted: records the answer you gave to the cookie notice. It is created with the value 0 when the notice appears and changes to 1 when you accept. It is a strictly necessary cookie: without it, the website would have no way of knowing that you had already answered and would show the notice again on every page.

identity: stores a unique identifier for your device and browser, as its name suggests. After you accept the cookie notice, the identifier is generated in your browser by the open source FingerprintJS library and the value is recorded in the cookie. We use it to recognise repeat visits, for usage statistics and to remember state between visits. The Device identification section explains in detail how it works and what guarantees we give you.

vsl-booking: stores the value 1 or 0 and records whether you watched the introductory video on the booking page to the end. When the value is 1, the booking calendar stays unlocked on subsequent visits, without you having to watch the video again.

vsl-who_we_are: stores the value 1 or 0 and records whether you watched the video on the About Us page to the end. It is used for statistical purposes only and changes nothing in what the website shows you.

staff: exists only in the browser of someone who accesses the website as a team member during maintenance periods. It contains a cryptographic digest (hash) of the access credential, never the credential in plain text. It is valid for 400 days from authentication and is not renewed on subsequent visits. If you have never accessed the website under those conditions, this cookie does not exist in your browser.

The identity cookie involves identifying the device, so it deserves a full explanation. After you accept the cookie notice, the open source FingerprintJS library analyses technical characteristics of your browser (for example, the rendering engine, the available fonts and other properties of the environment) and combines them into a unique identifier. That analysis takes place locally, in your browser: nothing is sent to third parties to calculate the identifier. The resulting value is stored in the cookie.

Because the identifier is calculated from characteristics of the browser itself, deleting this cookie alone does not remove it permanently: as long as your acceptance remains recorded, the calculation is repeated on your next visit and, if your browser remains the same, the same value is likely to be recovered. If you also delete the cookies-accepted cookie, the notice reappears and nothing is calculated without fresh acceptance. This behaviour sets it apart from an ordinary cookie, which is why we describe it here in such detail.

The identifier is used to:

• recognise repeat visits to alturys.dev;
• produce usage statistics for the website;
• remember state between visits, such as videos already watched.

Certain uses are expressly excluded:

• it is not shared with third parties;
• it is not used for advertising or for building advertising profiles;
• it is not matched against your activity on other websites.

If you wish to object to this form of identification, write to [email protected] and we will stop associating your device identifier with any processing. You may also lodge a complaint with the CNPD, the Portuguese data protection authority, at www.cnpd.pt. Your rights over personal data, and how to exercise them, are described in the Privacy Policy.

We do not set third-party cookies by default. They only reach your browser when you interact with content embedded from other platforms:

• YouTube (Google): the videos on the website are embedded from YouTube. Only when you play a video may YouTube set cookies in your browser, in accordance with Google's privacy policy.
• Business Hub (Savvy Growth): meeting bookings are made in an iframe from Business Hub, the management platform of Savvy Growth, which acts as processor. Within that iframe, the platform sets its own functional cookies, which are necessary for the calendar to work. The data you submit there (name, email address, telephone number and answers) is processed on that platform on behalf of the provider, as described in the Privacy Policy.
• Cloudflare: the website infrastructure is served through Cloudflare, which may set technical cookies, such as __cf_bm, used for security and performance, for example to distinguish automated traffic from real visitors. See Cloudflare's privacy policy.

We do not control the cookies set by these platforms or the data they collect, and their policies may change without any involvement on our part. It is worth reading the original documents at the links above.

You can view, delete or block cookies at any time in your browser settings. All current browsers let you see the cookies stored by each website, delete them individually or all at once, and block third-party cookies or cookies from specific websites. Look for the privacy section in the settings of the browser you use (Chrome, Firefox, Safari, Edge or another).

The website continues to work without cookies. The practical consequences, cookie by cookie, are as follows:

• cookies-accepted: deleting it causes the cookie notice to reappear on your next visit, and no non-essential cookie is set until you accept again. It is the most direct way of withdrawing consent from within the browser itself.
• identity: deleting it removes the identifier from the browser; as long as your acceptance remains recorded, the calculation is repeated on your next visit and the same value is likely to return, as explained in the Device identification section. To withdraw consent, also delete cookies-accepted or contact us at [email protected].
• vsl-booking: deleting it means the booking page will once again ask you to watch the introductory video to the end before unlocking the calendar.
• vsl-who_we_are: deleting it changes nothing in what you see. It simply means that the fact you had already watched the video on the About Us page is no longer recorded for statistics.
• staff: deleting it requires the team to authenticate again during a maintenance period. If you are not part of the team, this cookie does not exist in your browser.

Blocking third-party cookies in your browser may prevent the embedded videos from playing or the booking calendar from loading.

This policy is revised when the cookies we use, the technologies behind them or the content embedded on the website change. Each revision is published on this page, with the revision date shown at the top, and the version published here is the one in force.

The processing of personal data associated with these cookies is described in the Privacy Policy, and the conditions of use of the website and the services are set out in the Terms of Service. For any question about cookies, please write to [email protected].