Legal Document

Privacy Policy

Effective date: May 19, 2026

Last updated: November 9, 2026

Your privacy matters to us. This Privacy Policy explains what data Emekly collects, why we collect it, who processes it on our behalf, how long we keep it, and what control you have over it. We have written it in plain language because you deserve to understand what happens to your information.

1. Introduction

Emekly (“we,” “us,” or “our”) operates the platform at emekly.com. This policy applies to everyone who uses the platform — job seekers on the Free, Pro, or Premium plan, and employers who post jobs.

The data controller responsible for your personal data is [[TO BE FILLED: registered legal entity name]], [[TO BE FILLED: registered business address]], [[TO BE FILLED: country of registration]]. You can reach us at support@emekly.com.

Please read this policy together with our Terms of Service. Where we rely on your consent (for example for analytics), you can withdraw it at any time without affecting the rest of the Service.

2. What We Collect

2.1 Information You Provide Directly

Data typeWhen collected
Email address, nameAccount registration
Password (hash only)Account registration (email sign-up)
CV / résumé file and its textCV upload, CV analysis and CV Creator
CVs you build, cover letters and other generated documentsCV Creator and AI writing features
Advisor chat and mock-interview messagesWhen you use the Emekly Advisor
Application-profile answers (contact details, work authorization, notice period, salary expectations and similar)Auto-Apply Kit questionnaire
Optional voluntary self-identification (gender, race/ethnicity, veteran status, disability status)Only if you choose to answer these optional questions; “Decline to self-identify” is always available
Job preferences & search historyJob search interactions
Telegram chat ID and delivery preferencesOnly if you connect Telegram (Section 6)
Company details and job postsEmployer accounts (Section 5)
Payment identifiers (no card numbers)Subscription purchase
Support messagesWhen you contact us

We never store raw card numbers. Payment processing is handled entirely by Stripe, our PCI-compliant payment processor.

2.2 Information Collected Automatically

  • Service and security logs — requests, errors, IP address and device/browser information, kept by our hosting and database providers to run and secure the Service
  • Session identifiers — to keep you signed in
  • Usage analytics and session replay — only if you accept analytics cookies (Section 9)
  • Feature usage records — which AI features you have used and when, needed to apply plan limits and the refund rule

2.3 Information from Third-Party Sign-In Providers

If you sign in with Google, we receive your name, email address, and profile picture as provided by Google. We do not receive your Google password or access any data beyond what you explicitly authorize.

3. How We Use Your Information & Lawful Basis

Each purpose below is paired with the legal basis we rely on under the GDPR / UK GDPR and similar laws.

PurposeLawful basis
Provide the Service: CV analysis, ATS score, Job Fit, CV optimizer and reviews, Advisor and mock interviews, cover letters, Auto-Apply Kit answers, career plansPerformance of our contract with you
Job matching and search across job boards and Emekly company postsPerformance of contract
Account management, billing, plan limits, transactional emails (verification, receipts), weekly job digest by email or TelegramPerformance of contract
Optional voluntary self-identification answers, used only to fill the matching questions on applications you choose to makeYour explicit consent — given by answering; withdraw by changing the answer to “Decline to self-identify” or deleting it
Product analytics and session replay (PostHog) and traffic statistics (Google Analytics)Your consent via the cookie banner — withdraw any time (Section 9)
Security, fraud and abuse prevention, service logs, verifying employers and reviewing job postsOur legitimate interests in keeping the Service and its users safe
Keeping billing and tax recordsLegal obligation

We do not use your data for advertising, sell it, or use it for any purpose unrelated to delivering the Service.

4. AI Processing & Sub-Processors

Model training

We do not use your CV or messages to train AI models, and our AI providers process your data under their API terms, which do not use API data for model training.

4.1 What Is Sent to AI Providers

Emekly's features are powered by large language models (LLMs) run by third-party providers. To provide a feature, we send the content it needs over an encrypted (TLS) connection, and the provider returns the result. Depending on the feature, this includes:

  • the text of your CV (the extracted text, not the original file) — for CV analysis, ATS score, Job Fit, the CV optimizer, AI CV reviews, CV Creator assistance and cover letters;
  • your Advisor chat and mock-interview messages, together with relevant parts of your CV;
  • your application-profile answers — which may include salary expectations and, if you chose to provide them, voluntary self-identification answers (gender, race/ethnicity, veteran or disability status) — together with the questions on an application form, when you use the Auto-Apply Kit;
  • job descriptions you compare your CV against.

Our AI providers are:

  • Groq, Inc. — groq.com/privacy
  • Microsoft Azure OpenAI Service (Microsoft Corporation) — privacy.microsoft.com

Your data is processed under each provider's API terms, which do not use API data for model training. We have not opted into any data-sharing or model-improvement programme. Providers may keep request data for a limited time under their own terms (for example for abuse monitoring). If we add or change an AI provider, this list is updated.

4.2 Job Data Providers

To find job listings we send search parameters (keywords, job title, location, category) to these job-data providers: Adzuna, Jooble, Reed, USAJobs, Careerjet, and Indeed listings via RapidAPI. Careerjet's terms also require the IP address and browser user-agent of the person searching, so those two values are sent to Careerjet with each search. We do not send your name, email address, or CV to them. When you click through to apply, you leave Emekly and the job site's own privacy policy applies.

4.3 Full List of Sub-Processors

  • Supabase — database, authentication and file storage
  • Vercel — hosting and serverless compute
  • Groq and Microsoft Azure OpenAI — AI processing (Section 4.1)
  • Stripe, Inc. — payment processing and subscription billing. Card details are entered on Stripe's hosted pages and never reach our servers. stripe.com/privacy
  • Resend — transactional and digest email delivery
  • Telegram — optional delivery of your weekly job matches, only if you connect it (Section 6). telegram.org/privacy
  • PostHog — product analytics and session replay, only with your consent (Section 9)
  • Google Analytics (Google LLC) — aggregate traffic statistics, only with your consent. policies.google.com/privacy
  • Adzuna, Jooble, Reed, USAJobs, Indeed via RapidAPI — job data (Section 4.2; search parameters only)
  • Careerjet — job data (Section 4.2; search parameters plus the searcher's IP address and browser user-agent, as Careerjet requires)

Some of these providers process data outside your country, including in the United States. Where required, transfers rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses. We do not sell your data to any third party.

5. Employer Accounts & Company Job Posts

If you register as an employer, we collect your name, work email address, company name, company website/domain and the job posts you create. We use your email domain to verify that you belong to the company (posts from unverified domains are reviewed by our team before they go live), to prevent fraudulent listings.

Published job posts — including the company name and the post's content — are public: they appear on Emekly's job search, are matched against job seekers' CVs, and are published on their own page with structured data that search engines can index. Your personal contact details are not shown on the post unless you include them in it. Job seekers' CVs are not shared with employers through job posts.

6. Email & Telegram Delivery

Emekly can send you a weekly digest of job matches. By default this goes to your account email via Resend. You can instead (or additionally) connect our Telegram bot: when you open the connect link and start the bot, Telegram tells us your Telegram chat ID, which we store with your account so the bot can send you your matches. The digest messages (job titles, companies, links) are then delivered through Telegram's servers under Telegram's privacy policy.

Telegram delivery is optional. You can switch it off or change your delivery preferences in your account at any time; deleting your account removes the stored chat ID.

7. Data Retention

DataHow long we keep it
Account data — profile, CVs and their text, analyses, generated documents, Advisor history, application-profile answers, job history, delivery preferences, employer company data and postsKept until you delete it or delete your account (Settings → Delete account)
Data sent to AI providersProcessed under each provider's API terms (Section 4.1)
Service, security and hosting logsPer our processors' default retention settings (Supabase, Vercel)
Analytics and session replays (only with consent)Per PostHog's and Google Analytics' default retention settings
Billing recordsAs long as applicable tax and accounting law requires; held by Stripe and contain no CV or behavioural data

8. Data Deletion

Your right to erasure

You can permanently delete your account and its data at any time from Settings → Delete account. No email required.

When you confirm account deletion:

  1. Any active subscription is cancelled first, so you are not billed again.
  2. Your profile, CV files, analyses, generated documents, Advisor history, application-profile answers, job history, delivery preferences and (for employers) company data are deleted from our database and file storage.
  3. Your sign-in account is removed and you are signed out.

Exceptions: billing records kept by Stripe as required by tax law; copies in our providers' backups and logs, which expire under their default retention; and analytics data, which you can ask us to delete by emailing support@emekly.com.

Deletion is irreversible. If you wish to export your data before deleting, email support@emekly.com.

9. Cookies & Analytics

9.1 Cookies and Storage We Use

sb-* (Supabase auth)Essential

Keeps you signed in. Required for the Service to work.

emekly_analytics_consentEssential

Remembers your cookie-banner choice (stored in your browser).

ph_*Analytics

PostHog product analytics and session replay. Set only after you accept analytics. When you are signed in, PostHog links these events to your account ID and email address.

_ga, _ga_*Analytics

Google Analytics. Distinguish visitors and sessions for aggregate traffic statistics. Set only after you accept analytics; expire after up to 2 years.

9.2 Analytics

Both analytics tools are opt-in: they are not loaded and store nothing in your browser until you click “Accept” on our cookie banner.

  • PostHog records how the product is used — pages viewed, clicks, errors — and session replays (a reconstruction of what happened on screen). Everything typed into form fields is masked in replays, and areas showing CV content or interview transcripts are masked or excluded. When you are signed in, we link PostHog data to your account ID and email address so we can understand and fix problems for real accounts.
  • Google Analytics gives us aggregate traffic statistics (visits, referral sources, pages viewed). Google signals and ad personalization are turned off, and we do not send your name, email or CV content to Google.
  • Separately, our servers record a small number of account events (for example sign-up, a CV analysis being run, or a subscription change) with your account ID in PostHog, so we can measure the product and billing reliably.

We do not use Meta Pixel or any advertising trackers.

9.3 Your Cookie Choices

You can accept or decline analytics at any time. Declining stops PostHog capturing and session recording, removes PostHog's and Google Analytics' cookies from this browser, and stops both from loading.

10. Security

We implement industry-standard security controls to protect your data:

  • All data in transit is encrypted with TLS 1.2+.
  • All data at rest is encrypted using AES-256 via Supabase's managed infrastructure.
  • Passwords are never stored in plaintext; we use bcrypt hashing via Supabase Auth.
  • Access to production databases is restricted to authenticated services; no direct human access in normal operations.
  • API keys and secrets are stored as environment variables, never in source code.
  • We perform regular dependency audits and apply security patches promptly.

Despite these measures, no system is completely secure. If you discover a security vulnerability, please report it responsibly to security@emekly.com. Do not disclose it publicly until we have had a reasonable opportunity to address it.

11. Your Rights

Depending on your location, you may have the following rights regarding your personal data. We honor all of them regardless of jurisdiction.

Access

Request a copy of all personal data we hold about you.

Rectification

Correct inaccurate or incomplete personal data.

Erasure

Request permanent deletion of your account and data (see Section 8).

Portability

Receive your data in a machine-readable format (JSON/CSV).

Restriction

Ask us to limit processing of your data in specific circumstances.

Objection

Object to processing based on legitimate interests.

Withdraw consent

Where processing is based on consent, withdraw it at any time.

Lodge a complaint

File a complaint with your local data protection authority.

To exercise any of these rights, email support@emekly.com. We will respond within 30 days. For verified requests, we will not charge a fee.

12. Children's Privacy

Emekly is not directed at children under the age of 16. We do not knowingly collect personal data from anyone under 16. If we discover that we have inadvertently collected such data, we will delete it immediately. If you believe a child under 16 has provided us with their personal information, please contact us at support@emekly.com.

13. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will:

  • Update the “Last updated” date at the top of this page.
  • Notify registered users by email before material changes take effect.

Non-material changes (typo corrections, formatting) may be made at any time without notice. The current version of this policy is always available at emekly.com/privacy.

14. Contact

If you have any questions, requests, or concerns about this Privacy Policy or how we handle your data, please contact us:

Email: support@emekly.com

Operator: [[TO BE FILLED: registered legal entity name]]

Address: [[TO BE FILLED: registered business address]], [[TO BE FILLED: country of registration]]

Emekly — emekly.com