Privacy

The short version

Your resume is used to answer your own requests and nothing else. It is not shown to other users, not sent to employers, not sold, and not visible in the operator's own dashboard. There is no password to lose, because sign-in goes through Google.

What is stored

• Your Google identity — the account ID Google gives us, your email address, your name and your profile picture URL. No password is created or stored, because there is no password.
• The documents you upload. Resumes and achievement notes are converted to plain text when you upload them, and the text is stored. The original file is not kept.
• What the AI produces for you — your profile, match scores and their reasoning, rewritten resumes, draft messages, interview prep, and the stage each saved job is at.
• What you told us you are looking for — role types, cities, years of experience and salary floor.
• Usage records — which action ran, when, and how many tokens it used. This is how your credit count is calculated.
• Payment records — the Razorpay payment and order IDs, the amount, and the status. Card and UPI details never reach this service; they are handled entirely by Razorpay.

Who can see your documents

Only you. The operator's admin view is built to show counts, revenue and error status — how many documents exist, whether a profile has been built, how many jobs were scored. It does not display your documents, your profile, or anything generated for you.

This is enforced in the code and covered by tests, not only stated in this policy. Every query for your data requires your account ID; there is no unscoped way to read it. That is a deliberate limit on what a compromised operator account could expose.

Where your data goes

To run an AI action, the relevant part of your profile plus a job description is sent to our AI provider (OpenAI) over an encrypted connection, under an account belonging to this service — you do not need an AI account of your own. We do not send your data to any other third party, do not sell it, do not share it with recruiters, and do not use it to train any model.

Job postings are read from companies' own public careers feeds. Nothing about you is sent to those companies. When you apply, you do it yourself on their site.

Infrastructure: the application runs on a virtual machine in India, and the database is hosted in Singapore by Neon. Payments are processed in India by Razorpay.

Shared versus private

Two things are shared across all accounts because they are identical for everyone and fetching them once keeps the service cheap: job postings and company briefings. Nothing derived from you is shared — your scores, resumes, messages, saved jobs and usage are visible only to your account.

Cookies

One cookie holds your sign-in session, and a second short-lived one protects the Google sign-in handshake against cross-site request forgery. Both are strictly necessary for the service to function. There is no advertising, analytics or third-party tracking cookie on this site.

Deleting things

• Remove any uploaded document from inside the app at any time.
• Sign out to end your session immediately.
• To delete your account and everything attached to it, email hello@codeskate.com from your registered address. Deletion cascades: documents, profile, scores, generated content, saved jobs and usage records all go. Payment records are kept for as long as tax law requires.

Retention

Your data is kept while your account exists. Sign-in sessions expire after 30 days and expired ones are purged automatically.

Honest limitations

This is an early-stage product run by an individual, not a company with a security team. Tenant isolation is implemented and tested, traffic is encrypted, and payment details never touch our servers — but no independent security audit has been carried out. If that matters for your situation, it is a fair reason to wait.

Contact

Questions, corrections or a deletion request: hello@codeskate.com.