Data and account access

Privacy policy

Last updated: 29 October 2026

DRuler is a private AI-assisted service operated by its owner for personal and work organization. It is not open for public registration. This policy describes the current deployment; it is not a claim of Google verification, independent security certification, or zero data retention.

Information accessed

Depending on consent and the task, DRuler can access Gmail headers, message text and thread context; calendar metadata and events; Drive metadata and selected files; Docs and Sheets content; and Contacts. Configured Google permissions include read/write access for Gmail, Calendar, Drive, Docs and Sheets, and read-only Contacts access. OAuth capability does not itself authorize every available action.

How information is used

Selected information is used for the owner's requests, such as searching mail, triaging messages, identifying possible commitments, planning, and reviewing documents. Changes such as sending mail, sharing files, editing documents or modifying events require the owner's direct instruction. Automated summaries operate only within an agreed scope and schedule.

AI providers and other processors

Selected messages, document excerpts and other context needed for analysis may be transmitted to the configured AI service: OpenAI or a model provider reached through OpenRouter. Provider retention and processing depend on the applicable service terms and account configuration; this policy does not promise that processing stays on the VPS or that all providers offer zero retention. DRuler itself does not train AI models. Provider terms and settings must be reviewed before submitting sensitive or restricted information.

Telegram processes the owner's assistant conversation and delivered summaries. The hosting provider processes data stored or handled on the assistant server. These services are separate from Google.

Storage and retention

OAuth credentials are stored on the server with restricted access. Assistant conversations, tool records and scheduled digest records can retain excerpts or summaries. DRuler does not deliberately copy emails into its resource vault or build a separate persistent email knowledge base. Searching or summarizing a message should not be interpreted as a zero-retention guarantee.

The resource vault is for screenshots and URLs explicitly sent by the owner. Those notes and attachments, and selected native Markdown memories, are exported to a separate private GitHub repository. Email content must not be added to that export. Git history can retain earlier versions; private GitHub storage is not end-to-end encrypted.

Encrypted recovery backups can retain earlier runtime data until backup rotation. Deleting an item from a live system does not automatically erase historical backups, Git history, provider records or Telegram messages. Those layers require separate handling.

Controls, revocation and deletion

The owner can ask DRuler to stop a scheduled workflow, limit access, or remove retained assistant records through the existing authenticated assistant conversation. Google access can also be revoked directly in Google Account connections. Revoking access stops future authorized access but does not itself delete information already retained elsewhere. Deletion requests must identify which storage layers are included.

Security and limitations

Account content, attachments and retrieved pages are treated as untrusted data, not instructions. Access controls, bounded retrieval and separation of public pages from private storage reduce risk but do not eliminate prompt injection, unauthorized disclosure or software defects. This public website has no credential intake form and must never receive passwords, keys or authorization codes.

Contact

For this single-owner deployment, privacy questions and access or deletion requests are handled through the owner's existing authenticated DRuler conversation. There is no public signup or public support inbox advertised by this site. Any future multi-user service would require updated contact information and a revised policy before onboarding other users.