Cookies & browser storage
A clear account of the small pieces of information Palimpsa and its service providers may store on, or read from, your device.
This policy describes the current product as understood from its code and configuration. The exact production cookie inventory and provider behavior still need confirmation. See the open items ↗
The short version
Palimpsa uses browser storage to keep you signed in, remember preferences and support document editing, recovery and collaboration. Browser storage includes more than cookies: it can also include local storage, session storage and IndexedDB. These are not all the same thing, but privacy rules may apply to similar technologies too.
We have not found an advertising or analytics tracking tool in the current code review. That needs a final check against the production deployment and any provider settings before this statement is treated as final.
This page explains what we know; it is not a cookie-preference control. If Palimpsa uses any non-essential storage that requires consent, we will provide a suitable choice before it is used.
What Palimpsa uses
Your optional-font choice is cleared when the page is refreshed, so the banner appears again. Browser platforms do not reliably distinguish a hard refresh from a normal refresh.
These items are not a complete cookie-by-cookie inventory. The names, expiry periods and domains of cookies set by the live app and its providers are [TO CONFIRM BEFORE PUBLICATION].
You can remove stored data through your browser settings. This may sign you out and can remove local drafts or unsynced changes. Make sure important work has synced before clearing site data.
Third-party services
Google Firebase. Palimpsa uses Firebase Authentication and Cloud Firestore for accounts and document syncing. Google may set or access storage as part of those services. The exact storage depends on configuration and browser behavior and is [TO CONFIRM].
Google Fonts. The site currently requests fonts from Google Fonts rather than serving every font locally. When a page loads those fonts, the browser connects to Google and sends ordinary connection information such as an IP address and browser request details. The current code review did not identify a separate advertising or analytics tracker; that should be verified in the live production environment.
Providers and their behavior may change. For information about personal data processed by these providers, see the Privacy Notice.
Your choices
When you first visit, a small banner lets you accept or reject optional Google Fonts. Your choice applies while you move around the site in the same tab. Refreshing the page resets it and shows the banner again. Rejecting optional fonts leaves the site using its system-font fallbacks; essential sign-in, document and security functions continue to work.
You can also use your browser settings to block or delete cookies and other site data. Some parts of Palimpsa may then fail to work, and clearing storage can remove local unsynced document changes. The banner currently controls the optional font request; the exact production inventory and whether other provider storage needs a separate choice remain [TO CONFIRM].
Changes & contact
We will update this page if the technologies or their purposes change. The date above shows the latest revision. For a question about cookies or device storage, contact [PRIVACY EMAIL ADDRESS]. You can also read the Privacy Notice and review the open legal items.