DEASJobsDEASJobsVersion 2026-10-19-v25-deasjobs
DEASJobs processes account/contact information, job-seeker profiles, preferences and availability, location used for matching, CVs/profile images, employer/business information, jobs, applications, messages, interview/offer history, notifications, security records, privacy preferences, moderation reports, pilot feedback, first-party analytics, referral/partner/campaign attribution, risk-review records and employer integration metadata.
DEASJobs's initial launch does not offer paid subscriptions, card checkout or paid featured placements. Stripe payment routes and billing controls are disabled in this release. If payment functionality is introduced later, the Privacy Notice and Terms will be updated before it is enabled.
The main purposes are account operation/security, job matching, recruitment workflows, employer verification, transactional messages, fraud/abuse prevention, moderation, service measurement, pilot management, referrals/partner attribution and legal compliance.
The compliance register maps service delivery and recruitment workflows primarily to contract; security/moderation, first-party analytics and growth attribution to legitimate interests subject to balancing and ePrivacy review; and legal-compliance records to legal obligation. These are working positions pending final legal review.
The candidate feed uses rule-based filtering and match reasons based on job/candidate preferences such as category, availability, distance/location, pay preference, employment type and experience. Minimum-age eligibility is a filter. The score does not make employers' hiring decisions or automatically reject candidates.
Employers receive candidate information after an application, subject to privacy settings. For 16–17-year-old profiles, direct email, CV and profile-photo sharing is disabled by default. DEASJobs also uses service providers for hosting/security/storage and transactional email, including Cloudflare services and Resend, subject to the production processor review.
DEASJobs will document any transfer outside the European Economic Area and the applicable safeguards before broad public launch.
DEASJobs applies data minimisation and self-service deletion. Final retention periods for recruitment, analytics, moderation, messaging, risk and compliance records remain legal-review items. CVs/profile images are removed from DEASJobs storage as part of account deletion under the current implementation.
Job seekers must confirm they are at least 16. Users aged 16–17 receive additional privacy defaults. See the Young Users Privacy Guide.
Depending on the circumstances you may have rights of access, rectification, erasure, restriction, portability and objection. DEASJobs provides export/deletion controls and formal rights/complaint workflows. You may also complain to the Data Protection Commission or another competent supervisory authority.
DEASJobs uses email verification, bot protection, password hashing, session controls, private file storage and audit records. Personal-data incidents are recorded for human assessment and any required notification.
Referral/partner/campaign identifiers and UTM parameters may be stored first-party before signup and associated with an account after signup to measure acquisition and later product outcomes. They are not used for hiring decisions or third-party advertising.
See the Cookies & Device Storage Notice. Installed-app caching excludes signed-in API responses. If Web Push is enabled, DEASJobs stores the browser endpoint and cryptographic keys required to deliver notifications; users can disable this at any time.
Messages are limited to an existing application and can be reported. Behavioural risk flags support human safety/security review and do not rank candidates or make automated hiring decisions.
Verified employers can create hashed API credentials to import/update their own jobs. DEASJobs stores key metadata and external job identifiers; the full API secret is shown only once and is not stored in readable form.
Material changes to the Terms or Privacy Notice are versioned and signed-in users are asked to review the current versions.