ScaleCrafts

Privacy policy

ScaleCrafts is a place to practice system design interviews. This page explains what we collect when you use it, why, who else sees it, how long we keep it, and how to get it changed or deleted.

Last updated 16 November 2026.

The short version

  • We collect what we need to run your account and grade your designs.
  • Usage analytics and advertising cookies are off until you turn them on, and you can turn them off again at any time.
  • We don’t sell your data. We don’t show ads on ScaleCrafts.
  • Your designs go to an AI model, Anthropic’s Claude, only when you ask for an AI review or take a mock interview.

What we collect

Your account

Your name, email address and password. We store the password only as a salted hash, so nobody, including us, can read it. When you sign up we send you one welcome email, through our email provider, to the address you gave us.

Your work

The designs you draw, your notes, the descriptions you give components, your submissions and their scores, your lists, any “this grading looks wrong” reports you send, your AI review conversations, and your mock interviews (the interviewer’s questions, your answers, and its ratings and debrief).

Designs drawn before you sign up

You can draw without an account. That design is kept only in your browser’s local storage, not on our server, until you sign up or log in. Then it’s saved to your account. Clearing your browser’s site data deletes it.

Security records

When you sign up, log in, fail to log in, log out or hit a rate limit, we record what happened, when, and a shortened version of your IP address (the last part removed). We use these records to protect accounts from password guessing and abuse. We keep them whatever your cookie choice is.

Server logs

Each request to our server is logged with the page or API address (without query strings), the result, how long it took, your browser’s user agent, your account id if you’re signed in, and a shortened IP address. If a page crashes in your browser, the error message, its technical details and the page address are sent to these logs, so we can fix it. Logs never contain passwords, cookies, notes or designs.

Usage analytics (only if you allow it)

Which pages you visit, and which canvas tools you use: for example “a cache component was added”, “the checklist was opened”, or how long a visit to the canvas lasted. These records hold counts and the kinds of things you did, never what you typed. If you aren’t signed in, they’re linked to a random id in a cookie, and when you create an account, your earlier visits are linked to it. We use them to see where people get stuck and what to improve.

Advertising measurement (only if you allow it)

We advertise ScaleCrafts on Google Ads. If you allow advertising cookies, we load Google’s tag, which tells Google Ads that someone who saw our ad visited or created an account. Google handles that data under its own privacy policy. If you don’t allow it, the tag isn’t loaded at all.

Cookies

CookieWhat it’s forKindLasts
sc_sessionKeeps you signed inEssential30 days, or until you log out
sc_consentRemembers your cookie choiceEssential1 year
sc_vidA random id that links your visits before you sign inUsage analytics1 year
_gcl_au and other Google cookiesAd measurement, set by Google’s tagAdvertisingSet by Google, up to about 3 months

We also keep a random id for the current browser tab in session storage, so one visit’s analytics can be grouped. It’s used only with your analytics consent and disappears when you close the tab. Local storage also keeps a design you drew before signing up, your progress through the guided first problem, and on admin pages the currency chosen for the AI usage dashboard. These never leave your browser.

Who else processes your data

  • Render hosts the ScaleCrafts server, in Singapore, and keeps its logs.
  • SendPulse delivers our emails. It receives your name and email address, only to send you the welcome email after you sign up.
  • Amazon Web Services hosts our database, in Mumbai, India. The connection to it is encrypted.
  • Anthropic, the maker of the Claude AI model, receives a submitted design, its notes, the problem and its score when you ask for an AI review, and your follow-up questions. During a mock interview it receives your design and notes as they are when you answer, the problem, and your answers. Claude uses them to write the review or to interview you. Anthropic processes them outside India, under its commercial terms for API customers.
  • Google Ads, only if you allow advertising cookies (above).
  • Google Fonts serves our typefaces, so your browser contacts Google’s font servers when a page loads, which shows them your IP address.

Some of these providers process data outside India. We don’t sell or rent your data to anyone.

How long we keep it

  • Your account and your work: until you ask us to delete your account.
  • AI review conversations and mock interviews: 90 days. After that we keep only token counts and costs, not the content. The design graded at the end of an interview is kept as a normal submission.
  • Usage analytics: about 13 months. Security records: 12 months.
  • Server logs: for the period our host keeps them, usually days to weeks.

Deleting your account deletes your work, AI conversations, analytics and security records linked to it.

Your rights

You can ask us to:

  • tell you what personal data we hold about you and how we use it
  • correct or complete it
  • delete your account and its data
  • name someone to exercise these rights for you if you die or can’t act yourself

You can withdraw consent to analytics or advertising cookies at any time with Change cookie settings, as easily as you gave it. Write to support@scalecrafts.io for anything else, including complaints. If you’re in India and not satisfied with our answer, you can complain to the Data Protection Board of India.

Children

ScaleCrafts is for adults preparing for job interviews. Don’t create an account if you’re under 18.

Changes

When we change what we collect or why, we update this page and its date. If a change needs your permission, we ask for it again, for example by showing the cookie choice again.