Privacy & Data Use
Your reflection should not become
somebody else's dataset.
NBJB keeps private reflection local by default. Its interactive reflection tools run in your browser, while the free Flamewalker account uses Supabase for authentication, membership access, and limited account data.
What the current tools do
The Forge, Flame Check-In, Pattern Map, Boundary Builder, One Stone Planner, and Flamewalker commitment operate with client-side JavaScript. Your entries exist in the page while it is open. The current code does not send those entries to an NBJB database, account system, analytics service, or email platform.
What “copy” does
When you press a copy button, the site asks your browser to place the generated text on your device clipboard. The site does not receive a copy of that text.
Public email contact
NBJB can currently be contacted at notbrokenjustburning@gmail.com. If you choose to email that address, the message and ordinary email metadata are processed through Gmail/Google and may remain in the mailbox until intentionally deleted. Emailing NBJB does not enroll you in a newsletter or mailing list.
Flamewalker account data
Free Flamewalker accounts use Supabase for authentication and membership authorization. Account data may include your email address, authenticated user ID, membership entitlement, and limited low-sensitivity account or progress fields needed to operate the member experience. Private reflection bodies are not automatically uploaded merely because you create or sign into an account.
Account deletion and export
Self-service server-side account deletion and full cloud export are still being built. Until those controls are available in the member interface, account-removal requests can be sent to notbrokenjustburning@gmail.com. Clearing device-local member data does not by itself delete the authenticated account.
Minimal cookieless analytics
NBJB uses PostHog for basic aggregate website analytics so we can understand how many people visit, which public pages are being read, and which parts of the site are being ignored. The production site is configured in cookieless mode with no persistent browser identifier. NBJB does not enable session replay, heatmaps, click autocapture, console-log capture, automatic exception capture, or person identification. Browser Global Privacy Control and Do Not Track signals are honored by not loading the analytics script.
What analytics does and does not include
The analytics setup records ordinary pageview information needed for aggregate traffic reporting, such as the page/path requested, time of the visit, referrer, and basic browser/device context supplied with the web request. PostHog uses privacy-preserving cookieless processing for visitor counts, and the project is configured not to retain raw client IP addresses. The contents you type into The Forge, Flame Check-In, Pattern Map, Boundary Builder, One Stone Planner, or other reflection fields are not sent to PostHog.
Third-party requests
The current pages load web fonts from Google Fonts and, unless your browser sends Global Privacy Control or Do Not Track, the PostHog analytics library from PostHog's infrastructure. Flamewalker account pages also connect to Supabase for authentication and authorized member data. Those services receive ordinary technical request information necessary to provide their functions. Email links may open your chosen mail application. External links, including Facebook, crisis resources, and support resources, have their own privacy practices.
Hosting and technical logs
The site is hosted with GitHub Pages at notbrokenjustburning.com. GitHub may process routine technical information such as IP address, browser details, request time, requested page, and security-related request data as part of operating and protecting the hosting service. NBJB does not receive reflection-tool entries through this hosting layer.
Do not enter or email secrets you cannot afford to expose
Browser-only tools and ordinary email are useful communication methods, not magic armor. Shared devices, browser extensions, malware, screenshots, clipboard history, email forwarding, device backups, or other local software can affect privacy. Avoid entering or emailing passwords, financial credentials, government identifiers, medical records, or other high-risk secrets unless there is a specific and appropriate reason.