Privacy information

Your account and cloud shelf

Jammi stores your shelf records with your account in Supabase: captured links and captions, captured-file references, game titles, sources, reasons, status, ratings, reflections and recognition suggestions. Access is scoped to your authenticated account. A network connection is required to load and save the cloud shelf; an error does not mean a change reached the server.

Captured image files and the share inbox also use device storage. A captured-file reference in a cloud record is not a backup of that image. Clearing app storage or uninstalling can remove device-owned files. Device backups and copies you send to other apps are separate.

Link previews for saved games

When you save a link, Jammi’s server can fetch that public page’s title and site or creator name so your shelf can show its source. Jammi does not sign in to those sites, watch a video, or open anything private behind a login. The current app build does not fetch, display or store third-party preview thumbnails; you can still open the original source link.

Sign-in and guest access

You may use email/password sign-in or guest access. Sign in with Apple is available on supported iOS builds; Google sign-in is not offered in the current iOS build. Guest access creates an anonymous Supabase account and requires a connection. A guest account has no recovery email; removing its stored sign-in or uninstalling can make its shelf inaccessible.

Account actions send authentication information to Supabase over HTTPS. Email confirmation and recovery messages are sent by the configured delivery provider. The app keeps session tokens in iOS Keychain or Android encrypted storage backed by Keystore. It does not write your password into shelf records.

Deleting your account and data

Open You → Settings → Delete account under Account control to review and confirm permanent account deletion. You can cancel before choosing Permanently delete account. The app submits an authenticated deletion request; it does not treat a sent request or a timeout as proof of deletion.

Deletion is designed to remove your Supabase account and its linked shelf, profile, shared-shelf, followed-shelf, activity, Ask Jammi history, receipt-share and account-linked quota records under the service's deletion rules. Copies already shared with other people, device-owned captures, aggregate daily totals and store transaction records are separate. Deletion is not a subscription cancellation or refund request.

If you used Sign in with Apple, you can also stop using Jammi for Apple sign-in after deleting your Jammi account in iPhone Settings → your name → Sign in with Apple → Jammi → Delete. Apple explains these steps.

Signing out does not delete the cloud account. For privacy questions or an out-of-app deletion request, email privacy@jammi.app. The launch email list is separate from an app account; use the unsubscribe link in its messages.

Optional Ask Jammi AI

Ask Jammi searches your shelf on your device first. With your consent and an account, including a guest account, a question that needs the AI helper can send your question and up to 20 shelf item IDs, titles and short reason or preview hints to Jammi's Supabase function. That function sends the limited text to OpenRouter and a selected model provider. It does not send your full shelf, reflections, original screenshots or voice audio in this request. AI suggestions can be wrong.

The visible conversation is stored with your account in Supabase so you can reopen it, and the app offers a clear-chat action. Account deletion is designed to remove linked conversation rows. OpenRouter and the selected model provider process the limited request to return an answer; contact us for questions about their handling of a specific request.

Capture recognition — not offered in this app build

Jammi's prepared capture-analysis service can process a selected caption or context and first screenshot, or supported public-link information, only after explicit submission. Screenshots are resized and re-encoded to remove metadata. Supported YouTube links may request a public title; Jammi does not watch a video merely because you share its URL. The model receives the caption, retrieved title or selected image, not the original link. Suggestions require your confirmation.

The current app build does not offer this analysis path. The server keeps account-linked attempt identifiers and times for limits; older records are cleaned on later requests, so there is no guaranteed seven-day deletion deadline.

Receipts you choose to share

You can preview and share a finish receipt image. Reflection and source-name inclusion each start off; full source links, captions and original screenshots are excluded from receipts. The image goes to the app or person you choose in the system share sheet. Jammi cannot delete copies held by recipients.

Public receipt links open on jammi.app. Their content is readable by anyone with the complete link and can be forwarded or edited. Links do not verify a person's identity or completion and cannot be revoked. The receipt page contains no analytics or third-party scripts; the selected web host may process standard request data.

Shelf links and Friends

If you choose to publish a shelf link, Jammi stores your chosen display name, selected shelf statuses and a link token in Supabase. Anyone with that link can see the selected games' titles, status, ratings and source site, but not your save reasons or reflections. You can stop sharing; a copied link may remain with a recipient, but it should no longer resolve after revocation. Opening someone else's link can add that shelf to your followed list. Saving a game from it can create an activity item for its owner containing an actor name and game title. If you report a shelf, Jammi stores your account ID, the reported shelf ID, your selected reason and report times in a private queue. Blocking stores both account IDs and hides that publisher's shelf and activity from your signed-in view; it does not revoke a public link held by someone else. Reports and blocks follow the account and shelf deletion rules described above.

Jammi+ subscriptions

Jammi+ offers monthly and yearly auto-renewing subscriptions through the app store. The store processes payment; RevenueCat receives purchase and entitlement records associated with your Jammi account ID so the app can check access and restore eligible purchases. Jammi does not receive your payment-card number or send your email to RevenueCat as a customer attribute. Your selected Stargazer appearance is saved on your device and does not by itself prove an active entitlement.

The current iOS products have an eligible first-time 14-day introductory trial; the exact price, eligibility and renewal terms appear in the App Store purchase sheet. Store transactions and provider records have separate retention. Deleting your Jammi account does not cancel a store subscription or request a refund.

iOS app diagnostics

Jammi's iOS app uses PostHog in the EU region to count app opens and receive native crash and related diagnostic data. PostHog assigns an app installation identifier and may receive standard app and device details and network information with those events; location enrichment is disabled for these mobile events. Jammi does not add your Jammi account ID, email, shelf entries, game links, Ask Jammi text or voice audio to these events; it removes free-form exception reasons before sending crash reports. Screen recording, interaction capture and surveys are off. A crash report can be queued for sending when you next open the app.

Launch notifications and website measurement

The optional Jammi launch form collects your email, chosen platform and consent. Your browser sends those fields directly to the published Brevo form. Brevo also receives standard connection information. Choosing Join wishlist requests immediate signup for launch updates on your selected platform; no confirmation email is required. This does not create a Jammi app account. Brevo processes form submissions and unsubscribe requests. You can unsubscribe using the link in launch emails.

PostHog (EU region) measures marketing-page visits, demonstration interactions and notification/store button clicks. It uses cookieless audience measurement without session replay, person profiles or form autocapture. Jammi does not send your email, form contents, receipt content, account identity or arbitrary link parameters to analytics. Cookieless measurement still involves processing network requests. Global Privacy Control and Do Not Track disable this site's analytics.

Receipt pages do not load analytics, third-party assets or signup forms. Website store clicks are not proof of an app installation. Cloudflare serves the website and may process standard request data; the active form submits directly to Brevo. Jammi is operated by Kaung Zin Hein. For privacy questions or an out-of-app data-deletion request, email privacy@jammi.app.