Privacy Notice

Updated: 18 October 2026

Introduction

Job Clerk Ltd is responsible for the personal data described in this notice. It covers jobclerk.com and the Job Clerk mobile app, including its UK & Ireland and Germany markets. Contact us at hello@jobclerk.com. For the German website and its account services, also see the German privacy notice.

Data Collection

We collect personal information that you provide to us when creating an account, using our services, or interacting with our website. This may include, but is not limited to, your name, contact details, resume, employment history, and any other information pertinent to aiding your job search.

Google sign-in

Google sign-in is optional. When you choose Continue with Google, Google shares your name, email address, email verification status, profile picture and Google account identifier with Job Clerk. We use these details to create your account or connect your sign-in to an existing account after verifying ownership.

We store the Google account identifier with your account and remove it when your account is deleted. Google access, refresh and ID tokens are used to complete sign-in and are not retained in our account database. We request no access to Gmail, contacts or Google Drive. Google's handling of your data is described in its Privacy Policy.

Sign in with Apple

When you use Sign in with Apple in the iPhone app, we store your Apple account identifier and the email address Apple provides to create or connect your account. We store an encrypted Apple authorization token so we can revoke that authorization before deleting your account. The token is then deleted with the account. Identity tokens and one-time authorization codes are not retained.

For Job Clerk Germany, see the Datenschutzerklärung für Job Clerk Deutschland.

Data Usage

Your data is used to personalize and improve your experience with Job Clerk. Specifically, we use your information to:

  • Create and manage your account
  • Provide you with job recommendations
  • Generate personal statements using Large Language Models

AI features send the relevant profile, document or application content to model providers to produce the requested result. This processing is separate from product analytics. Where My Match is available, it sends professional experience and qualification facts from your existing profile with job criteria to OpenAI to generate a match assessment. The assessment is saved to your account. It is guidance for you, not an employer hiring decision.

Some website offers involve partners such as Medical Protection Society. The offer explains the recipient and information involved and asks for your consent where required. Signing in to the mobile app does not itself opt you into partner marketing. When you follow an employer's application link, that external website handles your application under its own privacy notice.

Mobile app

On supported Android and iPhone versions, you can create a UK & Ireland account and buy an access pass through Google Play or Apple, or sign in with an existing account. Your selected market determines which Job Clerk service receives account requests: jobclerk.com for UK & Ireland and jobclerk.de for Germany. The accounts are separate. We process your email, authentication and session information, account ID and profile details to sign you in and provide account features. Access purchased on the website, through Google Play or through Apple works with the same UK & Ireland account.

Google Play purchases

Google processes Android in-app payments. Job Clerk does not receive your card details. We send Google an opaque account reference to associate a purchase with your Job Clerk account. We receive and store the purchase token, order identifier, pass and plan identifiers, purchase status and access dates. We use these records to verify purchases with Google, provide and restore access, prevent a purchase being claimed by another account, and process expiry, refund and other payment updates. Google sends purchase-status notifications to our backend. Payment records may be retained where needed for accounting, fraud prevention or resolving disputes, as described below.

Apple purchases

Apple processes iPhone in-app payments. We do not receive your card details. We send Apple a random account reference to link the purchase to your Job Clerk account. We store the transaction identifier, product, price, currency, access dates, payment environment and purchase or refund status. Our backend verifies these details with Apple to provide and restore access, prevent duplicate grants or use by another account, and handle refunds. Apple sends signed purchase-status notifications to our backend. Sandbox transactions are marked separately from production purchases. Payment providers may retain records for their legal obligations after your Job Clerk account is deleted.

Searches and selected filters are sent to our service to return matching jobs. Saved jobs, saved searches and application status changes are associated with your account. Feedback sends your message, optional reply email, operating system and app version information to our support service. Do not include patient data or other sensitive information in feedback.

Product analytics

We use PostHog's EU service to understand app usage and diagnose problems. Events include app opens, screen views, search and filter actions, result-count ranges, save actions, sign-in outcomes, purchase and restore outcomes, and notification actions, with app/build versions and technical outcome codes. The mobile analytics events do not include raw search text, feedback text, passwords, email addresses or CVs. Session replay and automatic screen recording are disabled.

We process product analytics on the basis of our legitimate interests in understanding use of our service, diagnosing faults and improving reliability. You can object to this processing by contacting hello@jobclerk.com.

UK analytics can be linked to your account ID and include approximate location derived from your network IP address. This is not GPS location; the app does not request device location permission. The UK project discards stored raw IP addresses after processing. German analytics does not use your account ID and uses PostHog's cookieless processing to estimate usage. When you tap a push notification in either market, we record an opaque delivery ID and the time the app handles the tap. The delivery ID can be linked to our sending records to identify the intended recipient and target phone. This helps us understand which alerts are opened and investigate problems. It does not tell us when the notification appeared on your phone. Connection data still reaches the service. Analytics is currently enabled by default with no in-app opt-out switch. Contact us to object to this processing or request deletion of identifiable analytics.

Job-alert link tracking

Links in job alerts record redirect requests, the intended recipient, browser information and approximate location. To investigate automated traffic and shared links, we also record a protected network-address identifier that changes daily and is scoped to the intended recipient, the network provider, and bot or preview indicators. We do not store raw IP addresses in these click records. When a link opens a Job Clerk job page while you are signed in, we may record your account as the observed viewer. Network identifiers, network-provider details and observed-viewer records are cleared after seven days by a cleanup task that runs every 15 minutes. Clicks and these indicators do not by themselves prove who shared a link.

Notifications and updates

If you enable push notifications, we register an installation identifier and push token to deliver alerts through Expo and Google's Firebase Cloud Messaging on Android and Apple's Push Notification service on iOS. These providers process the token and notification payload, such as alert text and the job link. You can turn off job alerts in the app and notification permission in your phone settings. Turning off delivery does not itself delete your account or historical delivery records.

Installation identifiers also help protect our service against excessive requests. Expo's update service receives connection, platform and app/runtime version information when checking for compatible app updates. Local session credentials are kept in protected device storage. Requests to our services use HTTPS. The app does not use the Android Advertising ID.

We use service providers for hosting, storage, email, analytics, AI processing and notification delivery, including Vercel, PlanetScale, Cloudflare, Resend, PostHog, OpenAI, Expo and Google. They process relevant service data on our behalf. See PostHog's privacy information, Expo's explanation for app users, and Firebase's privacy information.

Your Rights Under UK GDPR

As per the UK General Data Protection Regulation (UK GDPR), you have the following rights:

  • The right to be informed about the processing of your personal data
  • The right to access your personal data
  • The right to rectification if your personal data is inaccurate or incomplete
  • The right to erasure of your personal data in certain circumstances
  • The right to restrict or object to the processing of your personal data
  • The right to data portability
  • Rights related to automated decision-making including profiling

Data Protection Measures

We strive to protect your information with the utmost care and take substantial measures to ensure its security:

  • Implementing industry-standard data security protocols
  • Regularly reviewing and updating our data protection practices
  • Minimizing data collection to what is strictly necessary
  • Providing transparency about how your data is used

Data Storage

Our services use infrastructure in the UK, the European Union and other countries. PostHog EU stores analytics in Frankfurt, Germany; notification and other providers may process data in the United States and elsewhere. Data does not stay exclusively in the UK or Ireland. Where international-transfer safeguards are required, the applicable provider agreements govern those transfers. Contact us for information about the safeguards applicable to your data.

Data retention

Account records, saved work, profile information and stored files are kept to provide your account services until you remove them or delete the account. Push registrations and delivery records support notification delivery and troubleshooting; disabling notifications stops delivery but is not a deletion request.

Analytics, support correspondence, provider logs and backups are separate from the live account database. PostHog's event-retention window depends on the project plan and whether retention is enforced; it is not an account-deletion mechanism. See its event-retention rules. OpenAI may retain API content in abuse-monitoring logs, normally for up to 30 days under its default API controls, with exceptions for legal or security needs. Retention depends on the feature and service configuration; see its API data controls. These separate records are not automatically erased by deleting your Job Clerk account; use the data-deletion request below.

We retain support and security records while needed to handle the request, investigate abuse or resolve disputes, and records required by law for the applicable legal period. Contact us to request deletion or the retention details for a specific record.

Account and data deletion

You can request deletion of your Job Clerk account and personal data without installing the app. Germany and UK & Ireland use separate accounts. Tell us if you want both deleted.

Request deletion by email

Email hello@jobclerk.com from your account email address with the subject “Job Clerk account deletion”. Specify UK & Ireland, Germany, or both. You can also request deletion of particular data, such as feedback or identifiable analytics, without deleting your account. We may need to verify account ownership. Never send your password or a sign-in code.

We normally respond within one month. If more time is permitted and needed for a complex request, we will explain the reason and timing.

Delete through your account

  • UK & Ireland: sign in at jobclerk.com, open Settings → Account, and select “Email me a deletion code”. Enter the emailed code while still signed in and confirm “Delete my account permanently”.
  • Germany: sign in at jobclerk.de, open Einstellungen, select “Konto löschen”, and confirm with your current password. If you cannot use this method, use the email request above.
  • Android app: select the relevant market, sign in, and open Profile → Delete account (Profil → Konto löschen in German). Follow the email-code or password confirmation for that market.

What is deleted or retained

Deletion permanently removes the selected market account, sign-in sessions, saved jobs and searches, application tracking, profile data and account-linked stored files. UK deletion also cancels recurring subscriptions. It applies to the website and app account together. Uninstalling the app does not delete your account or cancel a subscription.

Feedback emails and analytics are held separately from the account database. Account deletion alone does not automatically erase those separate records. Include them in your email request so we can identify and address them. We may be unable to link anonymous analytics to you. Public employer and vacancy information is not your account data and is not removed by account deletion.

Restricted backup copies may remain until the backup retention cycle expires. Payment providers may retain transaction records for their legal obligations. We may retain records needed to resolve a dispute, prevent fraud or meet a legal obligation for as long as that reason applies. If an exception affects your request, we will explain the data retained, why, and the applicable retention period. See the privacy notice’s retention information for separately held service data.

Contact Information

Job Clerk Ltd, Flat 4b, Larcom Street, London SE17 1NQ, United Kingdom. For privacy questions or rights requests, contact hello@jobclerk.com

For data protection matters, you can also reach out to the Information Commissioner's Office: