Privacy Notice
Pushpop Interactive provides Fireside. For privacy questions or requests, contact pushpopinteractive@gmail.com.
Apple or Google sign-in supplies account identifiers and, depending on your choices, name and real or relay email. When email/password sign-in is available, Supabase also processes your email address and password to authenticate you; Fireside does not store your password in its story database. Supabase authenticates your account and stores your private library: player descriptions, stories, messages, private narrator conversations, notes, summaries, drafts and artwork, favorites and settings. Local device storage also keeps copies.
When you allow AI processing and request a reply or summary, Fireside’s server on Render sends the relevant conversation and story context through your chosen service (OpenRouter or Infron) to the provider serving your selected model. This can include substantial history, private narrator exchanges, player descriptions, story setup, notes and summaries. Information you type may contain personal details. The available models are made by Xiaomi (MiMo), Zhipu AI (GLM), DeepSeek and Moonshot AI (Kimi), which are based in China, and by Anthropic (Claude) and Google (Gemini), which are based in the United States. Your request may be processed by the model’s maker or by another company that OpenRouter or Infron selects to host that model, such as Alibaba Cloud; Infron requests pass through its routing service at onerouter.pro. Some of these companies may process your data in China.
Optional story pictures send the selected passage, relevant context and character descriptions to NovelAI or through OpenRouter to the selected image provider. Supported picture requests can also include your saved persona portrait as a reference, as shown before creation. Your account picture is not sent as a character reference. Read aloud sends the passage text and chosen voice to Inworld after you enable it; automatic narration has its own confirmation. Generated pictures and recordings are stored privately for your account, including media in Cloudflare R2 and local replay copies.
When you enable push notifications, we store an Apple push delivery token with your account and send announcements through Apple Push Notification service. The lock-screen message asks you to open Fireside; it does not include your private story text. Your account also stores in-app announcement and reward records. Apple handles payment-card details for App Store purchases. Stripe handles payment details for website checkout and recurring web memberships. Website memberships renew monthly until cancelled through Manage website subscription, with benefits continuing through the paid period. Each confirmed paid month delivers the selected plan’s Embers once to your shared balance. Fireside receives customer, checkout, subscription and invoice references, product, amount, paid period, renewal and cancellation status, payment and refund status to deliver purchases and reconcile the shared Ember balance. We do not store your full card number. Apple transaction and subscription information also supports rewards and restores.
Render hosts our Ember and reply-recovery records, including completed reply text. Creator submissions, approved story versions, review decisions, reader access grants and reports are also stored on our server. Private copies of that database are backed up to Cloudflare R2. These services process technical and usage information to operate and secure the service. Public sharing is a separate action; AI processing does not publish your private stories to other players.
The website is hosted and routed using Cloudflare Workers through OpenAI Sites. Website requests pass through this routing to the Fireside service on Render and can include your signed-in account token, requested story content and media. Your Fireside account and private library continue to use Supabase; website hosting does not require a separate ChatGPT account.
OpenRouter, Infron and model-provider retention and data-use practices depend on provider and configuration. We do not promise zero retention or that every provider excludes all training use. Their processing may occur outside your country. You can decline AI processing or stop future requests in Privacy settings.
We record policy versions, your permissions, age-screening result and server timestamps with your account. The standard age check is your declaration that you are 18 or older. Older app versions use a birthday to calculate adult status without storing the birthday. These are self-reported age checks. Where a stronger check is required, we keep a limited verification receipt with its method or provider assurance, region and expiry separately from your content choices. Consent records do not contain selfies or identity documents.
Where an additional age check is required, you can choose Verify with AgeVerif. The available flow uses non-selfie methods; information for the method you choose goes directly to AgeVerif. We receive a verification reference, adult threshold, assurance level, applicable region and expiry, rather than a selfie, identity document or full payment-card details. A short-lived return code is exchanged by our server and is not retained with your verification receipt. This separate check does not turn on Mature or 18+ for you.
Delete account in Profile → Account starts removal of your identity, private library, published creations, comments, generated media and account records. A saved receipt shows progress after sign-out. Our managed Render database snapshots older than seven UTC dates are removed after a successful replacement backup; cloud-provider backups follow their retention settings. A minimal deletion marker prevents restored backups from reopening the account. Anonymous cost records may remain for billing reconciliation. Other players’ independently saved copies and information already sent to AI providers are not recalled. Offline devices clear their account copies when they reconnect and learn of deletion. Contact us for access or correction requests. Access controls protect private records but cannot guarantee perfect security.