Privacy Policy

AiQlick is an AI-assisted recruitment platform. Employers and recruitment teams use it to post roles, manage candidates and collaborate; job seekers use it to build a profile, see how they match open roles, and apply.

This policy explains what personal data we process, why, and what you can do about it. For anything covered here, contact us at support@aiqlick.com.

Controller

[to be confirmed]

Registration number

[to be confirmed]

Registered address

[to be confirmed]

Contact

support@aiqlick.com

Data Protection Officer

Not appointed. Privacy questions go to the contact address above.

What we hold depends on how you use the platform. In outline:

Account data

Name, email address, password (stored only as a hash, never in readable form), and optionally a phone number, profile photo and display preferences. Your age group as you told us (18 or older, or 16 or 17) and when you answered. We do not ask for your date of birth. If a birth date was saved on your account earlier, for example read from a CV you uploaded, we keep it until you delete it from your profile (“Birth date (saved earlier)”, then Delete). It is never shown to companies and never used by AI or matching. Which version of these terms you accepted, and when.

CV and profile data

Any CV you upload and the information our AI extracts from it — work history, education, skills and proficiency, languages, certifications — plus what you add yourself: salary expectations, availability, location and job preferences. If you choose to enter your gender, companies see it only if you turn on “Show gender to companies”; it is off by default.

Application data

The roles you apply to, your salary expectation and motivation for each, your stage in the employer's pipeline, match scores with their AI confidence and requirements checklist, interview records and any notes an employer adds about you. If a company offers your profile for another company's job on the job market, a record of that submission: the score and AI confidence at the time, and whether you were asked first or told.

Meeting and notice records

For meetings on the platform: which transcription notices were shown or sent to whom, when, in which language and how (invitation email, join screen, in the meeting); when transcription was started or stopped and by whom; and requests to stop transcription, with the organiser's answer and reason. Where transcription is on, the transcript and the AI meeting summary. For the job market: the notice sent to a talent who was submitted without being asked first, and any objection. For AI models outside the EU: that you saw the notice, for which model and when.

Employer and CRM data

Company details, team members and their roles and permissions, and business contacts recorded in the CRM, including clients, partners and collaborating recruiters.

Communications

Messages and conversations sent through the platform, notifications, and — where you use the built-in video meetings — meeting records and, if transcription is enabled for that meeting, a transcript.

Billing data

Subscription and plan, credit balance and credit transactions, a log of AI operations for invoicing, and invoices. Card details are entered on Stripe's own checkout and are never sent to or stored by us.

Technical data

Server logs needed to run and secure the service, including IP address, timestamps and error diagnostics.

A CV can contain more about you than the role requires, and sometimes more than you intended — health information, for example, or details that reveal ethnicity or beliefs. We do not ask for special categories of data and we do not use them for matching. Please avoid including them.

To provide the service — performance of a contract

Creating and running your account, parsing CVs you upload, producing match scores, running pipelines and interviews, delivering messages and notifications, and processing payments.

To keep it working and secure — legitimate interests

Diagnosing faults, preventing abuse and fraud, maintaining backups, and improving how the product works. We do not sell personal data, and we do not use your CV to train third-party AI models.

To meet legal obligations

Retaining invoices and accounting records for the periods tax law requires.

Age check, terms record and notices — [legal basis: confirm with counsel]

Asking your age group when you sign up, or at your next sign-in if you already had an account, so that nobody under 16 uses AiQlick; keeping a birth date saved earlier until you delete it; recording which version of the terms you accepted; telling a talent when they were sent to another company's job without being asked first; and recording that you saw the notice when you picked an AI model outside the EU.

With your consent

Optional communications, and any processing we ask you about separately. You can withdraw consent at any time without affecting what was lawful beforehand.

When you apply to a role, or an employer adds you to their talent database, that employer can see your profile, CV and application. Employers using shared talent lists or collaborating with partner recruiters can share your profile onward within the platform. You control profile and CV visibility from your account settings, and you can see and revoke shares you have granted.

Beyond that, we use a small number of processors to run the service. Each is bound by a data processing agreement and may only act on our instructions:

CorePress — Denmark

The server the production platform runs on: the application and its database.

Amazon Web Services — Sweden (Stockholm)

File storage (CVs, documents, images) and Amazon Bedrock, which runs the AI models behind document reading, matching, the assistant and writing help. AWS can serve these AI requests from its other EU regions.

Amazon Web Services — Ireland

Speech-to-text for meeting transcripts, only when transcription is turned on for a meeting.

Amazon Web Services — outside the EU (worldwide routing)

Only if you or your team pick Claude Fable 5.1 or GPT-6 Astra (or Kimi K3, once it is offered). What you send to those models can be processed in AWS regions outside the EU, for example the United States. Transfer basis: [transfer basis — confirmed by counsel]. Companies can switch these models off with the EU-only setting.

Self-hosted infrastructure — Sweden [confirm: Sweden or Denmark]

Our support system, our internal observability and our in-house document parser run on infrastructure we operate ourselves.

Stripe — Ireland, with transfers to the United States [confirm with counsel]

Payment processing and card handling. Stripe acts as an independent controller for payment data under its own privacy policy.

Google — Ireland [confirm with counsel]

Only if you choose to sign in with Google. We request the minimum scopes — your OpenID identifier, email address and basic profile — and nothing else.

Email delivery — one.com, Denmark [confirm with counsel]

Delivers transactional messages such as verification links, password resets, invitations, reminders and job market notices.

We may also disclose data where the law requires it, or to establish or defend legal claims.

The production platform runs on the CorePress server in Denmark. Files you upload are stored with Amazon Web Services in Stockholm, Sweden, and the AI models we use by default are reached there too; AWS can serve those AI requests from its other EU regions. Speech-to-text for meeting transcripts runs with Amazon Web Services in Ireland. Our support and observability systems run on infrastructure in Sweden [confirm: Sweden or Denmark].

One exception: two optional AI models, Claude Fable 5.1 and GPT-6 Astra, are only offered by AWS through worldwide routing, so what you send them can be processed outside the EU, for example in the United States. They are marked “Outside the EU” wherever you pick a model, a short notice opens when you pick one, and a company can turn them off for everyone with the EU-only setting. Transfer basis: [transfer basis — confirmed by counsel].

If you sign in with Google, Google processes your sign-in under its own terms and transfer mechanisms.

We keep personal data for as long as your account is active and you are using the service. When you delete your account we delete the personal data associated with it, other than records we are legally required to retain — invoices and accounting records in particular, which are kept for the statutory period and then removed.

Data an employer has separately recorded about you — an application you submitted, or notes made during a hiring process — sits in that employer's workspace, and they act as controller for it. If you want it removed, contact them directly; you can also contact us and we will pass the request on.

AI records about a candidate in a hiring process — match scores with their AI confidence and requirements checklist, AI interview reports and meeting summaries, and job market submission records — are kept until two years after the job closes, and then deleted.

Meeting transcripts, AI meeting summaries and the meeting notice and transcription records are kept for [confirm retention period]. They are deleted with the meeting, and an organiser can delete a meeting's transcripts and AI insights before then.

Backups roll off on their own schedule, so deleted data can persist in a backup for a short period after removal from the live system.

Under the GDPR you have the right to:

• Access the personal data we hold about you, and receive a copy.
• Have inaccurate data corrected, and incomplete data completed.
• Have your data erased. You can do this yourself — deleting your account from your profile settings removes your account and its associated personal data.
• Restrict how we process your data, in the circumstances the GDPR allows.
• Receive your data in a portable, machine-readable format, and have it transmitted to another provider where technically feasible.
• Object to processing carried out on the basis of our legitimate interests.
• Withdraw consent at any time, where consent is the basis we rely on.
• Complain to your national data protection supervisory authority.

To exercise any of these, write to support@aiqlick.com. We will respond within one month, and will tell you if we need longer because the request is complex.

We use AI in these ways:

• Reading documents: extracting structured information from a CV or job description you upload, so it does not have to be typed in by hand. You can review and correct everything it extracts.
• Match score: a number from 0 to 100 for how well a profile's skills and work experience fit a job. It is the one score we show for a job match, wherever it appears.
• Requirements checklist: practical requirements — location, salary, availability, languages, job type, remote or hybrid working and driving licence — are checked separately and shown as a checklist next to the score. They never change the score; a requirement the employer marks as essential can change the recommendation the employer sees.
• Job market: when a company offers its talents for another company's public job, talents are grouped and suggested by the same match score. If a talent is sent without being asked first — because their account was never activated, or they are on the submitting company's team — we tell them by email at once (team members also in the app), with a link to object. An objection withdraws the submission. When a company asks the assistant to rank talents for a job, it ranks them by the same score, says so, keeps talents with a lower score or no score in the list, and shows the AI confidence for each.
• Writing help: AI can draft or rewrite text such as job descriptions, CV sections, messages and motivations. We store a marker with that text saying it was AI-generated, by which model and when, and the marker is kept in the file details of exported PDF CVs. The author sees an “AI-assisted” tag until they edit the text themselves. Recipients of a message the assistant drafted see no label, and emails it drafted carry the marker in a technical header.
• Assistant: the AI assistant answers questions and suggests actions. It never sends a message or changes anything by itself. Every message it drafts and every change it proposes — to a candidate, a talent, a job, a meeting, team members, roles or company settings — waits as a card until a person at the company approves it, and the activity log records who approved or declined it. It proposes rejections one candidate at a time.
• Meetings and interviews: when transcription is turned on, AI writes a meeting summary and, in an interview, a report for the employer showing the evidence for each of the job's requirements. The section “Meeting transcription and AI interview reports” below explains how this works and how to object.
• Interview practice and feedback: AI practice interviews you start yourself, and, where the employer allows it, a private coaching report on your own interview answers that you choose to buy with your own credits. Both are private to you: employers never see them, and they never affect your match score.

Every AI result we show a person comes with the AI's confidence — High, Medium or Low, with a one-line reason drawn from the evidence, for example that the job has no parsed skill requirements. Confidence describes how much the AI had to go on; it is never a rating of you.

A score is not a decision. Employers can set a minimum match for a job; if your score is below it you can still apply, and the employer sees that your profile is below their minimum. No application is rejected automatically: every decision about your application is made by a person at the employer, and no offer, rejection or shortlist is issued on the strength of a score alone. Any match can be opened to see how skills and work experience contributed and how much each counted.

By default every AI model we use runs in the EU. Two optional models, Claude Fable 5.1 and GPT-6 Astra, run outside the EU through AWS worldwide routing, for example in the United States. They are marked “Outside the EU” in every model picker, a short notice opens when you pick one, and we record that you saw it. Companies can switch them off for their whole team. Transfer basis: [transfer basis — confirmed by counsel].

If you are 16 or 17, you can create a profile, be matched and apply like anyone else, but when a company interviews you, we never produce an AI interview report about you: no insights, scores or summaries are generated from that interview, and the company is told why. Interview practice you start yourself is not affected.

If you believe an automated score has been applied to you unfairly, contact us and we will explain how it was reached and route your concern to the employer responsible for the decision.

A meeting on the platform may be transcribed. When the organiser turns transcription on, everyone in the meeting is told, on the join screen and in a notice that stays visible while it is on, and what is said is transcribed. The invitation email says so in advance.

AI uses the transcript to write a summary and, in an interview, a report for the employer on how the answers cover the job's requirements, with quotes. The interviewer may also see AI suggestions during the interview. The AI does not rate anyone as a person and makes no decision: people at the employer decide.

The employer that organises the meeting relies on its legitimate interest in documenting the meeting and assessing the answers against the job, not on your consent. You are told, not asked. The employer is responsible for this processing and for its own assessment of whether it is justified.

You can object. Tell the organiser, or use “Ask to stop transcription” in the meeting. A person at the employer decides whether transcription continues, and you are told the answer. You can also object afterwards by contacting the employer, or us, and we will pass it on.

AI interview practice is different: it is something you start yourself, and it still asks for your consent before it begins. You can withdraw that consent at any time.

Traffic to the platform is encrypted in transit. Passwords are stored only as hashes and cannot be read back by us or by anyone else. Access inside a workspace is governed by role-based permissions, so colleagues, clients and partner recruiters see only what their role allows. Payment card details never reach our systems.

No system is perfectly secure. If a breach occurs that is likely to result in a risk to your rights, we will notify the relevant supervisory authority and, where required, you.

AiQlick is for people aged 16 and over. When you sign up, and at your next sign-in if you already had an account, we ask whether you are 18 or older, or 16 or 17, and keep that answer and when you gave it. We do not ask for your date of birth. Nobody under 16 can create an account or continue to use one. If you believe someone under 16 has given us personal data, contact us and we will delete it.

If we change this policy we will update the date at the top of this page. Where a change materially affects how we use your data, we will tell you directly rather than relying on you noticing.