The small print, in plain English
Privacy Policy.
Effective date: 16 November 2026 · Version 1.1
PAN AU PTY LTD, trading as Axion Jobs (we, us, our), operates Axion. This policy covers our website, waitlist, support, application, browser-assisted features and trial, beta and early-access testing. Privacy requests and security reports can be sent to [email protected].
You do not need to join the waitlist or provide a résumé to browse this website. Using the application involves additional processing described below. A demonstration does not itself give us permission to connect your accounts or submit applications.
1. Information we collect
- Website and waitlist: your email address, signup and unsubscribe information, and optional survey answers about roles, location, application frequency and difficulties.
- Support and testing: your name, contact address, messages, feedback and relevant diagnostic information you provide or that is recorded while resolving a problem.
- Account and profile: sign-in and account identifiers, preferences, location, target roles, salary expectations, availability, work rights and information you choose to provide about your job search.
- Documents and answers: résumés, cover letters, education and employment history, skills, uploaded files, application answers, edits and generated document versions. These can include contact details and referee information.
- Job-search activity: listings, matches, scores and reasons, followed employers, saved and dismissed jobs, application status, approvals, questions, receipts and records of browser actions.
- Connected sessions: browser cookies and session information, account credentials used for supported job-site workflows, and relevant page content, form values, screenshots and verification or receipt information.
- Technical information: IP address, browser and device information, request and error records, security events, timestamps and, if enabled, push-notification endpoints and subscription keys.
We collect information directly from you, from the browser and accounts you authorise us to use, from publicly accessible or authorised job sources, and from service providers involved in those interactions. If a paid plan is introduced, its payment notice will identify the processor and information required before checkout; do not send payment details through support.
2. Why we use it
We use information to provide access, discover and assess jobs against your preferences, prepare and edit documents, answer questions, operate requested browser tasks, record your approvals and track application outcomes. We also use it to respond to support requests, diagnose failures, secure the service, prevent abuse, manage billing where offered and meet legal obligations.
We use optional feedback and survey answers to improve the product. We do not sell your personal information, rent your résumé, operate an advertising data marketplace or use your application content for targeted advertising. We do not use your private application content to train our own general-purpose AI models. Provider handling is explained separately below.
If you do not provide information needed for a feature, that feature may be unavailable or less accurate. You may leave optional questions unanswered. We do not treat use of Axion as permission to collect unrelated information.
3. Sensitive and third-party information
Job applications can reveal health or disability information, racial or ethnic origin, religious beliefs, union membership, criminal history and other sensitive information. We do not require this for a general profile. Avoid including it unless you intentionally choose a supported application workflow that requires it. Where required by law, we obtain your consent before collecting sensitive information; accepting the terms is not a substitute for that consent.
Review voluntary demographic questions yourself. Do not upload identity documents, tax file numbers, banking details or health records into general chat, feedback or contact forms. Remove unnecessary personal details from résumés and screenshots. Obtain appropriate permission before providing referee or other third-party details, and tell those people how their details will be used.
4. AI processing and matching
Axion’s production service uses Anthropic’s Claude API for AI tasks, including job interpretation, matching, drafting and browser assistance.
Depending on the task, Anthropic receives résumé or profile content, preferences, job descriptions, questions and answers, document text, browser page content, screenshots and relevant verification messages. Derived matching information, including scores and reasons, is treated as personal information where it relates to you.
Processing is not confined to your device. Anthropic’s handling of API data is governed by the applicable commercial terms and data-processing arrangements. Provider-side retention, abuse monitoring and any authorised access depend on those arrangements. Contact us before providing confidential material if you need confirmation of the arrangements for your test or account.
AI helps you decide what to pursue; Axion does not make an employer’s hiring decision. Matching can be wrong or reflect bias, and you can review, dismiss or correct its suggestions. Ask support if you want to question a result or correct the underlying profile.
Provider information: Anthropic privacy.
5. Browser, job-site and email access
Browser assistance can read the content of pages it uses, enter information, upload documents and interact with the job sites you authorise. Connected sessions may remain signed in between tasks. The current testing workflow uses a connected browser; a browser extension is not a prerequisite or a security guarantee.
If you enable email-assisted verification or receipt checking by connecting a Gmail session, Axion searches recent messages for the relevant code or application confirmation. Message-list entries can include unrelated senders, subjects and snippets; these may be processed to identify a match. A selected verification message’s content may be sent to AI to extract a code. This feature is intended to read codes and receipts, not to compose, send, forward or delete mail. It is browser access to a signed-in mailbox, not a guarantee of narrowly scoped mailbox permissions.
Do not connect a mailbox or browser profile containing information you are not comfortable making available to the workflow. You can leave email assistance disconnected and handle verification manually where supported. Revoke external sessions directly to end their access; contact support to remove retained session material.
Application forms may transmit answers or documents as you type, upload or move between steps, even without final submission. Final submission requires separate approval, but preparatory work is still processing and disclosure to the relevant job site. Employers and their recruitment systems handle what they receive under their own notices; they are not merely storing it for Axion.
6. Who receives information
We disclose information only where needed for the purposes in this policy, where you direct us, or as permitted or required by law. Recipients include:
- Infrastructure and security providers: hosting, application storage, network delivery, access protection and diagnostics. Cloudflare hosts the public site and provides Turnstile form protection.
- AI provider: Anthropic, for the Claude API tasks described above.
- Email: Resend receives waitlist addresses, optional survey answers and sends contact messages to our support mailbox.
- Website analytics: Umami counts page visits and waitlist signups on the public site without cookies. It receives your IP address and browser details to estimate your country and device, and does not store your IP address or use it to identify you. It never receives your email address or free-text answers.
- Application recipients: employers, recruiters, job boards and applicant-tracking systems involved in jobs you choose, including account and form preparation before final submission.
- Notification services: your browser or device’s push-delivery service, if you enable notifications.
- People providing support: authorised operators, contractors or advisers who need relevant information to operate, troubleshoot or protect Axion, under appropriate confidentiality obligations.
We may disclose information to comply with a lawful request, protect a person’s safety, investigate misuse or establish or defend legal rights. If the business is transferred, information may transfer as part of that transaction under appropriate confidentiality and privacy safeguards; we will notify you of a material change in who handles your information.
See also Cloudflare’s Privacy Policy, Resend’s Privacy Policy and Umami’s Privacy Policy. Third-party links have their own privacy practices.
7. Overseas processing
Information may be stored, routed or processed outside Australia. Our providers include US-based businesses and global infrastructure networks, so overseas recipients are likely to include the United States. Other locations depend on the provider, its subprocessors, routing and the employer or job platform you use. We do not promise Australian-only storage or processing.
Ask us for the current arrangements if location is important to you. Where Australian Privacy Principle 8 applies, we take the reasonable steps it requires in relation to overseas recipients, subject to applicable exceptions. We do not rely on this policy as a blanket waiver of responsibility for overseas disclosure.
8. How we protect information
Production accounts: user workspaces are isolated, with access rules that restrict users to their own information. Account passwords are hashed rather than stored in a recoverable form. Protected stored user content is encrypted using keys derived from your password. Public connections use HTTPS. These protections apply to the released production service; pre-release invitations must make clear if the environment differs. Do not use a shared demonstration for private documents or personal account connections.
Processing and recovery: password-derived encryption protects stored content; it does not mean Axion processes everything without access to readable information. Authorised tasks require relevant information to be read and sent to the processors or recipients described in this policy. Password hashing for Axion sign-in is different from storing a usable credential or browser session for a connected job site. Connected credentials and sessions need protection as secrets. Recovery options for encrypted content depend on the available recovery mechanism; a sign-in password reset alone may not recover that content. Keep copies of important documents.
Application controls: final submission requires approval; submission attempts are recorded to reduce repeats. Browser controls check whether a destination belongs to the application before typing or uploading. The dedicated job-site password tool requires HTTPS and types the stored password without returning it in its tool response. These are safeguards, not a guarantee that page interpretation, third-party content or automation will never fail.
Website forms: server-side input and request-size validation, same-origin checks, Turnstile verification and rate limits help reduce abuse. Runtime form secrets are kept out of the public browser bundle. Security headers restrict framing and unnecessary browser permissions. These protections do not make an ordinary contact form suitable for passwords or identity documents.
Authorised support access may be needed for troubleshooting or security. No online service is risk-free. We do not claim independent security certification, a completed penetration test, end-to-end encryption of every workflow or that no operator or provider can ever access task content. Report concerns to [email protected]; do not include live credentials or other people’s data.
9. Cookies, browser storage and notifications
The public site remembers your colour preference in local storage. You can clear it in browser settings. Our website analytics do not use cookies or other storage on your device.
Cloudflare and Turnstile process technical signals including IP address and browser information to deliver and protect the site. Our form limiter stores a hash derived from IP address and minute, with a two-minute expiry; expired rows are removed on subsequent requests. This short-lived identifier is not a claim that the original IP is anonymous to infrastructure providers.
The public site does not include advertising pixels, third-party behavioural analytics or session-replay scripts. Necessary access, application and connected job-site sessions may use cookies and local storage. Clearing or blocking them may break sign-in or automation. The app’s service worker can retain application assets on your device.
Push notifications are optional and require browser permission. We store the subscription endpoint and keys to deliver them. Notifications can reveal job-search activity on a lock screen or shared device. You can turn them off in browser or device settings and ask us to remove the subscription. Disabling notifications does not close your account.
10. Retention and deletion
We keep information for as long as reasonably needed to provide your account and requested work, support you, maintain security and meet legal obligations. We consider whether your account remains active, the type of record, unresolved issues and applicable record-keeping requirements. There is no single automatic deletion period for every category of app data.
- Waitlist and messages: retained while relevant to updates or the enquiry; you can unsubscribe or request deletion. A minimal suppression record may be kept to respect an unsubscribe.
- Profile, documents and application history: retained to provide the service until removed or account closure is processed, subject to lawful exceptions.
- Diagnostic and browser records: screenshots, page captures, AI decisions, task events, receipts and error logs may contain personal information. They are retained for operation, investigation and support and are included in the scope of a deletion request.
- Sessions and backups: connected-session material and backup copies may outlast a live record. Backup schedules and provider retention differ; deletion from live systems is not a promise of immediate erasure from every backup or external service.
Deletion is currently a support-assisted process. Ask us to include your documents, derived profile and matching information, application artifacts, connected sessions, push subscriptions and relevant provider-held copies. We will verify your identity proportionately, explain the scope and expected timing, and tell you about material exceptions. We aim to respond within 30 days; that is a response target, not a guarantee that every backup is erased within that period.
We delete or de-identify information no longer needed, subject to legal requirements. Where a backup cannot reasonably be edited immediately, we restrict its use and remove deleted information again before returning restored data to ordinary use. Copies held independently by employers, job sites or services you connected are subject to their policies; you may need to contact them directly. Disconnecting an account, unsubscribing and deleting stored data are different actions.
11. Access, correction and your choices
You can review and edit information through available app controls, decline optional survey questions, disconnect accounts, stop requested work, decline push notifications and ask us to close your account. Email [email protected] to request access, a usable copy, correction or deletion, or to withdraw a specific consent. Tell us what you want changed; do not send identity documents unless we arrange a suitable verification method.
We may need reasonable proof that the request is yours. Access and correction are subject to lawful exceptions and other people’s rights. If we cannot meet a request, we will explain why and how you can complain. Withdrawing permission may prevent a feature from working and does not undo an application already sent or processing lawfully completed.
Waitlist signup authorises launch and early-access updates, not unrelated marketing. Use the unsubscribe link in those emails or contact support. We action marketing opt-outs within five working days and keep necessary service, security or legal messages separate from marketing.
12. Testers and children
The same privacy commitments apply to testers. Invitations should identify whether you are using a shared demonstration or a personal testing workspace and explain any differences from production protections. Use dummy data in shared demonstrations. If you are unsure, do not upload personal documents or connect accounts until support confirms the environment.
We may review relevant test records to investigate a failure. Do not include other people’s information in bug reports, and redact screenshots before sending them. We seek separate permission before using identifiable tester material in public marketing or demonstrations.
Axion is intended for people aged 18 and over. We do not knowingly invite children to create accounts. If you believe a child has provided information, contact us so we can investigate and remove it where appropriate.
13. Security incidents
If we become aware of a suspected breach, we investigate, contain it and assess the information and people affected. Where notification is required, we notify affected people and the relevant regulator with information about the incident and protective steps. Where the Australian Notifiable Data Breaches scheme applies, we take reasonable steps to complete a suspected eligible-breach assessment within 30 calendar days and notify as soon as practicable when required; the assessment period is not a reason to delay urgent protective action.
If you suspect your account or connected browser has been accessed, contact us promptly and revoke affected external sessions or change credentials directly with the relevant service. Do not wait for a support response to secure an account you control.
14. Privacy law and complaints
We handle information in accordance with the laws that apply to us. Australian Privacy Act coverage depends on the business and its activities; we do not claim that publishing this policy establishes statutory coverage, regulatory approval or certification. Our stated privacy commitments apply to our service regardless. We do not represent that Axion is certified compliant with every international privacy regime.
To complain, email PAN AU PTY LTD, trading as Axion Jobs, at [email protected] with the issue and outcome you seek. We aim to acknowledge within five business days and respond within 30 days, or explain a delay. If unresolved, you can contact the Office of the Australian Information Commissioner, which can advise whether it can consider your complaint. Other rights or regulators may apply where you live.
Further information: the OAIC’s guidance on Australian Privacy Principles, small-business coverage, overseas disclosures and data-breach notification, and the ACMA’s email marketing rules.
15. Policy updates
We publish the current policy here with its version and effective date. We will notify existing users of material changes through the app or email before they apply where practical, and obtain consent where a new use requires it. A policy update does not retrospectively authorise unrelated use of information already collected. You can request a copy of the version that applied when you joined.