> Is Retype GDPR compliant? See which local storage keys Retype docs sites use, when Google Analytics needs consent and how to keep your docs privacy friendly. > > Canonical: https://www.flowconsent.com/en/services/framework/retype Frameworks # Retype Unclassified · [Official website](https://retype.com) Retype is a static site generator, developed in Canada, that turns a folder of Markdown files into a complete documentation website. The output is plain HTML hosted wherever you choose, such as GitHub Pages, Netlify or your own server. By default it sets no tracking cookies and only keeps interface preferences in local storage; analytics appear only if you enable an integration. [Block Retype until consent](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=framework) · [Scan my site](https://www.flowconsent.com/en/scan) At a glance - Category [Frameworks](https://www.flowconsent.com/en/services/framework) - Consent Unclassified - Prior consent Not required - Documented cookies 4 - Third-party domains 5 - Servers Retype itself does not host content: the site is served by the hosting provider chosen by the owner, so the server location is that of the host (for example GitHub Pages on a global CDN, or an EU host). The Retype project is developed in Canada. Optional integrations send data to their own servers, for example Google in the United States or Plausible in the EU. Overview ## What does Retype do? ## **What is Retype?** Retype is a static site generator built for documentation. You point it at a folder of Markdown files, run the retype build or retype start command, and it produces a complete website with navigation, full text search, a colour scheme toggle and a blog section. The project is developed in Canada and offered in a free edition and a paid Retype Pro edition that unlocks extra features such as private search configuration and outbound link control. The retype.com website is itself built with Retype. The important point for privacy is that Retype runs on your machine or in your CI pipeline, not on the visitor's device in a connected way. The output is plain HTML, CSS and JavaScript that you publish on a host of your choice: GitHub Pages, Netlify, Cloudflare Pages, an EU hosting provider or your own server. Retype does not operate a hosting platform for your docs and does not receive your visitors' data. ## **Data and cookies a Retype site uses** Out of the box, a Retype site loads its own bundled scripts from the same origin (resources/js/retype.js and a local Lunr search index) and does not set tracking cookies. It keeps a few interface preferences in the browser: the localStorage key retype\_scheme stores the light or dark mode chosen by the visitor, keys such as doc\_history keep recent navigation, and sessionStorage keys such as doc\_sidebar remember the sidebar state during the session. The local development server also uses a very short lived reloadPosition cookie, valid for five seconds, to restore the scroll position after a live reload. Other processing only appears when you switch it on. The integrations setting can add Google Analytics, Google Tag Manager or Plausible Analytics. Author avatars can be loaded from Gravatar, which is enabled by default when authors are configured, so the visitor's browser contacts gravatar.com. Your hosting provider will also record server logs with IP addresses. ## **GDPR and ePrivacy implications** Under ePrivacy Directive 2002/58/EC art. 5(3), storing or reading information on a visitor's device requires consent unless it is strictly necessary for a service the user explicitly requested. Remembering a colour scheme the visitor chose, navigation state or the sidebar position falls squarely within that exemption, as confirmed by the CNIL guidelines, German TDDDG § 25 and the AEPD guide on cookies. A default Retype site therefore runs without a consent banner. The picture changes with Google Analytics or Google Tag Manager. These tools set identifiers such as \_ga, profile visitors across pages and send data to Google in the United States. That requires prior opt in consent under GDPR Art. 6(1)(a) and the national cookie rules. ## **When is consent required?** No consent is needed for the core Retype site, the local search index or the preference storage. Consent is required before loading Google Analytics or any tag deployed through Google Tag Manager. Plausible is cookieless and several authorities, including the CNIL under strict conditions, accept such audience measurement without consent, but check the rules of each country you target. Gravatar images reveal the visitor's IP address to Automattic, so privacy conscious teams often disable integrations.gravatar.enabled. ## **Data transfers outside the EEA** Retype itself creates no transfer because it never receives visitor data. Transfers come from your choices: GitHub Pages and Netlify are US companies, Google Analytics sends data to Google LLC, and Gravatar is operated by Automattic in the United States. These transfers can rely on the EU US Data Privacy Framework where the recipient is certified, or on SCC 2021/914 with a transfer assessment following Schrems II. Hosting the output on an EU provider and using Plausible keeps the whole stack in Europe. ## **Practical compliance steps** Review your retype.yml: keep only the integrations you really need, and consider setting integrations.gravatar.enabled to false. If you use Google Analytics or Google Tag Manager, load them through a consent management platform such as FlowConsent so that no tag fires before an explicit choice, and enable Google Consent Mode v2. Choose a host with a clear DPA and preferably EU data centres. Finally, publish a short privacy notice and cookie policy on the docs site that lists the retype\_scheme and doc\_history storage entries as strictly necessary, the hosting logs, and any analytics tool with its purpose, retention and transfer safeguards. Compliance ## Retype and the GDPR - Legal basis The core Retype site only uses local storage for preferences requested by the visitor (colour scheme, navigation state), which falls under the strictly necessary exemption of ePrivacy Directive art. 5(3), so no consent is needed and hosting logs rely on legitimate interest under GDPR Art. 6(1)(f). If the owner enables Google Analytics or Google Tag Manager, prior consent under Art. 6(1)(a) is required for those tags. Plausible is generally treated as consent exempt audience measurement depending on the national authority. - Risk level low - Applicable regulations GDPR (Regulation (EU) 2016/679), ePrivacy Directive 2002/58/EC art. 5(3), French CNIL guidelines on cookies and trackers, German TDDDG § 25, Spanish LSSI CE art. 22.2 and AEPD guide on cookies. When US based integrations are enabled: EU US Data Privacy Framework, SCC 2021/914 and the Schrems II ruling. ### Impact assessment (DPIA) A standard Retype documentation site does not need a DPIA: it processes no personal data beyond hosting logs and stores only interface preferences in the visitor's browser. The assessment changes if you enable Google Analytics or Google Tag Manager, because those tags profile visitors and transfer data to the United States. Even then, a DPIA is rarely mandatory for a public documentation site, but you should document the analytics processing in your record of processing activities. Also review the hosting provider's DPA, since it is your actual processor. ### Sample text for your banner > We use our own storage to remember your display preferences, such as dark mode. With your consent, we also use analytics to understand which documentation pages are read so we can improve them. You can accept or refuse analytics at any time without affecting access to the documentation. Cookies and trackers ## What Retype sets and contacts - Tracking method Retype is a static site generator: it builds plain HTML, CSS and JavaScript files from Markdown at build time, and the output is hosted wherever the owner chooses (GitHub Pages, Netlify, Cloudflare Pages, any web server). The generated site runs its own bundled script (resources/js/retype.js) from the same origin and contains no tracking by default. It stores interface preferences in the browser (localStorage key retype\_scheme for the colour scheme, doc\_history and similar keys for navigation state) and only adds analytics when the owner enables an integration such as Google Analytics, Google Tag Manager or Plausible. - Server location Retype itself does not host content: the site is served by the hosting provider chosen by the owner, so the server location is that of the host (for example GitHub Pages on a global CDN, or an EU host). The Retype project is developed in Canada. Optional integrations send data to their own servers, for example Google in the United States or Plausible in the EU. - Cookieless mode available Yes ### Cookies set (4) | Name | Type | Duration | Purpose | | -------------- | ------------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | retype\_scheme | Local storage | Persistent until cleared | Stores the light or dark colour scheme explicitly chosen by the visitor with the theme toggle. Removed when the visitor selects the system scheme. Strictly necessary preference. | | doc\_history | Local storage | Persistent until cleared | Keeps the list of recently visited documentation pages for in site navigation features. Stored only in the visitor's browser, never sent to Retype. | | doc\_sidebar | Local storage | Session (sessionStorage) | Session storage entry remembering the sidebar navigation state and scroll position (doc\_sidebar, doc\_sidebar\_scroll) while the tab is open. Strictly necessary for the interface. | | reloadPosition | HTTP cookie (first party) | 5 seconds | Very short lived cookie written by the Retype script to restore the scroll position after a page reload, mainly during live reload with the local development server. Contains only scroll coordinates. | ### Third-party domains contacted (5) - `retype.com` - `gravatar.com` - `googletagmanager.com` - `google-analytics.com` - `plausible.io` Questions ## Frequently asked questions about Retype Can't find your question? Write to us, we answer fast. [Write to us](https://www.flowconsent.com/en/demo) ### Which cookies does a Retype site set? A default Retype site sets no tracking cookies. It uses local storage keys such as retype\_scheme (chosen colour scheme) and doc\_history (recent navigation), plus session storage for the sidebar state. The local development server briefly uses a reloadPosition cookie lasting five seconds. Any other cookies come from your host or from integrations you enable, such as Google Analytics. ### Do I need cookie consent for a Retype documentation site? Not for the core site: preference storage requested by the visitor is strictly necessary under ePrivacy art. 5(3), TDDDG § 25 and LSSI CE art. 22.2. You do need prior consent as soon as you enable Google Analytics or Google Tag Manager. Plausible can often run without consent, depending on the national authority. ### What is the legal basis for processing on a Retype site? Hosting logs and preference storage rely on legitimate interest under GDPR Art. 6(1)(f) and the strictly necessary exemption. Analytics through Google tools relies on consent under Art. 6(1)(a). Document both in your record of processing activities. ### Does Retype transfer data to the United States? Retype itself receives no visitor data, because it only runs at build time. Transfers depend on your host (GitHub Pages and Netlify are US companies), on Google Analytics or Google Tag Manager, and on Gravatar avatars served by Automattic. Rely on the EU US Data Privacy Framework or SCC 2021/914, or choose EU hosting to avoid transfers. ### Is a DPIA needed for a Retype site? Usually not. A public documentation site with preference storage and server logs presents low risk. If you add Google Analytics, assess the tracking in your records, but a full DPIA is rarely required unless you combine it with large scale profiling. ### How do I make a Retype site compliant? Keep only necessary integrations in retype.yml and consider disabling Gravatar with integrations.gravatar.enabled set to false. Load Google Analytics or Google Tag Manager only through a consent management platform such as FlowConsent, with Google Consent Mode v2. Host the output with a provider that offers a clear DPA, ideally in the EU. ### What are privacy friendly alternatives to Retype? MkDocs with the Material for MkDocs theme, Sphinx and Hugo are open source generators that you can host on any EU provider. For analytics, EU based tools such as Plausible, Matomo or Pirsch fit well with any static documentation site. ### How should I update my cookie policy for Retype? List retype\_scheme, doc\_history and the session storage keys as strictly necessary preference storage, and mention the hosting provider's server logs. Add each enabled integration, such as Google Analytics or Gravatar, with its purpose, retention period and transfer safeguards. Review the policy whenever you change retype.yml. Same category ## More services: Frameworks [See the whole category](https://www.flowconsent.com/en/services/framework) ### [PyData Sphinx Theme](https://www.flowconsent.com/en/services/framework/pydata-sphinx-theme) [PyData Sphinx Theme is a versatile web technology that supports digital platforms with specialized functionality and enhanced capabilities. It provides robust tools and services that integrate with modern websites and applications seamlessly. PyData Sphinx Theme is designed to improve operational efficiency, user experience, and digital performance. Trusted by developers and businesses alike, PyData Sphinx Theme offers reliable solutions that scale with organizational needs and evolving web standards.](https://www.flowconsent.com/en/services/framework/pydata-sphinx-theme) [Frameworks](https://www.flowconsent.com/en/services/framework/pydata-sphinx-theme) · ### [jQuery Migrate](https://www.flowconsent.com/en/services/framework/jquery-migrate) [jQuery Migrate is a JavaScript library that simplifies web development by providing utility functions, DOM manipulation tools, and cross-browser compatibility. It offers a clean, chainable API that reduces code complexity and development time. jQuery Migrate supports AJAX requests, event handling, and animation effects. With extensive documentation and a vast plugin ecosystem, jQuery Migrate remains a reliable choice for developers building interactive, performant web experiences.](https://www.flowconsent.com/en/services/framework/jquery-migrate) [Frameworks](https://www.flowconsent.com/en/services/framework/jquery-migrate) · ### [Tipso](https://www.flowconsent.com/en/services/framework/tipso) [Tipso is a foundational web service that powers critical website functions and digital experiences. It provides reliable infrastructure, seamless integration capabilities, and consistent performance across all devices and browsers. Tipso supports modern development practices and scales with growing business needs. With a focus on stability and compatibility, Tipso ensures your website delivers a smooth, uninterrupted experience to every visitor and search engine crawler.](https://www.flowconsent.com/en/services/framework/tipso) [Frameworks](https://www.flowconsent.com/en/services/framework/tipso) · ### [Replicache](https://www.flowconsent.com/en/services/framework/replicache) [Replicache is a foundational web service that powers critical website functions and digital experiences. It provides reliable infrastructure, seamless integration capabilities, and consistent performance across all devices and browsers. Replicache supports modern development practices and scales with growing business needs. With a focus on stability and compatibility, Replicache ensures your website delivers a smooth, uninterrupted experience to every visitor and search engine crawler.](https://www.flowconsent.com/en/services/framework/replicache) [Frameworks](https://www.flowconsent.com/en/services/framework/replicache) · ### [Closure Library](https://www.flowconsent.com/en/services/framework/closure-library) [Closure Library is a development framework and toolkit providing developers with a structured foundation for building modern web applications. It offers reusable components, standardized architecture patterns, and comprehensive documentation. Closure Library accelerates development through code generation, testing utilities, and build optimization. With an active community and extensive ecosystem, Closure Library enables teams to build scalable, maintainable applications following industry best practices.](https://www.flowconsent.com/en/services/framework/closure-library) [Frameworks](https://www.flowconsent.com/en/services/framework/closure-library) · ### [Layui](https://www.flowconsent.com/en/services/framework/layui) [Layui is a foundational web service that powers critical website functions and digital experiences. It provides reliable infrastructure, seamless integration capabilities, and consistent performance across all devices and browsers. Layui supports modern development practices and scales with growing business needs. With a focus on stability and compatibility, Layui ensures your website delivers a smooth, uninterrupted experience to every visitor and search engine crawler.](https://www.flowconsent.com/en/services/framework/layui) [Frameworks](https://www.flowconsent.com/en/services/framework/layui) ## Make your site compliant today. Free up to 25,000 sessions a month. No credit card, no commitment. [Create my banner](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=general) · [Scan my site](https://www.flowconsent.com/en/scan)