Privacy, in plain language

Your private practice stays in this browser

Your intention text, personal goals, training choices and availability, challenge progress, food preferences and avoidances, and suggested personal plans stay in this browser. The site does not send these private entries to our server or post them to the community. The site owner has no access to read them through the service. They do not sync between devices; clearing this site's browser data removes them.

Anyone using the same browser profile may be able to see locally saved information. A training backup you choose to export includes your saved personal inputs, so keep that file private. These tools are for everyday planning and reflection, not a medical record or a confidential clinical service.

Newsletter and launch requests

If you submit a signup form, we store your email address, selected language, the list or launch update you requested, and the time of your consent in a Cloudflare D1 database. We use these records to manage that request and your preferences.

At launch, these are pending, unverified requests. Automated confirmation emails, newsletters, and marketing campaigns are not sending yet. Saving your request does not mean email delivery has started. We do not sell these signup records or add you to unrelated partner lists.

When a new request is saved, the page provides a private management link. Its token is in the URL fragment, after the # symbol, and the database stores only a hash of that token. Save the link and keep it private: anyone with it can check the request’s status or unsubscribe. We do not send this link or a confirmation by email at launch.

Unsubscribing marks your email record as unsubscribed. We retain the email record, its status, and the original consent information as a suppression record so another signup does not automatically reactivate your address. Unsubscribing does not delete that information. Contact us on Instagram to correct your details or request deletion.

Optional sign-in and saved articles

You can read the publication without signing in. If you choose ChatGPT sign-in, we associate your saved article bookmarks with the account identifier provided by the sign-in service. We do not receive your ChatGPT password.

The sign-in and hosting services may use necessary session information to operate. Their own privacy policies also apply to information they process.

Joining the community and choosing a public handle

Reading public rooms does not require sign-in. To participate, you sign in with ChatGPT and separately agree to create a community profile. We store a chosen handle, optional short bio, language preference, discovery and message-request choices, consent version and time, and the account association in Cloudflare D1. The community does not store your account email or publish your sign-in identifier or account name.

Your chosen handle appears beside public messages. A handle is a pseudonym, not a guarantee that nobody can identify you from what you write. Exact-handle discovery and incoming direct-message requests are off by default. If you enable discovery, another signed-in member who knows the exact handle can find that handle and bio. Both discovery and incoming requests must be enabled to receive a new private-conversation request.

Public rooms and private conversations

Messages in the Campfire, Training, Perspective, and Outdoors rooms are public and readable by anyone, including visitors without an account. They are plain-text posts. Do not include personal information you do not want shared publicly. Other people may copy public content.

A direct-message request must be accepted by the recipient before either participant can send text. Through the app and API, the conversation is accessible to its participants. Direct messages are stored as plain text in the site's database and are not end-to-end encrypted. Hosting systems process this information, and technical database access is not cryptographically prevented. Do not treat a direct message as a confidential clinical conversation.

Community profiles, room posts, direct messages, request statuses, blocks, and moderation records are stored on the server. Your browser-local personal goals, training progress, food preferences, and plans are separate and are not included in those community records. No community notification emails are sent.

Reporting, blocking, deletion, and retention

Reporting a room or direct message shares a snapshot of that specific message, your selected reason and details, and the relevant public handles with the site owner for moderation. The moderation screen shows reported messages; it does not provide a general inbox of members' private conversations. A previously filed report can retain its snapshot after the original message is removed.

You can remove the text of your own room or direct messages. This clears the original message body while retaining limited records such as identifiers, timestamps, and participants. It does not erase copies someone else made or existing report snapshots. There is no self-service profile or account deletion feature in this version.

Blocking closes a private conversation and stops messages in both directions. It also prevents exact-handle discovery between those members. The signed-in room view hides authors you have blocked, but public posts remain public and can be read outside that view. Unblocking does not reopen a closed or declined conversation or allow that pair to send a new request.

Community records have no automatic retention purge at launch. We do not promise a fixed deletion deadline. Contact us through the channel below for access, correction, or deletion requests; we may need to verify that the records are yours. Reports are not monitored continuously, and the community is not a crisis service.

Requests, abuse prevention, and external links

We use short-lived hashes derived from network information to limit repeated submissions and abuse. Our hosting services process web requests and may retain operational request logs. Hashing is not a promise of anonymity.

No third-party advertising or audience-analytics scripts are active. Links to sources, support services, social platforms, and other websites lead to services with their own data practices. No affiliate commission links are active. We will update this notice when the site's data use changes.

Creator Dock authorization returns

The manual Creator Dock return page keeps authorization query values in browser memory so you can copy a return value to your local app. It does not exchange authorization codes for access tokens or complete a connection itself.

Your local Creator Dock app must validate the response, including its state and provider requirements. Authorization URLs and codes can be sensitive: copy them only into the app that started the connection. Hosting infrastructure may process the incoming return URL.

Your choices and contact

For access, correction, or deletion requests about signup, bookmark, or community records, contact @steeltoestoic on Instagram using the link below. We may need to verify your relationship to the account or email address. Clear this site's browser data to remove local goals, intentions, training records, food preferences, and plans; the owner cannot remove those browser-local entries remotely.

Please do not send passwords, authorization codes, payment details, or private medical records, or post personal information in public comments. This contact channel is for site matters and is not monitored for emergencies.