AI Information in Ritemark
When you use the AI sidebar, you are interacting with artificial intelligence. Ritemark shows the selected runtime and model in the composer and provides an AI information button for details.
AI output can be inaccurate, incomplete, or misleading. Review factual claims, citations, calculations, commands, and file changes before you rely on, publish, or act on them.
Which AI Service Is Used?
Ritemark does not send AI requests through a Productory server. It launches an AI runtime on your computer, and that runtime connects to the provider using the account or API key configured for it.
| Runtime in Ritemark | Provider or service | Authentication used by the runtime |
|---|---|---|
| Claude Code | Anthropic | Claude account sign-in or an Anthropic API key |
| Codex | OpenAI | ChatGPT sign-in or OpenAI API authentication |
| OpenCode | The service selected in Ritemark: Google, OpenAI, Anthropic, or OpenRouter | Your API key for the selected service |
The exact model is the one shown in Ritemark's model picker. Available model names can change as the installed runtime and Ritemark's shared model catalogue are updated.
What May Leave Your Device?
Your Markdown files remain normal files on your computer. Using cloud-connected AI is a separate data flow: content needed for a turn can be sent to the selected runtime and provider.
Depending on the task and the context visible in the composer, this can include:
-
Your prompt, plus hidden instructions Ritemark adds so the runtime can complete the task
-
The active file, including its path and content the agent reads
-
Selected text, its file path, and a short surrounding context window
-
Files or images you attach when the selected runtime supports them
-
Shared browser context, such as the page URL, page summary, and an optional screenshot for supported runtimes
-
Tool results and recent conversation context, including a handoff when you switch runtimes in the same chat
An agent may also read other files in the open workspace or use tools and commands while completing a task. What it can do depends on the selected permission mode and the approvals you give.
Removing a context chip excludes that item from the turn where the control is supported. It does not prevent an agent from later reading the same workspace file with an allowed tool.
What Stays Local?
Ritemark stores and edits your files locally. Productory does not receive a copy of your workspace through an AI proxy, and Ritemark does not provide cloud storage for your documents.
This does not mean all AI content stays on the device. A cloud-connected runtime must send prompts and relevant context to its provider to generate a response. The provider handles that data under the terms and privacy settings attached to your account.
You can use Ritemark as a Markdown editor without using the AI sidebar.
Ritemark Analytics
Ritemark analytics is separate from AI-provider processing. When analytics is enabled, the desktop app sends anonymous product-usage events to PostHog's EU service. The setting is enabled by default and can be turned off in Ritemark settings.
The product events cover app sessions, feature use, selected agent use, and reactions. They do not include your prompts or file contents. If you explicitly submit written feedback, the feedback text you enter is sent with that feedback event.
Ritemark stores a random anonymous identifier on your device so sessions can be counted without a user account.
Review and Approval
Permission and approval controls help reduce unintended file changes or commands. They do not verify that an AI answer is true, lawful, unbiased, complete, or suitable for your situation.
Before using AI output:
-
Check important facts and sources against reliable originals.
-
Inspect file changes and commands before accepting them.
-
Do not send confidential or regulated information unless your organisation permits the selected provider and account configuration.
-
Apply meaningful human review before publishing or making consequential decisions.
Provider Information
Provider data retention and model-training choices can depend on your account type and settings. Check the current provider documentation for the account you use.