GDPR · PDPA

Privacy policy.

This notice explains what personal data Resume Screening AI collects, why, who we share it with, and how to exercise your rights. It is a privacy notice, not a contract, and not a data processing agreement.

Last updated 20 August 2026.

1. Who we are

Resume Screening AI (resumescreening.ai) is operated by Ksaitor Media Pte. Ltd. (UEN 201431979G), a company registered in Singapore.

133 Lorong K Telok Kurau
Singapore 425770
Singapore

Privacy requests: [email protected]. We have not appointed a data protection officer, and we have not yet appointed an EU or UK representative.

2. Who this notice covers

This notice covers personal data we process in three situations:

  • Website visitors, including people who use public tools (calculators, PDF to Word, the AI resume builder).
  • Customers: recruiters, hiring managers, and workspace members who create an account.
  • Candidates, when a customer uploads a resume, emails one to a job inbox, or a visitor uploads their own CV to a public tool.

This notice covers the public site, accounts, billing, and candidate data a customer uploads, including when that customer or candidate is in the EU or EEA.

3. Controller and processor

We are the controller of account data, billing data, website analytics, support mail, and of a resume a person uploads on their own behalf (for example the AI resume builder or PDF to Word).

We are the processor of candidate resumes and job descriptions a customer uploads or emails in, and of the scores and rationales we generate from them. The customer (the employer or agency) is the controller of that candidate data. They must have a legal basis to collect it and must tell candidates that automated screening is used. A signable data processing agreement is not yet published; email [email protected] if you need one before uploading EU candidate data.

4. Data we collect

Account and workspace

Name, email, company name, profile image (if you sign in with Google), password hash or OAuth tokens, workspace membership, optional OpenAI API key if you bring your own, optional custom ranking fields, country inferred from the request (Cloudflare cf-ipcountry, stored once as signup country), newsletter preference, EU waitlist opt-in time, referral codes, and usage and credit balances.

Billing

Stripe customer and subscription identifiers, invoices, plan, and payment status. Card numbers are handled by Stripe; we do not store full card details.

Job and screening data (processor, when you use the product)

Job title and description, uploaded resume files as parsed text and structured fields (name, contact details, work history, education, and anything else in the document), filenames, scores, written rationales, strengths and weaknesses, recruiter notes, and similarity embeddings. Original files are parsed and are not kept as downloadable originals after processing.

Public tools

The AI resume builder may create an account from the email you verify. The PDF to Word converter sends extracted text to an AI model to check whether the file is a resume and, if it is, may store the parsed text. Calculators run in the browser and do not need an account.

Support, email, and logs

Emails you send us, account-deletion reasons if you provide one, error reports (which can include user id and email), and server logs (IP address, user agent, timestamps). Inbound Mailgun messages to a job address include the sender, subject, and attached resumes.

What we do not collect

We do not collect video, voice, photos of faces, biometrics, or emotion data. We do not scrape social profiles. We do not buy marketing lists of candidates.

5. Purposes and legal bases

Where GDPR applies, we rely on the following bases in Article 6. We do not use candidate resumes to train our own foundation models.

  • Contract (Art. 6(1)(b)): creating and running your account, screening and ranking resumes you submit, workspaces, credits, sign-in links, and receipts.
  • Legitimate interests (Art. 6(1)(f)): securing the service, preventing abuse, measuring product use, improving parsing quality, and sending product-update email to existing customers. You can object, and you can unsubscribe from product email in Settings or via the link in any message.
  • Consent (Art. 6(1)(a)): optional analytics cookies where consent is required, newsletter signup where it is not a service message, and the former EU availability notify list. You can withdraw consent at any time.
  • Legal obligation (Art. 6(1)(c)): tax and accounting records for invoices.

New accounts are added to the product-update list by default. That is service communication about a product you asked for, not a third-party marketing list. Turn it off in Settings at any time.

6. Candidate resumes

When you upload or email in someone else's CV, you instruct us to parse it, store the text, compute embeddings (contact details are stripped before embedding), and score it against your job description. Name, email, and phone are removed from the text sent to the ranking model. Graduation years, school names, and other identity signals can still appear in that text. The recruiter view still shows the original name.

You must only upload data you are allowed to process. If you screen people in the EU or EEA, tell them in your own privacy notice that automated processing is used, what it does, and that a person makes the hiring decision. See our EU AI Act and hiring-law page for the employer-side duties.

Candidates who want access or deletion of a CV we hold because an employer uploaded it should contact that employer first. We will help the employer fulfil the request. Candidates who used a public tool themselves can email [email protected].

7. AI scoring and automated processing

We use AI models to parse documents, compute similarity, and produce a score and a written rationale against the job description you supply. The product does not reject, advance, hire, or contact a candidate. A person reviews the ranked list and decides.

That is decision support, not a solely automated decision by us that produces legal effects (GDPR Article 22). If you treat the score as the decision and never deviate from it, Article 22 can still apply to you as the employer. Keep a human who is able to disagree.

The AI resume builder is a chatbot. You are interacting with an AI system, not a human recruiter.

8. Who we share data with

We do not sell personal data. We share it with the providers who run the service, and only as needed for the purpose listed. Workspace members see the jobs and resumes in that workspace.

ProviderWhat they doRegion
OpenAIResume parsing, ranking, embeddings, resume-builder chat, document classificationUnited States
Voyage AIResume and job embeddings, when configuredUnited States
Amazon Web ServicesAmazon Textract for document text extractionUnited States
GoogleCloud Vision OCR fallback, Google sign-in / One Tap, Google AnalyticsUnited States
StripePayments, subscriptions, invoices, billing portalUnited States / Ireland
MailgunSign-in and transactional email, inbound job applications, product-update listUnited States
LoopsProduct events and contact records for email programmesUnited States
Functional Software (Sentry)Error monitoring (may include user id and email)United States
HotjarSession analytics, when the Hotjar id is configuredEU, with possible onward transfers
Plausible (self-hosted)Cookieless page analytics at plausible.cjl.istOur analytics host
CloudflareCDN, TLS, and country detection used for the EU pauseGlobal

If you paste your own OpenAI API key in Settings, ranking and parsing calls for your workspace go through that key under OpenAI's terms with you.

We may disclose data if required by law, to protect the service, or in a merger or sale of the business, with notice where the law requires it.

9. International transfers

We are established in Singapore. Resume text and account data are processed by providers in the United States and other countries that are not covered by an EU adequacy decision. Where GDPR applies, those transfers rely on the provider's GDPR terms and, where they offer them, Standard Contractual Clauses. We do not yet offer EU-region processing or zero-retention agreements with model providers.

10. How long we keep data

  • Account and billing: for as long as the account exists, and invoices for as long as tax law requires.
  • Jobs, scores, and resumes you uploaded: until you remove them or delete the account. There is no automatic retention window yet.
  • Sessions and magic-link tokens: until they expire.
  • EU waitlist: until we send a one-time notice, or you ask us to delete the address.
  • Server and error logs: for a short operational period, unless needed to investigate an incident.

You can delete your account in Settings. That removes the user, jobs, workspace membership, and Loops contact. Email [email protected] if you also need a stored resume record removed (including one created via PDF to Word) or a copy of the data we hold about you. Complete, verified erasure of every derived copy (embeddings, caches) is still being tightened.

11. Your rights

Where GDPR or a similar law applies, you can ask us to:

  • access the personal data we hold about you
  • correct inaccurate data
  • delete data (subject to legal keep-records duties)
  • restrict or object to certain processing
  • receive a portable copy of data you provided
  • withdraw consent where we rely on consent

Email [email protected]. We may need to verify that the request comes from you. For candidate CVs uploaded by a customer, we will usually point you to that customer and assist them.

You can complain to your local supervisory authority. In Singapore you can contact the PDPC. EU and EEA residents can contact the authority in their country of residence (for example CNIL, BfDI, ICO for the UK after Brexit).

We do not sell personal information. If you are in California you can make the same access and deletion requests at the email above.

12. Cookies

We use the following cookies and similar technologies:

  • Authentication (necessary): NextAuth session cookies so you stay signed in.
  • Theme (preference): stored in the browser (typically localStorage) so light or dark mode persists. Not used for advertising.
  • Consent choice (necessary in the EU/EEA): rsa_cookie_consent remembers Accept or Reject for six months.
  • Google Analytics: page views and events, via cookies Google sets. Loaded only after consent in the EU and EEA, or outside those countries where a banner is not required.
  • Hotjar: session analytics when enabled, via Hotjar cookies. Same consent rule as Google Analytics.
  • Plausible: page analytics without cookies.
  • Cloudflare: security and country detection at the edge.
  • Google sign-in / One Tap: cookies Google sets on its own domain if you use Google to sign in.

Analytics cookies are not strictly necessary. Visitors in the EU and EEA (detected from Cloudflare's country header) see a consent banner before Google Analytics or Hotjar load. Reject is as available as Accept. Plausible does not use cookies and is not gated. .

13. Children

The service is for recruiting and workplace use. It is not directed at children, and we do not knowingly collect data from anyone under 16.

14. Security

We use TLS in transit, access controls on the application and database, and hashed passwords. No method of transmission or storage is perfectly secure. If we become aware of a breach that requires notice, we will tell affected customers and authorities as the law requires.

15. Changes

We will update this page when our practices change. The date at the top is the latest version. Material changes will be flagged on this page and, where they affect customers, by email or an in-product notice.

16. Contact

Ksaitor Media Pte. Ltd.
133 Lorong K Telok Kurau, Singapore 425770
[email protected]

Related: Terms of Service, EU AI Act and hiring laws.

Keep reading

Related