Road to Purity Hermes — Internal Bot Privacy Notice

Effective date: September 27, 2026

Operator: Road to Purity Inc.

Contact: ask@roadtopurity.com

Who may use the bot

Road to Purity Hermes is intended only for authorized Road to Purity Inc. team members. It is not a public-facing ministry, counseling, or recovery service. Bot access is restricted using a list of approved Microsoft Entra user IDs. Road to Purity controls who is on that list.

Information processed

When an authorized team member uses the bot, Road to Purity’s systems may process the Microsoft Teams account and conversation identifiers, the messages and attachments the person sends, bot responses, and operational information needed to run and troubleshoot the service. Users should not send passwords, payment-card data, government identifiers, confidential donor information, identifiable recovery or health histories, personnel records, or information about minors unless a separate approved workflow and safeguards are in place.

Why and how information is used

We use this information to authenticate and route bot conversations, generate responses to authorized work requests, maintain conversation continuity, apply access controls, troubleshoot failures, and protect the service. Bot output can be inaccurate and should be reviewed by a person before use or distribution.

Systems involved

Microsoft Teams and Microsoft’s bot infrastructure deliver the message to the registered bot endpoint. The HTTPS endpoint is provided through ngrok and forwards traffic to Road to Purity’s always-on Mac, where the Road to Purity Hermes profile processes the request. The configured AI provider then processes the context necessary to generate a response. As of September 27, 2026, this profile is configured for an OpenAI Codex-backed model; that configuration may change. If an authorized user asks the bot to use another connected service or tool, relevant request data may also be sent to that service. Each external provider’s own terms and privacy practices may apply. Road to Purity should not assume that local deletion also removes records held by these providers.

Storage and retention

Hermes stores conversation history and operational logs locally on Road to Purity’s Mac. As of September 27, 2026, the RTP profile has automatic session pruning enabled with a 90-day setting. That setting is not a promise that every message or copy is erased after 90 days: logs, backups, Microsoft Teams copies, ngrok traffic metadata, and AI-provider records may have different retention periods. Road to Purity has not established one uniform deletion period for all of these records. Road to Purity may retain records longer when necessary for security, legal obligations, or approved business purposes. Deleting a Hermes session does not necessarily delete copies held by Microsoft or other providers.

Access and security

Only authorized Road to Purity team members should be able to interact with the bot. The bot verifies Microsoft Bot Framework requests, and the local configuration uses an Entra-ID allowlist. Road to Purity personnel with administrative access to the Mac or relevant accounts may access records as needed for operations and support. No security measure guarantees absolute protection.

Requests and changes

Team members can contact ask@roadtopurity.com to ask about access, correction, export, or deletion of information held by Road to Purity, subject to legal and operational limits. Requests concerning copies held in Microsoft Teams or another provider may also need to be handled through that provider. We will update this notice when the bot’s processing materially changes and state a new effective date.