Privacy Policy

Candidates

• Account: name, email address, password (stored only as an Argon2id hash), interface language, and the identifier the provider returns if you sign in with GitHub, Google, LinkedIn or Telegram.
• Profile: photo, headline and summary, date of birth, location, citizenship and work permits, languages, work history, education, projects and publications, skills, salary expectations, preferred roles, locations, markets and working arrangements, and the contact channels you choose to add (phone, Telegram, WhatsApp, LinkedIn, GitHub, Hugging Face, X and others).
• Resume: a file you upload. We extract its text, use it to fill in your profile and then delete the file (section 08).
• Activity: jobs you save, hide or apply to, searches and filters you save, answers you give to application questions, messages you send to other users, and the settings you choose.
• Payments: the plan you buy and the payment status. Card or crypto details are entered on the payment provider's own page and are not received by us.

Employers and recruiters

• Name, work email, company, role, the jobs you publish, the candidates you shortlist, screen, message or add to a pipeline, and your notes about them.
• If you run an AI screening, the material you provide about the candidate (a GitHub or Hugging Face handle, a resume, a name). For that material you are the controller and we act as your processor (section 06).

A Gmail account you connect

Candidates who let Alion send job applications on their behalf can connect their own Gmail account, so that those applications leave from their own address instead of an Alion address. Connecting is optional and can be undone at any time.

• What we receive: your Gmail address, your Google account identifier and access tokens that allow one thing only: sending email from your account (the gmail.send permission). With this permission Alion cannot read, search, change or delete any of your email.
• What we use it for: only to send the applications you asked Alion to send for you, and a test email to your own address when you request one. For each email sent we keep the recipient, the time and the message identifier Gmail returns, in the email delivery log (section 08).
• What we never do: we do not sell data received from Google, do not use it for advertising and do not use it to train AI models. No person at Alion reads it unless you ask us to, it is needed for security, or the law requires it.
• How it is protected: the access tokens are stored encrypted (AES-256-GCM) on our servers in the EU, are never written to logs and are sent to no one but Google.
• How to stop it: press Disconnect next to the mailbox in your Alion account, or remove Alion's access at myaccount.google.com/permissions. When no part of your account uses the mailbox any more, we revoke the access at Google and delete the tokens; deleting your Alion account does the same.

Alion's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Everyone who writes to us

The content of your message, your email address and, for web forms, your IP address and browser user agent.

• Page views: IP address, browser user agent, the page and referring page, interface language and a random device identifier from a first-party cookie. Raw page-view rows are kept for about two days and then reduced to statistics without IP addresses.
• Bot detection: a small script reports whether the browser looks automated (for example, a webdriver flag). The result is stored with the IP address and device identifier for 30 days.
• Sign-in and security: sign-ins, new devices, password and email changes, with IP address and user agent.
• First visit source: the campaign, referrer or search term that first brought you to the site, kept in a first-party cookie and, if you register, copied to your account.
• API and MCP: for each call, the key or account, IP address, the tool and its arguments, the client name and the outcome.
• Browser extension: when you press Fill or report an outcome, the job, the application page address, the ATS, and counts and labels of the fields that were filled or missed.

We do not use third-party advertising or analytics tools. The cookies involved are listed in the Cookie Policy.

Much of Alion is about companies and jobs rather than people, but company and job data contain some personal data about people who have no Alion account.

• People at companies: names, job titles and roles (founder, executive, hiring contact) of people connected with a company, the source page, and where the source publishes them a work email address, telephone number or LinkedIn address. Sources: the company's own website (legal notice or imprint), public company registers (for example SEC Form D filings in the United States and national business registers), startup directories, public job portals on which an employer names a contact person for its vacancy, and edits made by the company's own representatives. Names and roles are shown with the company; a person's email address or telephone number is never shown or sold. The notice for these people is at People in Company Profiles.
• Company mailboxes: email addresses published on a company's website or in its job postings. Most are role addresses such as jobs@ or info@; some are named individuals' work addresses. To find a company's recruiting address we may also ask an AI search service, giving it only the company's domain.
• Job postings: the text an employer publishes, which can include the name or contact details of a recruiter or hiring manager.
• Sign-in providers: if you sign in with GitHub, Google, LinkedIn or Telegram, the provider sends us your name, email address, profile photo and account identifier, and for GitHub your public repositories, which we use to fill in your profile.
• Screenings: the public GitHub or Hugging Face activity of a candidate that an employer asks us to screen, including the names and public commit addresses of that candidate's co-authors, which appear only in the private screening report.

We do not create Alion profiles or accounts for people who have not signed up, with one exception: an AI screening creates a private record of the screened candidate that only the employer who ran it can see and that is deleted after 180 days.

We do not ask for special categories of data (health, religion, ethnic origin, political opinions, sexual orientation, trade-union membership, biometric or genetic data). Please do not put them in your profile or resume.

• Resume reading: the text of an uploaded resume is sent to an AI model to extract your work history, skills and other profile fields. You can edit everything it extracts.
• Profile descriptions: for candidates who connect GitHub or Hugging Face, AI models summarise public work into skill descriptions and an experience level shown on the profile.
• Matching: jobs are ranked for you by comparing your profile with each posting (role, skills, location rules, salary, level). The ranking decides what you see first, not what you may apply to.
• Tailored resumes: if you ask for them, an AI model writes a resume version and a cover letter for a specific job from your profile.
• AI screening for employers: an employer can ask for a report on a candidate's public work. The employer decides what to do with it. Registered candidates can refuse to be screened in Settings, under Privacy.
• Telegram assistant: replies in Telegram conversations are written by an AI model, which receives your name and the recent messages of the conversation.

Alion itself makes no decision about you that has legal or similarly significant effects based solely on automated processing. Hiring decisions are made by employers.

The AI models we use are listed in section 07. They receive the text needed for the task, not your whole account.

Service providers acting for us

Other recipients

• Employers you apply to: when you apply, the employer receives your application, your resume and the contact details in it, in your name and with your email as the reply address. If you connected your own Gmail account, the application leaves from that address.
• Other users: your profile is visible within the privacy settings you choose for each field. Employers on paid plans can open more of the list, download resumes and see the contact channels you allow.
• Business subscribers: paying business users can open a company's own role mailboxes, such as jobs@ or info@, and its main telephone number, up to a monthly limit per account. Each opening is logged. No one can open or buy a person's email address or telephone number.
• API, MCP and dataset users: they receive job and company data. These outputs carry no fields about individual people, and email addresses are removed from the posting text they include.
• Authorities and advisers: when the law requires it, to protect rights and safety, or to our professional advisers under confidentiality.
• A buyer of the business: if Alion is sold or merged, personal data would pass to the new owner under this policy, and we would tell account holders.

We do not sell candidates' profiles or share them with advertisers.

Deleting an account removes the profile and everything linked to it: files, messages, applications, matches, Telegram conversations, API keys and the logs that carry the account's identifier. What stays is listed above: payment records, the record of the request, the suppression hash and a single line saying that an account with that number was deleted.

We do not keep separate archives of the database. Server snapshots taken by our hosting provider, if any, are overwritten on its rotation cycle.

Our servers and database are in the European Union (Amsterdam, Netherlands). Some providers in section 07 process data outside the EEA. Where the GDPR applies to such a transfer we rely on the European Commission's Standard Contractual Clauses included in the provider's data processing terms, or on the EU-US Data Privacy Framework where the provider is certified.

Traffic is encrypted with TLS and HSTS. Passwords are stored as Argon2id hashes and session tokens as hashes, never in plain form. Sign-in is rate-limited and a new device is confirmed with a one-time code sent by email. Administrative access is limited to the founder and named staff. The site sends security headers that restrict framing, scripts and browser permissions.

No system is perfectly secure. If a breach puts your data at risk, we will tell you and the competent authority as the law requires.

You have the right to know whether we hold data about you and to get a copy (access), to have it corrected (rectification), deleted (erasure), limited (restriction) or given to you in a reusable format (portability), to object to processing based on legitimate interest, including profiling for that purpose, and to withdraw any consent you gave. These rights apply whether or not you have an account.

• With an account: edit your profile at any time; choose who sees each field under Settings, Privacy; download your data under Settings, General, Your data; delete the account under Settings, General, Your data.
• Without an account (for example, if your name appears in a company's profile): see People in Company Profiles and write to [email protected] with the page address, or use the removal request form.
• Anything else, including a full copy of everything we hold about you: write to [email protected].

We answer within one month. If a request is complex we may extend this by up to two more months and tell you why. We may ask you to confirm that the request comes from you, usually by replying from the email address concerned. Requests are free unless they are manifestly unfounded or excessive. More detail is on the data subject request page.

• Account emails (confirmations, security notices, replies from employers, application status) are part of the service. You can switch individual notification types off under Settings, Notifications.
• Marketing email is sent to account holders only with consent, which you can withdraw under Settings, Notifications, or with the link in any such email.
• Emails to companies go to published business addresses. Each one carries an unsubscribe link; after you use it, that address is not written to again.
• Telegram: if you add a Telegram username to your profile, our assistant may start a conversation about your profile and matching jobs. Remove the username or write to [email protected] and it will not write to you again.

We use a small number of first-party cookies, for sign-in, security, language and to count returning visitors and their first source. Each one, its purpose and its lifetime are listed in the Cookie Policy.

The Services are for people looking for work or hiring, and are not meant for anyone under 16. We do not knowingly collect data from children. If you believe a child has given us personal data, write to [email protected] and we will delete it.

When the way we handle personal data changes, we update this policy and the date at the top. If a change materially affects account holders, we tell them by email or on the site before it takes effect.