Privacy Policy

Version 0.1 · September 2026

This describes what PrepHike holds about you, why it holds it, who else gets to see it, how long it stays, and how you destroy it. It is written against what the software actually does rather than against what would sound best. Where the mechanism is weaker than you might hope, this page says the weaker thing. It sits alongside the terms.

01What this covers

Two surfaces. This website, prephike.com, which is informational and processes no document you supply. And the application at app.prephike.com, which needs an account.

02What you give us, and why

• Your resume, for the free check. If you upload a PDF, the file is read inside your browser and the file itself is never uploaded. Only the text pulled out of it crosses the network. If you paste text instead, that text crosses the network. Either way the text is encrypted before it is stored, and it is stored so the check can be run and so the result can be shown back to you.
• The role you are aiming for. Free text you type. It is stored as an ordinary column, not encrypted, because the check is scored against it.
• Your connecting IP address, briefly. The free check counts requests against the address your connection arrives from, so one machine cannot run the check thousands of times. The counter is keyed on the address, lives in a short lived store, and expires with its window. It is not written next to your check and it is not kept.
• A sign in. Signing in with Google asks Google for two things only, an identifier and a verified email address. It does not ask for your name and it does not ask for your picture. The verified value is turned into a one way hash and it is the hash that is stored, so signing in the same way again reaches the same account. A sign in link sent to an email address works the same way: what touches disk is a hash.
• What you type in a mock interview. Your answers are stored as ordinary text, up to 8,000 characters per turn, so the session can be scored and so you can read it back. This one is not encrypted. See section 05.
• Your offer figures, if you enter them. What you earn now, what you are aiming at, and how long your notice is. These are encrypted with the same key that protects your resume text. No query in this system can filter, sort or average a salary, because there is no column to filter on. They are not sent to any model.
• The companies you are talking to, if you record them. The company name, the role title and where the conversation came from are encrypted. The stage it has reached, the rounds you log, when each happened and how each ended are stored as ordinary columns. A company name is a fact about somebody other than you, and that is why it is called out separately here.
• A payment, if you buy something. What is stored on our side is an internal order id, a product code, an amount in paise, a currency, a status, and the payment provider's own reference. No name, no email address, no card number and no card fragment. Card details are entered with the payment provider and never reach us.

03What we work out, rather than ask for

• Findings. Each one quotes a span of your own document word for word, and is discarded before you see it if that span cannot be found verbatim in your text.
• Findings, each one quoted from a document you supplied, recorded with the character offsets the quote was taken at.
• A record of every model call made for your check: which model, which provider, how long it took, what the gates decided, and a hash of the exact request that was sent. The request itself is never stored, because it contains your resume. The model's raw reply is stored, and because the model is required to quote you, that reply contains sentences copied out of your resume. It is kept so a disputed finding can be reconstructed exactly. It is deleted when you delete your account.
• Counts and timings from your use of the application, used to show you where you are and to work out whether the product helps anybody.

04What we do not have

• We do not have your name. Nothing asks for it and the sign in scope does not include it.
• We do not have your email address on any account record. There is no email column in the identity database and there is not meant to be one. What exists is a hash of what you signed in with.
• We do not have your phone number, your photograph, your address or your date of birth.
• We do not have your current employer's name unless you type it into your resume or record it as a company you are talking to.
• We do not have a password, because this product has none anywhere.

05Where it lives, and who runs the machines

Everything runs on Cloudflare. The code runs as Workers, the databases are Cloudflare D1, short lived counters and your session record are in Cloudflare KV, generated report bodies are objects in Cloudflare R2, and this website is served by Cloudflare Pages. Cloudflare is therefore the infrastructure provider for all of it, and where data physically sits is a function of their network rather than a choice we make per request.

Two things about how it is protected, stated precisely. Your resume text, your offer figures, and the company and role names you record are AES-GCM ciphertext held under a per subject key, and the row that points at them holds only a reference, a hash and a length. That encryption is real. It is not end to end: the key material exists on the server, and server side code holds what it needs to decrypt in order to show you your own data. What changes that, permanently, is deleting your account. See section 10.

What you type in a mock interview is not covered by that. It is ordinary text in an ordinary column until you delete your account, at which point the rows are deleted outright. We would rather say that than imply a protection it does not have.

Report bodies in R2 are never publicly readable. The only way to fetch one is through a route that resolves ownership against the database first.

06Who else sees it

• The model provider. To run a check we send the text of your resume and the role you named to OpenRouter, which routes it to the specific pinned model we use for that step. The same applies to a mock interview: what you type is sent so the interviewer can answer and so the session can be scored. Your offer figures are not sent, and your recorded company names are not sent.
• Cloudflare. As the infrastructure above, and additionally as the operator of the anti bot check on the free resume form, which is a Cloudflare product and which sees what it needs in order to decide you are not a script.
• Google. Only if you choose Google to sign in, in which case Google knows you signed in to PrepHike. Separately, both this website and the application load their fonts from Google's font servers, so Google's servers see the request your browser makes for a font file.
• The payment provider, Razorpay. If you buy something, you transact with them. They see what a payment needs. We see their reference for it.
• An email provider, Brevo. Configured to deliver sign in links, which means an address you type for a sign in link would be handed to it. Read section 14 before assuming this works.

07Who never sees it

• We do not sell your data, and there is no arrangement under which anybody pays us for it.
• We do not send your resume, your figures or your search to recruiters, employers or the companies you are talking to. We are not a placement agency and we do not contact companies on your behalf.
• There is no advertising network, no advertising pixel, no data broker and no third party session recorder anywhere on either surface.
• Anything we publish about how well the product works is counted from records that carry no name, no email address and no resume text. Your figures are never counted into it, because there is no query that could count them.

08Measuring this website

This website records what pages were opened, what was clicked, roughly what size of screen it happened on, which page sent you here, and the country Cloudflare's edge reports. It writes those to Cloudflare's analytics store. It stores nothing at all on your device: no cookie, no local storage, nothing to clear. It does not store your IP address.

To count how many different people visited on a given day, our server works out a short code for your visit. It is made by taking a random secret, your IP address, your browser's user agent string and the website address, and running them through a one way hash. Only that code is kept. Your IP address and user agent are used for the length of one request and then dropped.

The random secret is thrown away and replaced every 24 hours, and we keep no copy of the old one. So the code you get today cannot be recreated tomorrow, and yesterday's visit cannot be joined to today's, by us or by anybody else. The price of that is a real one and we would rather say it than hide it: we cannot tell a returning visitor from a new one, and we do not try.

Two people sharing one internet connection with the same browser can land on the same code, and one person whose connection changes during the day can produce two. The number is a rough count of visits, not a count of people, and nothing we publish treats it as one.

09How long we keep things

• A free check you never sign in for: 30 days. The temporary profile, the document and its key are destroyed by a scheduled sweep after that.
• A result link: 30 days. Anyone holding the link can read that one result until it expires, which is worth knowing before you forward it.
• A check you signed in and claimed: kept until you delete it or delete your account. Be aware of one honest wrinkle: after day 31 the row that names the underlying assessment is gone, so a claimed check can keep its document and still stop being able to show you its findings. Your export says so explicitly rather than returning an empty list.
• Rate limit counters: minutes. They expire with their window.
• The record that a check happened and the score it produced: kept indefinitely, including after you delete your account, and the database physically refuses to delete them. What they contain is in section 10.

10Deleting your account, and what unreadable means

You can delete your account from inside the application. It asks you to type a confirmation phrase, because there is no backup of your key, no soft delete, no undo, and no support process that can reverse it. What runs is five passes, in order: the model reply log and the shareable result links, then the mock interview transcript and the sessions that describe it, then the companies you recorded with their rounds and their key, then your documents, your offer note, your key and your profile, then your identity record. Your browser session is cleared at the end.

The application states the outcome in these words, and this page repeats them rather than paraphrasing them:

• Deleting your account destroys the encryption key that protects your resume text and your account details. From that moment the text cannot be read again by anyone, including us. There is no undo and no support process that can bring it back.
• The record that a reading happened stays. It carries no name, no email address and no text from any document you supplied: which surface asked for the reading, which model answered, how many findings survived grounding, and timestamps, keyed to a random identifier that after deletion points at nothing. It stays because it is how we measure, across everyone who has used this, whether the product actually helps.
• If you record a company you are talking to, we keep it: the company, the role, the stage it has reached, the rounds you log against it and how each one ended. The company and the role are encrypted with the same key that protects your resume text. They are never shown to anybody else and they are never counted into anything we publish. Deleting your account destroys that key and deletes those rows, so the record of who you were talking to does not survive it.

The word is unreadable, not deleted, and the difference is the point. Your resume text is encrypted bytes sitting in a database. Deleting your account destroys the key rather than the bytes. The bytes remain and nothing can open them, including us. Where a surviving row would still say something about you even with its contents unreadable, the row itself is deleted as well: an offer note that still said you had an offer on a date, or an application that still said you reached round three somewhere and stopped on the eleventh, is a fact about you with the numbers filed off, so those rows go.

And the sentence the application refuses to leave out: this is not a certified erasure under any named regulation and it has not been reviewed by a lawyer. It is what the mechanism above does, described as plainly as we can put it.

11Taking your data out

The application will give you one JSON file containing what it holds about you: your account record, every check with its target role, the decrypted text of the document you gave it, the findings with the spans they quote, and the score. Where something is missing the file says why it is missing rather than quietly leaving it out. You do not have to be leaving to ask for it.

One thing is deliberately left out of the export: the raw model reply described in section 03. It is an internal audit artifact, and the evidence span it contains is already on every finding in the file. Leaving it out of the export changes nothing about deletion, which removes it either way.

The export takes no identifier of any kind. It returns what belongs to whoever is signed in, and there is no link, no token and no administrative route that reaches it.

12Age

PrepHike is for working software engineers. It is not intended for anyone under 18, and we do not knowingly collect anything from anyone under 18. If you are under 18, a parent or guardian must agree on your behalf, as the terms say. If you believe a person under 18 has given us something, tell us using section 14 and we will destroy it.

13Changes to this policy

We may update this over time, and we intend to update it whenever the software starts holding something it did not hold before, rather than afterwards. The version and date at the top of this page say which one you are reading. The policy that applies to you is the one in force when you use the service.

14Contacting us, and a gap we are not hiding

PrepHike is based in Coimbatore, India. Write to [email protected], which is the same address our terms carry.

Now the honest part. This product cannot send you email. The mail integration has never successfully delivered a message, so nothing about your account, your purchase or your data will ever arrive in your inbox from the software. Any reply you get comes from a person reading that mailbox, and we are not going to promise you a response time we have not yet earned. We have also not appointed a named grievance officer or a data protection officer. When we do, this page will say who they are.

Because of that gap, the two things you are most likely to want do not depend on reaching us at all. Your export and the deletion described in section 10 are both controls inside the application, they run immediately, and nobody at PrepHike has to be involved.