STRIVEEarly alphaAdd a run

Privacy

STRIVE · Updated 11 October 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.

The native sitting picker and browser import read the source on your device. A selected sitting may contain web searches, failed tool calls and errors. Where the source supports it, the preview can show counts or status from those events; it does not upload raw search queries, error text, prompts or the source file. Optional estimates may store a source hash and session dates as measurement provenance. Check every title, project name, caption, link and image you choose before saving: those fields are yours to publish.

Optional file import and unlisted cards

A session file you drop or choose on Add a run is read inside your browser tab and is never uploaded. Parsing the selected file does not upload the raw file. Saving or creating a share link is a separate network action. 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 for rate limiting. The creation handler removes rate-limit hashes older than 24 hours when it next runs; this is not a timed physical-erasure guarantee.

Your profile 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, XUDOS, replies, blocks, reports and notifications.

If you choose email sign-in, Supabase Auth stores your email address with your shared sign-in identity. A one-time sign-in link is sent through Resend. Your email address and the link are used for authentication; the address is not put on your public profile or run card. The website limits repeated link requests and shows a countdown, but delivery can fail or be delayed. Do not forward a sign-in link. Public email sign-in is enabled only when the option appears on the site. To remove your STRIVE profile, use Delete my STRIVE profile in Settings; this does not delete the shared Supabase Auth identity, as explained below.

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. Followers runs are relationship-gated: a signed-in reader must follow the builder or be on the builder's Close friends list. 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 saved run. A new captured run starts under Only me when you save it; change its audience after reviewing the saved result. The separate unlisted-card flow described above is a bearer-link share, not a Followers run. Text you enter into captions or replies is stored as entered. Never include credentials or other people's confidential information.

Photos

You choose which photos to upload to a saved run. The server decodes, resizes and re-encodes supported still images without embedded camera or location metadata. This does not remove private information visible in the picture. Uploaded derivatives follow the run's audience; original files on your device are unchanged. Private images require an authorized read through the photo API. There is no end-to-end encryption claim: authorized service operators have privileged access.

Feedback

The signed-in feedback form stores your message, category, page path, profile reference and server time for the operator. It is not a public post; other app users cannot browse these submissions. Do not include credentials, confidential code or private session text. A separately configured notification may send a reference, category, timestamp and private inbox link to the operator's chosen service, not your message, profile or email. Feedback can remain saved even if no notification is delivered. Delivery retries may repeat a notification.

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. Pages load fonts from Google Fonts, which receives the corresponding request. These access controls do not mean the website is offline or that saved content is inaccessible to service operators.

Delete your data

Signed in, open 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. Profile deletion follows the app database rules: dependent records are deleted or their profile references are detached. 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 run or its photo record revokes normal photo API access. Stored image objects may remain queued until the cleanup worker successfully removes them. Immediate physical deletion is not guaranteed. We do not claim that app deletion instantly erases provider operational records or backups.

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