Data Policy

Last updated: October 23, 2026

1. What This Policy Covers

This Data Policy is the technical companion to our Privacy Policy: where your data lives, how long we keep it, what happens when you delete something, and what export gives you. It describes the systems we run today.

2. Where Your Data Is Stored

DataWhere it livesNotes
Account, sign-in methods (email address, phone number), sessions and API keys Primary database (PostgreSQL) Passwords, where an account has one, are stored only as hashes
Resumes, cover letters, previous versions, AI resume reviews, view/download counts Primary database Resume content is stored as structured data inside the record
Plan, subscription status, payments, invoices, credit balance and credit history Primary database Card, UPI and bank details are handled by the payment provider and are not stored by us
Applications, notes, attachments you upload, recruiter details you enter Primary database + object storage Uploaded documents are stored as files, referenced from the record
Job-agent conversations, attachments, and the resume snapshots they change Primary database + object storage Attachments are stored in a private area that is not publicly readable
Job-search preferences, including salary expectations Primary database + object storage Your uploaded CV for the agent is stored privately
Uploaded images (resume photos) and application attachments (resume or cover-letter files) Object storage, publicly readable by URL See section 4 for how this interacts with deletion
Recovery links for visitors who leave before paying or sign up without buying Primary database Email address or phone number, the resume or plan in view, and message history; expires after 30 days
Analytics and conversion events, including campaign click identifiers Primary database, and our analytics and advertising providers Event and device data, plus a one-way SHA-256 hash of your email address or phone number for ad matching - resume content is never sent
Sign-up, checkout and purchase events sent to Google Ads and Meta Our conversion record, and the provider (Google Ads, Meta) Hashed contact details plus the ad click identifier, with an event id so a conversion is counted once; see sections 3 and 4
Short-lived technical state: in-progress AI streams, rate-limit counters, repeated-view checks In-memory caches and a key-value store (Redis) Cleared on expiry or restart; not used to build profiles

3. How Long We Keep It

DataRetention
Account, resumes, versions, applications, job-agent data and uploadsWhile your account is active
Email and WhatsApp sign-in codesMinutes - they expire and are then discarded
SessionsUntil they expire or you sign out
View/download statisticsWhile the resume exists
In-progress AI streams and abuse-prevention countersHours at most
Billing, invoice and tax recordsFor the period tax and accounting law requires, even after account deletion; we keep these because we are legally obliged to, and they are no longer linked to an active account
Recovery links30 days from creation, then no longer resolvable
Analytics eventsRaw events for 90 days; daily aggregate counts are kept without the event detail
Conversion events sent to Google Ads or MetaKept by the provider under its own retention (Google Ads matches a click identifier for up to 90 days); our own copy is kept without a link to your account, because it is that advertising account's record and no longer identifies you
Marketing and follow-up consent and message historyFor as long as you are subscribed, plus a short proof period after you unsubscribe

4. Deletion

You can delete individual items at any time - a resume, an application, a job-agent conversation, an uploaded attachment or an API key. You can delete your whole account from your account settings.

When you delete your account, we:

  1. delete your uploaded files from object storage;
  2. delete your account record, which also removes your resumes, cover letters, versions, analyses, statistics, applications, job-agent conversations and preferences, credit balance and credit history, recovery links, and connected API clients; and
  3. sign you out and invalidate your sessions.

Known limitations, stated plainly. Uploaded images and application attachments are served from a public URL with a one-year cache lifetime, so a copy can remain in browser and CDN caches after deletion until that cache expires. If a file-removal step fails, our systems log it but the account deletion still proceeds - if you want us to confirm that everything is gone, ask us and we will verify it for you. Payment and subscription rows are kept, without a link to your account, for tax and accounting retention. Conversion events Google or Meta have already received are part of those advertising accounts' records and cannot be recalled by us; our own copy of them carries no link to your account. Short-lived technical state (in-progress AI streams, rate-limit counters) expires on its own rather than being deleted immediately.

5. Export

From your account settings you can export your profile and resume data as a structured file. Export today covers your account details and your resumes; we are extending it to also include applications, job-agent history, agent-modified snapshots, statistics and your uploaded files, so that a single export gives you everything you have put into the Service.

Separately, any resume can be downloaded as PDF and other document formats from the builder at any time.

6. Third Parties and AI

We use a small set of providers to run the Service - hosting and storage, payment processing (Razorpay), email and WhatsApp delivery, and the AI model providers we route each feature to. AI requests are made from provider accounts we hold; you do not need to supply your own AI key. We do not sell your data and we do not use your content to train AI models.

We also use Google Tag Manager, Google Analytics, Google Ads and Meta to measure visits and conversions. They receive event and device data, campaign click identifiers and a one-way SHA-256 hash of your email address or phone number for matching - never the plain contact details and never the content of a resume. The hash is used only to credit a sign-up or purchase to the ad that produced it, including when the purchase happens later from a WhatsApp link. If we add a provider, we will name it here before it processes your data.

7. Security

  • Data is encrypted in transit.
  • Passwords, where an account has one, are stored only as hashes; stored provider credentials and messaging-channel secrets are encrypted with AES-256-GCM.
  • Production systems are access-controlled, and administrative access is restricted to named operators.
  • We keep backups so the Service can be restored; backups age out on a rolling basis.
  • Private uploads (job-agent attachments and CVs) are not publicly readable.

In the event of a personal-data breach we will notify affected users and the relevant authority within the timelines required by law.

8. Where We Process Data (Cross-Border Transfers)

Our infrastructure, and the providers listed above, may process your data outside your country of residence. Where we transfer personal data internationally we rely on appropriate safeguards and standard contractual clauses with our providers.

Production systems and backups run on our own server infrastructure. Payment processing, email and WhatsApp delivery, AI model calls and analytics/advertising run on the providers' infrastructure in the regions they operate.

9. Contact

For any data request - access, export, correction, deletion, or a question about this policy - email hello@oxyresume.com or use our Contact page.

OxyResume Loading