Privacy
Boundaries, local-first workflows, and careful handling of authorized work.
Boundaries, local-first workflows, and careful handling of authorized work.
Last updated: September 26, 2026
This page describes the privacy practices for DanBot, an AI assistant service operated by Daniel Beem for people Daniel authorizes who independently opt in.
The service may process an authorized user's mobile phone number, SMS message content, message timestamps, consent history, and technical delivery information as needed to send, receive, and operate personal assistant messages.
Information is used only as needed to operate DanBot, including conversational answers, requested task assistance, requested status updates, and links to requested results when an applicable capability is available. Texting DANBOT does not grant access to Daniel's private email, calendar, files, work information, or privileged tools.
Mobile information and SMS opt-in data or consent will not be sold, rented, or shared with third parties or affiliates for marketing or promotional purposes.
SMS messages are conversational and transactional only. Message frequency varies based on user initiated interactions. Message and data rates may apply. The user may reply STOP to opt out and HELP for assistance.
Technical service providers, including Twilio for SMS transport and hosting or connectivity providers, may process information only as necessary to provide messaging, hosting, connectivity, or related infrastructure used by DanBot.
DanBot may support conversational answers, authorized task assistance, status updates, and requested creative results. Specific integrations, including image or song generation and result links, are staged capabilities and should not be treated as available unless the service confirms them.
BeemOps, powered by Hermes, is Daniel Beem's personal operations system for authorized workflows such as creative generation, reminders, project continuity, and selected local integrations. Public visitors do not receive access to private conversations, files, calendars, work information, local dashboards, or privileged tools merely by visiting this site or using a public page.
Depending on the requested capability, Hermes may process prompts, task inputs, generated-artifact metadata, delivery metadata, and technical status information. Local generation may be performed on Daniel's own computer. External providers are used only for capabilities that explicitly require them and should not be assumed from the public page alone.
Generated images, audio, documents, prompts, and related metadata may be retained locally to operate a request, verify an output, support a retry, or deliver a requested result. Actual retention and deletion behavior depends on the applicable local workflow and is not a promise of permanent storage or automatic deletion.
Generated content may contain errors or artifacts and should be reviewed before use. Hermes does not make public-site visitors' private content available to other people.
Do not submit government, resident, health, case, work-confidential, or other sensitive information through a public page. Sensitive integrations require an explicitly approved environment and separate authorization.
BeemOps capabilities may be staged, unavailable, or limited to authorized users. A capability description on this public page does not by itself grant access or guarantee that a workflow is active.
Questions about this policy may be directed to the site owner through the GitHub profile associated with this site: https://github.com/dbeem123.