Cookie Policy
Last updated: November 16, 2026
This policy describes cookies and similar technologies used by Chia Lab Srl on modula.dev. Read it with our Privacy Policy, which explains the data controller, purposes, legal bases, recipients and your rights.
1. Cookies and Local Storage
Cookies are small values a browser stores and sends with requests to a website. Browser storage, such as IndexedDB and local storage, can also remember information on your device. They serve different purposes: a sign-in cookie keeps you authenticated, while the editor can keep your work locally between visits.
We do not use advertising cookies. We use the following technologies to provide the features you request. Necessary sign-in and security cookies do not require consent; a language preference remembers your chosen interface language.
2. Cookies Used by Modula
| Cookie | Provider and purpose | Lifetime |
|---|---|---|
__Secure-better-auth.session_token | Modula: authenticates your signed-in session | 7 days; may be renewed while you use the service |
__Secure-better-auth.session_data | Modula: signed session cache to avoid a database lookup on every request | 60 seconds; may be refreshed |
PARAGLIDE_LOCALE | Modula: remembers the interface language selected | Up to 400 days; updated when the language changes |
The __Secure- prefix is used on the HTTPS production site; development over HTTP uses the same authentication names without that prefix. Authentication cookies are HTTP-only, so page scripts cannot read them. Cookie expiry and server-side session validity are separate: signing out or revoking a session can make a cookie unusable before its browser expiry.
3. Editor Storage on Your Device
| Storage | Purpose and information | Lifetime |
|---|---|---|
editor-recent-files in browser storage | Remembers up to ten recent file handles, last-opened times and document summaries for the editor’s recent-files list | Until removed, replaced by newer entries, or browser site data are cleared or evicted |
try-editor-state and zanichelli-editor-state in browser storage | Saves the working document in the corresponding editor demo, including content you add | Until reset or overwritten in the demo, or browser site data are cleared or evicted |
These data are stored locally to support editing and reopening your work. They are not analytics identifiers. Opening files requires the browser permissions applicable to your device. Local storage does not prevent content from being sent to Modula when you request rendering or export, or to external services when you use search or load media, as explained in the Privacy Policy.
4. Security and External Services
Amazon CloudFront (AWS) delivers the site and processes request information for delivery and protection. Its involvement does not mean that Modula sets an analytics or advertising cookie.
ALTCHA, hosted by Modula, protects sign-in, sign-up and contact forms with a proof-of-work challenge computed in your browser and verified by our server. It sets no verification cookie, uses no browser storage for verification and makes no request to an external bot-protection provider. A random challenge identifier expires in Redis within 20 minutes, plus a one-second expiry margin, and prevents reuse; it is not an analytics identifier.
If you open a Stripe payment page, Stripe may use its own cookies on its service. Media previews and embedded resources can also connect your browser to their providers. Their technologies and policies depend on the service and resource you choose; they are not covered by the first-party cookie lifetimes above.
The demos also use server-side IP/request-header identifiers and short-lived counters to enforce request limits and prevent abuse. These are separate from audience measurement; see the Privacy Policy for their purpose and retention. Avatars are generated locally by Modula without contacting external avatar services.
5. Aggregate Audience Measurement
We count complete public-page loads on our server using daily aggregate counters. Page totals and country totals are kept separately. We do not use analytics cookies, browser storage, browser analytics beacons, IP-derived visitor identifiers, or records of individual visits. Account and service-event totals are separate and are not linked to website visits. We do not measure unique visitors, individual browsing paths or time on page.
Only loads that reach the application are counted; CDN/browser-cached responses and browser-only navigation may not reach it. Known bots and prefetches are excluded. See Privacy Policy, Section 1.3 for the counters and Section 6 for retention.
There is no analytics cookie to accept or reject. Cookies necessary for sign-in and security and storage used for the features you request are described above. External media and other providers must be assessed separately; this page does not classify every third-party technology as necessary.
6. Managing Cookies and Stored Data
You can inspect, block or delete cookies and stored site data in your browser’s privacy or site settings. Blocking sign-in cookies prevents authenticated features from working. Clearing the language cookie resets the remembered language. Clearing site storage removes local demo work and recent-file entries; it does not delete HTML files already saved to your device or delete your Modula account.
Signing out ends the current session. To disconnect an AI assistant, revoke it on your connections page. To request account deletion or exercise your data-protection rights, write to info@chialab.it.
7. Exported Pages
This policy concerns the Modula website. Exported Pages keep their block script with them and do not require Modula to run. The author chooses where to publish them and which external media or services to include, and must assess the privacy information and consent required for those Pages.