Pcnaid Memory OS
Get started

Cookies and local storage

A short policy, because there is very little to describe. This site sets no cookies at all, and the one thing it does store never leaves your browser.

  • Zero cookies on this site
  • One localStorage key
  • Reviewed 16 August 2026

This website sets no cookies

Every page you are reading is a static file. There is no server session, no login and nothing to remember about you, so there is nothing for a cookie to carry.

Specifically, this site:

  • sets no cookies, first-party or third-party;
  • runs no analytics — no page-view counter, no tag manager, no session recorder, no heatmap;
  • loads no third-party scripts of any kind;
  • loads no fonts from a content delivery network — the typeface is served from this origin as a single self-hosted file;
  • embeds no third-party media: no video players, no maps, no social widgets, no comment systems;
  • runs no advertising or conversion pixels, and carries no marketing identifiers in its links.

The web host that serves the files keeps ordinary request logs — IP address, timestamp, path, status, user-agent — as any host must in order to deliver a page and absorb abuse. Those are logs, not cookies, they are not linked to an identity, and they are described in the privacy policy.

The one thing we store: memoryos-theme

The site has a light and a dark theme. If you press the theme toggle in the header, your choice is written to your browser’s localStorage under the key memoryos-theme, with the value light or dark. On the next page load a small inline script reads it back before the stylesheet is applied, so the page does not flash the wrong colours at you.

Three things are worth being precise about.

  • It is strictly necessary for the feature. There is no way to remember a preference across page loads without storing it somewhere, and this is the smallest possible somewhere.
  • It is never transmitted. localStorage is not attached to HTTP requests the way a cookie is. The value is read by a script on your own machine and used to set an attribute on the page. It is never sent to us, and we have no record of it.
  • It identifies nothing. The value is one of two words. It cannot distinguish you from anyone else who picked the same theme, and it is not combined with anything.

If you never touch the toggle, nothing is written at all, and the site simply follows your operating system’s light or dark setting. If your browser blocks storage, the toggle still works for the page you are on; it just will not be remembered.

How to clear it

Clearing site data for this domain removes it. The exact path differs by browser:

  • Chrome, Edge and other Chromium browsers — click the icon to the left of the address bar, choose Cookies and site data, then Manage on-device site data, and delete the entry for this site. Or open Settings → Privacy and security → Third-party cookies → See all site data and permissions.
  • Firefox — click the padlock in the address bar, then Clear cookies and site data. Or open Settings → Privacy & Security → Cookies and Site Data → Manage Data.
  • Safari on macOS — open Settings → Privacy → Manage Website Data, search for the site and remove it.
  • Safari on iOS — open Settings → Apps → Safari → Advanced → Website Data, find the site and swipe to delete.
  • Any browser, quickly — open the developer tools, go to the storage or application panel, find Local Storage for this origin and delete the memoryos-theme row.

Private or incognito windows discard it automatically when the window closes.

The Memory OS application

The signed-in application at memoryos.pndsvcs.com is a different surface with different needs, and it is worth describing separately.

It uses sessionStorage — storage scoped to a single browser tab and discarded when that tab closes — to hold the access token issued at sign-in, the tenant identifier the session is scoped to, and, where an operator signs in with an admin token instead of through Auth0, that token. These are strictly necessary: without them the application cannot prove who you are or which tenant to read, and every request would be rejected. The Auth0 client library itself is configured to keep its token cache in memory rather than in browser storage. One further localStorage key records which release note you last dismissed, so the same panel is not shown to you twice.

During login, Auth0 sets its own cookies at its own domain. That is how an authorisation server maintains a login session and performs silent token renewal, and it is also strictly necessary — without them you would be asked to sign in again on every navigation. Those cookies belong to Auth0, are governed by Auth0’s own policy, and are not readable by this website or by the Memory OS application.

None of this is analytics. The application sets no tracking cookie and measures no behaviour for marketing.

Every storage item, in full

This is the complete list across both surfaces. If something is not in this table, we do not set it.

Name Type Where Purpose Duration
memoryos-theme localStorage This website Remembers whether you chose the light or dark theme, so the choice survives a page load. Holds the single word "light" or "dark". Until you clear it
access_token sessionStorage memoryos.pndsvcs.com Holds the Auth0 access token for the signed-in session so API calls can be authorised without a round trip on every request. Until the tab is closed
admin_token sessionStorage memoryos.pndsvcs.com Holds the operator admin token when signing in through the admin-token path rather than through Auth0. Until the tab is closed
tenant_id sessionStorage memoryos.pndsvcs.com Remembers which tenant the session is scoped to, so every request carries the right tenant header. Until the tab is closed
pcnaid.lastSeenChangelog localStorage memoryos.pndsvcs.com Records the last release note you dismissed, so the same "what changed" panel is not shown twice. Holds a version string. Until you clear it
Auth0's own session cookies Cookies, set at the Auth0 domain The Auth0 login domain — not ours Keep you signed in at the authorisation server during login and silent token renewal. Set by Auth0, governed by its policy, and never readable by our sites. Set by Auth0

Consent is required for storage that is not strictly necessary for a service the user asked for — analytics, advertising, profiling, cross-site measurement. We set none of it. Everything in the table above is either a preference you deliberately expressed by pressing a button, or a token without which a signed-in application cannot function.

So there is no banner, because there is nothing to consent to, and a banner that asks permission for nothing is theatre. Blocking storage entirely costs you only the memory of your theme choice.

If that ever changes, this page changes first. Should we ever add analytics or any non-essential storage, this policy will be updated before the change ships, and a genuine consent mechanism will accompany it.

Questions

Write to support@pcnaid.com if anything here does not match what you observe in your browser. We would want to know.

Last reviewed 16 August 2026. Related: privacy policy · terms of service · accessibility.