STRIVEAdd a run

Privacy

STRIVE · Updated 25 September 2026

Your session starts on your machine

Local capture reads session files already on your machine. Captured drafts stay local. Automatic exports exclude raw transcripts, code, typed prompts, local source paths and agent credentials. Review the preview before saving or sharing: project names and text you add may still be sensitive.

A file dropped on the home page

A session file you drop or choose on Add a run is read inside your browser tab and is never uploaded. Nothing is sent until you choose who sees the run. Choosing Anyone with the link sends only the counts on the card (turns, tool calls, files changed, commits, time, the hour the session started, the activity line, the folder map as numbered stops with no folder names) and the title you type. No account is created. The link is unlisted, is not shown in the feed and expires after 90 days. The delete link shown once when you make it removes the card for everyone. To limit abuse, the address your request came from is hashed and kept for 24 hours.

Your account and posts

Sign-in uses Supabase Auth and the provider you choose on the sign-in screen. Your public profile contains your chosen handle, display name and any avatar you share. Runs store the measurements, caption, output link and audience you choose. The service also stores follows, ACKs, replies, blocks, reports and response notifications.

STRIVE shares its sign-in service with Agent Grinder. Profiles and posts are kept separately. Signing out of STRIVE ends the current STRIVE session; it does not intentionally sign you out of the other app.

You choose the audience

Private runs are for their owner. Public runs and profiles can be read without signing in. Link runs are relationship-gated: a signed-in reader needs a follow or close-friends relation with the builder (or be the owner). The URL alone is not enough. Blocking limits signed-in discovery and interactions; it cannot make already-public pages invisible to someone who signs out. A public output link opens another site with its own privacy practices.

A preview is not a post. You choose an audience and save the run to share it. Text you enter into captions or replies is stored as entered. Never include credentials or other people's confidential information.

Storage and browser data

The website is hosted on Vercel. Supabase stores accounts and app records with database access policies. Your browser stores the sign-in session and may keep an unfinished import temporarily so it survives login. Hosting and authentication providers may process technical request information to operate their services.

Delete your data

Signed in, open Account settings and choose Delete my STRIVE profile. A card you made from a dropped file without an account is removed with the delete link shown once when you made it. Use the run and reply controls to delete single items. Deleting your STRIVE profile removes its owned app data; it does not delete your shared sign-in identity or Agent Grinder profile. If a deletion fails, the app must report the failure. Copies other people have already made are outside these deletion controls.

Deleting a local draft does not delete the source transcript. Hosted deletion and local-file deletion are separate actions.

Questions

For general questions, use the project issue tracker. Issues are public: do not include private records, session exports or credentials.

Back to STRIVE