Privacy policy

Last updated: 13 October 2026. In force from 13 October 2026.

The short version

Folio is self-hosted software. When you run your own Folio, your pages, accounts and files live on your servers, and Evergreen does not receive them. This policy covers the little we do hold: this website, the public demo, and the Folio connector for AI clients such as Claude and ChatGPT.

WhereWhat happens to your data
Your own Folio instanceStays on your servers. We never receive it, and we cannot read it.
This websiteTwo analytics tools. PostHog (EU) is anonymous and uses no cookies; it records sessions with what you type masked, deleted after 30 days. Google Analytics 4 uses cookies, and if we show you a cookie banner, only after you accept them. No forms, no ads. Our web server keeps ordinary access logs. Some images and videos load from GitHub and YouTube.
Public demo (demo.foliowiki.online)Runs on our server. Shared login, shared data, reset regularly. Do not enter personal data or keys. Visits are measured with PostHog, as on this website; page content is masked. Google Analytics is not used on the demo.
Connector (Claude, ChatGPT)Talks to a Folio instance, normally yours. Tokens are stored on that instance. On the demo, that means our server.
Folio AI assistantUses a Cursor key: your own, or one that an administrator of your Folio shares for a space or for the whole instance. Questions and page text go to Cursor, a third party, not to us.

1. Who we are

Folio is a project of the Evergreen team. For the website and the public demo, the data controller is EVERGRIN ENTERPRAIZ, TOV, Creative State of Senator, BC Senator, Kniaziv Ostrozkykh str, 32/2, Kyiv 01010, Ukraine ("Evergreen", "we", "us").

You can reach us at tech@evergreens.in.ua.

2. What this policy covers

This policy covers three things we operate:

  • the website at foliowiki.online;
  • the public demo at demo.foliowiki.online;
  • the Folio connector: the MCP server and the OAuth sign-in that let AI clients such as Claude and ChatGPT reach a Folio instance, and the listings of that connector in AI client directories.

It does not cover a Folio instance run by you or your organisation. Whoever runs an instance decides what it stores and why, and answers for it. If you use a Folio run by your employer or another organisation, ask them for their privacy notice.

Sites we link to, such as GitHub, YouTube, Anthropic, OpenAI and Cursor, have their own policies.

3. Your own Folio instance

Folio is open source (MIT licence) and runs on your infrastructure. Your pages, tables, files, accounts, tokens and Git repositories are stored there. We have no access to them and we do not receive a copy.

The Folio software has no telemetry: it does not send usage statistics or any other data to Evergreen. The assistant analytics page that Folio includes is local: it shows your own instance's data to your own administrators. (Folio has an optional hook to connect an analytics service. It is off by default, and we switch it on only for the public demo, see section 5.)

4. This website

foliowiki.online is a static site. It has no accounts, no forms, no comments and no newsletter.

What we collect

  • Server access logs. Our web server (nginx) records, for each request: your IP address, the time, the page requested, the response status, the amount of data sent, the referring page and your browser's user-agent string. We use them to keep the site running and to find abuse and errors. We keep them for 14 days.
  • Visit analytics. We use PostHog, on its EU cloud (servers in Germany), to learn which pages are read and which buttons are used, so that we can improve the site. It records: the pages you open and leave, clicks on the main buttons and on links to other sites, which integration or install guide you look at, when you copy a code snippet, when you use one of the free tools under /tools/ and which of its buttons you press (copy, download, share), the site you came from and any campaign tags in the link (utm_*), your browser, operating system, device type and screen size, and your approximate location (country and city), which PostHog derives from your IP address. The events are anonymous: the project is set to discard the IP address itself, and no person profile is created for a visitor. We never identify anyone, and we do not join these events to any account or name.
  • Session recordings. PostHog also records how you use the pages (mouse movement, clicks, scrolling and what is on screen) so that we can see where visitors get stuck. Text you type into a field is masked. This site has no forms. The working area of each free tool under /tools/ (what you paste, type or draw, and the result) is excluded from recordings. Recordings are deleted after 30 days.
  • Google Analytics 4. We also use Google Analytics, a service of Google (Google Ireland Limited and Google LLC), to count visits and see which pages are useful. It records: the pages you open, the site you came from, your approximate location (country and city), your browser, operating system, device type and screen size, and how long you stay. Google receives your IP address to work this out and does not store it in Google Analytics. It sets cookies in your browser to recognise a returning browser (see "Cookies" below). If we show you a cookie banner, this runs only after you accept; before that, Google receives only anonymous pings without cookies or identifiers. We do not use Google Analytics for advertising and we do not link it to any advertising account.
  • Nothing else. No advertising, no fingerprinting, and no tracking by other companies beyond what is described in this section.

Cookies

We set no cookies of our own. The only cookies on the website come from Google Analytics. PostHog uses none. (The video player sets its own once you press play, see "Content from other companies" below.)

CookieWhat it does
_gaGoogle Analytics. A random identifier that tells Google Analytics that two visits come from the same browser. Valid for up to 2 years.
_ga_BMTB0JTH4LGoogle Analytics. Keeps the state of the current session. Valid for up to 2 years.

When they are set. If your browser's time zone is in Europe, your first visit shows a banner with two equal buttons, Accept and Reject. If we show you the banner, Google Analytics sets no cookies until you press Accept, and until then Google receives only anonymous pings without cookies or identifiers. Google Analytics is also off by default if Google places you in the EEA, the UK or Switzerland, even when no banner is shown. For visitors who are not shown the banner (outside Europe), Google Analytics is on by default. They can turn it off with "Cookie settings" in the footer, or with the opt-out add-on below. Wherever you are, you can change your mind at any time with "Cookie settings" in the footer of every page. Rejecting also deletes the two cookies above from your browser. Your choice is remembered in local storage (see below).

Opting out in other ways. You can block these cookies in your browser settings, or install the Google Analytics opt-out browser add-on. Google Analytics does not react to the Do Not Track signal.

What stays on your device

  • If you pick a light or dark theme, your browser remembers it in local storage under the key folio-theme. It never leaves your device, and you can delete it in your browser settings.
  • Your cookie choice (Accept or Reject) is saved in local storage under the key folio-consent-v1, so that we do not ask again. It never leaves your device.
  • The PostHog analytics identifier is a random string that lives only in the memory of the open page. It is not stored in a cookie or in local storage, and it is gone when you close or reload the page. A reload counts as a new anonymous visit.
  • The free tools under /tools/ (the Confluence converter and the Mermaid editor) run in your browser. What you paste, type or draw is processed on your device and is not sent to us or to anyone else. The Mermaid editor puts your diagram, compressed, in the part of the address after #, so that you can share a link; browsers do not send that part to servers, but anyone who gets the link can read the diagram.
  • If your browser sends the Do Not Track signal, PostHog analytics stays off.
  • When you press "Try the demo", the link carries that random identifier and a session identifier in the address (ph_did, ph_sid), so that the demo can see that the same visit continued. They identify no one. The demo removes them from the address bar when it loads.

Content from other companies

  • Screenshots on the pages load from GitHub (raw.githubusercontent.com). GitHub sees your IP address and browser details when they load.
  • Video preview images load from YouTube (i.ytimg.com), which is run by Google. Google sees your IP address and browser details when they load.
  • The YouTube player (youtube.com) loads only when you open a video, not with the page. From that moment YouTube, which is run by Google, receives a request with your IP address and browser details, and can set its own cookies or use local storage in your browser, as described in Google's privacy policy. We do not control that, and we do not receive that data.
  • Blog posts embed YouTube videos as a player in the page. We use the standard YouTube player (youtube.com). The player loads together with the post (it is set to load lazily, when you scroll near it), so YouTube, which is run by Google, receives a request with your IP address and browser details even if you never press play, and can set its own cookies or use local storage in your browser, as described in Google's privacy policy. We do not control that, and we do not receive that data.
  • Analytics events go to PostHog (eu.i.posthog.com), which processes them for us under a data processing agreement.
  • If Google Analytics is on (see above), your browser contacts Google (www.googletagmanager.com and google-analytics.com), which processes the data for us under Google's data processing terms. Data can be processed in the United States; Google takes part in the EU-US Data Privacy Framework, which the European Commission recognises as providing adequate protection.
  • Links to GitHub, the author's site and other sites open those sites, which have their own policies.

5. The public demo

The demo at demo.foliowiki.online is a real Folio instance that we run so you can try it without installing anything. It holds invented data about a fictional company called Acme.

How it works, and what that means for you

  • Shared login. Visitors use a shared demo account. Anything one visitor sees or changes, another visitor can see and change.
  • Data is reset. We reset the demo to its starting state every 24 hours. Anything you add, including tokens and connections you create, is deleted by a reset, and may disappear sooner.
  • Do not enter personal data or secrets. No real names or contact details of other people, no passwords, no API keys, no tokens for other services, no confidential business information. Assume that everything you type into the demo is public.
  • Where it runs. On a server rented by Evergreen from Hetzner Online GmbH, in Germany. The data does not leave the EU unless you send it to a third party yourself (see sections 6 and 7).

What we process on the demo

  • What you type or upload: pages, table rows, comments, files, and tokens you create.
  • A session cookie that keeps you signed in. It is strictly necessary for the demo to work, and is not used for tracking.
  • Server logs, as in section 4, including the IP address.
  • Visit analytics and session recordings through PostHog, as in section 4: which pages and kinds of pages you open (document, table, board and so on), whether you edit or search (never what you wrote or searched for), sign-ins, and which AI app you connect through the connector. Everything you type, and the text of pages, tables and boards, is masked in recordings and is not sent as analytics. The events are anonymous, and the shared demo login is never linked to a visitor. On the demo the random visit identifier is kept in your browser's session storage (not in a cookie), so that a reload or the sign-in of an AI app does not split your visit. It is deleted when you close the tab.
  • Records the Folio software keeps of actions, such as who changed a page and when. On the demo, "who" is the shared account.

We use this only to run the demo, keep it secure and fix problems. We do not read demo content to profile visitors, and we do not sell or share it. Because the demo is shared and reset, it is not a place to keep anything.

6. The Folio connector: Claude, ChatGPT and other AI clients

Folio includes an MCP server (the /mcp address of a Folio instance). An AI client such as Claude or ChatGPT can connect to it, with your permission, to search and read pages and, if you allow it, to change them. Signing in uses OAuth 2.1 (with PKCE), so that you approve the connection on a consent screen of your Folio instance and never give your password to the AI client.

Where it runs

  • If you connect an AI client to your own Folio instance, the connector runs there. We are not in the path. We do not run a relay or proxy between the AI client and your instance, and we do not see the traffic.
  • If you connect an AI client to our demo, the connector runs on our demo server and this policy's section 5 applies as well.

What the Folio instance receives from the AI client

  • The sign-in request: the AI client's name and return address, and the permissions it asks for: read, or read and write. Write permission is optional on the consent screen, and you can allow read only.
  • After you approve: an access token, valid for 1 hour, and a refresh token, valid for 30 days and replaced each time it is used. They are tied to your Folio account and the permissions you gave. The instance stores them only as SHA-256 hashes, never as plain text, and they work only on the /mcp address of that instance, not on the rest of its interface. You can see the connection under Settings, API tokens, Connected apps, and disconnect it there at any time; the app then loses access immediately.
  • A record that the connection was made and ended: which app, which permissions, and when it was last used.
  • Each tool call the AI client makes: for example a search query, a page identifier, or the text it wants to write. The instance answers with the page or table content you have the right to see: the connection acts with your rights only.

What the AI provider receives

  • Everything the instance returns to the AI client goes to the company running it (Anthropic for Claude, OpenAI for ChatGPT) and is handled under that company's terms and privacy policy. You decide what to connect. Give an AI client only the permissions it needs, and the read permission if it does not have to write.
  • Folio sends no page content to Anthropic or OpenAI by itself. Content leaves your instance only because the AI client you connected asked for it.

What Evergreen receives

  • For your own instance: nothing.
  • For the demo: what section 5 lists.
  • When Anthropic or OpenAI review the connector for their directories, they use a test account on our demo. They may tell us about errors or abuse they find. We use that only to fix the connector.

7. The built-in assistant (Folio AI) and other third parties

Folio has an optional assistant in a side panel. It runs on the Folio server and uses your own Cursor API key (or a key your administrator set for everyone). Each person enters their key in their account settings on their instance.

  • When you ask the assistant something, your question and the page text it reads to answer go to Cursor, a third party, and are handled under Cursor's terms and privacy policy.
  • We do not receive the key, the questions or the answers, unless the instance is ours (the demo).
  • On the public demo the assistant is switched off: no API key is configured there, and assistant runs are blocked in demo mode.

Other third parties named in this policy: Hetzner Online GmbH (hosting of our servers, acts for us under a hosting agreement), PostHog (visit analytics and session recordings, EU cloud, acts for us under a data processing agreement), Google (Google Analytics on this website, acts for us under Google's data processing terms; also YouTube content), GitHub (content on this website), Anthropic and OpenAI (AI clients you choose to connect), and Cursor (assistant). We do not sell personal data, and we do not use it for advertising.

We may disclose data if the law or a competent authority requires it, or to protect the security of our services.

8. Why we use data, and on what basis

PurposeDataLegal basis (GDPR)
Serve the website, keep it secure, find errors and abuseServer logs, IP addressLegitimate interests (Art. 6(1)(f))
Understand how the website and the demo are used, and improve themPages and buttons used, referrer and campaign tags, browser and device, approximate location (IP address not stored), masked session recordings, random visit identifierLegitimate interests (Art. 6(1)(f)). PostHog uses no cookies or local storage, and Do Not Track is respected
Count visits and see which pages are useful (Google Analytics)Pages opened, referrer, approximate location, browser and device, Google Analytics cookies _ga and _ga_BMTB0JTH4L. Google does not store the IP addressConsent (Art. 6(1)(a)) wherever we show the banner, where we ask first and you can withdraw at any time with Cookie settings. For visitors who see no banner (outside Europe): legitimate interests (Art. 6(1)(f))
Run the demo and the connector on itWhat you type, session cookie, logs, tokensLegitimate interests (Art. 6(1)(f)); the session cookie is strictly necessary
Answer messages you send usYour email address and what you writeLegitimate interests (Art. 6(1)(f)), or steps you ask for before a contract (Art. 6(1)(b))
Meet legal dutiesWhatever the duty requiresLegal obligation (Art. 6(1)(c))

Our legitimate interest is running a free, open-source project and its demo safely. If you object, see section 11. Turning on Do Not Track in your browser is the quickest way to object to PostHog analytics; for Google Analytics, choose Reject in Cookie settings.

9. How long we keep data

DataHow long
Website access logs14 days
Demo content, tokens and connectionsUntil the next demo reset (every 24 hours), at the latest
Demo server logs14 days
Session recordings (PostHog)30 days
Google Analytics dataAccording to our Google Analytics data retention settings
Google Analytics cookies in your browserUp to 2 years, or until you reject analytics in Cookie settings or delete them
Your cookie choice (local storage)Until you clear your browser data
Analytics events (PostHog)Anonymous, with no IP address and no person profile. PostHog keeps raw events for up to 12 months, the shortest period its plan allows; after that, aggregated anonymous usage statistics may be kept longer
Emails to tech@evergreens.in.uaUntil your question is answered, then for as long as needed to follow up and for up to 12 months, unless the law requires longer
Your own instanceWe keep nothing. You decide.

We do not keep backups of the website, the demo or their logs. Demo data that has been reset cannot be restored.

10. Security

Our sites use HTTPS. Access to our servers is limited to the people who run them. Access and refresh tokens in the connector are stored only as hashes and expire (after 1 hour and 30 days). No system is perfectly secure, which is one more reason not to put personal data or secrets into the demo.

If you find a vulnerability, please report it privately, as described in our security policy. If something we hold about you is affected by a breach, we will tell you and the authorities as the law requires.

11. Your rights

If the GDPR applies to you (for example, you are in the European Economic Area), you have the right to:

  • ask whether we hold personal data about you, and get a copy;
  • have inaccurate data corrected;
  • have data deleted;
  • limit how we use it;
  • receive it in a portable format;
  • object to processing based on our legitimate interests;
  • withdraw consent, where we rely on it (for Google Analytics, use Cookie settings in the footer of any page);
  • complain to a data protection authority, in the country where you live, work, or where you think a breach happened.

Ukrainian law gives people similar rights over their personal data, and you can complain to the Ukrainian Parliament Commissioner for Human Rights. Other countries have their own rules, and we will respect the ones that apply to you.

To use a right, write to tech@evergreens.in.ua. We may ask you to prove who you are. We answer within one month, as the GDPR requires.

Because the demo has a shared login and is reset regularly, we often cannot tell which entries are yours. Tell us where to look (a page title or the time) and we will look, or just wait for the next reset.

For data in a Folio instance run by someone else, ask the operator of that instance. We cannot see it.

12. Children

Our website and demo are meant for people who work with software and documents. They are not directed at children under 16, and we do not knowingly collect data from them. If you think a child has given us personal data, write to tech@evergreens.in.ua and we will delete it.

13. Changes to this policy

We may update this policy, for example when the connector changes or when we add a feature that handles data differently. The current version is always at foliowiki.online/privacy, with its date at the top. A change takes effect when it is published on this page. We do not send separate notices, so please check the page from time to time.

14. Contact

Privacy questions and requests: tech@evergreens.in.ua. Postal address: Creative State of Senator, BC Senator, Kniaziv Ostrozkykh str, 32/2, Kyiv 01010, Ukraine. Questions about using Folio are better asked through GitHub.

Back to the Folio site.