Beta information
Privacy Policy
This policy explains the information Jumino currently uses to operate its small web beta and the choices available to you.
Last updated August 27, 2026
Information Jumino handles
- Account and profile information: your email address, authentication identity, display name, username, profile image, bio, and account timestamps.
- Conversations and Story interactions: messages you send, AI responses, conversation identifiers, Story events, choices, and associated timestamps.
- Characters and Stories: content you create, upload, or generate, including descriptions, prompts used to define creations, images, visibility settings, casts, locations, objectives, and factions.
- Saved state and memory: bookmarks, recent visits, Story progress, inventory, notes, summaries, character memories, and relationship state used to resume and personalize your experience.
- Reports and feedback: the reported item, reason, optional details, page path, status, conversation rating, and the reporting account where applicable.
- Operational data: product event names, session identifiers, request/error diagnostics, and technical details needed for security and reliability. Signed-in product events may be associated with your account.
AI processing and usage measurement
To generate a response or image, Jumino sends the relevant prompt, recent conversation or Story context, and character or world instructions to its configured AI provider or gateway. AI output can be inaccurate, incomplete, or inappropriate and should not be treated as professional advice.
Jumino separately records limited AI usage metadata for cost and reliability measurement: provider, model, call type, token counts, estimated cost, turn scope or identifier, and time. This usage table does not store prompts, responses, message text, credentials, or user IDs. Conversation content is stored in the conversation and Story systems described above, not in that usage table.
How information is used
- Authenticate accounts and keep sessions secure.
- Generate, save, resume, and improve conversations and interactive Stories.
- Provide user-created characters, Stories, images, bookmarks, and account controls.
- Investigate reports, enforce rules, prevent abuse, and maintain service reliability.
- Measure beta usage, AI costs, and failures without placing message text in AI-usage records.
Service providers
Jumino currently relies on Supabase for authentication, database, and file storage; Replit for application hosting and operational logs; Google when you choose Google sign-in; and configured AI providers or gateways, including OpenAI-backed services, to generate text and images. These providers process information as needed to deliver their part of the service and apply their own terms and privacy practices.
Visibility, retention, and deletion
Chats, Story runs, and private state are intended to be scoped to your account. Characters and Stories can be visible to others when you publish them. Beta data is retained while needed to provide the service, investigate reports, protect the service, or meet legal obligations. Jumino does not currently promise a fixed retention period.
You can delete your account from the Privacy & account section of your profile. Deletion removes your account, profile, owned characters and Stories, conversations, private Story progress, memories, relationships, and associated generated files. Generated-file cleanup may finish shortly after the account is deleted. Moderation reports and aggregate operational records may be retained after their account association is removed.
Your choices
- Choose whether your created characters and Stories are public.
- Turn product analytics sharing off for the current device from your profile.
- Delete individual content where the product provides that control.
- Delete your account and associated user-owned data from your profile.
Questions and support
Jumino does not currently operate a public support email or separate ticket desk. During the beta, use the signed-in bug and content reporting tools described on the Support page. That page also explains the current limitation for users who cannot sign in.
