Privacy

Get a Job is a guild fan site. The leveling guide keeps your progress in your own browser; the name vote sends what you pitch and how you vote to our server; the apply form sends your raid application to the guild's officers; tooltips go to Wowhead. Here is the whole map.

Effective 2026-06-03

What we store about you

The hub and the leveling guide are static pages: no account, no signup, no analytics, no advertising, no tracking pixels, and nothing about you kept on our server. Two tools are the exceptions: the guild-name vote keeps the names and votes people submit, and the raid application keeps what you send so the officers can read it. Each gets its own section below.

The leveling guide and your browser

The TBC leveling guide remembers which steps, keys, and rep goals you have checked off using localStorage in your browser, under the key tbcGuide.progress.v1. That data:

• never leaves your device and is never sent to us or anyone else;
• is specific to that one browser on that one device — it does not sync;
• can be wiped any time with the Reset progress button on the guide, or by clearing site data for this domain.

Wowhead tooltips (third party)

The leveling guide links every in-game item, quest, NPC, zone, and faction to Wowhead and shows a tooltip when you hover. To do that, the page loads Wowhead's tooltip widget and fetches each entity's data from Wowhead's servers (wow.zamimg.com, nether.wowhead.com, wowhead.com). As a result, Wowhead receives your IP address and which entities you hover or click, the same as if you visited Wowhead directly. Their handling of that is covered by Wowhead's privacy policy, not ours. Clicking a link opens Wowhead in a new tab.

Fonts (third party)

The guide's heading font (Cinzel) loads from Google Fonts (fonts.googleapis.com, fonts.gstatic.com), so Google receives your IP address for that request. No cookies are set by it.

Cookies

Get a Job sets no cookies of its own and registers no service worker.

Server logs

Our web server keeps standard access logs (IP address, user agent, request path, status code) for a limited time, for debugging and abuse prevention. They are not used to profile you or shared with anyone.

Cloudflare (network delivery)

Get a Job is served through Cloudflare, so every request to the site passes through Cloudflare's network before it reaches our server. Cloudflare therefore sees the same connection details our access logs do — your IP address, user agent, and the path you requested — and handles them under its own privacy policy. This is delivery infrastructure: it keeps the site up and absorbs attacks, and we do not get a per-visitor report out of it. The bot check on the vote and apply forms (below) is a separate Cloudflare feature that only runs when you submit.

The guild-name vote

Voting is shared, so unlike the guide it has to keep some data on our own server (a small SQLite database). Here is everything it stores:

• the guild names people pitch, and the optional one-line reason attached to each;
• each vote: which name it is on, whether it is up or down, and when it was cast or last changed;
• an anonymous browser id that ties your own votes together so each name gets one effective vote from you.

The anonymous browser id

The first time you open the vote page, your browser makes up a random id and saves it in localStorage under guildVote.voterId.v1. It rides along with each name you submit and each vote you cast, and it is the only thing connecting your votes to each other. It is not an account, it is not linked to your name or email, and it says nothing about who you are. Clear your site data for this domain and it is gone — you get a fresh id, and your earlier votes are no longer tied to you.

Your IP address

When you submit a name or cast a vote, our server reads your IP address to rate-limit the request — that is what stops one source from flooding the ballot with submissions or spamming votes. This use is transient: the IP is not written into the voting database next to your votes. (Our general web-server access logs still record IPs the same way they do for any page, as described above.)

Bot check on submissions (Cloudflare Turnstile)

To keep bots from stuffing the ballot, submitting a name runs a Cloudflare Turnstile check. Your browser loads a small widget from Cloudflare and gets a one-time token, and our server hands that token back to Cloudflare to confirm before it stores the name. Cloudflare therefore receives your IP address and the token for that check; what it does with them is covered by Cloudflare's privacy policy, not ours. The token is single-use and we do not store it. Voting up or down does not trigger a check.

How long it is kept, and how ballot-stuffing is handled

Names and votes stay as long as the tool is running; it is a live tally, so there is no automatic expiry. One effective vote per name per browser is enforced through that anonymous id: switching your vote or clearing it just updates the same record, and duplicate names are merged so the same idea cannot appear twice. None of this is airtight — someone determined can wipe their browser storage or hop networks and vote again. It is a guild-name vote, not an election, and the defenses are sized to match.

The names and votes are never sold, shared, or used to profile anyone. They exist to pick a guild name, and that is the end of it.

The site owner can remove any submitted name (and the votes attached to it) — for example to take down something abusive. There is no public delete; it is owner-only.

The raid application

If you fill out the apply form, you are choosing to send us real details about yourself so we can consider you for the raid team. Unlike the rest of the site, this is identifying information you hand over on purpose, so here is exactly where it goes.

What you send us

• your character name, Discord username, and class;
• your raiding experience and why you want to join, in your own words;
• an optional logs link, if you add one;
• the two acknowledgements you check off — that you bring full consumables and gemmed/enchanted gear, and that you'll reach out on Discord — recorded as yes/no.

Where it goes

The moment you submit, your application is:

• saved in our database so we can review it and get back to you;
• posted to a private channel in our Discord server, where the guild's officers read it;
• emailed to the officers who handle recruiting.

Two outside services see your application so they can deliver it: Discord carries the channel post, and our email provider Resend sends the email. Each handles it under its own privacy policy. We do not post your application anywhere public, sell it, or use it for anything but recruiting.

Bot check and your IP address

Same as the vote: submitting runs a Cloudflare Turnstile check (your browser gets a one-time token from Cloudflare, our server confirms it), and our server reads your IP address to rate-limit submissions. That use is transient — the IP is not stored next to your application, though the general access logs record it like any page request.

How long we keep it, and removing it

Applications stay until we have dealt with them; there is no automatic expiry. The site owner can delete any application. If you want yours gone, before or after we review it, email the address below with your character name and we will take it out.

Your rights

The guide holds no personal data about you on our side. The vote keeps an anonymous browser id and the votes tied to it; because that id is random and not linked to your identity, we generally cannot connect it to a specific person on our own. If you are in the EU, UK, or California and want a name you pitched or the votes from your browser removed, email the address below and bring your browser id (it is in localStorage under guildVote.voterId.v1), and we will delete the records tied to it. If you sent in a raid application, email us your character name and we will remove it.

Contact

Privacy questions, data requests, or anything else: [email protected].

Changes to this policy

If we change how Get a Job handles data — a new tool, or a new place something gets sent — this page updates and the effective date moves forward. The full history is visible in the project's public Git repository.