Privacy
This page describes how the public infrastructure site at jobdatapool.com processes information. It is not a substitute for policies on sibling products such as mewannajob.com or jobpool.live, which have their own surfaces and features.
Pages and API routes served through this domain run on Netlify. Like any hosted site, requests may generate access logs that can include timestamps, paths, status codes, IP addresses, and user agents. Netlify Log Drain data sent to this project is aggregated for coarse traffic reporting; it is not published as per-request logs.
Job queries and health endpoints may be served from this hostname or from api.jobdatapool.com.
Those requests are subject to normal edge processing, including rate limits described in the site README, and may be logged for operations and abuse prevention.
We design JobDataPool so downstream products and operators can use the canonical metadata we already provide instead of repeatedly crawling underlying business career sites. Our intent is to reduce duplicate bot pressure on publisher infrastructure and keep access to source sites aligned with legitimate human review and publisher terms.
In practice, this means we prioritize serving normalized records from JobDataPool first, apply abuse controls at our edge, and treat unnecessary recrawl behavior as an operations and trust issue.
The homepage displays a public launch request total backed by /v1/launch-metrics and optional service worker caching.
The browser may store a recent metric snapshot in Cache Storage and a small JSON payload in localStorage to avoid redundant network calls. You can clear site data in your browser to remove it.
When Firebase is configured, the optional "Join the review committee" flow may authenticate you with Firebase Auth and write your submission to Firestore after you consent on the form. If Firebase is not configured, submissions may be held locally in the browser only. Do not submit sensitive secrets through the intake form.
The optional profile page uses Firebase Authentication to display the name, email address, profile image, verification status, user ID, and role provided by your Firebase account. The API uses the verified Firebase user ID to maintain a separate account-based rate-limit bucket. JobDataPool does not accept a role asserted by browser code.
API playground defaults configured on the profile page are stored in localStorage in your browser. They are not written to Firestore and can be removed by resetting the settings or clearing this site's browser data.
Signed-in users may choose to support JobDataPool through a Stripe-hosted payment page. JobDataPool sends Stripe an opaque checkout reference; Stripe processes the payment and returns payment status, amount, currency, customer contact details, and transaction identifiers through signed webhook events. JobDataPool stores the resulting donor entitlement and selected dataset month in Firestore under the Firebase user ID.
Donor download links are short-lived and account-authorized. Unmasked datasets can include original source and application URLs and must be handled in accordance with applicable source terms, privacy obligations, and responsible-access expectations.
Typography loads from Google Fonts. The profile and intake pages load Firebase SDK scripts from Google static hosting to support authentication; the intake also uses Firestore.
Internal usage dashboards under restricted paths may store a session PIN or UI preferences in browser storage so operators can authenticate. Those pages are not part of the public docs surface; do not use them unless you are authorized.
This page may be updated as the infrastructure evolves. The canonical URL is https://jobdatapool.com/privacy/.
