Cowrie Research

guild-company-primary-sources-2026-08-12

4 min read

Guild.xyz company primary-source snapshot

Fetched: 2026-08-12 UTC

1) Main site / positioning

Source: https://guild.xyz/

Selected excerpts from the official site:

One platform with 100+ integrations.

Automated and engineered to scale from 100 to 1 million members.

Additional signals from the homepage:

  • Guild markets a hosted operator stack, not only a rules engine.
  • The public positioning is about scaling communities, integrations, and workflow packaging rather than about a neutral protocol primitive.

2) Docs overview

Source: https://docs.guild.xyz/guild

Selected excerpts from the official docs:

Guild is a tool that helps you grow and reward the right community members by tracking onchain and social activity.

It manages access to Discord and Telegram, runs quests, and provides analytics to help you better understand your community.

You see your members’ wallet address(es) and their linked social accounts in one place.

Additional signals from the source:

  • The docs make the hosted identity and profile layer explicit.
  • Guild is packaging access control, quests, analytics, and linked-identity visibility into one operator shell.

3) Terms of Use / named service provider

Source: https://guild.xyz/terms-of-use

Selected excerpts from the terms:

The Services are provided by Z Gen Kibernetika Korlátolt Felelősségű Társaság …

Guild creator onboarding may require a Google account or verified email address for creator contact and service updates.

The Service Provider may update the Services or modify features and functionality from time to time.

Additional signals from the source:

  • This is strong evidence that the practical dependency is on a named hosted service provider, not only on wallet-based role checks.
  • The company controls onboarding requirements, feature changes, and the legal shell around the product.

4) Privacy Policy / data and subprocessor shell

Source: https://guild.xyz/privacy-policy

Selected excerpts from the policy:

This notice applies to the data processing of Z Gen Kibernetika Korlátolt Felelősségű Társaság … in relation to our Services and our Website available at https://guild.xyz/.

When you create your profile, we will request certain information about you through the identity you choose to connect, such as your Google account email and profile information, an email address verified by one-time code, a social media ID, or a public wallet address.

If you join a Guild, the Administrators of the relevant Guild may get access to your personal data in the course of the management of their Guild.

Additional signals from the source:

  • Guild is clearly operating a profile and member-data layer above the role logic.
  • The privacy page also names concrete third-party providers including Railway, Cloudflare, Sentry, PostHog, Intercom, Resend, Alchemy, Pinata, Stripe, and Coinbase.
  • That makes the company boundary analytically useful: the hosted membership system is partly vendor-composed and policy-mediated.

5) Docs index / breadth of managed workflow

Source: https://docs.guild.xyz/guild/llms.txt

Selected signals from the docs index:

  • The documented surface spans custom API calls, EAS, email, Discord, Telegram, Farcaster, GitHub, points, NFT rewards, secrets, and a developer API for automating token-gated access.
  • This confirms that Guild is not only a token-gated Discord helper. It is a broad cross-platform policy and reward shell.

6) SDK README / admin control plane

Source: https://raw.githubusercontent.com/guildxyz/guild-sdk/main/README.md

Selected excerpts from the SDK materials:

The Guild SDK library is a Typescript library for interacting with the Guild API.

manage your Guilds easily and automate token-gated access in any application with this SDK.

Additional signals from the source:

  • The README documents clients for guilds, admins, roles, requirements, rewards, users, addresses, and linked platforms.
  • The SDK exposes create, update, delete, join, access-check, leaderboard, and reward-management flows, which is strong evidence that Guild.xyz runs a real admin and member-management control plane.

Notes

  • Guild clears the bar for a separate company/entity note because the hosted profile graph, supported integrations, admin tooling, data-sharing shell, and legal/policy layer all sit with a named operator.
  • The project note should stay on the rules engine and community-policy mechanics. The company note should stay on the hosted identity, data, admin, and integration boundary around that engine.

Graph View