Privacy

Kyloth's public website and demonstration previews are available while new public sign-ups remain closed. This page describes current website behavior and identifies privacy work still required before customer enrolment.

Analytics runs only when its settings are configured. The preview supports PostHog for usage events and Google Tag Manager for loading configured tags. Which tags and providers will be used at launch still needs review.

PostHog and Google Tag Manager wait until you choose “Allow analytics”. Before a choice, or after “No thanks”, these optional analytics tools do not load. Events from before your choice are not saved for later sending.

The same choice applies when you are signed in. Signing in does not turn analytics on. Allowing analytics grants only the analytics consent signal; advertising consent signals stay denied. The actual tags in a configured Google Tag Manager container still need review before launch.

Usage events can include page addresses and technical request information. Signed-in usage can be linked to account and organisation IDs, product and plan. The application restricts direct contact details in its event fields, but that does not make every event anonymous or prove that a URL contains no personal information.

Kyloth’s PostHog and Google Tag Manager loaders are excluded from merchant storefronts, theme previews and private support-status links. Storefront analytics has a separate implementation and needs its own seller-facing notice before launch.

The preview uses browser cookies for preferences. These are the intended maximum lifetimes; your browser can remove them sooner. This list is not a complete inventory of account-session storage or third-party cookies:

kyl-theme saves light or dark mode for up to one year. kyl-intent remembers a selected theme for up to 30 days. kyl-announce remembers an announcement dismissal for up to 30 days.

kyl-consent saves the banner choice for up to 180 days. It is shared across the configured site domain and its subdomains.

kyl-src saves campaign labels and the referring site for up to 30 days. It is also shared across subdomains. These values come from links and request information; they must not be treated as automatically free of personal information.

When persistent PostHog storage is enabled, its browser identifier can be shared across subdomains. Signed-in events can link that identifier to an account. Its presence on a subdomain does not mean the analytics loader runs on that page. Provider settings, retention and data destinations still need launch review.

Preview images can load from Cloudinary. Fetching an image sends a request to that host, which can receive network and browser information. This is separate from the analytics choice.

If you choose to like a guide or article, the preview sets a signed feedback cookie for that item, for up to one year. It stores keyed browser and daily network identifiers with the item, choice and timestamps. The feedback table does not store a raw IP address or email. These identifiers help limit duplicate likes; counts are not verified people or purchases. Undo removes the public like, while the duplicate-prevention record remains.

If you submit a Journal comment in the preview, it stores your display name, comment, submission ID, timestamps, moderation status and a keyed daily network identifier. Only approved comments are public. No email is required, and commenting does not subscribe you. There is no automatic comment-retention schedule yet. Avoid posting private information.

Newsletter activation is pending. When enabled, the general newsletter forms send an email address and signup source to Resend. Journal signup records the selected topics and its agreement version and time. These forms use an unchecked agreement box. Their provider contact records are separate from the guide-request records described below. Unsubscribe handling, provider retention and the public contact process must be checked before promotional emails begin.

A marketing PDF request requires an email address and a separately checked agreement to Kyloth promotional tips, product updates and offers. Kyloth records the encrypted deliverable address, a keyed email lookup identifier, the requested guide and version, request source, exact agreement text and version, and server timestamps. A keyed network identifier helps limit repeated requests; the guide record does not store the raw network address. These local records support the document request and preserve agreement evidence. Requesting a guide does not reverse an existing promotional unsubscribe or automatically enroll a provider contact, and this feature does not send promotional campaigns.

When guide email delivery is configured, the selected mail provider receives the deliverable address and a message containing the PDF link. Request recorded means the request is queued, not that it arrived in an inbox. The link expires seven days after the request is recorded and gives access to that specific guide version while the guide remains available. Anyone with a forwarded link can use it until expiry or revocation. Opening it does not verify the reader’s identity, confirm promotional signup or change unsubscribe status. Kyloth staff manage the guide’s content and publication; this feature does not create a customer document library. Retention periods and the access, correction and withdrawal process remain part of the pending launch review.

The local support preview can store enquiry contact details, messages and case history. Configured email and AI features can send selected information to their providers. Their scope, retention and permission requirements need review before public use. Do not put passwords, payment details or sensitive customer information into a preview enquiry.

Ask Kyloth provides guidance from public product pages and guides. When AI is configured, pressing Send shares your question and recent questions with Groq to prepare an answer. Do not include passwords or private customer, patient or student records. Kyloth keeps this chat in the current browser tab's memory until you clear it or reload; it does not save chat text in its database or analytics. Groq applies its own processing and retention terms. A generated answer can be mistaken; check its source links. Opening the support form does not send your chat to a person.

“Change your analytics choice” stops optional analytics, clears the saved choice and reloads the page to remove loaded analytics scripts. When analytics is configured, you can then choose again, whether signed in or out. This cannot recall requests already sent or delete records already held by providers.

Clearing preference cookies can reset your choices. Clearing account-session cookies can sign you out. Provider deletion requests, retention periods and a staffed privacy contact are still to be confirmed before launch.