A small data footprint, explained plainly.

Privacy at a glance

• No site analytics. AgentGuild does not currently run an analytics service on this website.
• No site cookies. The AgentGuild website does not currently set analytics, advertising, or preference cookies.
• No card data. Checkout and payment information are handled by Polar, not collected through an AgentGuild payment form.
• GitHub access is the entitlement. Polar’s GitHub Repository Access benefit connects the purchase to repository access.

Website data

The public website does not provide an AgentGuild account, newsletter form, behavioural analytics, or advertising tracker. It does not currently set its own cookies.

Ordinary hosting and network infrastructure may necessarily process technical request information—such as an IP address, browser or user-agent details, requested URL, and timestamp—to deliver the site, diagnose failures, and protect it from abuse. The exact infrastructure and its operational retention settings must be reviewed as part of the production-hosting launch.

Embedded gameplay clips are served as local site files. The site does not embed a third-party video player for those clips.

Checkout and repository access

If checkout opens, Polar will process the checkout, payment, order, tax, and customer information needed for the transaction. Polar’s own privacy terms apply to that processing. AgentGuild does not receive or store full payment-card details through this website.

To receive the product, a buyer connects a GitHub account through Polar’s GitHub Repository Access benefit. Polar and GitHub process the account and access information needed to grant or revoke read access to the private Games Kit repository. Their respective privacy terms also apply.

Signed Polar webhook records

The AgentGuild webhook accepts signed Polar fulfilment events. Its current audit log records the event type, a Polar resource identifier, relevant product or benefit identifiers, and a receipt timestamp. It is deliberately not designed to log customer names, email addresses, checkout secrets, or payment details.

Support messages

If you contact support, AgentGuild will process the information you choose to send so the request can be understood and answered. For an access problem, that may include your purchase email, GitHub username, order identifier, and a redacted error message.

Never send a password, personal access token, OAuth token, recovery code, payment-card number, or unredacted credential output. AgentGuild does not need those secrets to investigate a purchase or repository-access issue.

How information is used and shared

Information described above may be used to:

• deliver and administer the purchased repository entitlement;
• answer support, refund, and access requests;
• diagnose reliability or security problems;
• prevent misuse and protect AgentGuild, buyers, and service providers; and
• meet tax, accounting, legal, or regulatory duties that apply.

Information is shared only as needed with checkout, repository, hosting, and infrastructure providers, professional advisers, or authorities where required by applicable law. AgentGuild does not currently sell personal information or use it for behavioural advertising.

Retention, security, and your rights

Operational records and support messages are retained only for as long as reasonably needed for fulfilment, troubleshooting, security, accounting, disputes, and applicable legal obligations. Final retention periods must be confirmed with the production hosting and commerce configuration before launch.

Reasonable safeguards are used, including signed webhook validation and avoiding payment or credential secrets in application logs. No internet transmission or storage system can be guaranteed completely secure.

Depending on where you live, applicable law may give you rights to request access, correction, deletion, restriction, or a copy of personal information, or to object or complain to a regulator. Those rights are not limited by this notice. A request may require reasonable identity verification.

Changes and privacy contact

This notice may be updated when the production host, checkout, support process, or legal requirements change. The effective date will change when a material revision is published.