last updated october 2, 2026
privacy
this page says what rush keeps, why, who handles it for us, how long it stays and what you can do about it. questions go to team@therush.fun.
what we collect
account. your email address (or the address apple gives us when you sign in with apple, which can be a hidden relay), a handle, an optional display name, bio and avatar, the moment you confirmed you are 13 or older, your plan, and the settings you change. nothing else about you is asked for.
what you make. the apps you publish, the result cards you choose to save or share, room chat messages, and reports or hides you file.
what you try. what you hand a drop — a photo, a screenshot, pasted text — is sent to the model that answers it and then thrown away. it is not stored, not logged and not uploaded anywhere else. an image has its metadata, location included, removed before it goes anywhere. the model providers are told not to keep it wherever their api lets us say so. what is kept is the result card, for ninety days, so a link you sent still opens.
personal apps. JumpHigh measurements, goals, workouts and set logs, Vybez memories and Linkpls wishlist entries are saved to your account when you choose to save them. they are private to you, reachable from your signed-in devices, and encrypted at rest in our database.
usage. counts of what was opened, played and shared, so the floor can be ordered, plus a random device id in a cookie so the same browser is not counted twice. analytics never carries your ip address, and you can switch it off (see what you control). if you turn notifications on, the push address your browser or phone gives us.
billing. if you subscribe, the customer and subscription ids stripe or apple give us and which plan is active. card numbers go to stripe or apple, never to rush.
technical. standard server logs (request path, status, time) and your ip address, used for rate limits and abuse protection. where we keep an address to count abuse, we keep a hash of it, not the address. a sign-in email carries a one-time code; we keep a hash of it until it expires or is used.
why
to run the product you asked for: sign you in, keep what you save, order the floor, deliver notifications you turned on, bill the plan you chose, and act on reports. to keep the service safe: rate limits, bot checks and moderation. to understand the product in aggregate. we do not sell personal data, do not build advertising profiles and do not show third-party ads.
who handles it for us
rush runs on infrastructure providers under contract, each handling only what its job needs: hosting (Fly.io, united states), the database (Supabase, united states), content delivery, bot checks and image storage (Cloudflare; its Turnstile bot check sees your ip address and browser to tell a person from a script), transactional email (an email delivery provider that sends sign-in and plan emails), product analytics (PostHog, which receives event names and a random device or user id, never your ip address, app records, share tokens or what you typed, and nothing at all once you switch analytics off), subscription billing (Stripe on the web, Apple through the app store), and the model providers that answer a try (OpenAI, Anthropic and Google, which receive only that try's input, only to produce its result, and are told not to store it wherever their api allows).
other people see what you make public: your apps, room messages and profile. a hosted app runs on its creator's website under that creator's rules; rush does not send it your account details.
the ChatGPT plugin
when an assistant uses the rush plugin, it sends us only a short task, or an app description and audience, and we answer from a fixed catalog of reviewed apps and ideas. the request is not stored, not linked to any account and not sent to analytics; the ip address is counted in memory for a rate limit and not kept. the plugin cannot read, change or share anything saved in your rush account. saving progress happens on rush, after you sign in there.
when an assistant suggests a rush drop by link, that link carries a random id. we count whether it was opened and whether the same browser started a try. a signed cookie holds the id for up to one day and the count record is removed after thirty days. it contains no conversation, input, result or account.
connections and sharing
each personal app stays separate by default. you can connect selected apps to combine your own participation counts and dates, including earlier activity only if you choose it. connecting never exposes raw notes, workout details or measurements to other apps, creators or assistants. you can remove a connection in the app at any time.
sharing is optional. you preview and pick the fields before a link exists. anyone with the link can see that snapshot for up to thirty days; editing the source does not change it. revoking the link or deleting the source ends access. links are listed in my activity.
how long it stays
account data stays until you delete the account. result cards: ninety days, then the expired card is deleted. sign-in codes expire after fifteen minutes. assistant handoff counts and creator agent call records: thirty days. share links: thirty days or until revoked. deleted app entries are cleared at once; a content-free tombstone stays until the account is deleted so devices stop syncing them and a retried save cannot duplicate them. room messages stay while the room exists; a deleted message and its reports can remain for moderation review. server logs are kept for a short time by our hosting provider. database backups roll off automatically on a rolling schedule.
device-only data — airplane journals, game scores and entries from older device-only apps — lives in your browser and is never uploaded. clearing this site's browser data removes it, along with downloaded flight apps. anyone with access to that browser profile may be able to read it.
what you control
download a copy of everything tied to your account — profile, apps, results still kept, tickets, notifications, follows, sign-ins, app entries and plan — as one file: settings, then download my data. switch analytics off for a device in settings; it starts off when your browser sends do not track or global privacy control. we then send PostHog nothing for that device or account, from your browser or from our servers.
delete any entry inside its app (deleting a workout also deletes its set logs). export device-only data from its screen. remove app connections and revoke share links in my activity. turn notifications off in settings or your browser. hide a creator or report anything from its ••• menu. manage or cancel a plan from settings (app store plans are cancelled in your iphone's subscriptions).
delete your account yourself: settings, then delete my account, at the bottom. your apps come down and everything tied to you goes, including app entries, connections and share links. we also delete your customer record at Stripe and your person data at PostHog.
a few records stay, linked to an account with every personal field cleared — no email, handle, name, bio or avatar: published app versions, which are immutable (the app itself comes down and nothing serves them); the ticket ledger, an append-only money-like record that has to add up; and moderation records, so a removal can be reviewed and abuse does not come back under a fresh account. stuck, or can't sign in? write to team@therush.fun from the address you signed up with and we will do it for you.
children
rush is for people 13 and older. we do not knowingly keep an account for anyone younger; tell us and it comes down.
changes
when this page changes in a way that matters, the date at the top changes with it.
back to the strip →