Privacy · product boundary
Your assessment stays on this device.
Reality Architect does not submit or store your assessment inputs. This page separates that local workflow from the ordinary request data a hosting platform may still process when it serves a website.
In your browser
What stays local
- — Your answers, system name, and repeating job exist only in the page’s in-memory browser state while you use the assessment.
- — They are used in your browser to render the result and assemble the Markdown architecture brief.
- — Reloading or leaving the page clears that in-memory assessment state. The app does not restore it later.
Not part of the app
What is not collected
- — There is no account, assessment submission endpoint, or app database for these inputs.
- — The assessment does not put its inputs in URLs, cookies, localStorage, or sessionStorage.
- — No analytics or telemetry provider is active in this app, and no provider receives assessment content.
The Imaginal Act uses the same local boundary
Your scene, chosen giving, present fact, obstacle, response, next act, timing, proof criterion, and agency boundary stay in the Threshold page's in-memory state. They are not submitted to AI, saved automatically, or included in page requests. Refreshing or leaving clears them. Markdown, JSON, and clipboard exports happen only when you choose them; these exports may contain personal context.
Reality Studio keeps your practice on this device
Unlike the assessment, the Studio remembers your practice between visits, so it stores what you write in this browser on this device: text in the browser's local storage, and images you add to your map in the browser's IndexedDB. Nothing you write in the Studio is sent to a server, synced, shared, included in page requests, or read by any analytics. There is no account.
Anyone who can use this browser profile can open the Studio and see it, so use a profile that is yours. A private window or blocked site data keeps nothing, and the Studio says so. Clearing this site's data in your browser deletes the Studio. From Your data in the Studio you can export everything as a folder or a backup, import a backup, and delete everything at any time. The address bar only ever shows which view is open, never your words.
The Studio can copy a prompt for your own AI assistant. Pasting it anywhere is your choice and goes to that service under its own terms.
So that the Studio opens without a connection, and can be installed as an app, your browser keeps a copy of this site's pages and code in its cache. That copy holds only what every visitor receives; your words and images stay in the storage described above and never pass through it.
Copy and download happen at your direction
Choosing Copy brief writes the generated Markdown to your device clipboard. Choosing Download .md creates a temporary file object in the browser and downloads it to your device. The app does not automatically upload either artifact. After that, you control where it is stored or shared; review it for personal or confidential context first.
Ordinary server logs still exist
Loading any page sends an HTTPS request to the hosting and content-delivery infrastructure. That infrastructure may process or retain ordinary request metadata for delivery, reliability, and security—such as an IP address, timestamp, requested path, user agent, or referrer, depending on the browser and platform configuration.
Those page requests do not contain your assessment answers, system name, repeating job, or generated brief. The assessment never places those values in a URL or sends them in a network request. The one optional exception is a Vault waitlist application, described next.
Joining the Vault waitlist sends data
The reality.md Audit at /apply stays in your browser until you press Join the waitlist. That button sends your email address, the name you typed if any, and, only if you tick the box above it, your stated aim, your top priority, and the audit headline. Nothing else in the draft is sent.
The request goes to this site's /api/waitlist route, which forwards it to the FrankX subscriber system. There it is stored as a contact with the source reality-architect-vault-waitlist in Frank's email provider, Resend, and as a lead-capture record. Frank reads applications by hand. An application does not add you to the newsletter, and no automatic email is sent. To withdraw yours or have it deleted, ask in Frank's reply.
Measurement boundary
No analytics or telemetry provider is active. Any future measurement would require a separate consent and data-governance decision and would be limited to bounded, non-content lifecycle events. Assessment answers, system names, repeating jobs, and brief text are outside that boundary.
Links to other sites
GitHub and the sites listed in the Reality Architect network are separate services with their own privacy practices. This local-only boundary applies to the assessment on this site, not to actions taken after you follow an external link.
Inspect the workflow yourself
The assessment and this site are open source. You can review the implementation, then run the assessment without creating an account.