Privacy policy
Last updated: October 6, 2026
This policy explains what FortHire collects when you use forthire.com, why, who helps us process it, and how to reach us. FortHire is run by the FortHire team. Questions go to support@forthire.com.
The short version
- You can search and read every public listing without an account. We set no cookies.
- Some preferences live only in your own browser (your saved searches and saved jobs, which job pages you viewed, and your Pro key if you activate one).
- If you buy anything from us, our payment processor, Stripe, handles the payment. Earlier Pro purchases were made through Gumroad. We never see your card details.
- We don't sell your personal information, and we don't use advertising trackers.
Information stored in your browser
FortHire uses your browser's local storage. These entries stay on your device. They are sent to us only in the cases described below.
| Entry | What it holds | Why |
|---|---|---|
ciphire:pro | Your Pro license key or sign-in link token, your plan, when it was last checked, and any end date | Keeps Pro active on this device |
ciphire:saved | Your saved searches (up to 20) | Lets you rerun saved searches |
ciphire:lastVisit, ciphire:prevVisit | Two timestamps | Marks listings that are new since your last visit |
ciphire:savedJobs | The IDs of jobs you saved (up to 500) | Shows your saved jobs on the Saved jobs page |
ciphire:seenJobs | The IDs of job pages you opened (up to 5,000) | Dims jobs you already viewed in lists |
ciphire:moved (session storage) | A one-time flag | Used once when moving settings from our old address (ciphire.pages.dev); cleared when you close the tab |
ciphire:grplan, ciphire:purchase, ciphire:grmsgs (session storage) | The plan you picked at checkout and whether a purchase just finished | Helps you activate Pro after buying; cleared when you close the tab |
You can remove all of these at any time by clearing site data for forthire.com in your browser, or by choosing "Sign out" on the Pro page.
Information we receive and why
When you browse. Our site is delivered by Cloudflare. Like any web host, Cloudflare processes your IP address and basic request details (such as the page requested and your browser type) to deliver pages and protect the site from abuse. To stop abuse, our API and contact form count requests per visitor. The counters are filed under a one-way code made from your IP address with a secret key that changes every day, never the address itself, and are deleted within 2 days. Server logs are kept for up to 30 days.
Error reports. If a script on our pages fails in your browser, it sends us a short error report: the error message, the script and line, and the page path (without any query string). It contains no personal details. To stop floods of reports we count them per visitor using a one-way code made from your IP address that changes every day; we never store the address itself, and the counts are deleted after a day. We keep error reports for up to 30 days.
When you activate Pro. Your license key is sent to our API. A key from a Stripe purchase is checked against our own record of that purchase. A key from a Gumroad purchase is checked with Gumroad, which returns your plan, its status and the email used for the purchase; we keep the result of that check for up to 8 days, filed under a scrambled (hashed) version of your key, so we don't have to ask Gumroad every time. For both kinds of key we keep a one-way hash of your purchase email so we can send a sign-in link to that address if you ask for one later.
When you save a Pro profile, alerts or webhooks. We store these on our servers so daily alerts can work when your browser is closed:
- your profile (target roles, seniority, minimum salary, location and remote preference, certifications, clearance level, visa needs, preferred frameworks);
- your saved searches;
- your license key, so the daily job can confirm your membership is still active;
- for Slack or Discord alerts, the webhook URL you provide and the saved search it uses. We post only job listings to that webhook.
Email alerts and sign-in links. If you ask for email alerts, we store your email address, a record that you confirmed it (the time, and the IP address used at confirmation), when we sent messages, and an unsubscribe token. Alerts use double opt-in, and every message has a one-click unsubscribe link. A sign-in link you request works for 30 days. If an address bounces or reports spam, we keep a hashed copy of it on a suppression list so we don't email it again.
When you contact us. If you use the contact form or email support@forthire.com, we receive your email address, your message, the topic, any job or company you mention and, for Pro help, the last four characters of your key (never send the whole key). Contact-form messages and emails are stored as support tickets. We use them only to answer you and to handle removal requests, and keep them for 24 months.
Payments. New Pro purchases go through Stripe, our payment processor. Stripe runs the checkout page, holds your card details and runs the billing page where you cancel, update your card or download invoices, under its own privacy policy. When you buy, Stripe sends us your purchase email, your name, the plan, the amount and Stripe's reference numbers for the purchase, and later tells us when your subscription renews, changes, ends or is refunded. We use that to create your license key and email it to you. We keep a record of the purchase (plan, status, Stripe's reference numbers and a one-way hash of your purchase email, not your name) for up to 400 days after its last change, and the page you return to after checkout can show your key for 7 days. If you subscribe to Security Hiring Signals, we also keep your purchase email, plan and subscription status so we can send you the report. Pro bought earlier through Gumroad stays with Gumroad, which is the merchant of record for those purchases and handles their checkout, billing, taxes, receipts and refunds under its own privacy policy. For those, we receive your purchase email, plan and subscription status, and the license key. We never receive your card number.
Purchases (Featured roles, Employer Pro, Security Hiring Signals and our browser tools). Stripe handles the payment and holds your card or bank details; we never see them. From each purchase we store your email address, the company name you enter (Employer Pro), the job posting URL you enter (Featured roles), the license or member key we issue, and the Stripe ids for the checkout, customer, subscription, invoice and payment, so we can deliver what you bought, handle cancellations and refunds, and answer support requests.
Job listings. Listings are copied from employers' public job postings on their applicant tracking systems. A posting can include the name or contact details of a recruiter or hiring manager if the employer published them. If you're named in a listing and want it removed, email support@forthire.com.
Why we use it (legal bases, for visitors in the EU, UK and similar regions)
- To provide the service you asked for (contract): Pro activation, profiles, alerts, webhooks, sign-in links, support.
- Legitimate interests: keeping the site secure and available, preventing abuse, publishing employers' public job postings, and understanding site usage in aggregate.
- Consent: email alerts. You can withdraw consent at any time with the unsubscribe link.
- Legal obligations: records that we or our payment provider must keep.
Who we share it with
We use these service providers. They process data for us under their own terms:
| Provider | Role |
|---|---|
| Cloudflare | Hosting, serverless functions, data storage (KV), email routing for support@forthire.com, message queue |
| Stripe | Payment processor for new purchases: checkout, card details, billing page, invoices. Acts as a separate controller for payment data |
| Gumroad | Merchant of record for Pro purchases made through Gumroad before the move to Stripe. Acts as a separate controller for payment and tax data |
| Resend | Sends our emails (confirmation, sign-in links, alerts, support replies) |
| Slack or Discord | Only if you add a webhook. You choose the destination |
We don't sell or share personal information for cross-context behavioral advertising, as those terms are defined in California law. We may disclose information if the law requires it, or to protect the service and its users.
International transfers
Our providers are based in, or process data in, the United States and other countries. Where the law requires it, we rely on the providers' transfer safeguards (such as Standard Contractual Clauses or the EU-US Data Privacy Framework).
How long we keep it
| Data | Kept for |
|---|---|
| Browser storage | Until you clear it or sign out |
| License-check cache | Up to 8 days |
| Pro profile, saved searches, alert settings, webhooks | Until your membership is cancelled plus 30 days, or sooner if you ask |
| Hashed purchase-email pointer | Until your membership is cancelled plus 30 days, or sooner if you ask |
| Email suppression list (hashed) | As long as we send email, so we never mail a bounced or complaining address again |
| Support messages (contact form and email) | 24 months |
| Server logs and error reports | Up to 30 days |
| Our record of a Stripe purchase | Up to 400 days after its last change |
| Payment records | Held by Stripe or Gumroad under their own policies |
Your choices and rights
- Delete your Pro profile and email settings: use "Delete my profile" on the Pro page. To remove a webhook, choose Remove next to it.
- Stop emails: use the unsubscribe link in any email.
- Access, correction, deletion, portability, objection: email support@forthire.com. To protect your account, we'll ask for the last four characters of your license key or for a message from your purchase email. We aim to reply within 30 days. Residents of some US states and of the EU and UK have these rights by law. We offer them to everyone.
- You can also complain to your local data protection authority.
Children
FortHire is meant for people looking for work and isn't directed at children. Don't use it if you're under 16.
Security
Data travels over HTTPS. License keys and private feed links act like passwords, so keep them to yourself. Server-side, we store keys and email addresses in hashed form where the feature allows it. We limit request rates on our API.
Changes
If we change this policy, we'll update the date at the top. If a change is significant, we'll note it on the site.
Contact
The FortHire team, support@forthire.com