Loading…
Last updated: 11 June 2026
When you join Guild.cv we collect: your name, contact methods (email and/or phone, used for sign-in), professional details you choose to publish (current role, venue, city, work history, certifications, languages, specialties), and any external links you add (website, LinkedIn).
We also collect the IP address and user agent of inbound contact requests sent through the relay form, for abuse prevention only. We do not share this with the recipient.
Your profile at guild.cv/{slug} is publicly indexable by default. The fields shown there — name, current role, venue, city, bio, work history, certifications, accepted references, recent updates — are all visible to anyone.
Your sign-in contact methods (email, phone), pending reference requests, and contact-relay messages are not public. They're visible only to you (and, in the case of relay messages, to the recipient).
We don't store passwords. Sign-in is via one-time codes sent to your email or phone. Codes are stored hashed (sha256 with a secret pepper), expire in 10 minutes, and are single-use. We don't store the plaintext code.
When you request a reference, we email the colleague a token-bound link. They can accept or decline. Their email address is stored against the request so we can dedupe and resend; it's not shown on your profile.
Alongside member profiles, Guild publishes a curated graph of hospitality careers compiled from public sources — award lists, guides, press, and venue websites. These pages (at guild.cv/p/… and guild.cv/venues/…) show professional facts only: names, roles, venues, and years. We store no contact details for curated people, and the only way to reach anyone is our relay — which works only after they claim their profile.
If a curated page is about you, you can claim it (it becomes your member profile, under your control), correct it, or have it removed — use the request form on the page itself or write to privacy@guild.cv. Removal requests are honoured; we don't argue with people about their own careers.
Every entry in your work history has a visibility you control: public (on your public profile), members only (visible to signed-in verified members, never to the open web), or draft (only you). Public pages show at most a count of your member-only entries — never their contents.
Members can tag the people they worked with at a venue. A tag is a proposedconnection: it's visible to the two people involved and becomes verified only when the tagged person confirms. A connection appears publicly only when both sides allow it.
If a member invites someone not yet on Guild, we store the name and (optionally) email address the member typed, solely to deliver that one personal invite and link the connection if they join. Invitee details are visible only to the inviting member, are never published, and are never used for marketing. If someone invited you and you'd like that data removed, write to privacy@guild.cv.
When a coworker confirms you overlapped, your work-history entry can show a “Verified overlap” badge. The badge never names who confirmed it. A coworker may also leave you a recommendation after confirming — it stays hidden until you choose to publish it, and their sign-in email is never attached to it. “Did you work with…” suggestions are computed from your own venue history against the public graph; dismissing one is permanent and stored.
You can export, edit, or delete your profile at any time from Settings → Account. Deleting your profile removes your public page, your work history and certifications, and anonymises (rather than deletes) the references you've received — your colleagues' words don't disappear, but they're no longer attached to you.
We host on Supabase + Vercel in ap-southeast-2 (Sydney). Email is delivered via Resend; SMS via Twilio. We don't sell or share your data with anyone else.
Questions about this policy: privacy@guild.cv.