Jymni Ethics Advisor Privacy Policy

Effective date: August 11, 2026

This Privacy Policy explains how Jymni Ethics Advisor handles data in the mobile app, the Studio web app at /studio, the restricted Admin site at /admin, and related websites. In this policy, "we," "us," and "our" refer to the app and website provider.

1. Summary

The Jymni Ethics Advisor mobile app sends personal ethics analysis requests directly to a third-party cloud AI service for cloud processing. The mobile app does not include an on-device LLM model, does not require an account, does not include advertising, and does not include analytics tracking. We do not receive your prompts, model responses, or completed analyses through the mobile app.

Studio is an account-based web service. If you use Studio, we may collect and store account, authentication, prompt, evaluation, saved-use-case, feature-usage, credit, support, and security records as described below.

Studio users can create expiring, revocable shared-evaluation links and choose whether a link is public, available to signed-in users, or limited to members of a selected workspace. Workspace owners and admins can invite people by email, manage role and pooled-credit settings within seat limits, and export a workspace audit history.

The Admin site is a restricted operational tool. Authorized administrators can view and manage user accounts, Studio usage metadata, credit requests, policy memory rules, LLM token and cost metrics, and audit logs. Routine Admin usage reports show operational metadata and do not expose evaluation prompt text or generated-output details. Admin actions, notes, reasons, and policy-rule changes may be stored for account integrity, safety, and operational review.

We do not sell personal information and we do not use Studio or Admin records for third-party advertising.

2. Information processed by the app

The app may process personal ethics situations, prompts, decision descriptions, or other text you type; model responses generated by the cloud AI service; and basic app state needed to display the current analysis.

This information is used to provide the app's core function: structured personal-ethics reflection through the Jymni Guide.

3. Information collected by us through the app

We do not intentionally collect personal information through the app. The app does not require registration, login, email entry, payment entry, contacts access, location access, camera access, microphone access, SMS access, call log access, or advertising identifiers for its core operation.

The app does not transmit your prompts or analysis results to our servers. Prompts are sent directly from the app to a third-party cloud AI service and are governed by that provider's applicable terms and privacy policies.

4. Information collected through Studio

If you use Studio or account features on the Jymni Ethics Advisor website, we may collect and store:

• Account information, such as email address, display name, role, account status, created and updated timestamps, and password hashes.
• Authentication and security records, such as session token hashes, session timestamps, password reset token hashes, pending signup token hashes, WebAuthn/passkey credential IDs, public keys, sign counters, authenticator metadata, passkey names, challenge records, CSRF tokens, cookies, browser/device information, IP address, request metadata, and server logs.
• Evaluation content, such as the personal situation, prompt, decision description, Studio context fields, displayed use case, generated response, classification, rubric metadata, source type, created timestamp, and related model usage metadata such as runtime, model, token counts, latency, and estimated direct model cost when available.
• Saved use cases, including the saved name, use case text, generated response, Studio context, and created or updated timestamps.
• Shared evaluation records, including a share token, the shared name, use case text, generated response, classification, case description, created and updated timestamps, and revocation status.
• Workspace and review records, including workspace names, membership and workspace roles, seat limits, pending invitations, invitation email address and delivery status, policy guidance, reviewer assignments, review status, comments, approval records, pooled-credit settings, workspace billing ownership, audit events, and related timestamps. Invitation tokens are stored in hashed form.
• Controlled-sharing records, including access mode, workspace association, expiration, view count, allowed or denied access results, the signed-in viewer account when applicable, and timestamps. The application-level share-access record does not store viewer IP addresses, although ordinary security and web-server logs may.
• Batch-job records, including submitted cases, item status, completed responses, error summaries, credit reservations and refunds, and timestamps.
• Billing records, including checkout-session and payment-intent identifiers, plan and credit amount, order status, third-party customer or subscription identifiers when supplied, fulfillment references, payment-provider receipt links, paid timestamps, and other order timestamps. Payment card details are handled by the payment provider and are not submitted to our application server.
• Privacy-minimized first-party product events from a fixed allowlist, such as page view, signup, sample, evaluation, checkout, sharing, review, and batch milestones. These event records exclude raw prompts, case text, names, email addresses, and IP addresses.
• Feature usage records for custom evaluations, Counterargument Lens, and Strengthen This, including the submitted use case, completed evaluation or report used for the feature, generated output, credit cost, source type, and related history entry.
• Credit account records, including personal or pooled-workspace billing context, current balance, ledger entries, credit debits and adjustments, structured trial or support request reasons, intended use, organization, requested timeline, request amounts, user notes, admin notes, decision status, decision timestamps, and related admin or history references.
• Local browser data, such as the current conversation saved in local storage, the Studio history collapsed or expanded setting, service worker cache data, and first-party cookies used for sessions and evaluation history.

Do not enter names, addresses, account numbers, private communications, medical details, or other information that could identify you or another person unless you have the right and a sound reason to process it. Prefer anonymous descriptions.

5. Shared evaluation links

If you create a shared evaluation link in Studio, the shared page may include user-submitted personal decision information, Studio context, saved-evaluation names, generated evaluation text, classifications, scores, and other output included in the snapshot. The link is read-only. Depending on your selection, it may be public, require a signed-in account, or require membership in the selected workspace. A permitted viewer can still copy, screenshot, print, download, or further distribute what they can see.

Shared evaluation links are not intended to be indexed by search engines, and shared pages are served with no-store caching headers, but we cannot guarantee that recipients, browsers, search engines, network intermediaries, or other third parties will not retain copies or records. If you revoke a shared link, the old URL should stop opening the shared page through our service, but revocation does not delete copies already made by viewers.

Viewing or attempting to view a shared evaluation can create a share-access result and may also create ordinary server logs, such as IP address, user agent, request path, referring page, timestamp, and security metadata. Do not create shared links for evaluations containing confidential, regulated, sensitive personal, or third-party information unless you are authorized to share that information with every permitted viewer.

6. Information collected through Admin

The Admin site is available only to authorized admin and super-admin accounts. It may display Studio account, usage, credit, policy, audit, and LLM usage metadata so administrators can operate the service. This includes feature type, timestamps, credit activity, token counts, model, latency, estimated direct model cost, and aggregate per-user totals. The Admin dashboard is designed not to show prompt text, saved-use-case text, generated evaluation responses, or raw evaluation JSON in routine usage and cost reporting.

Admin actions may create or update records such as credit adjustments, credit request decisions, user disable or enable reasons, role changes, session-clearing events, policy memory rules, trigger terms, guidance text, active or inactive status, admin notes, audit metadata, and timestamps. These records may identify the administrator who performed the action and the account or object affected.

7. How we use information

We use the information described in this policy to provide evaluations and Studio features; authenticate users; save and retrieve evaluation history and saved use cases; send and administer workspace invitations; enforce roles and seat limits; operate pooled-credit and human-review workflows; create and export workspace audit records; create, control, display, refresh, and revoke shared evaluation links; run durable batch jobs; operate credit balances, reservations, refunds, structured trial or support requests, purchases, receipt links, and usage ledgers; distinguish AI-backed feature usage; apply platform and workspace policy rules; administer accounts; protect the service; investigate abuse or errors; measure product and model usage and cost; respond to support or privacy requests; comply with legal obligations; and improve reliability and product quality.

8. Third-party services

The mobile app communicates directly with a third-party cloud AI service to generate responses. Studio and related web features may send prompts, Studio context, completed evaluation reports, policy-rule guidance, and generated outputs to a third-party cloud AI service for processing. The provider may process that information under its own terms and privacy policy.

If secure checkout is enabled and you choose to buy credits, the checkout provider processes payment and billing information under its own terms and privacy policy. We receive identifiers and status information needed to match and fulfill the order, but not your full payment-card details.

If a workspace owner or admin invites you, we may use an email delivery provider to send the invitation. The message may identify the workspace, inviter, assigned role, expiration date, and secure acceptance link. If email delivery is unavailable, the authorized inviter may receive the link for delivery through another channel.

If you install the mobile app through Google Play, Google Play may process information needed to provide installation, updates, app integrity, crash reporting, purchase infrastructure, and device compatibility. Those activities are controlled by Google and are governed by Google's terms and privacy policy.

9. Cookies, local storage, and deletion

Your current prompt and response may be kept in memory while the app is running so the app can display the analysis. The app does not store an on-device LLM model.

You can clear the current analysis by using the app's reset or "Try another case?" control. You can remove locally stored app data by using your device's app storage controls or by uninstalling the app.

Studio uses first-party cookies for authentication sessions and evaluation history, and it uses local storage to keep the current conversation and interface preferences on your device. Logout attempts to clear cookies, storage, and cache where supported by the browser. You can also clear browser storage through your browser settings.

You can delete saved use cases in Studio and revoke shared evaluation links. Authorized workspace owners and admins can revoke pending invitations and download workspace audit records. Other account, invitation, membership, evaluation history, shared-evaluation audit, workspace audit, credit, billing, admin audit, and security records may be retained while your account is active and as needed for service operation, security, accounting, dispute resolution, legal compliance, and abuse prevention. To request access, correction, deletion, or other privacy help, use the contact method below.

10. Voluntary contact

If you contact us for support, legal, or privacy questions, we may use the information you voluntarily provide, such as your name, email address, device details, screenshots, or message content, to respond to your request, troubleshoot issues, improve the app, protect users, or comply with legal obligations.

We do not sell personal information.

11. Security

We use technical and organizational measures intended to protect the information we keep, including password hashing, session token hashing, CSRF protections, restricted Admin access, and audit logging. No method of transmission or storage is completely secure.

The app and Studio use cloud processing, so you should avoid entering information that you are not authorized to use or that would create unacceptable risk if sent to a cloud AI service, stored in your account, included in restricted support or admin workflows, or viewed on your device.

12. Children

The app is intended for users who can evaluate personal decisions responsibly. It is not directed to children under 13, and we do not knowingly collect personal information from children through the app.

13. International users

If you contact us or use related websites, information you voluntarily provide may be processed in the United States or other countries where we or our service providers operate.

14. Changes to this policy

We may update this Privacy Policy from time to time. The effective date above indicates when this version became effective. Continued use of the app after an update means you acknowledge the updated policy.

15. Contact

For privacy inquiries, use the developer contact mechanism listed in the Google Play Store listing for Jymni Ethics Advisor or the contact mechanism available through the Jymni Ethics Advisor website.