Privacy

Reading this site doesn't require an account, and nothing you read is tied to you. The Identity Lab's tools keep your work in your own browser. The few things that do reach me are the ones you send on purpose: a message, an email copy of your scorecard, a Lab membership, and, only if you say yes, a practice record. There are no ads, nothing is sold, and no tracking cookies are set.

The site uses Vercel Web Analytics to count page views: the page, the referring site, and the country, browser and device type. It doesn't use cookies. Anything after a # in an address is removed before a view is counted, because shared Lab snapshots carry their content there.

Links I post on LinkedIn and X carry a tag naming the post. When you arrive through one, the site adds one to that post's count, and adds one more if you join the Lab in the same visit. That's all it keeps: a number per post, with nothing about you, and the tag is never written to your membership. Your browser remembers the tag until you close the tab, in session storage rather than a cookie.

Your name, email address and message are sent to my inbox by email, through Resend, an email delivery service. The site doesn't keep a copy. To stop the form being abused, the server counts recent submissions per network address for ten minutes, in memory only.

Your answers are scored in your browser, and a summary of the result is kept there so the Identity Lab can show it back to you. If you ask for a copy by email, your answers, name and email address are sent to the server, which works out the result again, emails it to you through Resend, and stores nothing.

The self-assessment, protocol practice, worksheets and the members' tools save your work in your browser's local storage, not on this site. Clearing your browser's site data removes it. A shared link from a Lab tool carries its content inside the link itself, after the #, so it never reaches the server.

When you join, or ask for access, the Lab stores your email address and the name you give, so it can send your member link, and send it again if you lose it. A request for access also stores the room you picked and your note. Membership has no password: your link is signed, and opening it sets one cookie, lab_invite, that keeps you signed in on that browser until the link expires.

Against your membership the Lab counts visits (at most once an hour, with the first and last date) and records which tools your link has opened, to see which tools earn their place. It doesn't record when you opened them, how often, or what you did in them.

Protocol practice remembers the exercises you finish in your browser. A signed-in member is asked, once, whether to save a practice record. Only on a yes does the Lab store, with your membership details, which exercises you finish, when, and how many answers you got right first time. Your answers are never stored. Say no and nothing is stored.

If you turn on sharing, the name you type for the share page is stored too, for as long as sharing is on. Turning sharing off deletes the name and stops the link working. Turning saving off, on your practice record page, deletes the record and its share link straight away.

The site runs on Vercel, and Lab data is kept in a Redis database hosted there. Emails are delivered by Resend. Both process data on my behalf to run the site, and nothing else.

Lab membership, requests and practice records are kept until you or I delete them; removing a member deletes their practice record too. To have anything about you deleted, or to ask what's held, email contact@jamalsjones.comfrom the address you used. I'll do it and confirm.