Privacy

Who operates Rodon

Rodon is privately operated by an individual operator. This policy covers the public Rodon website and the optional connected features available in a Rodon workspace.

Data categories

Depending on the features a person chooses to use, Rodon may process account identity, workspace content such as conversations, documents, files, tasks, and generated artifacts, connection settings, operational records, and the technical information needed to operate and secure the service. Standard web-server logs may include IP address, request path, user agent, timestamp, and response status.

Google Mail data

A user may explicitly connect their own Gmail account through Google OAuth. Rodon accesses Gmail messages, threads, headers, labels or folders, metadata, attachments, and account identity only to provide the connected Mail workspace features.

• These features include displaying, searching, and synchronizing mail, together with user-initiated actions such as send, reply, archive, mark read or unread, move, label, star, restore, and delete.
• OAuth access and refresh tokens are stored server-side in encrypted form and are not exposed to browsers.
• Disconnecting or removing a Mail account revokes Rodon’s future local access and deletes Rodon’s local credentials, private mail index, sync state, and drafts for that account. It does not delete mail stored at Gmail.
• Where a user explicitly initiates or authorizes an agent or model feature to use connected Mail content, the relevant content may be sent to the selected external model, storage, transcription, execution, or other user-authorized integration provider to perform that feature. Connecting Mail alone does not authorize such a transfer.

Google API Services User Data Policy

Rodon’s use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Purpose and operational basis

Rodon processes information to provide the features a user chooses, maintain the requested connection, protect the service, and respond to support or security issues. The applicable legal basis for a particular deployment depends on the relationship with the user and the law identified by the operator for that deployment.

Storage and security

Connection credentials are kept server-side. Gmail OAuth access and refresh tokens are encrypted at rest. Rodon uses the information needed to operate the connected feature rather than exposing connection credentials to the browser.

Retention and deletion

Rodon retains information only for as long as needed to provide the chosen features, maintain the relevant workspace state, meet security or legal obligations, or respond to a user request. No fixed retention period is stated here because it depends on the applicable deployment and feature. The Gmail connection cleanup described above applies when a Mail account is disconnected or removed.

Processors and user-authorized transfers

Rodon may rely on infrastructure, storage, model, transcription, execution, and integration providers to operate features a user chooses. A transfer to such a provider is limited to the relevant feature and user authorization. Rodon does not sell Gmail or other Google user data, use it for advertising, use it to determine creditworthiness or lending decisions, or use it to train generalized AI or ML models.

Your controls

A user can disconnect a connected Mail account. Where implemented in the relevant workspace, a user may export or delete workspace data and remove an account or local index. Available controls depend on the feature and deployment.

Privacy contact

For privacy questions or requests, contact [email protected].

Changes to this policy

This policy may be updated when Rodon’s features, data practices, or applicable requirements change. The current version is published on this page.