Skip to main content
Last Updated: July 2, 2026 This Cookie Policy explains how Timekettle Developer (“Timekettle”, “we”, “us”, or “our”) uses cookies and similar technologies on Timekettle Developer websites, documentation, dashboards, account pages, support channels, and related browser-based services. This policy should be read with our Privacy Policy and Terms of Service.
This policy covers browser technologies such as cookies, pixels, local storage, and session storage. SDK local storage on Android or iOS, such as authentication caches, encrypted offline licenses, model files, diagnostic logs, Keychain, Keystore, UserDefaults, or app-private files, is described in the Privacy Policy and is not a browser cookie.

​
1. What cookies and similar technologies are

Cookies are small text files stored by a browser when you visit a site. Similar technologies include local storage, session storage, pixels, tags, software development kits used in browser applications, and device or browser identifiers. These technologies help sites remember sessions, protect accounts, keep preferences, understand usage, diagnose errors, and provide support features.

​
2. How we use cookies

We may use cookies and similar technologies for the purposes below.
These technologies are required for core site and dashboard functions, such as page routing, authentication, session continuity, load balancing, fraud prevention, service availability, and security.You cannot disable strictly necessary cookies through our cookie preference tools because the site or dashboard may not work without them. You can block them in your browser, but some Services may stop working.
These technologies help detect unauthorized access, credential abuse, replay attempts, suspicious traffic, excessive requests, bot activity, and other threats. They may process IP address, user agent, session identifiers, request timing, and account security events.
These technologies remember choices such as language, region, display preferences, cookie choices, documentation state, and dashboard settings so you do not need to re-enter them each time.
These technologies help us understand how developers use the documentation and Services, which pages or features are used, where errors occur, and how performance can be improved. Analytics data should be configured to avoid collecting raw customer audio, complete translation text, secrets, or direct identifiers where not needed.
These technologies may support documentation search, help widgets, product announcements, support chat, ticket forms, feedback tools, and account communications. They may remember your support session or connect an authenticated account to a support request.
Documentation hosting, search, analytics, support, security, payment, and infrastructure providers may set or read cookies when they provide services to Timekettle Developer. These providers may include documentation platforms, infrastructure providers, analytics providers, payment providers, and support tools used to operate the Services.
Do not place API keys, AppSecrets, tokens, private keys, authorization headers, raw audio, full translation content, or offline license material into browser storage unless the feature has been designed for that storage location and protected accordingly.

​
3. Cookies we do not use for SDK translation traffic

Browser cookies are not the mechanism used by native SDKs to perform device binding, offline license validation, real-time room connection, or local model inference. Native SDK integrations may use platform storage and app-private files for SDK-specific purposes, including authentication session caches, encrypted offline licenses, diagnostic logs, model files, Keychain, Keystore, and UserDefaults. See the Privacy Policy for more information about SDK storage and diagnostics. Where required by law, we request consent before using non-essential cookies. Strictly necessary cookies may be used without consent where they are required to provide a requested site, dashboard, security, account, or service function. If a cookie banner or preference center is available, your choices apply to the browser and device where you make them. You may need to set preferences again if you clear cookies, use a different browser, use a different device, or browse in private mode.

​
5. Your choices

You can manage cookies in several ways:
  • Use the cookie banner or preference center when available.
  • Change your browser settings to block, delete, or limit cookies.
  • Use browser controls to clear local storage, session storage, and site data.
  • Configure device or browser privacy settings where available.
  • Use account or dashboard settings for product communications where those settings are offered.
Blocking cookies can affect site behavior. For example, you may be logged out, preferences may not persist, dashboard features may fail, documentation state may reset, or support tools may not work.

​
6. Do Not Track and Global Privacy Control

Some browsers send “Do Not Track” signals. Because there is no consistent industry standard for responding to those signals, our sites may not respond to them. Where required by applicable law and technically supported, we will treat Global Privacy Control or similar legally recognized browser signals as an opt-out from applicable non-essential or sale/share-related processing. Timekettle Developer does not use SDK end-user data for cross-context behavioral advertising through browser cookies. Retention depends on the type of technology:
  • Session cookies usually expire when you close your browser or end the session.
  • Authentication and security cookies may persist long enough to keep you signed in, protect your account, and detect suspicious activity.
  • Preference cookies may persist so your settings and consent choices remain available.
  • Analytics and performance cookies are retained for a limited period consistent with the purpose of measuring and improving the Services.
  • Legal, billing, security, and audit records derived from cookie events may be retained longer where required for compliance, dispute resolution, fraud prevention, or service security.
You can delete cookies and browser storage through your browser controls at any time.

​
8. Changes to this policy

We may update this Cookie Policy when we change the technologies, providers, purposes, retention periods, legal requirements, or consent mechanisms used by Timekettle Developer. The updated version will be posted with a new last updated date.

​
9. Contact

Contact Timekettle through the support, account, legal, or security channels made available in the Timekettle Developer dashboard, documentation site, order form, or service agreement. If those channels are unavailable, contact support@timekettle.co.