Cookie policy
A clear explanation of cookies, browser storage and the choices this website provides.
What cookies and similar technologies do
Cookies are small pieces of information a website can ask a browser to retain and send with later requests. Local storage, session storage, tracking pixels and other device-access technologies can serve related purposes. Their purpose matters as well as their technical name.
What this application currently uses
The public planner, motion preference and selected demonstrations are not saved in local storage or session storage. The private workspace uses a necessary session cookie named build_studio, scoped to /api, to keep administrators signed in and protect requests. It expires at the end of the browser session, with server-side access expiring after eight hours of inactivity. No optional analytics, advertising or social-media tracking integration is installed.
- Project brief: drafts are held in page memory; sent briefs are saved in the private server database. A downloaded copy is saved only when requested.
- Motion preference: held in page memory. The site also reads the browser’s reduced-motion preference to adapt animations.
- Interactive previews: selections are held in page memory and do not connect to live customer systems.
- Font and image files: ordinary website assets, which a browser may cache to deliver pages efficiently. The application does not use asset caching as an advertising identifier.
Hosting and security mechanisms
The absence of application cookies does not guarantee the absence of infrastructure cookies. A production host, access gateway or security challenge can add its own delivery, authentication or abuse-prevention mechanisms. Those mechanisms must be checked on the actual deployed domain, including any restricted-access pages.
This policy describes the website application. A cookie appearing through a host or a browser extension should not be presented as an application cookie without verifying its source and purpose.
Managing your choices
You do not need to accept optional tracking to use this application. No optional tracking is enabled, so there is no optional tracking switch to turn off. The motion control is available in the footer.
Your browser settings let you review or remove cookies and site data and control future storage. Blocking all storage may affect a hosting sign-in or security check including the internal workspace session cookie. Clearing browser data does not necessarily remove text files you have downloaded.
If the technology changes
Before adding optional tracking, Build.krd must identify its providers, purposes and duration, update this policy, and implement the choice required by the applicable law. Where prior consent is required, the relevant technologies must remain inactive until consent is given. Refusing or withdrawing that consent must be as straightforward as giving it.
Consent is not obtained by using a website, scrolling, downloading a brief or accepting general terms. Any future preference control must describe a real integration and actually control it.