Privacy notice
Last updated: 14 August 2026
This notice covers exjsx.dev, including the demo archive at /showcase/. It is short because the site does very little with data.
Who we are
Algorismus LLC 3001 Hulen Street, Suite 201, Fort Worth, TX 76107, United States legal@wpos.ai
We are the controller of the small amount of personal data described below.
The short version
- There are no accounts, no logins, no passwords and no payments on this site.
- We do not sell, rent or share your data, and we run no advertising and no advertising pixels.
- We use one analytics product, PostHog, to count page views and a handful of clicks.
- Every form you see on a demo page is part of the fiction. It is not connected to us and nothing you type into one is sent to us. Please do not type real information into one.
That is the whole of it. The rest of this page is the detail behind those four lines.
How the site is served
exjsx.dev is a static site hosted on GitHub Pages (GitHub, Inc., a Microsoft company). There is no application server, no database and no server-side code of ours anywhere in the path.
GitHub receives your IP address and request headers in order to deliver the page to you, and uses them for delivery and for security and abuse prevention. That processing is GitHub's, under GitHub's own privacy statement, and we cannot see those logs — GitHub Pages does not expose access logs to the site owner.
Analytics: what PostHog collects
We use PostHog (PostHog, Inc., United States) on the US cloud region. The script is loaded from us-assets.i.posthog.com and events are sent to us.i.posthog.com.
What is collected on a page view:
- the page you viewed and the page you came from (the referring URL);
- your browser, operating system, device type, screen size and language;
- your approximate location — country, region and city — derived from your IP address by PostHog at the point of collection;
- a random device identifier, stored in your browser so that two page views in the same session can be counted as one visit rather than two.
Named events we record when you click something:
mode_switch (switching between the agent-facing and human-facing view) · copy_command (copying an install command) · watch_full_film · film_switch · cta_click · cta_close_click.
What is not collected: we do not use PostHog session recording, heatmaps, surveys or feature flags on this site; we do not record keystrokes or form contents; and we never call PostHog's identify function, because there is nothing to identify you as. The library is configured with person_profiles: 'identified_only', which means no person profile is ever created — your events are stored against a random device identifier and nothing else.
We do not combine analytics data with any other source, export it, or give anyone else access to it.
Cookies and similar storage
This site sets no cookies at all. It does not write to localStorage or sessionStorage either.
PostHog is configured with persistence: 'memory', which keeps the random analytics identifier in the page's memory only. It is discarded the moment you close the tab, and nothing is written to your device. The trade-off is ours, not yours: if you come back tomorrow we count you as a new visitor, because we kept no way to recognise you.
There are no advertising, marketing or social-media cookies, and no third-party trackers.
If you would rather not be counted at all, either of these works: use a content blocker (PostHog is on every major blocklist), or use your browser's private mode. Nothing on the site breaks if analytics is blocked.
The forms on the demo pages
The fifty demo sites are fictional businesses, and their contact forms, booking forms and order forms are part of that fiction. None of them submits anywhere, and nothing you type into one reaches us or anybody else.
To be precise, because precision is the point of this section: three of the fifty pages have working form fields at all. All three are now inert — pressing the button does nothing, by design. Two of them were generated with a mailto: action, which would have handed what you typed to your own email program; those addresses now use the reserved .example domain, which can never be registered and can never receive mail. The third was generated so that pressing the button reloaded the page and sent the fields to the web server; that no longer happens. The other forty-seven pages have no form fields on them.
Telephone numbers, email addresses and postal addresses on the demo pages are invented. Do not use them. If one of them reaches you in real life, that is a mistake on our part — tell us at legal@wpos.ai and we will remove it.
Legal bases, if you are in the UK or the EU
We are a United States company and we do not target the UK or the EU. But the site is public and in English, so UK and EU visitors reach it, and the UK GDPR and the EU GDPR can apply to us on that basis where we monitor visitor behaviour.
Where they apply, we rely on legitimate interests (Article 6(1)(f)) for basic audience measurement: knowing roughly how many people looked at the archive, and which pages they looked at, is necessary to run the project and has a minimal effect on you, because we cannot identify you from it and never try to.
Storing an analytics identifier on your device would be separately governed by the UK's Privacy and Electronic Communications Regulations and the EU ePrivacy Directive, which treat analytics storage as requiring consent rather than as strictly necessary. We do not store one. The analytics library runs in a cookieless, memory-only configuration, so there is nothing on your device to consent to — which is why you are not being asked to dismiss a banner.
International transfers
Analytics data is stored in the United States. If you are in the UK or the EU, that is a transfer out of your jurisdiction. It is covered by our data processing agreement with PostHog and the transfer mechanism in it. If you want to know which mechanism, ask us and we will tell you.
United States state privacy laws
We have assessed the Texas Data Privacy and Security Act, which is our home-state law, and the California Consumer Privacy Act. On our current size and traffic we fall below the thresholds in both, and we are not a data broker: we sell no personal data, share none for cross-context behavioural advertising, and process no sensitive data.
Falling below a threshold is a reason not to file paperwork, not a reason to behave differently. We will honour any access, correction, deletion, portability or opt-out request from anyone, in any state or country, whether or not a statute obliges us to. Email legal@wpos.ai.
Your rights
Wherever you are, you can ask us to tell you what we hold about you, correct it, delete it, or stop processing it, and you can object to analytics entirely. Practically, the honest answer to most such requests will be "we hold a random identifier and some page views, and we cannot connect them to you" — but ask, and we will look.
If you are in the UK you may complain to the Information Commissioner's Office; in the EU, to your national supervisory authority. We would rather you came to us first.
Children
This site is not directed to children, and we do not knowingly collect data from anyone under 13. Some demo pages depict businesses aimed at children — a coding club, a children's dentist. They are fiction, and they are not services offered to children or to anyone else.
How long we keep it
Analytics events stay in our PostHog project subject to its retention setting and are deleted when it expires. We do not archive them anywhere else. GitHub's delivery logs are GitHub's, on GitHub's retention.
Changes
If we change what the site collects, we will change this page and its date at the same time. Material changes are also recorded in the changelog.
Contact
legal@wpos.ai — privacy questions, rights requests, and anything on this page.