Cookie policy

What this policy covers

This policy applies to cookies and similar technologies used when you visit the Zuse marketing website, including pages at this site and the public waitlist form. It does not replace the Privacy Policy or describe the cookie practices of websites that Zuse links to. Those sites have their own operators, policies, and browser controls.

What cookies and storage are

A cookie is a small value that a website asks your browser to store and return with later requests. Similar technologies include local storage, session storage, and other browser-managed state. They can remember a preference, keep a requested feature working, or help a service understand how it is being used. The browser, not the page itself, controls whether these values can be stored; the website or service can request an expiry, subject to browser rules.

Categories we use to describe storage

These categories are a plain-language way to explain the role of a cookie or storage value. A particular browser or deployment may use a value differently, so this page describes purposes rather than promising particular cookie names or exact expiration dates.

Strictly necessary

Storage that is needed to deliver a page, maintain a requested security or routing function, or process a feature you chose to use. Turning this off can prevent the site or that feature from working.

Preference

Storage that remembers a choice, such as the website’s appearance, so you do not have to make it again on every visit. The current site can store the selected theme in browser storage and the selected language in a first-party cookie; these preferences are not used for tracking.

Analytics

PostHog measures website page views and selected link clicks using temporary memory. We disable persistent analytics cookies and local storage, session replay, and automatic interaction capture.

Third-party

Storage set by a service other than the page’s operator. The current website does not embed an advertising network, social widget. PostHog is the website analytics processor. A linked service may set its own cookies after you leave Zuse; its policy controls those cookies.

Current website practice

The marketing site does not intentionally set advertising cookies. Website analytics are disabled when your browser sends Do Not Track or Global Privacy Control. It has no website account sign-in flow evidenced in the current public routes, and the public waitlist endpoint does not require authentication. The site may still use browser-managed state needed by the web framework or a feature you request. For example, the appearance preference can be kept in local storage rather than a server cookie.

The language selector stores your choice in the zuse-language cookie for up to one year. Without a saved choice, the landing page uses your browser’s preferred languages, then an approximate country hint supplied by the hosting service from your IP address. This feature does not request precise location access. Clearing or blocking cookies prevents the site from remembering your language across visits.

The Zuse desktop and mobile apps have separate product behavior. Their usage analytics are described in the Privacy Policy. A desktop or cloud authentication flow may open a provider or service-owned page in a browser; any cookies that page sets belong to that service, not to this marketing website.

The desktop browser-session import

Zuse does not passively enumerate browser credentials. In the desktop app, you can explicitly choose Settings → Browser and import valid cookies from a supported local browser profile. This copies a browser session into Zuse’s isolated built-in browser; it is not a cookie placed by zuse.sh and is not a website analytics mechanism.

The import does not copy browsing history, bookmarks, autofill data, or saved passwords. Imported cookie values are kept in the desktop app’s encrypted local vault and can be restored after an app restart. Cookie values do not enter chat, renderer state, logs, or the browser settings interface. An agent must receive your explicit approval before using an imported signed-in session for a particular task and domain.

Ordinary cookies, site storage, and cache in the built-in browser use an isolated session. Clear imported removes the encrypted import record and any imported cookie whose value has not since been replaced by the site. A refreshed or rotated cookie can remain in the built-in browser session until you use Clear browsing data to remove cookies, site storage, and cache from that built-in browser. Neither control changes the source browser.

Session and persistent storage

Session storage usually lasts until the relevant browser session ends. Persistent cookies or local storage remain until they expire or you, the browser, or the service removes them. We do not state exact periods here because they can depend on the browser, deployment, and purpose. You can clear website storage through your browser controls.

For explicitly imported desktop cookies, Zuse preserves an expiry date when the source cookie provides one. Cookies without an expiry can remain in the encrypted local vault until you clear or replace the import. The imported copy is separate from the source browser’s copy.

Your browser controls

Most browsers let you block cookies, restrict third-party cookies, use private browsing, inspect stored values, and delete cookies or site data. The names and behavior of those controls differ by browser and device. Blocking all storage may affect appearance preferences or other requested features. Deleting cookies in your everyday browser does not automatically clear an imported copy held by the Zuse desktop app; use the app’s browser controls for that copy.

Do Not Track and Global Privacy Control

The current website does not advertise a separate Do Not Track (DNT) or Global Privacy Control (GPC) preference workflow. Because the marketing site currently has no advertising or website analytics program, there is no website analytics profile for these signals to opt you out of. If the site’s storage practice changes, we will update this policy and describe how those signals are handled.

Consent and choices

There is currently no cookie banner or cookie-preference center on the marketing website. You can use your browser’s storage controls and the website’s appearance setting to manage the browser state that exists today. If Zuse introduces non-essential website cookies or similar tracking technologies, this policy will be revised and the site will present an appropriate way to make the choices offered for that practice.

Linked and third-party services

The site links to services such as the Zuse source repository, community, releases, and social profiles. Those destinations may use cookies, storage, authentication sessions, or analytics under their own policies. Zuse does not control those technologies merely because the site links to them. Review the destination’s policy before signing in or sharing information there.

Changes to this policy

We may update this page when the website, desktop browser, or storage practice changes. The effective date at the top will show when the current version was published. Check this page periodically if cookie behavior is important to you.

Questions

Questions or corrections about this policy can be raised through the public Zuse repository or the Zuse Discord community. These are the contact channels currently published by Zuse; this policy does not provide an unverified email address or mailing address.