This policy explains how resumeink.app uses cookies and similar browser-storage technologies. The short version: we set no advertising or analytics cookies. Everything we store in your browser is strictly functional — it makes sign-in and draft-saving work.
| Item | Type | Purpose | Lifetime |
|---|---|---|---|
authToken, authPhone | localStorage | Keeps you signed in after phone verification | Until sign-out, or 30 days (server-side expiry) |
resumeDraft.v1 | sessionStorage | Saves your draft and edits so a page refresh doesn't lose work | Until the browser tab is closed |
resumePendingParse.v1 | sessionStorage | Lets an in-progress upload continue after a refresh | Until the browser tab is closed |
These are "strictly necessary" — the service cannot function without them, which is why no consent banner is shown for them.
Two providers may set their own cookies, only at the moment you use the feature they power:
| Provider | When | Purpose |
|---|---|---|
| Google (Firebase Authentication & reCAPTCHA) | When you sign in with your phone number | Delivering the OTP flow and protecting it from automated abuse. See Google's privacy policy. |
| Razorpay | When you open the payment window | Processing your payment securely and preventing fraud. See Razorpay's privacy policy. |
We also load typefaces from Google Fonts, which involves your browser requesting font files from Google (no cookies are set, but Google receives your IP address as part of the request).
If we ever introduce analytics, this policy will be updated first and a consent mechanism added where the law requires one.
You can clear or block storage in your browser settings (usually under "Privacy" → "Site data"). Be aware that clearing it signs you out and discards any unsaved draft; blocking it entirely will prevent sign-in, payment, and draft-saving from working.
Questions about this policy: support@resumeink.app · see also our Privacy Policy.