RushGen
Privacy policy
This document describes data handling implemented by the current RushGen version and does not claim features the product does not provide.
← Back to RushGenTelegram authentication
Login or registration requires a Telegram-verified phone claim. RushGen normalizes it only during bounded callback processing and derives a keyed fingerprint for uniqueness checks. The plaintext phone number is not stored, displayed, or returned by account reads.
Account and session data
RushGen stores a bounded profile name, the Telegram issuer/subject identity, the phone fingerprint, and a digest of a random browser session credential. The session secret remains only in the protected browser session cookie.
Generations and results
Generation requests, operational state, and result metadata are stored in PostgreSQL. Private result files are delivered only to their owner through an authenticated route and may be removed under application retention rules.
Prompt improvement through APIMart
Image prompt improvement is enabled by default. When enabled, RushGen sends APIMart the original text prompt and selected model identifier, but not the reference image, account data, or result. Customers can disable it in the generator or API to use the original prompt unchanged. If APIMart is unavailable, RushGen also continues with the original prompt.
Document boundary
RushGen does not sell personal data and this page is not consent for unimplemented billing, advertising, or data-sharing behavior. A behavior change must update this document together with the code.