Privacy
Last updated 18 Nov 2026
src/app/privacy/page.tsx.This page is a plain-English description of every piece of data Hireloop stores and what we do with it.
What we store
- Account. Email (lowercased), bcrypt-hashed password (work factor 12), optional display name, role (member or admin), status, email-verified flag, timestamps.
- Sessions. A SHA-256 hash of your session cookie, your IP address, and your User-Agent string at sign-in time. The raw cookie value is never stored server-side. 30-day expiry; revoked immediately when you sign out or change your password.
- Job postings you create.Title, company, description, salary range, location, type, level, category, apply URL, and your user ID as the owner. These are public by design.
- Saved jobs. A mapping between your user ID and the jobs you bookmarked. Only you can see it.
- Email-verification and password-reset tokens. One-time, hashed at rest, single-use, with a short expiry (24 h for verification, 1 h for reset).
What we don't store
- No analytics, telemetry, or marketing trackers.
- No third-party scripts or pixels.
- No payment information — the app is free.
- No applicant data — applying happens on the employer's site.
Cookies
One cookie: hireloop_session. It's strictly necessary for authentication — without it you can't stay signed in — so we don't show a consent banner (essential cookies don't require one under GDPR/ePrivacy). HttpOnly, Secure in production, SameSite=Lax.
We send transactional email (verify your address, reset your password) through our email provider. We don't send marketing email and there's no newsletter to opt out of.
How long we keep it
- Account + postings: until you delete your account.
- Sessions: 30 days, or until you sign out.
- Verification / reset tokens: until used or expired.
Your rights
You can delete your account at any time. Deletion closes all of your postings, scrubs your email and display name, invalidates every session, and marks the account as deleted. Postings stay in the database in a closed state so we can keep referential integrity on the audit trail; we can hard-delete on request — see Contact.
Contact
Questions or a data request: /contact.