Privacy

What we collect

• If you subscribe to the newsletter: your email address and which topics you chose.
• If you buy or are granted API access: your email address, and a hash of your API secret, never the secret itself.
• With your consent, when you first visit we store in your browser, for up to 30 days, how you found us (the referring site and page, campaign tags and the landing page); when you sign up we save this with your key, together with your optional answer to "How did you hear about us?", to understand which channels work. It is kept for as long as the key record exists; ask us to delete it via the contact form, like any other data we hold about you.
• If you write to us: your message and the address you gave, so we can reply.
• If you submit a listing: what you typed, plus a one-way hash of your IP address to stop flooding.

What we do not collect

• No advertising or cross-site tracking cookies. The ad slot on this site promotes our own products and is not personalised.
• We do not sell, rent or share your personal data with anyone for their own purposes.
• We never store your API secret in a form we could read, so we cannot recover it for you, and neither can anyone who steals our database.

How it is kept safe

• Everything travels over HTTPS. The site and the API refuse plain HTTP, and certificates are renewed automatically.
• Your API secret is never stored. We keep a SHA-256 hash of it, which is why we can check a key and still cannot tell you what it is, and why a stolen database yields no working keys.
• Card details never reach our servers at any point. Payment happens on the provider's own hosted page; we receive the outcome and an order reference, nothing else.
• Access to the production database is limited to the operator, over an authenticated tunnel, and is not exposed to the public internet.
• Backups are encrypted and kept off the machine that made them.
• If personal data of yours is ever exposed, we will tell you and the Hellenic Data Protection Authority within 72 hours of finding out, as the GDPR requires, even if the number of affected people is small.

Who else processes it

• Cloudflare: serves the site, and runs the bot check that keeps scrapers out.
• Lettermint: sends our email.
• Mistral AI, Cloudflare Workers AI, Hetzner (hosted inference), Alibaba Cloud (fallback only), Venice AI and Anthropic: classify job titles, tell employers from agencies and read employers' public careers pages; Anthropic is used only occasionally, for company-name classification at the most-listed employers. They receive only public company names and job-advert text, never your account, payment or visitor data. The AI disclosure explains exactly which fields are involved.
• Creem (creem.io): our Merchant of Record. It takes the card payment, calculates and collects VAT, and issues the invoice. We receive only the order outcome and a reference, never the card number or your billing details.
• PostHog, on their EU infrastructure, for three separate things. (1) Account events sent from our server, against your email address: signing in, subscribing, checking out, writing to us, creating or rotating a key, and the steps you take in your account area, for example choosing how you will use JOA, running a test query, starting a trial, turning on a job alert or asking for an upgrade link. They set nothing on your device, so they are not gated by the cookie notice; we rely on our legitimate interest in improving the product, and you can object at any time through the contact form. (2) Page views in your browser, with cookies, only if you turn on "Analytics (PostHog)" in the cookie notice. When you sign in, page views from the same browser are linked to your email address. Page addresses are sent without anything that could identify you: only campaign tags and the site's own view settings stay, never a token, an email address or what you typed in a search. (3) Only if you turn on "Account area steps (PostHog)" and while you are signed in, a few steps only your browser sees, such as copying a code sample, opening an install link or a guide, or seeing your plan limit, linked to your email address. They reach PostHog only if "Analytics (PostHog)" is on too; otherwise we keep them on our own server only. We also keep the account-area steps from (1) and (3) on our own server, with your account, for at most 400 days, and delete them when you delete your account. We never send your API key or any other secret, the text of your messages, or the addresses of your webhooks and chat channels, and we do not record sessions. PostHog does not keep IP addresses. When an event reaches it, it works out an approximate location (country and city) from the address the event came from and keeps that location: for (2) and (3) that is your connection's address, for (1) it is our server's. With both services off, nothing is recorded while you are only reading.
• Which channel you arrived from, recorded from the request itself when you ask for a sign-in link: the page you landed on, the site that referred you, and any campaign tags in the link. It is kept against the key you create so we can tell which channels actually bring people here. Nothing is stored on your device for this and it does not depend on consent; ask us and we will show you or delete it. To catch the first page you arrived on (the sign-in page only sees the page before it), our server notes for up to 48 hours, when you arrive from another site, from a link with campaign tags or without a referrer, the page, the referring site and the tags, against a one-way code made from your connection address and browser name, never the address itself. It is used only when the same connection asks for a sign-in link, and it is deleted after 48 hours.

The shared list

• We run one mailing list across jobopportunitiesapi.org and kaeros.app, both operated by the same company.
• Unsubscribing stops mail from every one of them, not just the site you signed up on.

Your rights

• You can unsubscribe from any email using the link in its footer, with no login.
• You can ask for a copy of your data, ask us to correct it, or ask us to delete it. Use the contact form and we will action it.
• We keep contact messages and enquiries only as long as we need them to answer you and keep our accounts straight.

Data controller