Jormie Privacy Policy
Updated 28 October 2026.
Jormie is a personal assistant operated for one owner on their Mac. This policy describes its connected Google data and the separate informational website.
Google information the app reads
Jormie requests 3 read-only permissions: Gmail messages, calendar events and the list of calendars. Access stays bound to the configured Google account and selected calendars.
The app may read message content and metadata, event details and calendar information. Selected facts, original source references and processing receipts can be stored in a private local database and diagnostic archives. Access credentials are stored privately on the Mac, separately from these public pages.
This connection does not send or change email or create, change or delete calendar events. Other tools and actions require separate supported access and explicit permission.
Why the app uses this information
Jormie uses selected context for personal summaries, reminders, preparation, planning, possible conflict detection and tasks requested by the owner. Incoming content is evidence; it does not itself authorize an action.
Explicit preferences and corrections may personalize the assistant. Observed messages, silence and completion check-ins are not automatically treated as training feedback. Jormie does not sell Google user data, use it for advertising or use it to train generalized AI models.
Cloud AI and local processing
OpenAI provides Jormie’s main AI model. Depending on the enabled workflow, selected private context may also be processed by Anthropic or TypeSafe’s JEV adviser. JEV currently runs in shadow mode; its suggestions are evaluated but not applied to current plans. Local Qwen is a fallback.
The app therefore does not promise that all Google information stays on the Mac. Cloud-provider processing is governed by the applicable service terms and account settings. This policy does not assert a provider-specific training exemption or data control that has not been verified.
Storage and retention
Selected source facts and working memory remain in private local storage. Diagnostic archives, failed or uncertain processing receipts and backups may also be retained until the owner carries out maintenance.
Some successful, settled Gmail reader packets become eligible for compaction after 30 days when their committed source record has been verified. That is a limited housekeeping rule, not a 30-day deletion rule for all app data. Partial or unresolved evidence can remain, and there is no fixed automatic deletion date for every record.
Disconnecting and managing local copies
The owner can revoke the app’s access through their Google Account connections. Revocation stops future reads using that grant; it does not automatically remove data already stored locally or in backups.
The owner can request an export, correction or deletion through their existing assistant channel or the support address displayed on Google’s consent screen. These are owner-managed operations, not an immediate, one-click deletion service. Existing local copies and backups need to be considered when carrying out a deletion request.
These public pages
These pages do not provide Google sign-in, accept private message or calendar uploads, or display the owner’s connected data. These static pages contain no added tracking scripts, external assets or registration form.
These informational pages are hosted separately on Cloudflare Pages. Cloudflare processes website requests to serve and protect these pages under its service policies. Website traffic handling is separate from the assistant’s connected Google data; private Google information should not be submitted to this website.
Google-derived information is used for the owner’s assistant features in accordance with the Google API Services User Data Policy, including its Limited Use requirements. This statement does not certify third-party account settings or constitute Google verification.
Questions and changes
Use the support address displayed on Google’s consent screen for questions or data requests. Review this policy when the app’s data handling changes.
See Jormie for the app overview and Terms of Use for its scope and limits.