Cheghel
Find JobsCompaniesSaved
Sign inGet startedGet started
Cheghel
Find JobsCompaniesSaved
Language
Get startedSign in
Cheghel شغل

Lebanon's verified jobs marketplace: real employers, real salaries, real reviews.

Legal

  • About
  • Fair-hiring policy
  • Privacy
  • Terms
  • Cookies
  • Your Data (Law 81/2018)

Contact

  • General enquirieshello@cheghel.com
  • Supportsupport@cheghel.com
  • Data rights (Law 81/2018)privacy@cheghel.com
  • Terms & legal noticeslegal@cheghel.com
© 2026 Cheghel
  1. Home
  2. Privacy Policy

Privacy Policy

Effective: April 2026 · Last updated: October 2026

DRAFT — pending legal review. This text was updated on 18 Aug 2026 to reflect a change in which hiring criteria the platform permits, and again in September 2026, to correct what it says about where your data is processed, which providers receive it, the cookies we set, the payment data we share and keep, whether a phone number is required, and what we say about children's accounts; each change since 29 September 2026 is dated in the change log in Section 15. It has not yet been reviewed by counsel.

النسخة العربية قادمة قريبًا. The Arabic version is coming soon. In case of conflict, the English version is authoritative.

1. Introduction

Cheghel ("we", "us", "Cheghel") is a Lebanese job platform operating at cheghel.com. We connect job seekers (white-collar professionals, blue-collar workers, freelancers, and Lebanese diaspora) with employers whose companies we verify before they can post a job.

This Privacy Policy explains what personal data we collect, why we collect it, who we share it with, how long we keep it, and the rights you have over it. It applies to:

  • The Cheghel website and Progressive Web App at cheghel.com
  • Future Cheghel mobile apps for iOS and Android
  • WhatsApp and Telegram alerts and integrations operated by Cheghel
  • Transactional and opt-in emails sent from @cheghel.com

English is the authoritative version of this policy. An Arabic translation will follow. If there is any conflict, the English version prevails.

2. Data Controller and Contact

  • Data controller: Cheghel (legal entity name to be finalised at launch).
  • Privacy contact / DPO: privacy@cheghel.com
  • Legal contact: legal@cheghel.com
  • Postal address: Beirut, Lebanon (full address to be added at company registration).
  • EU representative: Not currently appointed. Cheghel does not target EU residents, but we honour data rights requests from anywhere in the world.

3. Data We Collect

We group the data we collect into the same categories used by Apple's privacy labels and Google Play Data Safety, so you can compare directly.

a) Contact Info

  • Email address: required to create an account.
  • Full name: required on your profile.
  • Phone number / WhatsApp number: required when you create an account with an email address and a password. Signing up with Google does not ask for one; you can add one later in Settings. Employers do not see it.
  • Physical address: we do not collect a home address. We only store your Lebanese governorate selection.

b) Identifiers

  • A Cheghel user ID (a random UUID generated at signup).
  • Google account identifier: only if you sign in with Google OAuth.
  • A consent ID: a random ID for your browser, set in an essential cookie the first time a choice you make in the cookie banner is recorded, and used only to keep the record of your cookie choices (Section 4(c)). It is not PostHog’s ID.
  • Device identifiers: we do not use Apple's IDFA or IDFV, nor any equivalent cross-app identifier. If a future mobile app ships, it will use Apple's session-only, on-device identifiers only.

c) User Content

  • CV / resume file (PDF or DOCX) and extracted text.
  • Profile photo, headline, bio.
  • Skills, portfolio URLs, LinkedIn URL.
  • Salary expectation and availability.
  • Job applications you submit and cover messages.
  • Reviews you leave about companies. Your review text is public; your identity as the reviewer is never shown publicly and is permanently protected under Law 81/2018 (see Section 5).
  • Saved jobs and saved search alerts.
  • Messages you send to employers through Cheghel, if any.

d) Usage Data

  • Pages you view and links you click on Cheghel.
  • Search queries you run on the platform.
  • Which jobs you view, save, and apply to.
  • Session duration and activity timing.
  • Referrer URL (where you came from to reach Cheghel).

e) Diagnostics

  • Crash and error reports via Sentry. Personal data is scrubbed before a report leaves your device or our server. What we do send is limited to: the address (URL) and method of the request that failed, a small set of technical headers (browser type, language preference, content type and encoding), the error and its stack trace, and an error code. Account and record identifiers are replaced with a placeholder before a report is sent.

4. How We Use Your Data

a) App Functionality

  • Match seekers with jobs using profile data and search filters.
  • Process applications (CV + profile + the job you applied to).
  • Manage reviews, including moderation and employer replies.
  • Administer paid plans and payment status.

b) Communications

  • Transactional emails: welcome, application received, application status changes, review published, password reset.
  • Weekly "Top Jobs for You" digest: opt-in only, with a one-click unsubscribe link in every email.
  • WhatsApp messages via Twilio: used only for phone-verification codes, and not currently sent at all. We do not send job alerts over WhatsApp.
  • We do not send marketing or promotional emails without your explicit consent.

c) Analytics

  • We use PostHog for product analytics. It is pseudonymous, not anonymous: PostHog gives this browser a random ID, which we never link to your account.
  • With each event it records the page you are on and the page you came from — with anything after the “?” or “#” removed before it is sent — which links and buttons you click (the kind of element, its design class names and where it sits on the page, and for a link the page it leads to, again without anything after the “?”; never the words on it or any label attached to it), how far down the page you scroll, and your browser, device, language, time zone and screen size. PostHog also receives your IP address, as any site you connect to does, and may use it to estimate your approximate location.
  • In your browser, PostHog keeps that ID in a cookie that expires a year after your last visit, and in local storage, where it has no expiry. Local storage also holds the address of the first page of each visit — which can include what follows the “?” — and the page that sent you there. See the Cookie Policy.
  • Analytics only load if you accept analytics cookies in the consent banner. If you choose "Essential only" — at first, or at any time later — PostHog does not start, or stops straight away in every Cheghel tab you have open and deletes what it stored in this browser. Anything it had already sent is not deleted from PostHog, and events from the moments just before you chose may still arrive.
  • We keep a record of each choice you make in the cookie banner — what you chose, when, which version of the banner you saw and in which language — so that we can show that consent was given. “Accept all” takes effect only once it has been recorded; if we cannot record it, analytics stays off. The record is kept against a random ID for your browser, never PostHog’s ID. If you are signed in when you choose, it is linked to your account, and a choice made while signed out may be linked to your account when you next sign in on the same browser. If your browser chose “Accept all” before we began keeping these records, we ask you once more.

5. The 3-Tier Information Wall

Cheghel uses a tiered disclosure model for job listings:

TierSees
Visitors (logged out)Job title, category, governorate, type, workplace, experience level, when it was posted, whether it is promoted and whether it is still open.
Registered free usersEverything above, plus the company name, the full description, the location line, the required skills, the screening questions, and the company’s profile: its logo, whether it is verified, its sector, governorate, description and size, and a link to its page.
People on Cheghel Plus ($3.99/month tier)Everything above, plus the full salary and the Apply button.

Reviewer identities are never disclosed: not to other seekers, not to employers, not through the admin UI, and not via any API. This is a permanent protection under Law 81/2018 and is enforced at the database row-level security layer.

6. Legal Bases for Processing

PurposeLegal basis
Account, applications, plansContract performance
Fraud prevention, security, abuse detectionLegitimate interest
Marketing, analytics cookies, WhatsApp alertsConsent (opt-in)
Financial record retention, law enforcement cooperationLegal obligation
Keeping a record of your cookie choicesLegal obligation (we must be able to show that consent was given)
Keeping a record of the notices we give of a change to this policyLegal obligation (we must be able to show that notice was given)

7. Third-Party Service Providers

We rely on the following providers. Each one processes data only for the purpose listed below, under a written contract.

ProviderPurposeData sharedLocationPolicy
SupabaseDatabase, authentication, file storageAll user dataJapan (AWS ap-northeast-1, Tokyo)link
Upstash (Redis)Rate limiting on every requestClient IP address; Supabase user id when signed inNot stated by us — the region is set per deploymentlink
Tap PaymentsPayment processing (currently in test mode)First name, email address, amount and currency, a description of what is bought, and your Cheghel account ID. Your card details are entered on Tap’s own page, not on Cheghel; section 3(h) lists what Tap sends back.Kuwait / regionallink
Cloudflare (Turnstile)Bot protection on sign-in, sign-up and password resetIP address, user agent, browser challenge signalGlobal edge networklink

8. Data Retention

DataRetention
Account data (profile, applications, saved jobs)While your account is active
Deleted account dataRemoved within 30 days
Reviews written by a deleted userReview text remains published; reviewer link is set to NULL permanently
Payment and billing records7 years (Lebanese tax law)
IP address logs90 days
Email delivery logs90 days
Crash / error logs (Sentry)30 days
The compliance record of a refused employer question about applicants, in the applicant search or the per-job applicant assistant, including the question’s text90 days, then deleted automatically. Two copies of a question can be kept longer: a question the per-job assistant refused only after its AI was asked — because its AI declined it in the way it is instructed to, or because its answer was withdrawn — also stays in that job’s conversation history until the employer’s account or the job is deleted; and when an employer’s refused questions trigger a compliance alert, the alert email to our administrator quotes them, and that email is not deleted automatically
Database backups35-day rolling window
Email unsubscribe suppression listKept indefinitely, so we never send you another job digest after you unsubscribe. It does not stop the transactional emails in Section 4(b), or a notice of a change to this policy (Section 15).
Record of your cookie choices

9. Your Rights

Under Lebanon Law 81/2018 and GDPR-equivalent principles, you have the following rights:

  • Right of access: request a copy of the personal data we hold about you. Self-serve at /data-request.
  • Right of deletion: request deletion of your account. Self-serve at /data-request.
  • Right of correction: edit your profile, or email privacy@cheghel.com.
  • Right of portability: get a JSON export of your data via /data-request.
  • Right to withdraw consent: unsubscribe links in emails, WhatsApp STOP, your profile settings, and — for analytics cookies — the Cookie preferences link in the site footer or on the Cookie Policy page, which stops analytics straight away, and is then recorded (Section 4(c)).
  • Right to object to a specific processing activity: email privacy@cheghel.com.
  • Right to lodge a complaint with the relevant Lebanese data protection authority.

We respond to all rights requests within 30 days, as required by Law 81/2018. Self-serve actions are immediate.

10. Children's Privacy

  • Cheghel is not intended for users under 18.
  • We do not knowingly collect data from minors.
  • Parents or guardians can email privacy@cheghel.com to report a minor's account or request its deletion.

11. International Data Transfers

Your data is processed in Japan: our database, authentication and file storage, and the servers that run Cheghel’s pages and features, are in Tokyo. Each request is first handled at the location of our hosting provider’s (Vercel’s) network nearest to you, which may be in another country. Your data may also be processed in the United States or the European Union by the other providers listed in Section 7, including by Vercel, which may transfer data to the United States, and, when you make a purchase, in Kuwait and the wider region by our payment provider, Tap Payments. Where available, we rely on standard contractual clauses or equivalent safeguards. By using Cheghel from Lebanon, you consent to this transfer for the purposes described in this policy.

12. Security Measures

  • Encryption in transit using TLS 1.2 or higher.
  • Encryption at rest at the database level.
  • Row-level security on every database table.
  • Regular security reviews and dependency audits.
  • Documented incident response plan. Any confirmed breach is notified within 72 hours, as required by Law 81/2018.

13. Cookies and Tracking

  • Essential cookies (cannot be disabled): authentication session, language preference, the mode you chose (job seeker, employer or freelancer), your cookie consent choice itself, and a random ID used only to keep the record of that choice (Section 4(c)).
  • Optional cookies (require consent via the banner): PostHog analytics — pseudonymous, not anonymous (see section 4c and the Cookie Policy). Withdrawing consent stops it straight away and deletes its cookie and browser storage.
  • Bot-protection storage (cannot be disabled, auth screens only): Cloudflare Turnstile may keep short-lived data in its own frame while it runs its challenge on sign-up, sign-in and password reset. It is not analytics and is not used to track you between visits.
  • Storage on your device: some features keep working data in your browser — your progress through the welcome steps, a job post you are still writing, the jobs you have previewed, and a display choice. Our servers do not read these entries. They are removed whenever someone signs in or out on this browser or deletes their account, and if a session ends another way, the next time Cheghel loads a page; only the display choice is kept. If you accept analytics, PostHog keeps its identifiers there too, and they are different: they go to PostHog with every analytics event, together with the address your visit began on and the page that sent you there (each without anything after the “?”). They are replaced with new random ones when you sign out, and removed if you withdraw consent.
  • Cookies set by other companies: Google sign-in, Tap's payment page and your bank's security check, and Cloudflare in front of our database provider (the __cf_bm cookie on supabase.co) set their own cookies under their own policies; Cloudflare Turnstile may keep data in its own frame, as described above. We cannot read or remove them.
  • No third-party advertising trackers.
  • No Meta / Facebook pixels.
  • No cross-site tracking.
  • No fingerprinting for advertising or identity. We run no script that profiles your device to build a marketing or cross-site identity. Cloudflare Turnstile, on the sign-up, sign-in and password-reset screens (and on the resend-confirmation action inside sign-up), does inspect browser signals — that is how it distinguishes a person from a bot — and it is listed in the processor table above. It runs before any account exists and is not used to identify you.

See our Cookie Policy for details and controls.

14. Mobile App Privacy (Future iOS and Android Apps)

Cheghel is currently a web and Progressive Web App. When native iOS and Android apps launch, the following additional rules will apply, consistent with this policy:

  • App Tracking Transparency (ATT): We do not track you across apps or websites owned by other companies. Our ATT answer is "not tracking".
  • No IDFA or IDFV collected or used.
  • Push notifications: opt-in only, with system-level and in-app toggles.
  • Background location: not collected.
  • Contacts, photos, microphone, camera: accessed only with your explicit permission, and only when you use the feature that needs it (for example, uploading a profile photo).
  • Face ID / Touch ID: used on-device only to unlock the app if you enable it. We never see biometric data.

15. Changes to This Policy

This section was rewritten on 2 October 2026. The rewrite is a material change, so it takes effect 30 days after we notify users of it by email and an in-app banner. Until then, the previous rules of this section apply. Both are set out below.

When this rewrite takes effect

  • A change that reduces your rights or uses your data for a new purpose is a material change. We notify users of a material change by email and an in-app banner, at least 30 days before it takes effect. A change that fits none of the kinds in this section is treated as material and gets the same notice.
  • A change that strengthens your protection or that is required by law takes effect when it is published, and is recorded, with its date, in the change log below.
  • A change that extends a practice this policy already discloses to another part of the same service, for the same purpose and the same period, takes effect when it is published, and is recorded, with its date, in the change log below.
  • Non-material changes (typo fixes, clarifications, broken links) may be posted without notification.
  • Previous versions are available on request.

Until this rewrite takes effect

  • We notify users of material changes by email and an in-app banner, at least 30 days before they take effect.
  • Non-material changes (typo fixes, clarifications, broken links) may be posted without notification.
  • Previous versions are available on request.

Change log

Each entry says whether the change was treated as material, and why. An entry for a material change shows the date it was published and when it takes effect.

  • 29 September 2026: the servers that run Cheghel’s pages and features moved from the United States to Japan (Tokyo), beside our database. Each request is still first handled at the location of our hosting provider’s network nearest to you. See Sections 7 and 11. Basis: not material — it strengthens your protection: processing moved to a country the European Union recognises as protecting personal data adequately.
  • 29 September 2026: the applicant search stopped running searches by gender or nationality, and a refused search is logged. See Section 3(g). Basis: not material — it strengthens your protection: we process less.
  • 1 October 2026: the per-job applicant assistant stopped answering questions by gender or nationality, as the applicant search had; a question about the right to work in Lebanon is still answered, from applicants’ own screening answers. See Section 3(g).

16. Contact Us

  • Privacy questions: privacy@cheghel.com
  • Data access, export, or deletion requests (fastest route): /data-request
  • Legal notices: legal@cheghel.com
  • Postal: Beirut, Lebanon (full address at company registration).
  • What we remove before sending: session cookies and authentication tokens, IP addresses and the location derived from them, and any account or record identifier. We do not send the content of your data — your CV, applications, messages, screening answers, and profile fields do not appear in a crash report.
  • Performance traces of requests to Cheghel (route name and timing; currently every request is traced). Request and response bodies are not included.
  • f) Location Data

    • Your Lebanese governorate (Beirut, Mount Lebanon, North, Akkar, Bekaa, Baalbek-Hermel, South, Nabatieh) or "Abroad" selection.
    • We do not collect precise GPS or device-level location.
    • IP addresses are logged with login events for security, abuse detection, and fraud prevention, and retained for 90 days.

    g) Sensitive Data: what we do not collect

    • We do not collect religion, sect, political views, sexual orientation, or health data.
    • We enforce this at the platform level for employer questions to the applicant search or the per-job assistant that name religion or sect, political affiliation, age, marital or family status, physical appearance, sexual orientation or gender identity, or disability. A question our keyword check matches is hard-blocked and never reaches our AI provider; one it does not match is sent to our AI provider, where our checks are instructed to refuse it. The attempt is logged as a compliance event for moderation.
    • The applicant tools do not use gender or nationality. When an employer searches across their applicants with the applicant search (“Ask about your applicants”), or asks the per-job applicant assistant, a Cheghel Pro tool, about the applicants to one job, a question that asks for gender or nationality is refused, and the refusal is logged. Such a question is refused by our AI assistant and its checker rather than blocked before them, so its text does reach our AI provider. A question about the right to work in Lebanon or a work permit is not a question about nationality, and both tools are instructed not to refuse it: the applicant search is instructed to answer that its list does not show it, and the per-job assistant to answer it only from what each applicant wrote in answer to the employer’s own screening questions — never by inference, and without repeating a nationality an applicant gave as the reason. The per-job assistant is given applicants’ answers to the employer’s screening questions about the right to work only when the employer’s question mentions the right to work. A question that asks for foreigners or for applicants who are not Lebanese, or that groups, sorts or counts applicants by nationality, asks for nationality, and both tools are instructed to refuse it, even when it also mentions a permit. A question about whether applicants live in or come from a refugee camp or settlement is treated as a question about nationality, and both tools are instructed to refuse it. We hold no gender field about you, and the optional nationality you may add to your own CV appears only on that CV: it is never used for matching, ranking or employer search, and both applicant tools are instructed never to infer your gender or nationality from your name, languages or location.A change to this bullet, published on 7 October 2026, takes effect 30 days after we notify users of it (see the change log in Section 15). From then, for a question about whether an applicant holds a valid residence permit, the per-job assistant is instructed to answer it only from what each applicant wrote in answer to the employer’s own screening questions, never by inference, and is instructed not to repeat any nationality the applicant mentioned in that answer. On the same date, this bullet’s statement that the refusal is logged is corrected: when the applicant search or the per-job assistant declines a question in the AI’s own words, and our checks do not also refuse it, the question is not recorded as a refusal. Until then, this bullet applies as written above. Already, separately from that change, both tools are instructed to treat a question about whether an applicant holds a valid residence permit as one about the right to work, not about nationality, and not to refuse it; the applicant search is instructed to answer that its list does not show it (see the change log).
    • When we read your CV to build your profile, we leave out the personal details we detect in it, such as religion, age or family status, so that employers’ scoring never sees them (they stay in the CV you uploaded), and we keep one yes-or-no note of whether the latest successful reading left anything out — never what — which is shown only to you, on your profile page and in your data export, and is replaced each time your CV is read successfully, and cleared when you replace or remove your CV.

    h) Financial Info

    • Purchases of Cheghel Plus and credit packs are processed by Tap Payments, listed in section 7. Payments currently run in test mode; section 8 of our Terms of Service sets out what that means.
    • When you start a purchase, we send Tap the first word of the name on your account (if you have given one), your email address, the amount and currency, a description of what you are buying (the plan and its length, or the number of credits), and your Cheghel account ID, part of which also makes up the payment’s reference. You enter your card details on Tap’s own payment page, and Tap collects them there under its own privacy policy.
    • Your full card number, expiry date and CVV are typed into Tap’s own payment page, never into a Cheghel page, so they do not pass through our site on their way to Tap. What Tap sends back to us afterwards is set out in the next point.
    • We keep your paid plan’s status and period, with Tap’s identifier for you as its customer. For each payment notification Tap sends us, we keep only the charge’s references, its status and outcome codes, the amount, currency and timestamps, and the description of what the payment was for. Before a notification is stored, we remove any name, email address and phone number and every card detail: the card’s brand and network, any digits of the card number, the 3-D Secure data, and card and device identifiers. We do this for payment notifications we reject as well as for those we accept.

    i) Data Linked to You vs. Not Linked to You

    Linked to your identityNot linked to your identity
    Account data, CV, applications, saved jobs, job alerts, plan status, payment history, review content, and the record of your cookie choices if you were signed in when you chose, or it was linked when you signed in later on the same browser.Pseudonymous product analytics, only if you accept analytics cookies: usage events tied to a random browser ID that we never link to your account, which we look at in aggregate.

    Reviewer identity on company reviews is stored internally but is never returned by any API, UI, or admin screen. See Section 5.

  • We use analytics to understand feature usage in aggregate, not to profile individuals.
  • d) Product Personalisation

    • AI job recommendations based on your extracted profile and activity.
    • Search result ranking tailored to your history.
    • All personalisation happens server-side. The results are visible only to you.

    e) Fraud Prevention and Security

    • Detecting spam accounts, fake jobs, and abusive behaviour.
    • Rate limiting to prevent automated abuse.
    • Login anomaly detection based on IP and session patterns.

    f) Legal Compliance

    • Retaining financial records for 7 years as required by Lebanese tax law.
    • Responding to valid legal requests from Lebanese authorities where there is a lawful basis.
    • Keeping a record of each choice made in the cookie banner, so we can show that consent to analytics was given.
    • Keeping a record that we gave you notice of a change to this policy (Section 15): when, and whether by email or the banner on the site, so we can show the notice was given.
    ResendTransactional email deliveryEmail address, email contentsUnited Stateslink
    SentryError and crash reporting, and performance tracing of requestsScrubbed error reports and performance traces: request URL and method, technical headers, stack trace, error code, route timing. No cookies, authentication tokens, IP addresses, or user identifiers.Germany (EU region)link
    PostHogProduct analytics (opt-in only)Pseudonymous usage events: a random browser ID we never link to your account; the pages you view and the page you came from, with anything after the “?” removed; which links and buttons you click, by kind, design class name and position, never their text; how far you scroll; browser, device, language, time zone and screen size; and your IP address.EUlink
    Anthropic (Claude)AI screening, CV extraction, the applicant search and the per-job assistantCV text and job text submitted by our servers, employers’ questions to the applicant search and the per-job assistant, and applicants’ answers to employers’ screening questions. Anthropic does not train on API data.United Stateslink
    GoogleOAuth sign-in (optional)Email, name, avatar (only if you choose Google sign-in)United Stateslink
    TwilioPhone verification codes (not currently sent)Phone number, message contentUnited Stateslink
    VercelHosting: runs our pages and features and delivers the site through its global networkRequest logs (IP, user agent, path)Japan (Tokyo), where our pages and features run. Each request is first handled at the Vercel location nearest you, which may be in another country. Vercel may also transfer data to the United States and other countries where it or its providers operate.link

    What we do NOT do:

    • We do not sell your personal data.
    • We do not share your data with advertisers.
    • We do not use data brokers.
    • We do not transfer your data to any third party outside the providers listed above.
    While the choice applies, and 3 years after it is replaced or withdrawn. A choice stops applying when a new one is made on the same browser, or a year after it was made, when the banner asks again. If you delete your account, the record is kept for the same period, no longer linked to your account.
    Record that we gave you notice of a change to this policy (the date, whether by email or the banner, for an email a code derived from your address, and, if our email provider could not confirm an email to you, our privacy lead’s note of what they found and why)3 years after the change takes effect. If you delete your account, the record is kept for the same period, no longer linked to your account. The queue we send the notice from is deleted 90 days after the change takes effect, and with your account if you delete it sooner. A notice we never send never takes effect. Its record and its queue are deleted 90 days after it was approved — but not before the day it was to be sent has passed, and not while our privacy lead still has to check an email our email provider could not confirm. Any change it was to announce goes in a later notice.
    Basis: not material — it strengthens your protection: we process less.
  • 2 October 2026: we stopped deriving from your CV whether it has a “Lebanese context” (a Lebanese university, town or company, or Arabic text), a flag that could stand in for nationality, and we are removing the flags already stored. See Section 3(g). Basis: not material — it strengthens your protection: we process less.
  • 2 October 2026: we began keeping a record of each choice made in the cookie banner, linked to your account if you are signed in, and kept while the choice applies and for 3 years after; a browser that chose “Accept all” before then is asked once more. See Sections 4(c), 6 and 8. Basis: not material — it records a choice you already made, adds no new use of your data, and is required by law, because we must be able to show that consent was given (Article 7(1) of the EU’s GDPR).
  • 2 October 2026: a question the per-job applicant assistant refuses because of what it asks is now recorded, with its text, in the same compliance record as a question the applicant search refuses, and deleted after the same 90 days. See Sections 3(g) and 8. Basis: not material — it extends a practice this policy already discloses to another part of the same service, for the same purpose and the same 90 days.
  • 2 October 2026, taking effect 30 days after we notify users of it: this section was rewritten. It now says which changes take effect when they are published — one that strengthens your protection, one the law requires, or one that extends a practice this policy already discloses to another part of the same service, for the same purpose and period — and that a change that fits none of its kinds is material and waits for 30 days’ notice. Basis: material — it changes the notice rules themselves, and under it some changes take effect without notice.
  • 4 October 2026: we keep a record of every notice we give of a change to this policy — when, and whether by email or the banner on the site, and for an email a code derived from your address — for 3 years after the change takes effect. See Sections 4(f), 6 and 8. Basis: not material — it keeps a record that we sent you a notice this policy already promises — who it went to, when, and by which channel — adds no new use of your data, and lets us show that we gave the notice, as the law expects of us.
  • 4 October 2026: we began keeping one yes-or-no note of whether the latest reading of your CV left a personal detail out of your profile — never what — shown only to you, on your profile page and in your data export. See Section 3(g). Basis: not material — it extends a practice this policy already discloses to another part of the same service, for the same purpose and the same period.
  • 5 October 2026: when the per-job applicant assistant’s AI declines a question in the way it is instructed to, the question is now recorded, with its text, in the same compliance record as a question the applicant search’s AI declines, and deleted after the same 90 days. A decline it writes in ordinary words instead is not recorded, unless our checks also refuse the question because of what it asks (see the 2 October entry). See Sections 3(g) and 8. Basis: not material — it extends a practice this policy already discloses to another part of the same service, for the same purpose and the same 90 days.
  • 5 October 2026: the applicant search and the per-job applicant assistant are instructed to refuse a question that asks for foreigners or for applicants who are not Lebanese, or that groups, sorts or counts applicants by nationality, even when it also mentions a permit. See Section 3(g). Basis: not material — it strengthens your protection: these questions are no longer answered.
  • 7 October 2026, taking effect 30 days after we notify users of it: a question to the applicant tools about whether an applicant holds a valid residence permit will be treated like a question about a work permit — about the right to work, not about nationality. The applicant search will be instructed to answer that its list does not show it, and the per-job assistant to answer it only from what each applicant wrote in answer to the employer’s own screening questions. The same change corrects sentences in this policy, and two in our Terms of Service, that say each refusal by these tools is logged: when the applicant search or the per-job assistant declines a question in the AI’s own words, and our checks do not also refuse it, the question is not recorded as a refusal. See Section 3(g). Basis: material — the per-job assistant will answer it from applicants’ own screening answers, which it is not instructed to do today, and the change is none of the kinds that take effect when they are published.
  • 8 October 2026: the per-job applicant assistant is now given applicants’ answers to the employer’s screening questions about the right to work only when the employer’s question mentions it. See Section 3(g). Basis: not material — it strengthens your protection: the assistant reads these answers in fewer cases.
  • 8 October 2026: a job listing’s location line and its required skills are shown only to signed-in users, as its full description already was, and the table in Section 5 now lists everything a visitor, and a free account, can see of a listing. See Section 5. Basis: not material — it strengthens your protection: visitors now see less of a listing (the location line and the required skills need sign-in), and the table now lists everything else a visitor and a free account could already see; nothing was added to what either can see.
  • 8 October 2026: both applicant tools are instructed not to refuse a question about whether applicants hold a valid residence permit, and the applicant search is instructed to answer it by saying that its list of applicants does not show it. Answering it from applicants’ own screening answers is part of the change published on 7 October 2026 and takes effect with it. See Section 3(g). Basis: not material — it strengthens your protection: the tools are instructed to stop refusing a lawful question as one about nationality, and no applicant’s information is read or shown that was not before.
  • 8 October 2026: the applicant search and the per-job applicant assistant are instructed to refuse a question about whether applicants live in or come from a refugee camp or settlement, as a question about nationality. See Section 3(g). Basis: not material — it strengthens your protection: these questions are no longer answered.
  • 19 October 2026: for a notice of a change to this policy that we never send, what we keep about you now has its own period: its record and its queue are deleted 90 days after it was approved (Section 8 says when that waits), and any change it was to announce goes in a later notice. Where our email provider could not confirm whether it accepted a notice email to you, our privacy lead now checks its log and records what they found, and why — a note deleted on the same schedule as that record — and you can read that note in your data export. See Section 8. Basis: not material — it strengthens your protection: what we keep about a notice we never send now has a period, and an email we could not confirm is checked instead of being left unresolved; our privacy lead’s note of that check is deleted on the same schedule as our record of that email.
  • 19 October 2026: Section 3(g) now says which employer questions never reach our AI provider. When an employer asks the applicant search or the per-job assistant a question that names religion or sect, political affiliation, age, marital or family status, physical appearance, sexual orientation or gender identity, or disability, a question our keyword check matches is blocked before it reaches our AI provider; one it does not match is sent to our AI provider, where our checks are instructed to refuse it. The section used to say that no such question reaches our AI provider. Section 7 now names these two tools where it said “HR queries”. Section 7 now also lists employers’ questions to these two tools and applicants’ answers to employers’ screening questions among what we send to our AI provider. See Sections 3(g) and 7. Basis: not material — it clarifies this policy: what we do with these questions has not changed, and Section 3(g) already said that a question asking for gender or nationality, which our checks are instructed to refuse rather than block before them, reaches our AI provider.