A program of EffectiveSC
How We Use AIUpdated November 14, 2026
The site's pages and files are served by OneReach GSX Files, at files.edison.api.onereach.ai.
At howweuseai.org, a Cloudflare Worker fetches each page from GSX Files and passes it on, so your visit there also goes through Cloudflare. To a page opened in a browser it adds one short script, described under Analytics and cookies.
The typefaces are Google Fonts, served from this site's own fonts folder, so opening a page doesn't contact Google.
Nothing else loads from another site when a page opens: no outside scripts, images or embedded frames.
The pages as published carry no analytics, advertising or tracking code. Apart from the member check and the study form below, their scripts only switch what a page shows, such as a chart's view or a table's filter. Each page also carries a block of structured data that describes it to search engines; it doesn't run.
At howweuseai.org, the Worker records each HTML page it serves in Cloudflare Workers KV, the store described in Cloudflare's KV guide. The record keeps the page address, the referring address with its query string removed, the country Cloudflare assigns to the connection, the time, the browser's user-agent string (shortened), whether that looks like a person, a search engine or an AI system, and a code made by hashing the connection's IP address with the user agent, the day and a secret. The code changes every day, so a visit can be counted once a day but not followed from one day to the next. It does not use a cookie, and it does not store an IP address.
At howweuseai.org, the Worker adds one short script to each page it sends to a browser. When you hide or close the tab, the script sends the page's address, an id the Worker made for that one page view, and how many seconds the page was visible, to howweuseai.org/t, where the Worker keeps them with that page view. It sends nothing else.
Neither the pages nor their scripts set cookies.
To download the research, you enter your email on Get the data. The page sends it to UX Magazine's member check at uxmag.com, as part of the web address it requests.
If you aren't a member and choose to join, the page sends your email, name and role to the same UX Magazine address.
UX Magazine runs the membership. The page sends these details nowhere else and stores none of them.
The research file downloads from the same place as the pages.
The Send us a study or data page has a form for telling us about a study or data set. Along with the study's details, it asks for your email, and for your name if you want to give it.
Nothing is sent until you press the form's Send it button. The page then sends what you typed to /api/submit, at the address you opened the page from.
At howweuseai.org, the site's Worker checks the form and saves it in OneReach GSX storage, with the time it arrived and the country Cloudflare places your connection in. It sends the form nowhere else.
The Worker takes the form only from pages at howweuseai.org. Sent from the GSX Files address, the form goes to files.edison.api.onereach.ai, which refuses it, so nothing is saved.
After a successful check, the page saves a single flag in your browser's local storage, named howweuseai-research-member, so the download is ready when you come back. The flag holds no email, name or role.
No page uses session storage or any other browser storage.
The AI at Work Benchmark survey isn't open yet. Every page marks it Coming soon, and the site collects no survey answers.
How We Use AI has no accounts or passwords of its own. The only sign-in is the UX Magazine membership check for the research download.
Links to sources, and to X, LinkedIn and UX Magazine's email sign-up, take you to those sites. Nothing from them loads until you follow a link.
The AI at Work Benchmark
Score your organization's practices, measure your people with an anonymous pulse, and see both against the published evidence.