1. Who we are
ResumeNext ("we", "us") is a career-tools service. The controller is Maracuya Labs UG (haftungsbeschränkt), Dreschstrasse 5, 80805 Munich, Germany. For any privacy request, write to support@resumenext.io (see the contact page).
2. Data we collect
- Account data: your email address and a salted hash of your password. If you sign in with Google, we store your Google account identifier and email instead of a password. If you pay before finishing signup, we associate your purchase with your checkout email and use it to send account-access and recovery messages.
- Resume content: the text you type, paste, upload, or send to the builder, including files you import (PDF, DOCX, TXT). This is the product's purpose; we store it so you can edit and export your resumes.
- Career-tool data: your master profile, saved and hidden jobs, applications, saved searches, cover letters, interview answers and scores, and LinkedIn-review content you choose to save.
- Application autofill: when you start an Apply Queue, the core answers needed for applications are stored with your account so they work across devices. Voluntary demographic answers stay only in your browser and extension. Each application opening gets a signed, one-use PDF token that expires after ten minutes and stops working if that saved resume changes. The extension sends it from its background worker in an authorization header, not in the request URL, and starting a queue does not enable the resume's public share link.
- Prefill sessions: when a third-party integration sends resume or cover letter text to pre-fill the builder or the cover letter editor, that text is stored temporarily and expires after 7 days. When you open the link, we may save the imported resume or letter to your signed-in account or create a temporary account for it, so you can continue editing. A saved resume or letter has the account-data retention period below.
- Technical logs: standard server logs (IP address, request path, timestamps) kept for security and abuse prevention.
- Product analytics: when you import, save, export, search, open a job, track an application, start a checkout or use an AI action, we record the event name, its outcome, how long it took and a pseudonymous key derived from your account (never the email). These rows are kept for 90 days and deleted with the account. They are used to see where the product fails or is slow, not to profile you. The same events, with the same pseudonymous key, are also sent to PostHog (EU cloud), our product analytics provider, together with the pages you open and the buttons you click. On the page every text and field value is masked before anything is sent, so the content of your resume never reaches PostHog, and no session is recorded.
- Operational notifications: individual events and a daily summary help authorized operators monitor service use and reliability and diagnose failures. Individual events are completed signups, connector tool calls, editor sessions opened from an integration, purchases, renewals, cancellations and failed payments. A message can include the email address and plan of the account involved, the amount and currency of a payment, the reason a payment failed, the acquisition or integration source, the tool name and the time of the event; a tool call made without an account is reported as a guest. We also send service-health codes with pseudonymous references. These notifications do not include IP addresses, resume content, prompts, payment-card details, private editor links or authentication secrets. Login and uncompleted provisional accounts are not signup events.
We do not collect payment card details ourselves; payments are processed by our payment provider.
3. How we use your data
- To provide the tools, store the documents, process purchases and send account-access messages you request, to perform our contract with you or take steps at your request before that contract.
- To authenticate you, prevent abuse and diagnose service failures, based on our legitimate interest in running a secure, reliable service.
- To monitor service health and reconcile payment notifications in a restricted operational channel, based on our legitimate interest in operating a reliable service. Pseudonymous references are not anonymous data and are not used to profile users.
- To retain records required by applicable accounting and other legal obligations.
- To send the job alerts you activate. You can pause or delete an alert at any time from its email or your account.
- To measure which integration sent a prefill session (the "source" tag), so we can evaluate partnerships, based on our legitimate interest in understanding acquisition. We keep the source label with your account; it does not contain your resume content.
We do not sell your data. We do not use your resume content for advertising, and we do not share it with third parties except to operate the services described here, or when you choose to share a resume or send an application to an employer.
4. Where your data lives
Data is stored on Railway (application hosting and PostgreSQL in the United States). Payments, when enabled, are processed by Stripe. Transactional email, when enabled, is delivered through Resend. Product analytics are processed by PostHog in its EU cloud. When you use a generative feature, the resume, job, profile, letter, or interview text needed for that request is sent to Google's Gemini API. These providers process data only to deliver the requested service. Processing may take place outside your country, including outside the European Economic Area. Contact us for information about the providers, processing locations and transfer safeguards applicable to your data.
When enabled, we use Telegram to deliver the limited operational notifications described above to a private group accessible only to authorized operators. Telegram receives and stores those messages; they are not public posts. We do not send resume content or authentication secrets through this channel. Contact us for information about this provider and the safeguards applicable to your data.
If you enable the Cloud Agent, our hosted worker receives the resume and application answers needed for your selected applications and sends them to the employer forms you authorize. It returns application status and questions needing your review. Completed worker queue items erase their encrypted resume payload; operational records remain for reliability and to prevent duplicate applications. The browser extension described below is a separate, local autofill option.
5. Retention
- Prefill sessions: deleted after 7 days. A resume you keep by opening it in your workspace is account data and remains until you delete it or the account.
- Account and user-owned product data: kept until you delete the account or ask us to delete it.
- Purchase-recovery links: valid for 24 hours and one use. We keep the purchase association so you can recover access and we can handle billing correctly.
- Server logs: kept for a short rolling window for security.
- Operational notification content, its supporting payloads and Telegram message copies: up to 30 days. Minimal delivery receipts and deduplication references and minimal account links for access requests: up to 90 days. The dedicated signup completion record follows the 30-day content limit, separately from the existing 90-day product analytics. Authorized operators manage these deadlines manually; there is no automatic deletion job for this notification channel. Expiry blocks further operational use; it does not itself remove stored data. You can request the information still held about your account, including overdue records, without receiving another person's information from shared payment notifications. Cases that cannot be attributed safely require manual resolution through support. These limits do not replace the retention rules for the underlying account or legally required payment records.
6. Your rights
You can download every piece of data we hold on your account as one JSON file ("Download my data" in the dashboard) and delete the account and its user-owned product data directly from the dashboard. You can also request access, correction, or deletion by writing to support@resumenext.io from the address on your account. Payment processors and other providers may retain records they are independently required to keep.
Where applicable, you can also request restriction of processing or portability, object to processing based on legitimate interests, and withdraw consent for consent-based processing without affecting earlier lawful processing. You may complain to your local data-protection authority, including the authority where you live or work. We may need to verify account ownership before acting on a request.
7. Cookies
We use a single session cookie to keep you logged in, a short-lived cookie during Google sign-in, a cookie to connect an import session to your account, and short-lived access cookies for password-protected shared resumes. A first-touch source cookie records which integration brought you here. The editor also uses local browser storage for your draft and preferences. Product analytics run without cookies or browser storage: PostHog keeps its identifier in memory for the current page only. No advertising or cross-site tracking cookies.
8. Browser extension
The ResumeNext Autofill extension for Chrome fills job application forms on the applicant tracking systems listed in its manifest with the resume and application answers you choose to load into it. It fills only when you click its button or while an Apply Queue you started is running, it never submits a form, and it has no account of its own, no analytics, and no tracking.
- What it stores: the resume fields it fills (name, headline, email, phone, location, links, summary, and your most recent experience and education entries) and your application answers (work authorization, visa sponsorship, years of experience, notice period, salary expectation, relocation, and the voluntary self-identification answers). This data is kept in the extension's local storage in your browser; the extension does not sync it or send it anywhere.
- Where it comes from: your own ResumeNext page when you start an Apply Queue, or a public share link you paste into the extension popup. The extension exchanges data only with pages on the ResumeNext origin.
- What it sends: two kinds of requests, both toResumeNext over HTTPS: the public resume behind a share link you pasted, and your resume PDF, fetched with the signed one-use token described above, sent in a request header. It also writes your selected profile and PDF into the employer form when you use autofill; you control submitting that form.
- What it reads on employer pages: form field labels and attributes, to decide which empty fields to fill, and, after you submit an application opened from an Apply Queue, the page address and visible confirmation text, to tell ResumeNext that the employer confirmed the submission. Only the confirmation page address (without query parameters) is kept, in the extension's local storage, and shown back to you on ResumeNext; page content is never stored or transmitted, and that address is not sent to our servers.
- Deleting it: Clear saved data in the extension popup removes everything the extension stored. Uninstalling the extension does the same.
9. Changes
We will update this page when our practices change and revise the date above. Material changes will be announced in the product.