Cookies and Local Storage

1. Scope

This notice applies to InterfaceKit-operated web properties, including interfacekit.io, blog.interfacekit.io, guides.interfacekit.io, legal.interfacekit.io, agents.interfacekit.io, and related API, Worker, and preview endpoints.

It describes technology controlled by InterfaceKit application code separately from technology an infrastructure provider may use to deliver or secure a request.

2. Current InterfaceKit practices

InterfaceKit application code does not currently set browser cookies on these properties. It does not currently include advertising cookies, cross-site tracking pixels, third-party advertising scripts, or client-side behavioral analytics.

The authored Blog, Guides, and Legal applications do not currently write account, analytics, advertising, or preference data to browser local storage or session storage. The agents.interfacekit.io service returns authenticated resources to software clients and does not use browser storage for account sessions.

The main product at interfacekit.io uses one local-storage record after sign-in. Local storage stays in the browser and, unlike a cookie, is not automatically attached to each web request.

3. Signed-in session storage

After you successfully verify a passwordless code on interfacekit.io, the product stores an access token, token type, token expiry, email address, and internal account identifier under the local-storage key “interfacekit.auth.” This is used to keep you signed in, show account state, and authorize protected requests you choose to make.

The access token expires after seven days. The local record is removed when you log out, when the product detects that it is invalid or expired, or when you clear it through browser controls. Removing the record signs you out but does not delete your InterfaceKit account.

4. Infrastructure technologies

Cloudflare and other infrastructure providers process request information needed to route, secure, rate-limit, and operate the service. Depending on provider configuration and the nature of a request, a provider may use strictly necessary cookies or similar security technology under its own documentation.

InterfaceKit does not use provider-generated security data for advertising. A provider’s independent sites, such as a dashboard or policy page reached through an external link, are governed by that provider’s own notices.

5. Your controls

Most browsers let you inspect and remove cookies and local storage for a site. Blocking or deleting the “interfacekit.auth” record signs you out and prevents signed-in features from working until you authenticate again. Public pages remain available subject to ordinary security controls.

InterfaceKit does not currently use the advertising or cross-site tracking technologies that browser Do Not Track or Global Privacy Control signals are designed to address. If that changes, we will describe how we respond and provide controls required by applicable law.

6. Changes to this notice

Before InterfaceKit application code begins using non-essential cookies, client-side analytics, advertising technology, or consent-controlled preference storage, we will update this notice and provide notice, choices, or consent controls where required.

7. Contact

Questions about cookies, local storage, or similar technologies can be sent to humans@interfacekit.io.