Privacy Notice

haas-lab is operated by an individual based in the Republic of Korea. That person decides why and how the personal data described here is processed, and is the point of contact for any question about it.

There is no company behind haas-lab yet — no incorporated entity of any kind. We would rather tell you that than name one that does not exist. If that changes, this section changes with it and the date at the top moves.

Write to privacy@haas-lab.com. We aim to respond within 10 working days.

We do not ask for a password. Everything in the first row arrives from the identity provider you choose at sign-in.

Firmware binaries are treated as your content. We do not inspect them beyond the automated safety checks needed to protect the hardware, described in the documentation. If you put personal data inside a firmware image or print it over the serial port, it lands in the job record like anything else.

We do not build a profile of you to predict or influence what you do, we do not make automated decisions with legal or similarly significant effects about you, and we do not use your data to train machine-learning models. If you turn analytics on, we count what happens in the product, under a random identifier that we create when you turn analytics on and store with your account. It lets PostHog group your visits, across your devices, under one record, and lets us have PostHog delete that record when you turn analytics off or close your account. It is never your name, email or account number, and a new one is made if you turn analytics on again. We use analytics to see which features are used, so we know what to improve. If you also turn on session replay, we use the recordings only to see where people get stuck or confused on a page, or where it fails or is slow, so we can fix it.

Until August 2026 the service ran from a single workstation in Korea. It no longer does, and that is the reason this notice exists in its current form.

We do not sell personal data and we do not share it for anyone else’s marketing. Data reaches the following companies because they run infrastructure on our behalf, and they process it only on our instructions. Boards hosted by other users are the one recipient that is a person rather than a company we instruct; section 12 below says what a host receives and what they do not.

Analytics and session replay are sent to e.haas-lab.com, an address of ours that PostHog runs as a reverse proxy and that forwards to PostHog, Inc. in the United States. Because the address is ours, a tracker blocker may not recognise it, which is one reason we ask first and send nothing without a yes. The overseas-transfer items hold for visitors as for accounts: what is sent is listed in section 2, the country is the United States, it is sent as you browse after you say yes, the recipient and its contact are in the table above, its purpose and retention are in sections 3 and 6, and you can refuse by not ticking the transfer, which costs you nothing.

Because these companies and their facilities sit outside the Republic of Korea, using haas-lab necessarily involves transferring your personal data overseas, for the whole time your account exists, for the purposes in section 3. The categories transferred are the ones listed above. A self-hosted bench is different: it can be in any country, which we do not know and cannot name for you, and section 12 says what reaches one.

If you do not want your personal data transferred on these terms, do not create an account; if you already have one, write to us and we will close it and delete the data described in section 6. We cannot operate the service without these transfers, so refusing them and using haas-lab are not compatible.

We may also disclose data where the law requires it, and to professional advisers under a duty of confidence. If the business is ever sold or reorganised, we will tell you before your data moves to a different operator.

Being plain about this: most of what we hold is kept until you delete it or your account is closed. Only three things are deleted on a schedule, and their rows below say when: rate-limit counters, invite links and our bench's older logs. What Cloudflare or PostHog holds for us is kept under their retention, as stated. We would rather say that than publish a retention schedule nothing enforces.

When you close your account we delete your identity, jobs, firmware, C source, serial logs, tokens, feedback and ledger, but not yet the data files attached to C source (above). While a damage report that our own bench, or we, filed about one of your jobs is under review, closing your account waits until it is resolved, because closing it would delete the report. A report from a self-hosted bench about a free run does not make you wait: it is deleted with the job and is not reviewed. We may keep a minimal record that a given account existed and was closed where we need it to meet a legal obligation, and no longer than that requires.

These rights are open to everyone who uses haas-lab, wherever you live. You can ask us to:

• confirm whether we hold personal data about you, and give you a copy;
• correct anything inaccurate;
• export your data in a machine-readable form;
• delete your account and the data described in section 6;
• stop or restrict a particular use; and
• explain anything in this notice that is unclear.

Email privacy@haas-lab.com from the address on your account. If you write from a different address we will ask you to prove control of the account one, because acting on an unverified deletion request is its own kind of breach.

Two of these are buttons on your profile page: one downloads a machine-readable copy of your data, and one deletes your account and the data in section 6. The rest — correcting a particular field, restricting one use, or closing an account that still has a damage report from our own bench under review — a person handles from the email above. You can also revoke an individual API token from your settings. You can also delete any feedback you sent, a board suggestion included, from the Feedback page or your list of suggested boards; it is deleted for good, with our reply. Deleting a single job is not available yet; write to us and we will.

You turn this browser's analytics and session replay off under “Privacy choices” at the foot of every public page, signed in or not; inside your account, the account menu's “Privacy choices” opens your account's choice. Sending stops at once in this browser. The browser then sends the identifier to our server, which queues the deletion, and 23 to 47 hours after it is queued we ask PostHog to delete everything sent under it. If our server cannot be reached or does not accept the request, the browser keeps the identifier and asks again on your next visit. Turning session replay off while analytics stays on does the same and starts a new identifier. Privacy choices shows the identifier, so you can write to privacy@haas-lab.comwith it to see or delete what was sent. If you answer “no” for your account, this browser's grant ends too: at once if you answer in the panel, and on the next signed-in page you open if you answer on the Profile page, in both cases only when the “no” is later than this browser's “yes”.

Where you live may give you further rights, or a specific way to enforce them. We act on any request the law that applies to you entitles you to; tell us what you are asking for, and you do not need to cite a statute to get it.

haas-lab is operated from the Republic of Korea, so if we do not resolve your request you may complain to Korea’s Personal Information Protection Commission, or the Korea Internet & Security Agency’s privacy call centre (dial 118). If your own country has a data-protection authority, you may take it there instead.

• No advertising, no advertising identifiers, no ad networks.
• We use one analytics service, PostHog, and only for people who turn it on. It tells us which pages are viewed; on its own it does not record your screen, your keystrokes, what you type into forms, or what you copy. If you also turn on session replay, PostHog records a masked picture of the pages inside your account under your account's choice, and of the public pages under your browser's choice: their layout, your pointer, clicks and scrolling, which boxes you tick or options you pick (never their labels), and where you type and how many characters. Text and what you type show only as asterisks, with the number of characters kept (spaces and line breaks are kept too, so word and line lengths show), apart from words a recorded console message quotes; it does not record which keys you press or what you copy; of what the page prints to the browser's console it records only error and warning messages, and of its requests only their timing, size, method, result code, shortened address and technical details, both cut down as section 2 describes; and it leaves out the balance, your name, email and avatar, tokens, keys, invite links, serial output, job filenames and failure details. On the admin pages, the IDE, a job's live view, the welcome page, Tokens, My bench, Wallet and Profile it records only a masked top bar, the page address, your pointer and scrolling, with everything below the top bar a blank box and no console message or request recorded, as section 2 describes. On Docs and Join the page is blanked in a recording: only the address, the masked footer, your pointer and scrolling are recorded. Sign in sends nothing at all, neither analytics nor recording. We do not share anything with anyone for their own marketing.
• No selling or renting of personal data.
• No use of your firmware, serial output or feedback to train machine-learning models.
• No accounts for children. haas-lab is a developer tool and is not directed at anyone under 14. If we learn that a child has created an account we will delete it. Analytics and session replay, for accounts and for visitors, are only for people aged 14 or older, and the panel that offers them says so.
• No health, payment-card, biometric or government-identifier data. Do not send it to us; if you do, we will delete it.

Access to production data is limited to the people who operate the service. API token secrets are stored only as one-way hashes. Traffic to the site is encrypted in transit. Administrator actions check a database-backed permission on every request rather than trusting the interface.

We are not going to tell you the service is “secure” or claim certification under any framework, because neither has been independently verified. If we ever discover a breach affecting your personal data, we will notify you and the relevant authority as the law requires.

When we change how data is handled — a new recipient, a new country, a new purpose — we will update this page and change the date at the top. For a change that materially affects you, we will tell you before it takes effect rather than after.

When this notice changes what analytics or session replay sends, a yes given under an older version is asked again. A “no”, for a visitor or for an account, is not asked again, even when the notice changes.

Three kinds of storage are used in your browser.

Necessary. Keeping you signed in and protecting the sign-in form. Without these you cannot use an account, so there is nothing to turn off. They are set when you sign in.

Analytics, only if you turn it on.PostHog stores an identifier in your browser's local storage and a cookie so that separate visits can be counted as one person rather than several. They are set for haas-lab.com only, not for its other subdomains. Nothing of PostHog's is stored and nothing is sent until you turn analytics on.

Your choices, in local storage, not cookies. If you answer the panel on a public page, signed in or not, your choice and the random identifier made in your browser are kept in local storage under haas_visitor_consent, before and after a yes. After you close the panel with × without answering, the same item holds the date until which it stays closed. If you are signed in, closing the account panel with × keeps only that date, in local storage under haas_account_consent_dismissed_until; your answer itself is kept with your account, and the date is removed when you answer.

How to refuse.Analytics is off until you turn it on, so refusing means doing nothing. If you have turned it on in this browser for public pages, turn it off under “Privacy choices” at the foot of any public page. If you have turned it on in your account, turn it off under “Privacy choices” in the account menu or in your profile; we stop sending at once in this browser (on your other devices, the next time a page is opened or changed there, and within 30 minutes even if neither happens), clear what is stored in your browser, and within two days ask PostHog to delete everything sent under your analytics identifier. Session replay is a separate switch in the same place, available only while analytics is on and off until you turn it on: turning it off stops recording in the same way and has PostHog delete everything sent under your analytics identifier, recordings included, after which analytics carries on under a new identifier. Turning analytics off also turns session replay off. You can also block or delete these through your browser's own settings, and you can use a tracker blocker. Analytics is sent to e.haas-lab.com, an address of ours that PostHog runs as a reverse proxy, so a blocker may not recognise it. Turning analytics off changes nothing else: every part of haas-lab works the same either way.

Some boards on haas-lab are hosted by other users on their own machines. You can tell which: they are listed as self-hosted, with the display name of the person hosting them, and you choose them by name — a job never lands on one unless you picked it.

When you run a job on a self-hosted board, these reach that host’s machine: your firmware or, for C source, your code and any files you attach to it, which their machine downloads to compile; everything you type at the job’s console, which passes through their machine to the board; and the serial output the board produces. Anyone with access to that machine can read them. The host can also see your display name, the board, the job’s status and when it ran. They cannot see your email address. Runs on self-hosted boards are free.

Their bench deletes your firmware or code and files when the job ends, but its own log can keep the last lines of a compiler error, which can quote your code, and we cannot control what a host keeps on their machine. If you would rather none of this reached another person’s machine, choose a board on our bench instead.

A host can be anywhere in the world. We do not collect or verify where a self-hosted bench is, so choosing one can send your firmware or code and its files, what you type, its serial output and your display name to a country we cannot name for you.

We do not operate a self-hosted board and we do not guarantee one. We promise nothing about whether it is there tomorrow, how it behaves, or what its host does with the machine it is plugged into. If a host reports that your job damaged their board, that report counts against your reputation exactly as one from our own bench does, even though the run cost you nothing. Because the run was free, it does not delay closing your account: if you close it first, the report is deleted with the job and is not reviewed.

If you host a bench, a job’s firmware can use your board’s radio and receive what is transmitted around your machine — the names and addresses of nearby networks and devices, for example. We do not collect that. But anything the firmware prints becomes the job’s serial output, which we store and keep as section 6 describes and which its submitter reads.

Your bench also tells us how its boards are connected to your machine: the USB controller, the hubs the boards are on, and the port each board is in, with each board’s name and serial number. We use it so that you, and we when you ask for help, can see which port a board is in without being at your desk. It does not send anything else you have plugged in, and we refuse it if it does — including anything labelled as a board that your bench has not registered as one. We keep the latest one with your bench, show it to you on your bench page and to our administrators, and delete it when your bench or your account is deleted. A board’s name and serial number are not deleted with it: we already hold them as the board’s own record, and when your account is deleted the board stays on that record, with its job history and no longer linked to you.

If you host a bench, the people you open it to can see its name, its boards’ status and your display name beside them. If someone invites you to their bench by typing your email address, they are told whether an account exists for it and see the display name on that account. While the invite stands, the host who invited you sees your display name and the email address they invited, as it is on your account. If you join through an invite link a host shared, the host sees your display name and not your email address. A link is kept only as a one-way hash of its secret part, which your browser keeps out of the address it sends us. You can leave a bench you joined from My bench.