Privacy
policy.

§01OverviewP.01

Zevo Works ("we", "us", "our") builds AI-powered productivity tools, including my-resume.in. This Privacy Policy explains what data we collect across our websites and products, why we collect it, and the rights you have over it. We try to keep this human-readable — if anything is unclear, email us (section §11). We are the data controller for the personal data you submit. Zevo Works is a sole proprietorship (GSTIN 29DUUPG0736G1ZA) based in Kempanahalli, Davanagere, Karnataka, India, serving users worldwide.

We collect and process your personal data with your consent, which you give when you register an account and when you choose to use AI features. You may withdraw consent for AI features at any time by not using them, and withdraw consent entirely by deleting your account — which triggers deletion of your data as described in §04 (see also §07).

§02Data we collectP.02

Different Zevo Works surfaces collect different data. The marketing site (zevo-works.in) collects almost nothing. Product-specific collection is enumerated below.

• ▸Anonymous, aggregated traffic stats (pageviews, referrer, country-level region, browser/OS user-agent string).
• ▸No accounts. No cookies tied to your identity.
• ▸If you email us, we keep the message thread for support history.

• ▸Account data: name, email, hashed password (bcrypt). If you sign in with Google, we receive your Google email, name, profile picture URL and a Google ID — never your Google password.
• ▸Profile data: everything you fill in on the Profile Hub — personal details, education, work experience, internships, skills, projects, certifications, languages, achievements and links.
• ▸Résumé artefacts: uploaded PDFs, parsed text, generated LaTeX source, compiled PDFs, build metadata.
• ▸Job descriptions: any JD text you paste in for AI tailoring.
• ▸Usage telemetry: pageviews, route timings, user-agent string, approximate locale, and a randomly generated session ID created per visit and not linked to your account or identity.

§03How we use your dataP.03

We use the data above only to:

• ▸authenticate you and keep your session alive;
• ▸store your profile so you can generate unlimited résumés from it;
• ▸compile résumés, render previews, and let you download PDFs;
• ▸send your job description to our AI provider so it can tailor a résumé to it (see §05);
• ▸diagnose bugs, monitor performance, and improve the product;
• ▸respond to support requests.

We do not use your profile data to train AI models, and we do not run ads.

§04Storage & retentionP.04

Data is stored in our managed database and object storage. Compiled PDFs and uploaded résumés are kept until you delete them or close your account. Account and profile data are kept for as long as your account is active. When you delete your account from Profile Hub → Account, we permanently remove your account, profile, all résumés and JD data within 30 days from primary storage. Encrypted backups are rotated within 90 days. Support email threads are kept for up to 24 months, then deleted, unless a longer period is needed to resolve an ongoing issue or meet a legal or tax obligation.

§05Sharing & third partiesP.05

We share data only with the sub-processors needed to run our products:

• ▸Cloud hosting & database — our application, database (PostgreSQL) and file storage run on a Hostinger VPS; as our infrastructure provider, Hostinger has access to data at rest on that server.
• ▸AI providers — when you use AI features, the relevant text is sent to a model provider for inference through our provider chain: DeepSeek (via NVIDIA NIM), NVIDIA NIM, Anthropic (Claude) and Google (Gemini). We do not authorise providers to train on this data where that option is available, and we keep this list current as our providers change.
• ▸Razorpay (payments) — when you buy a paid plan, your name, email and payment details are processed by Razorpay to complete the transaction and issue a GST invoice. We never see or store your full card number, UPI PIN, or bank credentials.
• ▸Google OAuth — only if you choose Google sign-in.
• ▸LaTeX compiler — runs in our infrastructure (Docker); your data is not sent to a third party for compilation.
• ▸Legal authorities — only if compelled by valid legal process.

We never sell, rent, or trade your personal data.

Cross-border processing. Some of our sub-processors (including the AI providers above) operate servers outside India. By using the AI features, you consent to your data being transferred to and processed in the jurisdictions where these providers operate. We send only the text needed for the feature you invoked and rely on those providers' contractual and technical safeguards.

§06Cookies & trackingP.06

The marketing site uses no identifying cookies. The my-resume.in product uses a single first-party, HTTP-only session cookie that is strictly necessary to keep you logged in — it carries no advertising or tracking function, so it does not require separate consent. Our usage telemetry (pageviews, route paths, timings) is first-party and anonymised / non-personal — not linked to your account. We do not use third-party advertising cookies, fingerprinting, or cross-site trackers anywhere.

§07Your rightsP.07

You can, at any time:

• ▸Access & correct your profile data directly from the Profile Hub.
• ▸Export your generated résumés as PDF.
• ▸Delete individual résumés or job descriptions from the dashboard.
• ▸Delete your entire account from Profile Hub → Account → Delete Account.
• ▸Withdraw consent — for AI features, by not using them; entirely, by deleting your account, which triggers deletion of your data per §04.

Under applicable laws (GDPR, where you are in the EU/EEA, and India's DPDP Act, 2023), you may also have the right to data portability, restriction of processing, and to lodge a complaint with a supervisory authority. Email us to exercise any of these rights; we aim to respond to such data-rights requests within 30 days (general queries are usually answered sooner — see §13).

§08SecurityP.08

Passwords are hashed with bcrypt. Sessions use HTTP-only, signed cookies over HTTPS. We follow least-privilege access on our infrastructure and patch dependencies regularly. No system is perfectly secure; please use a strong, unique password and keep it private.

Data breach notification. In the event of a personal-data breach that is likely to affect you, we will notify affected users and the Data Protection Board of India without undue delay, as required by the DPDP Act, 2023.

§09ChildrenP.09

Our products are not directed at children under 16. If you believe a minor has created an account, contact us and we will remove it.

§10How your résumé is processedP.10

When you upload a résumé, we handle it in a deliberate, privacy-conscious sequence. The key point up front: your original file is never sent to the AI — only the plain text pulled from it is — and the uploaded file is deleted straight after that text is extracted.

• ▸1. Upload & validation. You upload a PDF or DOCX (max 5 MB), saved temporarily on our server under a random, unique filename.
• ▸2. Text extraction. We extract only the text content (pdf-parse for PDFs, mammoth for DOCX). If too little text comes out (under ~50 characters — usually a scanned or image-only file), the upload is rejected. Text is capped at ~200,000 characters.
• ▸3. Local pre-processing. Before any AI call, a local scan pulls your email, phone, links, name and interests as safety-net fallbacks — this runs on our servers and is not part of what is sent to the AI.
• ▸4. Sending to the AI. Only the plain text is sent to a model provider — never the original file — wrapped in a detailed set of instructions to return structured data. Requests run through our provider chain (see §05).
• ▸5. Retry & fallback. If the AI returns malformed data, we ask it to correct the format; for long résumés we use a two-pass approach and merge the results.
• ▸6. Post-processing. We merge the locally-extracted contacts over the AI result, normalise names, de-duplicate skills, and split long paragraph bullets into individual points.
• ▸7. Cleanup. The uploaded file is permanently deleted from our server — the original document is never kept long-term. Only the structured profile and any résumé you save are retained, per §04.

§11Grievance officerP.11

For any privacy or data-protection concern, our Grievance Officer under the IT (Intermediary Guidelines) Rules, 2021 and the DPDP Act, 2023 is:

• ▸Name: Gangadhara K S (Proprietor, Zevo Works)
• ▸Email: info@zevo-works.in
• ▸Address: Kempanahalli, Davanagere, Karnataka, India

We acknowledge complaints within 24 hours and resolve them within 15 days of receipt.

§12ChangesP.12

We may update this policy as our products evolve. Material changes will be highlighted on the home page or via email. The "Updated" date in the metadata sheet above always reflects the current version.

§13ContactP.13

Questions, deletion requests, or anything else — email info@zevo-works.in. We aim to respond within 5 working days.