Operational review 14 September 2026

Website privacy notice

This notice covers the Halo AI Services marketing website, aggregate measurement, enquiries and AI-assisted handling of requested work. The separate pages at /privacy/, /terms/ and /support/ are product-specific notices for Snag Pro. This operational notice is not a substitute for professional legal advice.

Who is responsible

David Shelley, operating under the Halo AI Services name in the Isle of Man, is responsible for the personal information described here. Contact hello@haloaiservices.com for privacy questions, rights requests or a postal contact.

What a brief contains

When you submit an opportunity audit or project brief, Halo stores the fields you enter: your name, email address, optional business and website, the selected service, your project context and, for a project brief, optional timing and budget range. The server also stores a random receipt identifier and idempotency key, submission time, scheduled deletion date, source page, environment, notification state, notification attempt timestamps and the provider message identifier when email notification succeeds. Structured operational logs may include a receipt identifier and status code, but not the form fields. It does not store your Turnstile token or raw IP address in the lead database.

If secure submission fails, the form remains on your device. You can choose to copy the brief or email it with your own provider. Do not submit passwords, customer records, health information or private account access.

Security and aggregate measurement

Cloudflare hosts and protects the site, validates the Turnstile security check and may process standard request, device, network and security information in its infrastructure. After Turnstile validates a submission and before it is stored, the submission route derives a keyed pseudonymous value from the Cloudflare-provided connecting address in memory and routes only that value to a private rate gate for a short-window abuse decision. Depending on the deployed gate, Cloudflare may maintain provider-managed counter state or a serialized security object with no more than ten active attempt timestamps. Provider caches, delayed alarms, automatic retries and recovery retention can outlast the active decision window. The Halo application does not write the address or derived value to the lead database or its structured logs. Cloudflare may also provide aggregate site-use and real-user performance signals through Web Analytics. Whether its beacon is injected depends on the visitor's region and the current Cloudflare account configuration; Halo does not add advertising profiles, cross-site marketing pixels or client-side form-event tracking.

After a new production brief passes Turnstile and is stored, the server writes one lead_submission count to an isolated Analytics Engine dataset. That point contains the brief type and fixed source page, but no receipt, name, email, message, IP address, cookie, user ID or session ID. It is separate from the lead database. Halo does not upload scorecard answers or results, and does not count client-declared form starts, errors, copies or email fallbacks as conversions.

Why information is used

Brief information is used to respond, assess a requested project, prepare or take steps towards an agreement, deliver requested work, maintain appropriate business records, protect the service and resolve disputes. The applicable basis depends on the context and may include steps requested before a contract, performance of a contract, legal obligations or legitimate interests in running and securing the business.

AI-assisted handling and replies

Halo uses AI-assisted tools, including OpenAI’s Codex, to process relevant brief and email content, research the requested problem, prepare replies, and produce and check requested work. Replies and routine work may be produced without a person reviewing every message. David Shelley remains responsible for the service. AI output can contain mistakes: reply with the receipt and ask David to review a concern or correct an answer.

A submitted brief is not a purchase and does not authorize changes to your live systems. Implementation needs agreed scope and authorized access. This enquiry service does not decide credit, employment or access to essential services. If your work has confidentiality, residency or other data restrictions, describe the restriction before sharing the affected material.

Halo also keeps private work records on its operator-controlled systems: receipt and source references, progress, checks, deliverables and delivery evidence. The queue stores references and status rather than full briefs; necessary working files are stored separately from the public website. These records help resume interrupted work and prevent duplicate replies.

Sharing and international processing

• Cloudflare provides hosting, security, form storage, aggregate measurement and notification delivery. The automated alert to a Google-hosted owner mailbox contains only the receipt, submission time, brief type and selected service, not the full brief.
• For the requested response or work, relevant brief and correspondence content is processed using OpenAI’s Codex and Google email. This is separate from the minimal owner alert. Your chosen email provider processes messages you send.
• Linear tracks receipt identifiers, work categories and non-sensitive progress. Obsidian and its storage/sync services keep corresponding operational notes. Full briefs, customer email addresses, payment records and deliverables do not belong in those shared project notes.
• Necessary information may also be shared with professional advisers or providers required for an agreed project. Additional customer-system or sensitive-data processing must be scoped before access.

Providers and their supporting services may process information outside the Isle of Man. Storage, retention and processing locations depend on the service and account arrangements; this notice does not promise that all copies stay in one country. Ask about a specific restriction before sending confidential material. External links have their own privacy practices.

Retention

Each website lead record is scheduled for automatic deletion 12 months after submission. A provider outage can delay a scheduled cleanup; failed scheduled runs are logged and cleanup retries on the next five-minute schedule. That database cleanup does not automatically delete related email, AI conversations, private work records or backups. Derived work records are reviewed against the same 12-month timeframe rather than covered by the database timer.

If an enquiry becomes an active project, information necessary for delivery, legal, accounting or dispute purposes may be retained for longer under those duties. Provider-managed copies and backups have separate retention arrangements. Aggregate measurement points do not contain a lead identifier. Quote your on-page receipt when asking Halo to locate, review or delete a brief and its related records.

Your rights

Depending on the circumstances, you may have rights to access, correct, erase or restrict personal information, object to some uses, or ask for a portable copy. You can also raise a concern with the Isle of Man Information Commissioner.

Cookies and changes

Halo does not intentionally set advertising or non-essential analytics cookies. This notice will be updated when the site’s data practices, retention or service providers materially change.

Contact

Email hello@haloaiservices.com and include the receipt if your request concerns a submitted brief.