Your information, handled deliberately.

Who is responsible

AGMM LTD, company number 16384156, is responsible for the information described here. Privacy questions and data requests can be sent to AGMM.ltd@gmail.com.

Website enquiries and bookings

If you contact AGMM or request a booking, we use the details you provide to respond, arrange the requested conversation and keep an appropriate business record. Depending on the route you choose, an authorised form, calendar, email, messaging or database provider may process that information for AGMM.

Guides and email updates

When you request a working file from an AGMM YouTube video, AGMM stores the email address you submit, the video and resource selected, the page or campaign source, the consent wording shown at the time, the request date and whether the delivery email succeeded. We use this information to deliver the requested file and send occasional practical emails about AI systems and AGMM services. The form states this exchange before you submit it. You can withdraw at any time by replying unsubscribe to any email. We do not sell or share this list with advertisers.

Website measurement

The main website records anonymous aggregate page loads without setting an analytics cookie or creating a visitor identifier. For each five-minute period, AGMM stores combined counts by page, campaign tags, referring website host, broad device category and country supplied by Cloudflare. The analytics database does not store an IP address, raw browser string or full referring URL for these counts.

The website asks before enabling detailed first-party analytics. The banner states the purpose in short; this section is the full description it links to. If accepted, a random visitor code and session code are stored in the browser so AGMM can measure journeys between pages, how far down a page is scrolled, active time on a page, which sections of a page come into view, which links and buttons are clicked, where on the page a click landed (recorded as a horizontal and vertical percentage of the page, never as a screen recording or a cursor trail), which stage of an enquiry or booking form was reached, whether a named field was completed, broad viewport size and page performance. Form progress records only the fixed option selected or the name of a completed field. It never records names, contact details or free-text field contents unless the form is deliberately submitted as an enquiry or booking. The visitor code persists in this browser across visits until the choice is withdrawn; the session code is discarded when the browser tab closes. No IP address is stored against these events, and nothing is shared with advertisers or any third-party analytics service. Aggregate counts and detailed website events are retained for 90 days.

Your choice is stored in this browser and you can change it at any time. Select Analytics choice at the foot of any page to bring the request back. Declining stops the measurement, and the visitor and session codes held in your browser are deleted.

The separate AI Bottleneck Blueprint campaign pages use their own measurement choice, described on the campaign analytics privacy page.

Meta ads measurement

The AI Decision Audit ads page uses one separate, versioned choice solely for Meta measurement. It never starts the site's detailed first-party visitor or session tracker. Anonymous server-side totals still count page requests and completed form stages without a visitor identifier, whether you allow Meta measurement or not. If you allow it, AGMM loads Meta Pixel and sends PageView, ViewContent and a diagnostic form-start event. A button press is not recorded as a lead.

Only after the booking service has confirmed a fit-call slot and the submitted fixed-choice answers meet the stated qualification rules does AGMM send a Lead event. The browser Pixel and server Conversions API use the same server-generated random event identifier so Meta can deduplicate them. The server event may include the Meta browser identifiers _fbp and _fbc, the canonical ads-page address, browser and network information supplied with the request, and one-way SHA-256 hashes of the submitted email and phone number. Campaign tags and fbclid remain in AGMM's booking record; they are not included in the CAPI page address. The raw booking details remain in AGMM's booking record and are not put in the Meta event.

AGMM uses this measurement to decide whether an advert produced a qualified fit-call booking and to improve campaign delivery. Declining does not prevent reading the page or booking. It prevents Pixel from loading and prevents a new booking from entering the Conversions API outbox. Selecting Analytics choice at the foot of the ads page lets you change that separate choice. Declining removes the Meta browser cookies AGMM can remove from this domain, records the random receipt as withdrawn, cancels queued delivery and removes queued browser and network identifiers. A delivery already in flight is marked for provider reconciliation because AGMM cannot truthfully claim it was not received.

The browser preference and signed HttpOnly receipt cookie expire after 180 days, when AGMM asks again. A minimal random revocation record is retained for no more than 180 days after withdrawal so an old receipt cannot be reused. If a consented booking was made, its business record keeps the random receipt identifier, disclosure version and acceptance time under the business-record retention described below. AGMM does not store the signed cookie value. Meta currently lists _fbp and _fbc with a 90-day lifespan in its Cookies Policy. Meta processes the data it receives under its own Privacy Policy and provides signed-in account controls for activity off Meta technologies.

TikTok connection

AGMM Auto-Poster uses TikTok Login Kit and the Content Posting API. When an authorised AGMM operator connects TikTok, TikTok supplies an account identifier, basic profile information, permission scopes and access credentials. The service uses these only to show the connected account, present TikTok’s current publishing choices and submit content that the operator has reviewed and approved.

Access and refresh credentials are encrypted and are not exposed to page scripts. The review interface does not sell TikTok data, use it for advertising profiles or share it with unrelated third parties. An operator can remove the connection in TikTok’s settings or ask AGMM to delete the associated session.

Retention and security

AGMM keeps business records only for as long as they are needed for the purpose collected, legal obligations, security and resolving disputes. TikTok browser sessions are short-lived. Production publication receipts retain the post identifier, destination, approved caption and media evidence needed to operate and audit AGMM’s own publishing system; they do not contain the access token.

Your rights

Depending on the circumstances, UK data-protection law may give you rights to access, correct, delete or restrict use of your personal information, object to certain processing, or receive a portable copy. You may also complain to the UK Information Commissioner’s Office. Contact AGMM first if you would like us to investigate or act on a request.

Updates

Last updated 21 August 2026. Material changes will be reflected on this page.