Cookie Policy

Cookies are small files that a website stores on your device when you visit it. They are used to remember information about your session, your preferences or how you use the site. We also use similar technologies such as local storage (localStorage) and pixels.

Strictly necessary cookies

Essential for the platform to work: signing in, security and basic preferences. They don't require your consent.

Functionality cookies

They remember options you have chosen (language, theme, editor preferences) to personalise your experience.

Measuring visits to Folios

Folioss doesn't use Google Analytics or any third-party analytics tool. So that whoever publishes a Folio can know how many visits it has had, we store a random identifier in the visitor's browser, in the local storage of the site where the Folio is shown (folioss.com, or the Folio's own domain if it has one), under the key "folio_visitor_id". That identifier is a randomly generated number: it doesn't contain your name, your email or any data about you, and it isn't shared with anyone.

Along with it we record which Folio was viewed, which page the visit came from and the date. If you click something inside the Folio (a button, a link, a poll option...) or submit one of its forms, we also record what you clicked or which form it was, but not what you write in it; the exception is the "Ask me" block, where the question you ask is recorded so that whoever publishes the Folio knows what they are being asked. Along with that we record the country the visit comes from, which we work out from the IP address at that moment and without storing it (never anything more precise than the country); whether it is a mobile, a tablet or a computer; and, if it can be known, the network or app the visit comes from (Instagram, TikTok…). The countries come from DB-IP's "IP to Country Lite" database (db-ip.com), licensed under CC BY 4.0. We don't store your IP address. The identifier is only used to avoid counting the same person ten times; it doesn't allow us to recognise you on other websites or to build a profile of you. All of this is deleted automatically after 25 months.

The identifier lasts thirteen months at most: the day it was created is stored with it ("folio_visitor_id_desde") and, once that period is over, it is thrown away and a new one is created, even if you keep coming back. You can delete it earlier whenever you want by clearing this site's data in your browser (in Chrome, Firefox, Safari or Edge: privacy and security settings, clear browsing data or website data). When you do, a new one will be generated the next time you visit a Folio.

Network profiles don't carry this measurement: when you look at a profile, no identifier for counting visits is stored in your browser, and if you are not signed in, nobody knows you have been there. If you are signed in and your profile is switched on, the visit may be recorded so that the other person knows who has viewed their profile, unless you visit anonymously. That isn't stored in your browser but in your account, and we explain it in the Privacy Policy, under "Your profile in the network".

What is stored on each Folioss site

Folioss runs on two sites: folioss.com, where the website, the Folios (folioss.com/@name) and the network (folioss.com/red) are, and app.folioss.com, where you create your account and manage your Folios. This is what we ourselves store in your browser on each one (what other services we use, such as Google or Stripe, may store is explained in "Third-party cookies"):

• On the website (folioss.com): a cookie called "idiomaElegido" with the language of the page you are viewing, so that sign-in and sign-up on app.folioss.com appear in that same language. It lasts one year and is shared by folioss.com and app.folioss.com. The website stores nothing else.
• On Folios (folioss.com/@name, or the Folio's own domain): the measurement identifier we explain above; if the Folio is protected with a PIN and you enter it, a cookie ("portfolio_pin") that keeps it for one hour so that you don't have to type it again; if you take part in a Folio block (a poll, a waiting list, a guestbook, a signature...), what you did in it, so that the Folio remembers it when you come back from that browser; and, if you open the "Created with Folioss" window and choose another language in it, that language ("folioss:idioma-de-la-ventana", in local storage), so that the window speaks to you in it next time. That language only changes the window: it doesn't change the language of the Folio or of your account.
• On the network (folioss.com/red): a cookie called "folioss-tema" with light or dark mode (at first, your device's), which lasts one year; a cookie called "idiomaEnLaRed" that remembers for one year which language you view it in; what you are writing, so that it isn't lost if you reload the page (it is deleted when you close the tab, except the draft of a case study, which stays until you publish it or discard it); while you confirm your email, a cookie called "folioss-vuelta" with the screen to go back to afterwards, which expires after one day, and small notices from the screen itself that are deleted when you close the tab. Those three cookies are shared by folioss.com and app.folioss.com, so that when you sign in or create your account you see the network as you had it and get back to where you were.
• On the platform (app.folioss.com): the session cookie, which keeps you signed in to your account. It is valid for the whole of folioss.com, not only app.folioss.com: that way the Folios and the network know you are signed in and you don't have to sign in again. In addition, the security cookies of the sign-in itself, those that remember your preferences (language, theme, editor), a few temporary ones that last an hour at most (for example, the language in which you started creating your account; what you were shown when you clicked "Continue with Google" to create it, "avisoDelAlta", which lasts 15 minutes and is deleted once used; if you reach sign-up from a Folio's window and click "Continue with Google", that Folio's identifier ("folioDelAlta"), which lasts 15 minutes and is deleted once used, so that we know which Folio you come from when Google sends you back to Folioss; or "folioss-rebote-red", which lasts 30 seconds and stops the browser from going round in circles when moving from app.folioss.com/red to folioss.com/red); if you close the free Pro trial notice, the date you closed it ("folioss:franja-pro-cerrada", in local storage), so that we don't show it to you again for 7 days; if you answer the notice in the dashboard that asks whether you want to receive news and offers, the date you did so ("folioss:aviso-novedades:" followed by your account identifier, in local storage), so that we don't ask you again in this browser; if you come from a Folio's window to claim a username ("Claim your @"), that name ("folioss:arroba-reclamada", in local storage), so that it is already typed in "Choose your username" when you create your account, which is deleted when you choose it and stops being valid after 7 days; while you take your first steps with your new account, what you came to do (for example, create a links page), stored as "folioss:bienvenida-vuelta" in the tab's storage, so that it isn't lost if you go through the payment screen, and what you answer in those steps ("folioss:bienvenida-respuestas", also in the tab's storage), so that it isn't lost if you go back with the browser (both are deleted when you finish those steps or close the tab); and, if you arrive through an affiliate's link, the cookie we explain below.
• On api.folioss.com, when you click "Connect" in the "Social Media Feed" block: "folioss_oauth_instagram" or "folioss_oauth_tiktok", which lasts 15 minutes and is deleted when you come back from Instagram or TikTok, to check that you were the one who started the connection, in this browser. It is essential to connect the account and is used for nothing else.

Affiliate programme cookie

If you reach Folioss through an affiliate's link (an address like app.folioss.com/r/<code>, or any app.folioss.com address ending in ?ref=), we store in your browser a first-party app.folioss.com cookie called "folioss_referral" that lasts 30 days. It is only stored when you open one of those links and it contains only the affiliate's code: no data about the person who opens it. If the link says where it was shared (for example, ?c=whatsapp), that channel goes in a second cookie, "folioss_referral_c", with the same duration. Neither of them is stored on folioss.com: not on the website, not on the Folios, not on the network. It is only used to attribute to which affiliate an account created within those 30 days corresponds; it isn't used for advertising or to build profiles, and it isn't passed on to third parties. You can delete it by clearing this site's cookies in your browser; if you do so before creating your account, the sign-up isn't attributed to anyone.

If you write from a Folio without an account

If you write from a Folio without an account, we store in your browser's local storage, on that Folio, an identifier of that conversation ("folioss-escribeme:" followed by the Folio's number) so that you can follow it when you come back. If you open it from the private link we email you, app.folioss.com stores that same identifier in the tab's storage ("folioss-escribeme-conversacion") so that it isn't lost if you reload the page, and it is deleted when you close the tab. They are necessary for the service you asked for, are used for nothing else and disappear if you delete the conversation or the site's data.

Marketing cookies

We don't use third-party advertising cookies or advertising pixels. The only first-party cookie related to promotion is the affiliate programme cookie described above, which doesn't show ads or build profiles. If we ever add third-party advertising, we will ask for your consent before enabling it and update this policy.

Right now Folioss doesn't show you any cookie banner, and that is on purpose: we don't use advertising or tracking cookies, or third-party analytics tools. The only things we ourselves store on your device are what we describe, site by site, in the previous section: what is essential for the service to work, what remembers your preferences (such as the language or the theme), the random measurement identifier and, if you arrived through an affiliate's link, the 30-day first-party folioss_referral cookie. What content from other services in a Folio may store is explained in "Third-party cookies". If in the future we add external analytics or advertising pixels, we will turn on a banner to ask for your permission before loading them.

To know how many people visit folioss.com and app.folioss.com and which page they land on, we count visits on our own server, without cookies, without storing anything on your device and without your IP address, keeping only daily totals that we delete after 25 months.

You can set your browser to block or delete cookies, and clear the site's data to also delete the measurement identifier. Bear in mind that if you block strictly necessary cookies, parts of the service (such as staying signed in) may stop working.

We don't embed third-party trackers. There are, however, external services that are part of how the platform works and that may store something in your browser when you use them: Cloudflare's anti-bot system on public forms, Google sign-in if you choose that option and Stripe's payment gateway if you buy a plan. They are necessary to provide the service and are not used for advertising.

In addition, whoever makes a Folio can put content from other services in it: YouTube or Vimeo videos, music from Spotify, Apple Music or SoundCloud, or designs from Figma, Canva or CodePen. Some of those blocks load when the Folio opens and others only when you click to see them, such as maps. When they load, that service may store its own cookies in your browser, under its own cookie policy.