Privacy & Data Use

This notice describes the public Digital Offload website, including the website chat, booking links, and public demonstrations. It does not replace the data-handling terms for a customer engagement. Any customer systems, permissions, retention requirements, and service providers are defined separately in a written agreement before customer data is connected.

Digital Offload LLC is based in Denver, Colorado. Questions and data requests can be sent to contact@digitaloffload.com.

On the production website, we record a limited set of operating events such as opening or starting the chat, choosing certain calls to action, following a demonstration link, and broad browser-error categories. Those records can include the public page path, referrer origin, timestamp, an event identifier, and a random browser-session identifier.

Digital Offload's first-party event logger keeps that identifier in session storage for the current browser tab. It normally survives reloads and same-tab navigation; a browser may also copy it when a tab is duplicated or restore it with a prior tab. An independently opened tab normally receives a different identifier. It is not an account, a verified person, or a durable device identifier. This first-party logger does not set a tracking cookie or use an advertising pixel. Browser-error reporting sends only a fixed error category—not the error message, stack, page URL, or rejected value.

Cloudflare separately hosts and protects the website. Production currently loads Cloudflare Web Analytics and Cloudflare bot-detection code, which can process request, network, browser, performance, and security signals under Cloudflare's service. Cloudflare's protection layer may set first-party security cookies such as cf_clearance after a challenge and, when the applicable bot-management feature is active, __cf_bm. These are separate from Digital Offload's first-party event logger. The preview application does not write Digital Offload's first-party analytics events; hosting and security infrastructure may still process requests and protective signals needed to serve the preview.

When you submit a message through the production website chat, the conversation is sent to Anthropic so its API can generate a response. Do not submit passwords, account numbers, government identifiers, health information, confidential customer records, or anything else you would not want processed by an outside AI provider.

After a successful reply, Digital Offload checks the newest visitor message for character patterns that look like an email address or United States phone number. If that newest message matches—even when the text was incidental rather than a request for follow-up—we retain a snapshot of the full conversation through that reply and may store the matched value with an AI-generated summary. A later message without a matching pattern does not create another snapshot merely because contact information remains in the conversation history; another later contact-bearing message can create a new snapshot. Providing contact information is optional; avoid email- or phone-shaped text if you do not want the conversation retained. The preview chat is isolated from production model and data services and does not send a conversation to Anthropic or create a lead record.

Anthropic states that standard commercial API inputs and outputs are not used for model training by default and are generally deleted from its systems within 30 days, subject to a different agreement, abuse-prevention needs, or legal requirements. Those are Anthropic's provider terms, not a promise about records Digital Offload stores. See Anthropic's current explanations of commercial-data training and retention.

• Operate, protect, troubleshoot, and improve the public website.
• Generate a requested chat response, detect text that matches contact patterns, and support follow-up when appropriate.
• Respond to email, booking, or other direct inquiries.
• Understand which public pages and demonstrations are useful without building an advertising profile.
• Review conversation quality, including bounded AI-assisted review, when a contact-linked conversation has been retained.

We use service providers only for the functions they perform for the website:

• Cloudflare hosts and protects the website, processes network and security signals, provides production Web Analytics and automated bot-detection functions, and may set first-party security cookies as described above.
• Anthropic processes production chat content and may assist with contact extraction or quality review.
• Supabase stores limited website telemetry and contact-linked conversation records.
• Google Workspace receives email sent to Digital Offload.
• Cal.com operates the external booking page when you choose to schedule.

We do not sell personal information or share it with advertisers. External booking pages and other linked services publish their own privacy terms, which apply after you leave this site.

Website telemetry and pattern-triggered conversation records do not currently have an automated deletion schedule. They may remain until Digital Offload deletes them manually. Short-lived technical records used for rate limiting expire automatically.

This is a current-state disclosure, not the desired end state. We are defining a formal retention schedule and will update this notice when it is implemented. You may ask us to delete information associated with your email address or phone number at any time.

You can use the public pages and demonstrations without giving Digital Offload your name, email address, or phone number.

• Do not include contact information, sensitive information, or incidental email- or phone-shaped text in the chat if you do not want a conversation snapshot retained.
• Close the browser tab or clear this site's session storage to end the current first-party analytics tab session, subject to any browser tab-restoration behavior.
• Email us to ask what contact-linked information we hold, request a correction, or request deletion.
• Use email instead of the chat if you prefer not to send a message to an AI provider.

We may need enough information to locate the relevant record and confirm that we are responding to the right person. We will explain if we cannot complete a request or must retain a record for a specific legal or security reason.

The website uses encrypted HTTPS connections and server-side provider credentials. Controls are route-specific: the production chat requires an approved website origin and JSON content type before model work; the first-party telemetry route rejects an unapproved origin when one is supplied; authenticated server routes use their own bearer or signature checks, allowlists, bounded bodies, and rate limits as applicable. Access to stored website records is limited operationally. No public statement on this site should be read as a claim that Digital Offload holds a security certification or that any system can be made risk-free.

The site is intended for business users and is not directed to children under 13. We do not knowingly collect personal information from children.

We will update the date at the top of this page when this notice changes materially. The current version will remain available at this URL.