Data security

Everything below belongs to one account and is readable by that account alone.

• ·Your identity, as your sign-in provider gives it: email address, name, photo, and an internal account id.
• ·The postings you paste or fetch: the full text, and the link if you gave us one.
• ·What we read out of a posting: the role, the company, the skills it asks for, the phrases it leans on, and the concerns worth noticing.
• ·The company research brief, including the public pages it was written from.
• ·Your resume, the one text you paste once. Every version written for you is built from it.
• ·The plan, the study notes, your interview answers, the scores and the feedback written about them.
• ·The two documents written for each posting, plus the list of the posting's own terms with whether each one appears in your draft, and the notes about what your resume does not evidence.
• ·Usage counters: how many postings, plans and interviews this month, and how much AI work that took.
• ·Billing identifiers from our payment provider: a customer id, a subscription id, the state of that subscription, and the date the current period ends.
• ·Files you upload: an avatar, and any document you save for yourself.
• ·Your study preferences: hours a week, time zone, and the role you are aiming at.

Your browser keeps nothing of this except your signed-in session, which your sign-in provider manages for you.

• ·In Google Cloud, inside the Firebase project this app runs on: Cloud Firestore for the documents above, Cloud Functions for the work done on them, Cloud Storage for files.
• ·The work runs in the us-central1 region, in Iowa in the United States. The database and the file storage are part of the same project, and the region a project's storage is created in is fixed for its life.
• ·The pages you load are plain files served by a static host (Firebase Hosting, or Azure Static Web Apps on the other deployment target). Everyone is handed the same bytes, and those files hold nothing about you.

The transfer that follows from the working region: if you are outside the United States, using the service means your data is processed in the United States.

• ·When you ask for your analysis, plan, notes or documents, the posting text, your resume and your interview answers go to the provider that writes them. That is the material a step works from: your email address, your name and your account id are not sent with it, though anything written inside your resume or your answers travels with them.
• ·When you ask for a research brief, the company name, the role title and the technologies named in the posting go to a search provider, which returns the pages the brief is written from.
• ·When you paste a link instead of the text, the page is fetched from the public web by our side rather than your browser. That request identifies the service, not you.
• ·Payment is handled by Stripe on Stripe's own pages. Your card details go straight to Stripe and never reach this app; Stripe also holds your email address, because that is where invoices and receipts go.

The providers that touch your data, and what each one does:

• Google Cloud (Firebase)

  Stores and processes everything the service holds: the database, the backend that does the work, and files you upload. The backend runs in the United States, in the us-central1 region.

• DeepSeek

  The default provider that writes your analysis, plans, notes and application documents. A deployment can be pointed at a different one. It receives the material a step works from: the posting text, your resume, your interview answers.

• Tavily

  The default provider for the company research searches. A deployment can use Brave Search instead. It receives the company name, the role title and the technologies named in the posting, and returns the pages the brief is built from.

• Stripe

  Takes payment, keeps the card details and the invoices, and holds the subscription record your plan is read from. We hold its customer and subscription identifiers, never a card number.

• Firebase Hosting and Microsoft Azure Static Web Apps

  Serve the app's files. The deployment is on one of them (Firebase Hosting as deployed today; Azure Static Web Apps is the other target in the runbook), and whichever one is live hands the same pages to every visitor and holds nothing about you.

• ·Owner only. A signed-in account can read its own documents and nothing else. Every other collection is refused outright, there is no public read anywhere, and a signed-out visitor has nothing to open.
• ·The parts that matter are written on our side, never from a browser: the analysis of a posting, the research brief, the plan, the notes, the transcript, the scores, your plan tier and your usage counters. An account cannot promote itself to Pro, return itself a credit, or change a score.
• ·What you can write yourself is a short list, held to those fields alone: your name and photo, your preferences, your resume, the ticks on your plan, and the wording of the two documents written for a posting, which are yours to edit.
• ·Uploads are owner-only and restricted by kind and size: images for an avatar, a document for anything you save.
• ·The credentials for the writing, search and payment providers are held on our side and never reach your browser. The only keys in the app you download are the project identifiers your account needs to reach its own data.
• ·The message our payment provider sends us about a subscription is checked against a signature it alone can produce, over the exact bytes it signed, before anything is written. A message that fails that check changes nothing.
• ·Everything moves over HTTPS with strict transport security, the app refuses to be framed by another site, and its content security policy limits what it may load and which addresses it may talk to.

Deleting your account, from the account screen, does four things in this order:

• ·Cancels the subscription, so nothing is charged again.
• ·Deletes every document in your account: profile, postings, plans, notes, interview transcripts and usage counters.
• ·Deletes your uploaded files.
• ·Removes your sign-in record, and the link between your referral code and the account.

The order is deliberate. Cancelling first means a failure part way through cannot leave you paying for an account that no longer exists.

It is irreversible. There is no soft delete, no recovery window, and nothing to undo it with. If a deletion fails part way, the account screen says so and the same button is safe to press again: the step is built to be repeated rather than to half-finish.

One thing outlives the account, and it is not on our side: the payment provider keeps its own record of the subscription and the invoices, which is why a receipt can survive an account. Nothing about you remains in this app's own data.

• ·We do not sell or rent your data, and we do not share it for advertising.
• ·We do not run advertising or tracking scripts, and no third party watches you use the app. The only outside addresses the pages are allowed to reach are Google's sign-in and data endpoints and Stripe's payment pages.
• ·We do not store card numbers, and we never see them.
• ·We do not train anything on your content ourselves, and it goes to nobody except the providers named above, to do the work you asked for.
• ·We do not use your postings, plans or transcripts to market to you.

One limit worth stating plainly: what a provider does with a request beyond answering it is governed by that provider's own terms, not by anything on this page. If that matters to you, ask before you paste anything sensitive, and the address below is where the answer comes from.

Write to interviewgymca@gmail.com from the address your account uses. Ask what we hold about you and who has seen it, and you will get an answer rather than a policy link.

If you think you have found a security problem, tell us before you tell anyone else, and give us a chance to fix it. We will never ask you for your password, and we will never ask you for a card number.