Legal

You can build a product on it, charge for that product, and show the data to your users. You cannot become a source of the dataset itself — no reselling it as a feed, a file, or an API, and no assembling a competing jobs dataset for resale. Section 6 of the Terms draws the line precisely, and data licensing covers the common cases. If your use case sits near the line, ask before you build.

No, and the Terms say so in section 11. Postings are mirrored from employers' own boards, so they go stale when the employer moves. Enrichment fields — skills, seniority, salary, taxonomies — are derived by classifiers and are wrong some of the time. Do not make it the sole basis of a decision that affects someone's employment. Found something wrong? Send the job id — see data corrections.

Two things. Product analytics — we use PostHog, and with your consent it stores an id on your device, links what you read to your account, and records session replay. And the device fingerprint taken at signup to catch bulk account abuse. Everything else we set is strictly necessary and needs no consent. Two things rejecting does not stop, because you should hear it here rather than find it: anonymous page counts that store nothing on your device, and our own backend's record of what your account did — that you created a key or bought a plan. There are no advertising or cross-site tracking cookies at all. The Cookie Policy has every cookie and the reasoning in full.

Only the developer newsletter, only if you ask for it, and only after you confirm by clicking a link we email you — subscribing is your consent under Art. 6(1)(a), and we keep a record of it. Every issue has a one-click unsubscribe link that works without logging in. Transactional mail — verification, password resets, billing notices — is separate, is not marketing, and does not stop when you unsubscribe. The Privacy Policy covers what we store and for how long.

At signup and sign-in, for abuse prevention — stopping one person farming free accounts. It uses the open-source FingerprintJS library, which runs entirely in your browser and sends nothing to FingerprintJS; they are not a subprocessor. There is no automated blocking and no automated decision-making, so Article 22 GDPR does not apply. The Privacy Policy explains the legal basis and how to object.

Email [email protected]. There is no self-serve delete button in the portal, and we would rather say that than send you looking for one. A person handles it. Billing records survive deletion because Italian tax law requires it, and a short post-deletion record exists to stop delete-and-resignup resetting a free quota — both are in the Privacy Policy, and deleting your account walks through it.

Email [email protected] with the posting link or job id. You do not need to make a legal argument; ask and we remove it. Section 7 of the Privacy Policy explains how a person ends up in a company's job ad and what we do about it.

Cancellation runs through the Stripe customer portal and takes effect at the end of the period you have paid for — access continues until then. Unused time is not refunded by default, but the Refund Policy has real exceptions: duplicate charges, service failures, and subscriptions you never used.