Privacy policy
What HAL AI LLC collects on this website and in the Hal service, what it is used for, who processes it, and how to reach us about it.
Effective 4 October 2026. This policy covers the website at runhal.com and the Hal service that HAL AI LLC (“we”) provides to managed service providers (“customers”). Where it says what we do with data, it describes practice, not aspiration; if practice changes, this page changes with it and the date above moves.
This website
The contact form. If you use it, we receive what you type: name, work email, phone, company and message. It is delivered to our mailbox by SMTP2GO, an email relay acting on our behalf. We use it to reply to you about Hal and for nothing else.
No analytics, no tracking. This site runs no analytics, sets no cookies of its own, loads no third-party scripts, and serves its fonts itself. We don’t know who you are when you read it.
The edge. The site is delivered through Cloudflare, which processes the technical data any web request carries (IP address, browser, pages requested) to serve the site, keep it running and protect it from abuse, under Cloudflare’s own terms and retention.
Verifying a report. The verify page checks a PDF’s signature inside your browser. The file never leaves your device. The page makes one network request: a DNS lookup, through Cloudflare’s public resolver, for the record that publishes our signing key.
The Hal service
Portal sign-in. Customer portals sit behind Cloudflare Access. When you sign in, your sign-in identity (your email address, and your name if you sign in with Google) and sign-in events are processed by Cloudflare as our sub-processor, and the portal records who created each note, tag, watch and chat thread. Your administrator can additionally turn on per-user logging of portal visits and chat text; it is off by default.
Customer telemetry. Hal reads the security and activity logs of the tenants a customer connects: Microsoft 365, Google Workspace, Entra ID, endpoints, network devices and the other sources described in our documentation. Those logs contain personal data about the customer’s staff and its own clients’ personnel. We process that data only as a service provider, on the customer’s instructions, to deliver the service the customer has contracted for. Specifically:
- It is not sold, and not shared except with the sub-processors listed below, each acting on our behalf; with Anthropic for Hal’s analysis, under the customer’s own account; with the services the customer connects; as the law compels; or at the customer’s instruction.
- It is never used to train AI models by us. Hal’s analysis runs on the customer’s own Anthropic account, whose commercial terms prohibit Anthropic from training on API inputs and outputs.
- It is stored at rest only in the United States.
- On the customer’s instance it is retained for 365 to approximately 395 days and then deleted, and the instance and the data on it are deleted at the end of the customer’s agreement, its backups within 90 days of it. Our operational records, what each instance reports to us about its operation and the records of our own work on the service, may keep excerpts of it for as long as we need them to run, support, secure and improve the service.
The people who appear in those logs, the customer’s staff and its clients' employees, are not our customers. Requests about data held about them go to the MSP whose tenant it is.
Google Workspace data
Where a customer connects a Google Workspace tenant, Hal reads that tenant
through Google APIs, over an authorization granted by the tenant’s own
administrator. Every scope is read-only except apps.alerts, the Alert
Center’s only scope, which Google offers in a form that can also change
alerts; Hal only reads with it. The scopes, and what each is for:
| Scope | What Hal uses it for |
|---|---|
admin.reports.audit.readonly | Audit-log events (sign-ins, sharing, admin changes), the primary signal Hal triages |
apps.alerts | Google’s own Alert Center security flags, correlated with the audit events |
admin.directory.customer.readonly | The Workspace customer ID, to route events to the right organization |
admin.directory.user.readonly | Listing users to count billable identities once a day (not suspended, not archived) and to confirm access at onboarding |
admin.directory.group.readonly | Grants read access to your Workspace’s groups and their members |
admin.directory.domain.readonly | Your Workspace’s verified domains, so Hal knows which of your addresses are yours |
Hal never writes to a Workspace. Google user data is used only to provide and improve the security-monitoring features the customer has connected it for. It is not used for advertising, is not sold, and is not transferred to anyone except the sub-processors below as necessary to provide the service, to comply with law, or to address security. HAL AI LLC’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
AI processing
Hal’s analysis runs on Claude models from Anthropic under the customer’s own Anthropic account and API key: the customer holds that relationship and its terms directly, and those terms prohibit Anthropic from training on what is sent through the API.
Sub-processors
| Provider | Role |
|---|---|
| Cloud infrastructure provider (United States) | Hosting of each customer’s Hal instance and its storage. Its role and United States location are the contractual commitment; the provider is identified to customers on request under the service agreement’s confidentiality terms |
| Amazon Web Services (S3) | Encrypted backups |
| Cloudflare | Edge delivery and security for this site; Cloudflare Access sign-in for portals |
| SMTP2GO | Email relay, for the contact form and for the service’s own notifications |
| Anthropic | AI processing for HAL AI’s own reviews of the service’s detection rules, under HAL AI’s own account: the excerpts of customer telemetry those reviews quote. Stored in the United States; inference routed as Anthropic publishes. The service’s own analysis runs under the customer’s own Anthropic account instead (AI processing, above) |
Children
Neither this website nor the Hal service is directed at children, and we do not knowingly collect personal data from them.
Changes
We post changes here and update the effective date at the top. Material changes to how the service handles customer data are also communicated to customers directly.
Contact
HAL AI LLC, Atlanta, GA. For anything about this policy or your data, write to info@runhal.com. Other ways to reach us are on the contact page.
See what Hal surfaces on your own clients.
No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.
- 01You ask us your questions. No deck, no demo dataset.
- 02You sign a short evaluation agreement, and we stand up your own instance.
- 03You connect one tenant from your own admin console. Hal watches it for 14 days.
- 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.