Privacy Policy

Closed beta · Last updated 15 November 2026

Taqdim (تقديم) helps you apply for jobs: it reads your CV, checks how well you fit a job, and writes a tailored CV and cover letter from your own information. This policy explains what personal data we handle, why, where it goes, how long we keep it, and how to delete it. It also covers the waitlist on taqdim.app, which you can join without an account, and how we count visits to taqdim.app and use of the app.

Who is responsible for your data

The data controller is Bassam Tantawi, an individual who operates Taqdim during the beta. Taqdim is the name of the service, not a company. For any privacy question or request, write to the address in the “Contact” section below.

What we collect

  • Account details: your name, email address and, if you add one, your phone number. If you sign in with Google, we receive your name, email address and profile picture from Google, and nothing else.
  • Your CV and profile: the file you upload and the information we extract from it (work history, education, skills, languages, certifications, links and similar). We also store a photo if you upload one for Gulf-format CVs.
  • Saved answers: answers you give to common application-form questions (for example, notice period or work authorisation status), stored so you do not need to retype them for each application.
  • Jobs you check: the job postings you paste or link, and the fit results we produce for them.
  • Documents we generate: tailored CVs and cover letters, and your application tracker. We also keep a snapshot of your profile at the time each document was generated, so your document citations remain accurate even if you later update your profile.
  • Application submission records: when you use the browser extension to fill a form, we record which form was filled, the page URL, and counts of filled and corrected fields. We never store the text values you type into the form; only the structural outcome.
  • Email preferences: whether you want each kind of service email we send (see “Why we use it”), and the date we last sent you a follow-up reminder.
  • Credits: your balance and a record of all charges and refunds.
  • Free starter credits: whether your account received them and, if not, why. So that each person gets them only once, when your account receives them we keep a one-way, keyed fingerprint of your email address, never the address itself. It is made after small differences are removed (capital letters, a +tag, and dots in a Gmail address), so variants of one address count as one. We can’t turn it back into your address; we can only check whether a given address matches it, and we do that only when we decide whether a new account gets the free starter credits. When you sign up, we also count free-credit grants per network per day with a one-way, keyed fingerprint of your IP address (for IPv6, of its network part), never the address itself, and not linked to your account.
  • Purchases: if you buy a credit pack, we keep Paddle’s transaction id, the pack, the number of credits, the amount and currency you paid, the date, and any refund or chargeback on it. We never see your card or other payment details: you enter them in Paddle’s checkout, and Paddle keeps them. To start the checkout we send Paddle your account’s email address, so you don’t have to type it again, and a signed note with your internal account id and the pack you chose, so the payment adds the right credits to the right account.
  • Waitlist sign-ups: if you join the waitlist on taqdim.app (no account needed), we store your email address, the language you chose, the page you signed up from, any campaign tags in the link you arrived by (source, medium and campaign), when you signed up and when you confirmed. We also store a one-way, salted fingerprint of your IP address, used only to limit abuse of the form and deleted when you confirm, and a one-way fingerprint of your inbox, so that variants of one address (such as name+tag@) count as one sign-up and share one email limit.
  • Visits to taqdim.app: We count visits to taqdim.app with our own counter, without cookies and without storing your IP address. When you open a page on this website, your browser sends us a small record of it, and of a few clicks: links to the app (for example to sign up or sign in), our email link, the Chrome Web Store link, the language switch, and reading most of a blog post. Each record holds the page address without anything after a “?”, the language of the page, the name of the website that sent you here (for example google.com, never the full link), any campaign tags in the link you arrived by (source, medium and campaign), the kind of browser and device you use (for example Chrome on a phone, never the full browser details), and a random visit number. The visit number is kept in your browser tab for that visit only and is gone when you close the tab. These records are not linked to your account or to the waitlist, even if you are signed in to the app. Visits from browsers that look automated (such as search engine robots) are not stored, and visits from our own team or test tools are marked so we can leave them out of our counts. If your browser sends Do Not Track or Global Privacy Control, the website sends nothing at all.
  • Using the app: app.taqdim.app counts how its features are used with our own counter. For this it keeps a first-party cookie called tq_session, set by app.taqdim.app only, that holds a random visit number. The cookie expires 24 hours after your last activity in the app. We use it only to count product usage, to connect feedback or a problem report you send to the same visit, and to trace an error in our server logs back to the same visit (the visit number is written into the error’s log line; see “Kept by our providers” for how long server logs are kept). We record these steps, and only these: opening the app; opening a page in it; starting a fit check; seeing a fit report; preparing an application; preparing an application from a fit verdict; spending credits; switching language; sending feedback; telling us whether a fit verdict was fair; seeing the profile-strength card; seeing the setup checklist; seeing the card that shows the time Taqdim saved you; clicking a suggestion to complete your profile; seeing the credit packs; choosing a credit pack; clicking pay; leaving the payment step without paying; and clicking a link to the browser extension. For each step we store its name, the page address without anything after a “?”, the app’s language, the kind of browser and device you use (for example Chrome on a phone, never the full browser details), the visit number, the time and, if you are signed in, your account. The first step of a visit also holds the name of the website that sent you to the app (for example google.com, never the full link) and any campaign tags in the link you arrived by (source, medium and campaign). We also mark a step that comes from our own team or our test tools, or from a browser that looks automated (such as a search engine robot), so we can leave it out of our counts; to decide, we read your browser’s details when the step arrives and keep only the mark. A step can also carry a few short labels or numbers, such as the fit verdict, a credit pack, a count of remaining items or the internal id of the job or application it is about. They never include your CV, the job text, your documents or your email address, and text that looks like an email address is removed before it is stored. We store at most 500 of these records per visit per day, and at most 20,000 a day across all users. If your browser sends Do Not Track or Global Privacy Control, the app sends none of them and does not create the tq_session cookie to count usage; the cookie is then only created if you send us feedback or a problem report.
  • PostHog (optional): the app can also send the same steps, with the same labels, to PostHog, a product-analytics service, on its EU Cloud in Frankfurt, Germany. This happens only when a PostHog project key is configured for the app; without one, the app does not load PostHog at all. We have set PostHog up so that it saves nothing in your browser (no cookie and no local storage); it knows you only by the visit number, never by your name, email address or account; every page address it is sent is cut before any “?” or “#”, and it is not started at all on a page whose address, or the address of the page that sent you there, has anything after a “?” or “#”; its own automatic tracking (clicks, page views, errors, performance) is off; and screen recording is off. With each request PostHog also receives your IP address and your browser’s own details (such as browser, operating system and screen size). PostHog would keep your IP address unless its “Discard client IP data” setting is on; we will turn that setting on before we turn PostHog on. If your browser sends Do Not Track or Global Privacy Control, the app does not load PostHog at all.
  • Processing history: a record of each AI pipeline run (what kind of task, which model, how many tokens, whether it succeeded), linked to your account.
  • Security records: a log of sensitive actions (for example sign-ins, credit changes and deletions) and short-lived rate-limit counters that protect the service from abuse.
  • Feedback you send us: if you use “Report an issue” (available when we enable the debug feedback feature for testers), the text you write, a screenshot if you allow it, and your email address — all sent to our private GitHub repository so we can follow up.
  • Feedback and fairness notes you write in the app: if you use the feedback box or tell us whether a fit verdict was fair, we store what you write, the category you choose, and the context it was written in: which screen, the job posting and application it refers to, and, for a verdict, the verdict, score and scoring version you saw. These notes are stored in our database. Each feedback note (not the fairness answer) is also emailed to our team inbox (Google Workspace, listed below, sent through Resend), with the screen, the language, the time, and whether you were signed in, shown only as a short code made from your account number, never your name or email address. That way a person on our team reads every note. They are not sent to GitHub. Please do not put phone numbers, addresses or other personal details in them.
  • Feedback from the website, or from the app while signed out: if you use “Send feedback” at the bottom of taqdim.app, or the feedback button in the app while signed out, we store what you write, the category, the page you sent it from, the language, your browser’s user-agent string and the time, and email a copy to our team inbox (Google Workspace, sent through Resend). On the website you can add your email address if you want a reply. We do not store that address in our database: it goes only into the copy in our team inbox, so we can answer you. To limit abuse, the website form counts notes per network per day with a one-way, salted fingerprint of your IP address, never the address itself.
  • Notes after an offer (optional): when you mark an application as Offer, you can send us a short note about what helped, and tick a box if we may quote it. We store the note, your choice and which application it belongs to, with your account.
  • Exit survey (optional): if you answer “Why are you leaving?” when you delete your account, we keep your reason and any note you write, with the month you left and two rough ranges: how long you had an account and how many fit checks you ran. We don’t keep your name, email or account with it, and we remove contact details we can detect from your note. Because there are still few of us, we treat it as personal data.

We do not use advertising trackers, and we do not sell your data.

Why we use it

  • To provide the service you ask for: extracting your profile, checking fit, and writing your documents. This is necessary to perform our agreement with you.
  • To send you service emails about your own use of Taqdim, as part of the service: a “report ready” email when a fit report you asked for is finished, and a follow-up reminder when a follow-up date you set in your tracker has passed (at most one reminder a day). The “report ready” email does not include the job, verdict or score; it links to your report, which you see after signing in. The reminder lists the job title, company and due date of each overdue follow-up; your own notes stay in the app. We also send a one-time notice 30 days before we delete an account that hasn’t been used for 6 months (never to an account that still holds credits from a purchase, because we don’t delete those); it is about your account itself, so it has no unsubscribe link. When you buy credits, we email you a note that the credits were added. Paddle, which sells the credits, emails you the invoice. The note is about a purchase, so it has no unsubscribe link. Apart from the waitlist emails described below, we do not send marketing email. You can turn off the “report ready” and reminder emails separately, at any time, with the one-click unsubscribe link in each of those emails or with the email toggles on your profile page.
  • To run the waitlist, with your consent. When you join, we send an email with a link to a page where you confirm your address with a click (double opt-in); the confirmation link works for 7 days. Until you confirm, we keep your sign-up (your email address, the page and campaign tags, and the IP fingerprint) for up to 30 days, then delete it. Only a confirmed address stays on the list, until launch or until you leave it, and we use it only to email you when your invite is ready. When you confirm, we also email your address, the language you chose, the page you signed up from, the campaign tags and the sign-up and confirmation times to our own team inbox (Google Workspace, listed below), so a person on our team sees every request and can send your invite. Every waitlist email has a link that removes you from the list, which deletes your address from the list. The copy in our team inbox is kept as described under “How long we keep it”.
  • To publish a short quote from your note, only with your consent: you tick the box, then approve the exact wording we email you. On taqdim.app we show your first name only. On Taqdim’s LinkedIn page we may share the quote without a name. You can withdraw at any time by emailing us, and we take the quote down from both within 7 days. When you delete your account, we take it down within 14 days. We can’t recall copies that others have already shared. We keep your approval email, and any withdrawal, for 12 months after the quote comes down, as a record of your consent.
  • To see how many people visit taqdim.app, which pages they read, which websites and campaigns bring them, and how many go on to the app. We look only at totals, never at one visitor.
  • To see which parts of the app are used and where people get stuck, so we can improve Taqdim, and to look into a problem you report.
  • To sell credit packs: to add the credits you bought, handle refunds and chargebacks, answer questions about a payment, and keep the purchase records that tax and accounting rules may require. This is necessary to perform our agreement with you and to meet our legal obligations.
  • To keep the service secure and prevent abuse of free credits. For the free-credit fingerprints described above, we rely on our legitimate interest in giving the free starter credits once per person. We keep only fingerprints, never your email or IP address. We don’t sell them, and apart from us only the providers listed in “Who processes it for us” that run our app or host and back up our database handle them, to deliver their service to us. We delete them as described in “How long we keep it”.
  • To fix problems you report and improve the beta, including checking whether our fit verdicts are fair. We do not use your feedback notes to train AI models.

We do not use your CV or documents to train AI models. Every document is generated from your own information. Taqdim is designed not to invent experience, but AI can still make mistakes, so review everything before you send it.

Who processes it for us

ProviderWhat forWhere
ClerkSign-up, sign-in and account securityUnited States
NeonDatabase: your profile, CV file, jobs and documents, and the waitlistFrankfurt, Germany (EU)
VercelHosting the website and app. Vercel keeps our server logs for 1 hour.Global network
Cloudflare (Workers AI)Running the AI models that read your CV and write your documents. Cloudflare’s terms confirm prompts and AI outputs are not retained beyond the request and are not used to train models.Global network
Cloudflare (R2)Storing encrypted backups of our database for up to 30 days. They are encrypted before they are sent to Cloudflare, so Cloudflare cannot read them.European Union
GoogleOnly if you choose “Sign in with Google”Global
Google (Google Workspace)Receiving and storing the emails you send to contact@, support@, privacy@, billing@, careers@ and security@taqdim.app, and our replies. Also our team inbox’s copy of each confirmed waitlist sign-up (see “Why we use it”) and of each feedback note (see “What we collect”). Google receives your email address and the content of each of these emails.Global network; Google LLC is based in the United States
ResendSending our service emails (“report ready”, follow-up reminders, notes that credits you bought were added, and the inactive-account notice) and waitlist emails. It also sends the copy of each feedback note to our own team inbox. Resend receives your email address and the content of each email. Resend keeps sent emails and their delivery logs for 30 days.Sent from the EU (Ireland); Resend, Inc. is based in the United States
Paddle (Paddle.com Market Limited; Paddle.com Inc. for buyers in the United States)Only if you buy a credit pack. Paddle is our reseller and the Merchant of Record: it sells you the credits, takes the payment, charges tax, sends your invoice, and handles refunds and chargebacks. In its checkout Paddle collects your email address, country, payment details (such as your card) and, where tax rules need it, your postcode, and it receives your IP address. Paddle is not just a processor for us: it decides how it uses this data for the sale, its payment and tax records and fraud checks, as a separate controller under its own privacy notice. From Paddle we receive the transaction id, the amount, currency and status of the payment, and any refund or chargeback; we never receive your card details.United Kingdom (Paddle.com Market Limited, London); United States for Paddle.com Inc.
PostHogOnly when a PostHog project key is configured for the app: the app’s usage records (see “Using the app” and “PostHog (optional)” above)EU Cloud (Frankfurt, Germany); PostHog, Inc. is based in the United States
GitHubOnly if you use “Report an issue”: the text you write, a screenshot if you allow it, and your email address are sent to our private GitHub repository. GitHub, Inc. also runs our automated backup and restore-check jobs on its servers: each night a job reads our whole database and encrypts it before it is sent to Cloudflare, and once a month a job may restore a backup on a temporary GitHub server to check that it works, then delete it. GitHub does not keep a copy of the database from these jobs.United States

Some of these providers are outside your country. We have data processing agreements with each provider listed above, and rely on those agreements (and where required, on standard contractual clauses) to lawfully transfer your data. For Resend, a United States company, we rely on Resend’s data processing terms, including standard contractual clauses. For Google Workspace, we rely on Google’s Cloud Data Processing Addendum, including standard contractual clauses. For GitHub, Inc., a United States company that runs our backup and restore-check jobs, we rely on GitHub’s Data Protection Agreement, including standard contractual clauses. Each provider processes your data only to deliver its service to us. Paddle is the exception: when you buy credits, your details go to Paddle in the United Kingdom (or in the United States, for buyers there) because you are buying from Paddle, and Paddle handles them as a separate controller under its own privacy notice, which explains the safeguards it uses for international transfers. The cross-border transfer mechanisms for each applicable law are being confirmed with legal counsel before public launch.

Our How to apply page offers a video on YouTube that loads only when you press play; when you do, YouTube (Google) receives your IP address and may set cookies under its own privacy policy, even though we use its privacy-enhanced mode (youtube-nocookie.com).

How long we keep it

We keep your data only as long as the service needs it. Everything below that has a time limit is deleted automatically by a daily clean-up job, or by the provider named. Because the clean-up job runs once a day, each period it enforces can run up to one extra day (the “within 2 days” for profile snapshots already includes that day). The emails about quotes we ask you to approve are the exception: we delete those ourselves.

Until you delete your account

  • Your account, CV, profile, jobs and documents: until you delete your account, or until we delete an account that hasn’t been used for 6 months (see below). This includes the CV file you uploaded, your photo, your saved answers, your fit results, the PDFs of your documents, your application tracker and the records of forms the extension filled.
  • The profile snapshot each fit result and document was made from, so its citations stay accurate.
  • Your credit balance and the record of charges and refunds.
  • The record of each successful AI task (what kind of task, which model, how many tokens).
  • Feedback and fairness notes: until you delete your account. The copy of a feedback note in our team inbox is not deleted with your account (see “Feedback” below).
  • Email preferences and the date of your last follow-up reminder: until you delete your account.
  • Notes you send after an offer (or until you delete that application).

Purchase records

  • If you buy credits, we keep a minimal record of each purchase for 7 years from the end of the calendar year of the purchase, including after you delete your account, for our tax and accounting records and to deal with refunds and payment disputes. It holds Paddle’s ids for the purchase and payment, the pack, the number of credits, the amount and currency, the dates, and any refunds or chargebacks on it. It holds no name, email address, address or card details, and when you delete your account its link to your account is removed. Then it is deleted.
  • Records of payment problems (for example a payment we could not turn into credits, or a refund we could not fully apply) hold the same kind of ids and amounts, never your name or email address. We keep them for 7 years from the end of the calendar year they were raised in, including after you delete your account, and their link to your account is removed when you delete it.
  • The details of each “credits added” note we email you (the pack, credits, amount and date, used to resend the note if sending fails): until you delete your account.
  • Paddle keeps its own records of your purchase, for as long as its privacy notice says.

The waitlist

  • Waitlist sign-ups you never confirm: 30 days, then deleted automatically.
  • A confirmed waitlist address: until launch, or until you remove yourself with the link in any waitlist email. At launch we email confirmed addresses once with your invite, then delete the whole list within 30 days.
  • The copy of a confirmed sign-up in our team inbox: kept until the waitlist closes at launch, then deleted. If you ask us at privacy@taqdim.app, we delete it sooner.
  • Your sign-in account at Clerk. Your sign-in sessions expire on their own, and you are asked to sign in again.

Deleted automatically, sooner

  • Profile snapshots that no fit result or document uses any more (for example the earlier one, after you answer a fit report’s questions): within 2 days.
  • The draft we extract from your CV for you to review: 30 days after upload, once you have applied it to your profile or discarded it (if you do that later, the draft is cleared then). The CV file itself stays until you delete your account.
  • The record of an AI task that failed, including its error details: 30 days.
  • Records of visits to taqdim.app: 90 days.
  • Records of how the app is used: 90 days. The tq_session cookie expires 24 hours after your last activity.
  • Rate-limit counters: 7 days. This includes the waitlist’s and the website feedback form’s counters, and the daily count of free-credit grants per network, which hold only one-way fingerprints, never an email or IP address.
  • Security log: up to 365 days.
  • Accounts that aren’t used for 6 months are deleted automatically, with everything in them, exactly as if you had deleted the account yourself. We email you 30 days before; signing in once keeps your account. If our warning email can’t be delivered, we try again monthly; after three failed attempts the account is deleted. An account that still holds credits from a purchase is never deleted for inactivity, and we send it no deletion notice.
  • After you delete your account we keep a one-way fingerprint (not your email or name) for 90 days, so a delayed sign-in cannot recreate your data; then it is deleted too. If your account received the free starter credits, we keep the fingerprint of your email address that limits them to one per person while your account exists and for 90 days after it is deleted (by you, or by us for inactivity), so the same address can’t claim them again; then it is deleted automatically. If you answered the exit survey, we keep that answer for 12 months from the month you left, then delete it. If you want it deleted sooner, email us with the month you left; we’ll delete it if we can still tell which answer is yours.

Feedback

  • Feedback sent without an account (from the website, or from the app while signed out): there is no automatic time limit yet. We keep it while it helps us improve Taqdim, and delete it if you ask us at privacy@taqdim.app.
  • The copy of each feedback note in our team inbox, including a reply address you typed: not deleted automatically, and not removed when you delete your account. We delete it if you ask us at privacy@taqdim.app.

Quotes we ask you to approve

  • If you approved a quote for publication, we keep your approval email, and any withdrawal, for 12 months after the quote comes down, as a record of your consent, including after you delete your account.
  • If we asked you to approve a quote and it is never published (you say no, you don’t reply, or we decide not to use it), we delete that email exchange within 30 days of dropping the quote.

Kept by our providers

  • Database backups: our database provider, Neon, keeps a restore history of up to 6 hours, so anything we delete, including a deleted account, can remain in that history for up to 6 hours.
  • Encrypted backups: we keep encrypted backups of our database for up to 30 days, then delete them, so a deleted account can remain in an encrypted backup for up to 30 days. They are stored with Cloudflare. If we ever restore from a backup, we delete again every account that was deleted after that backup was taken, so a deleted account never comes back.
  • Server logs: Vercel keeps our server logs for 1 hour. We design our logs not to contain your CV, profile or documents.
  • Emails we send: Resend keeps each email and its delivery log for 30 days.
  • AI processing: Cloudflare does not keep your prompts or the AI’s answers after the request.
  • App usage records sent to PostHog, if that connection is on: kept by PostHog under the retention settings of our PostHog project.
  • Issue reports sent with “Report an issue”: kept in our private GitHub repository; email us to have yours removed.

Your rights

You can ask to access, correct, export or delete your personal data, and you can withdraw your consent at any time. You can delete your account yourself from your account settings: this permanently removes your profile, CV file, jobs, documents, feedback notes, email preferences and credit history in one step, except the fingerprint of your email address that limits the free starter credits to one per person (kept for 90 days), an exit-survey answer if you gave one, the copies of your feedback notes in our team inbox, emails about a quote we asked you to approve, and the minimal records of credit packs you bought and of any payment problems (see “How long we keep it”). Copies held by our providers expire as described in “How long we keep it”. You can turn off the “report ready” and reminder emails at any time, as described in “Why we use it”, and leave the waitlist at any time with the link in any waitlist email. For anything else, email us and we will respond within 30 days, or sooner if the applicable law requires it.

These rights apply under the data protection laws that cover you, including Egypt’s Personal Data Protection Law (Law 151 of 2020), Saudi Arabia’s Personal Data Protection Law, and the UAE’s Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data.

Security

Data is encrypted in transit (HTTPS) and at rest by our providers. Access is limited to what is needed to run the service. Card and other payment details go only to Paddle’s checkout, never to our servers. No system is perfectly secure; if a breach affects your data, we will notify you and the relevant supervisory authority without undue delay and within any fixed window the applicable law sets.

Children

Taqdim is for people aged 18 and over. We do not knowingly collect data from children.

Changes

This is a beta policy and it will change as Taqdim grows. We will post the new version here and tell you by email about any important change.

Contact

Bassam Tantawi, data controller
Email: privacy@taqdim.app