Privacy Policy

Privacy and Data Protection

This policy explains what Resumetail handles, where resume drafts are saved, and which providers receive data when you choose to use authentication, AI, export, analytics, or payment features.

Information We Collect

We collect the following types of information from our users:

• Authentication Information: Account identifiers and basic profile details returned by Google and Supabase when you sign in, plus the policy versions and server time recorded when you confirm the age and policy statement.
• Credit and Payment Records: Your balance, selected package, amount, currency, transaction status, and payment-provider references. Razorpay handles full payment-method details and receives the name and email prefilled into checkout. For signed webhook recovery, we retain minimized event metadata such as bounded provider event/payment/order/refund/dispute identifiers, amount, currency, status, and review codes. Email, contact, notes, card, and UPI details are excluded from that durable event record. Normally processed or ignored event metadata is cleared promptly; metadata for unresolved, processing, failed, or manual-review events may remain for up to seven days. If verification is uncertain, this browser may retain, separately for each signed-in account, the internal transaction, an unrelated random conversion-deduplication ID, and support reference with a seven-day expiry so you can retry a server-confirmed status check without paying again; expired entries are removed when the application next runs.
• AI Control Metadata: To enforce idempotency, abuse limits, and daily spend ceilings, we store the account ID, operation/model/status, token and cost counters, and HMAC-protected request and client correlators. The free job-match estimate uses a separate token-limited control record. These records do not contain the resume, job description, extracted requirements, embeddings, prompts, or generated output. Non-processing correlator records older than 30 days are deleted; durable credit-ledger and aggregate spend records are retained separately for accounting and dispute handling.
• Resource Control Metadata: To prevent automated PDF/DOCX export and uploaded-document parser abuse across serverless instances, Supabase stores your account ID for export counters plus HMAC-protected account/client correlators for import counters. These short-window counters do not contain resume content and are deleted after two days of inactivity.
• Technical Information: IP address, request time, device or browser details, security signals, and limited operational logs processed by our hosting, authentication, payment, and security providers.
• Support Communications: The messages and diagnostic details you choose to send when requesting help.
• Usage Data: Product events such as starting the builder, choosing a template, or completing an export. A verified-purchase event may include a random conversion-deduplication ID that is separate from the payment, account, and provider identifiers. Resume text, names, contact details, job descriptions, letters, and access tokens are excluded from our product-event payloads.

Resume and Job Content

Resume drafts autosave in your browser's local storage, not in a Resumetail resume database. Drafts expire after 30 days and can be removed immediately with “Start over,” “Clear draft & sign out,” or by clearing browser storage. On a shared device, choose the clear-draft sign-out option. A job description entered through the homepage match path, pending AI reviews, undo snapshots, and cover-letter drafts may also remain in that tab's session storage for up to two hours so sign-in or navigation does not discard your progress.

• Manual editing: Stays on the device unless you invoke a feature that needs a server.
• Resume import and AI features: The relevant file, resume fields, and job description are sent to our API and AI provider for the requested operation. Job-match scoring excludes your name, email, phone, profile links, and custom contact fields from its API request.
• PDF and DOCX export: Resume content is sent to a short-lived Vercel function to build the requested document.

Our application does not intentionally write resume or job-description content to application logs or a server-side draft table. Infrastructure providers still process requests under their own terms and retention policies.

How We Use Your Information

We use the collected information for the following purposes:

• To authenticate your account and provide access to our services.
• To process payments and maintain your credit balance.
• To communicate with you about your account and our services when necessary.
• To respond to your inquiries and provide customer support.
• To analyze aggregated or pseudonymous usage patterns and improve service performance when you allow optional analytics.

Your choice: Editing and local autosave do not require sending resume content to our AI provider. Content is sent for AI processing only when you deliberately run an import, job-match score, tailoring, experience, or cover-letter action.

Data Security

We implement appropriate technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. These measures include:

• HTTPS encryption in transit.
• Server-authoritative credit and payment updates with restricted database functions.
• Input limits, file validation, authenticated exports, and time-bounded provider calls.
• Restricted access to operational systems and minimal application logging.
• Signed payment verification and idempotent credit grants.

Operational logs: Application logging is designed to exclude resume bodies, job descriptions, contact details, tokens, and payment identifiers. Operational metadata may still be processed by our infrastructure providers under their policies.

Your Rights

Depending on applicable law, identity verification, and legal retention exceptions, you may request the following:

• Right to access and receive a copy of your personal data.
• Right to correct inaccurate or incomplete data.
• Right to delete your personal data in certain circumstances.
• Right to restrict or object to the processing of your data.
• Right to data portability in a structured, commonly used format.

Signed-in users can permanently delete their account from the account menu in the resume builder. The deletion also clears the browser-saved resume and pending workspace data on that device; drafts saved in another browser or device must be cleared there. If you cannot sign in, send a request from your account email to support@resumetail.com.

Account deletion removes the active authentication identity and data that no longer needs to identify you. Payment, refund, dispute, tax, fraud-prevention, credit-ledger, and security records may need to be retained after deletion. Where practical, retained records are detached from the active login or otherwise minimized, and they cannot be used to sign back in.

Cookies and Tracking Technologies

Supabase uses essential browser storage to keep you signed in, and Resumetail uses local storage for your draft and editor preferences. Optional Google analytics and advertising measurement remain denied until you make a choice in the privacy-preferences panel; advertising personalization remains denied. You can reopen that panel at any time. Authentication callback, password-recovery, and unknown routes are excluded from measurement. URLs sent in measurement omit fragments and unrelated query data. With analytics permission, approved campaign source, medium, name, and ID codes may be included; with advertising permission, validated Google ad click and aggregate campaign identifiers may be included. We temporarily hold only these approved landing fields in page memory so a privacy choice after navigating can retain attribution; they are not saved to browser storage before consent and are discarded when you reject their corresponding purpose. After advertising permission, we may append missing approved Google ad identifiers to the current public page URL, preserving other query data and functional fragments, so Google's native tag can retain attribution. Google may then store permitted identifiers in its cookies or local storage. Reloading loses our temporary memory copy but identifiers already in a consented URL or Google storage may persist. Revoking advertising removes only unchanged identifiers we added to the current owned browser-history entry; it does not erase original or edited URL values, other history entries, or previously permitted Google storage. Referrers sent in configured measurement omit query strings and fragments, and retain only public same-origin paths or external origins. Because Google's Ads consent requests independently read the document referrer, we skip Ads measurement for the whole visit if that referrer contains a query, fragment, credentials, an external path, a private same-origin path, or an invalid URL. Invalid, duplicated, unsupported, or unpaired landing ad parameters also keep Ads measurement disabled for that visit, even after navigation. We withhold Ads measurement when later ad parameters conflict with approved landing identifiers or cannot be safely used, or when safe URL restoration is unavailable. Your saved advertising choice stays unchanged; permitted Analytics measurement remains available without Google ad identifiers. Ads signup and purchase attribution is omitted on those visits, including some returns from sign-in.

Third-Party Services

We use trusted third-party services for specific functions:

• Vercel: Hosts the web application and document-export functions. Resume content passes through a Vercel function when you request PDF or DOCX export.
• Razorpay: Handles secure payment processing and sends signed transaction events used for verification, delivery, refund, dispute, and fraud review. We store the payment records and minimized recovery metadata described above, but do not receive or store full card numbers, PINs, or UPI credentials.
• Supabase: Provides authentication and stores account, credit-balance, credit-operation, and payment-transaction records. It does not store your browser-saved resume draft.
• OpenAI: Processes the resume fields, uploaded-document text, and job description needed for the AI action you request. OpenAI states that API data is not used to train its models by default; under default controls, abuse-monitoring logs may retain content for up to 30 days. Review OpenAI's API data controls for current details.
• Google: Provides optional sign-in and may provide analytics/advertising measurement on configured deployments. Verified-purchase measurement uses an unrelated random conversion ID rather than a payment-provider or account identifier.

Each of these services has their own privacy policies, and we encourage you to review them for complete understanding of how your data is handled throughout our ecosystem.

Retention and International Processing

Browser-saved drafts and short-window control records follow the expiry periods described above. Account, credit, payment, consent, security, and support records are retained only as long as needed to provide the Service, resolve disputes, prevent fraud, and meet legal, accounting, or tax obligations. Deleting an account removes the active sign-in identity; records that must remain for those purposes are retained in minimized or detached form where practical. Our providers may process data outside your state or country under their contractual and legal safeguards.

Age Requirement

The Service is intended only for people aged 18 or older. We do not knowingly offer accounts or paid services to children.

Updates to This Policy

We may update this Privacy Policy to reflect changes in our practices or legal requirements. The version and last-updated date on this page identify the policy in effect. We will provide additional notice where applicable law requires it.