Privacy Policy

Overview

You can read Preptima without an account. Accounts are optional and exist so your progress can follow you between devices. We do not sell your data, we show no advertising, and we set no advertising cookies. Google Analytics sets cookies to measure how the site is used - see Cookies below.

If you create an account

You can sign up with an email address and password, or with Google or GitHub. Accounts are run on Supabase, hosted in Mumbai, India. With an account we store:

• your email address and name, and, if you sign in with GitHub or Google, the profile details they share (such as your name, username and profile picture);
• your answers to the optional profile questions: experience level, main goal, the role and kind of company you are preparing for, and when your interview is. We use them only to build your study plan, and you can change them on your profile page;
• which questions you marked mastered or needing review, and which you bookmarked;
• which questions you liked (only you can see your likes; everyone else sees the total);
• study plans you save: their title, the options you picked to build them, any questions you added to them, and for a plan built from a job description, its topics and (if you keep it) the job description;
• the days you were active and the last question you opened, for your streak and the “continue where you left off” link.

When you sign in, anything you had saved in this browser beforehand is copied to your account.

Free-view limits

You can open three pages in full - questions, learn guides, fundamentals sheets and masterclasses, counted together - before you need an account (the short answer or introduction at the top of every page is always free). To count them, we create an anonymous identity for your browser the first time you open one, and record which pages it has viewed. It holds no name or email address, and it cannot save likes, progress or plans.

Signing in with Google

The sign-in page loads Google's sign-in button from accounts.google.com. When you are not signed in, other pages load the same Google script a few seconds after they open, to offer “Continue as” (Google One Tap) if your browser is already signed in to a Google account. Google receives the usual request details from your browser when the script loads, as it does on the sign-in page. We receive your Google account details only if you choose to continue. Signed-in readers, and the sign-in pages themselves, do not load it.

Cookies

Preptima sets two kinds of cookie:

• Sign-in: Supabase cookies named sb-…-auth-token, set only when you sign in, or when the free-view limit above needs to count your views. Those features need them to work.
• Analytics: Google Analytics cookies named _ga and _ga_…, which hold a random identifier so Google Analytics can tell a returning visitor from a new one and count visits and engagement. They are first-party (set for this site only), last up to two years, and are not used for advertising. You can block or delete them in your browser settings, or with Google's opt-out add-on; the site works the same without them.

We set no advertising cookies.

Stored in your browser

Marking questions, bookmarking, liking and your streak need an account: they are saved to your account as you go, and signed out the site is read-only. Your browser's local storage keeps a working copy, on your device only; clearing this site's data removes it and the next visit reads your marks back from your account.

• preptima_progress_v1: a copy of your mastered, review and bookmark marks.
• preptima_progress_pending_v1: marks you made that have not reached your account yet (for example while offline), so they are sent on your next visit.
• preptima_activity_v1: active days and the last question you opened, copied from your account.
• sweqb-theme: whether you chose the light or dark theme.
• preptima_bookmarks: an older bookmark list, moved into preptima_progress_v1 and deleted the next time you visit.

Answer feedback

When signed in, you can say at the end of each answer whether it helped and, optionally, write a short comment (up to 500 characters). We store the question, your yes/no, the comment if you wrote one, the time, and your account, so we can follow up and so you can only rate each answer once. You can see your own feedback; nobody else can, and we use it solely to improve the answers - please don't include personal details in comments.

Questions you submit

When signed in, you can send us an interview question you were asked, with optional details (company, role, round, context). We store what you entered, the time, your account and its review status, so you can see whether it was added. You can see your own submissions; nobody else can. If we publish a question, we publish an edited version and never your name or anything that identifies you.

Plans from a job description

When you paste or upload a job description, it is read in your browser: the file is never uploaded, and email addresses and phone numbers in it are removed first. Building the plan sends us only the topics, level, employer type, domain and time you confirmed - not the text. If you save the plan, we store those choices and, unless you untick it, the job description text with it, so you can rebuild the plan later. Only you can see it, and deleting the plan deletes it. If you ask us to cover skills we don't have yet, we store that request like a submitted question, with the job description only if you tick “include”.

Analytics

We use three analytics tools:

• Vercel Web Analytics: page views, and the events listed below. No cookies.
• Vercel Speed Insights: how fast pages load. No cookies.
• Google Analytics 4: page views, visits and the events below, using the cookies described above. Google Signals, ad personalisation and every advertising use are turned off. Like any website request, it also sends your IP address and browser details to Google.

Besides page views, we record when someone uses these features, so we can tell which ones help:

• searching: the search term (lowercased, up to 80 characters) and how many results it found;
• loading more search results;
• marking a question mastered or needing review, bookmarking it, liking it, or copying its link;
• saving or deleting a study plan, or adding a question to one or taking it out, and whether it worked;
• submitting a question: whether it sent and the round type, never the question;
• using the job-description planner: each step (file read, analysed, built, saved, requested) with counts such as how many topics were found - never the text;
• signing up or signing in: the method used and whether it worked;
• requesting or completing a password reset, and whether it worked;
• saving or skipping the profile questions (whether, never your answers);
• rating an answer helpful or not (the rating only, never your comment);
• seeing the free-view limit message;
• an error page being shown: which kind of error and an opaque error code, never its details.

These events carry the question involved and the outcome. They never include your email address, your account, or anything you type except a search term.

The events go to both Vercel Web Analytics and Google Analytics, so Google receives your IP address along with the pages you view and any search terms you enter.

Deleting your data

You can delete your account yourself: open your profile while signed in and use “Delete my account”. It removes the account along with your progress, bookmarks, likes, saved plans and notes, submitted questions, answer feedback and profile answers, at once and for good. If you cannot sign in, send us a message through our LinkedIn page telling us the email address your account uses and we will do it for you. To remove what is stored in your browser, clear this site's data in your browser settings.

Changes to This Policy

We may update this policy from time to time. Any changes will be posted on this page with an updated revision date.

Contact Us

If you have any questions about this Privacy Policy, please contact us via our LinkedIn page.