You’re invited.

Why this is a second step. Your code on its own opens nothing. Accepting it issues a short-lived token that expires in ten minutes; only the button below opens the preview. That is why you are reading this before you are inside rather than after.

Who is asking. This preview is operated by BuildTwin. It is not a public website — it is shown by invitation, and every visit is attributable to the invitation that opened it.

Why any of it is collected. Two reasons, and there is no third. The first is access control: the invitation has to be checked and the session has to be remembered. The second is that the people sending these invitations want to know whether they were opened, and which parts of the site were read.

The cookies. Two keep you signed in: a short one that expires after twenty minutes, and a longer one that lasts thirty days, extends while you keep visiting and stops at ninety days regardless. A third lives for ten minutes, between entering your code and this dialog. All are HttpOnly — this page cannot read them, and neither can any script on the site.

The record. Page views, time on page, scroll depth and clicks are sent to our own server as you browse. A 1×1 image and the server's own request log record page views as a backstop, so blocking scripts reduces the detail but does not stop the record.

Who reads it. BuildTwin, and the person whose invitation you used — they see that their invitation was used, from where, and which pages were read.

Where it lives. On our own servers. Nothing here is sold, and nothing is sent to an advertising network. There is no third-party tracker on this site; the one external resource is a webfont.

How long it is kept. Detailed activity is kept for up to 400 days and then deleted automatically. Summary counts per invitation are kept for as long as the invitation exists.

Your rights. You can ask us what we hold about you, ask for a copy, or ask us to delete it — hello@buildtwin.com. We will answer within 30 days.

Changing your mind. The basis is your consent, stored with the version below and the moment you gave it. Write to hello@buildtwin.com and we delete the record and close the session. Withdrawing is meant to be exactly as easy as giving consent. Declining now costs you nothing: your code stays as it was and you can come back to it.

If you decline. Nothing happens and nothing is stored beyond the record that a code was entered. The preview does not open: we are not able to show an invitation-only site without knowing which invitation opened it.