Legal

Privacy notice

Hireek holds the records a hiring marketplace cannot work without — your profile, what you applied to, what you were paid — and nothing beyond them. There is no advertising, no data sale and no analytics script. This page lists what is stored, who can read it, how long it stays and how to get it back.

In effect since January 12, 2026

What we store

Written against the actual tables rather than in categories, because the categories are where these documents usually stop being useful.

Account: Name, email address, password hash or the identifier from the Google or GitHub account you signed in with, your avatar, and the sessions currently signed in.
Talent profile: Headline, biography, city and country, seniority, hourly rate, job-search status, freelance availability, skills with levels, languages, work history, education, certifications and portfolio items. Everything here is optional, and the profile can be set to private.
Employment activity: Applications with their cover letters and screening answers, the pipeline stage each is at and every stage change, interview times and participants, scorecard ratings, and offers with their terms.
Freelance activity: Proposals with their rates and milestone plans, contracts, milestones, time logs, invoices, disputes and reviews.
Money: Payment records, their purpose and status, subscription state, credit wallet balances and every credit transaction. Card numbers never touch our servers — Stripe holds those and returns an identifier.
Communication: Conversations and messages between you and the other party, notifications, and your notification preferences.
Files: CVs, portfolio images, contract deliverables and company logos, with the kind, size and content type recorded alongside them.
Operations: An audit log of consequential actions — money released, roles changed, listings published, accounts suspended — with the actor, the target record and a timestamp.

Who can see what

Visibility is enforced per query, not by hiding controls in the interface. Every read is scoped to the account making it or to an organization that account belongs to.

Anyone, signed out: A public talent profile and the parts you marked public; live jobs and open projects; published company profiles; reviews attached to completed contracts.
An organization you applied to: Your application, your screening answers, the attachments you sent, your profile as it stood, and your position in their pipeline. Only members whose role includes that capability — not everyone in the workspace.
A client you contracted with: The proposal you sent, the contract, its milestones and time logs, the files you delivered, and the messages in that thread.
Other organizations: Nothing. An application to one company is never visible to another, and no employer can see where else you applied.
Hireek staff: Administrators and moderators can open a record when a report, a dispute or a support thread requires it. Those views are written to the audit log with the staff member named.

Setting a talent profile to private removes it from search and from the public directory. It does not retract applications you already sent — the organization that received one keeps its copy.

Why we hold each thing

To run what you asked for: A profile has to be stored to be searched; an application has to be stored to be reviewed; a contract has to be stored to be paid. This is the bulk of it.
To take payment: Subscriptions, listings, credit packs and escrowed milestones require a record of what was charged, to whom, and what was released.
To keep the marketplace honest: Reports, disputes, moderation decisions and the audit log exist so that a claim about what happened can be checked against what actually happened.
To tell you things: Notifications about your own records, and job alerts from searches you saved. Alert frequency is yours to set, and every category can be turned off in notification preferences.

Who else is involved

Four processors, each doing one job. None of them is sold anything, and none of them receives data for their own purposes.

Stripe: Card processing, subscriptions and escrow movements. Stripe holds the payment instrument; we hold its identifier and the outcome.
UploadThing: File storage for CVs, portfolio images, logos and deliverables.
Google and GitHub: Only if you choose to sign in with one. They confirm the account and return a name, an email address and an avatar.
Resend: Transactional email — sign-in links, offer notifications, alert digests. Your address is passed at the moment of sending and not retained for marketing.

We do not sell personal data, we do not run advertising trackers, and there is no third-party analytics script on any page of this site.

How long it is kept

While your account is open: Your profile, your saved searches, your saved items and your notification preferences stay until you change or remove them.
Applications and proposals: Kept for as long as the organization keeps the listing, then for twenty-four months after the listing closes so that a hiring decision can still be explained.
Contracts, invoices and payments: Kept for seven years. Financial records are the one category we cannot delete on request, because tax and accounting obligations attach to them.
Messages: Kept for as long as both participants have accounts, and for twelve months after either closes.
Audit log: Kept for twenty-four months. It records what an account did, not who the account belongs to beyond an identifier.
After you close your account: The profile is removed within thirty days. What remains is what another party also holds — contracts, invoices, released milestones and reviews of work that happened.

What you can ask for

A copy: Everything on your account as structured data. Requests are answered inside thirty days.
A correction: Most fields you can edit yourself in settings. Anything you cannot, we will change on request.
Deletion: Closing your account starts it. Where a record must survive — a contract, an invoice, a review — we will say which one and why rather than quietly keeping it.
An objection: You can turn off every notification category and every saved-search alert without affecting anything else on the account.

Ask through the contact form using the account queue. Signed in, the request opens a support thread in your Hireek inbox so the whole exchange stays in one place.

Security and location

Passwords are stored as salted hashes and are never recoverable in plain text. Sessions can be ended from settings. Data is encrypted in transit, and access to production data by staff is limited to the people who need it and written to the audit log when used.

Data is held in the European Union and the United States, depending on the processor. Transfers between the two rely on the standard contractual clauses.

No system is perfect. If a breach affects you, we will tell you what was exposed and what to do about it — not that we take security seriously.

Cookies

Three cookies, all first-party. A session cookie that keeps you signed in; a CSRF token that stops another site submitting forms as you; and a theme preference so the interface does not flash the wrong colours on load.

There is no advertising cookie, no cross-site tracker and therefore no consent banner to dismiss.

Hireek is a demonstration product seeded with fictional accounts, so the data described here is largely invented. The handling is nevertheless what the code actually does. The companion document is the terms of service.