If you create an account, Supabase Authentication handles your email, password credentials, and session. Kuchloge stores your selected products, named comparisons, and their product membership. Search text is evaluated in the application and is not currently saved as customer history.

On the web administration page, unfinished product-intake fields are kept in local browser storage so navigation, refreshes, or another tab do not destroy the draft. They are removed after a successful save or when the administrator chooses Clear draft, and are not uploaded until the administrator saves.

When you affirmatively continue to a merchant, Kuchloge records the product, listing, source route, time, and—when signed in—your user ID. The server transforms network address and browser information into a one-way keyed session hash for short-window abuse prevention; raw network address and browser text are not stored in the affiliate event.

If a page fails to render, Kuchloge sends the error type, sanitized message, route path without its query string, platform, app release, and occurrence count. Reports are deduplicated and do not contain stack traces, search text, full URLs, user IDs, email addresses, tokens, raw network addresses, or browser text. A one-way keyed session hash is used only to enforce a short reporting limit.

The data is used to provide private saves and comparisons, secure accounts, prevent handoff abuse, and measure aggregate affiliate activity. Supabase hosts authentication, database, and server functions. Cloudflare serves the web application. Embedded videos are delivered by YouTube, and merchant handoffs open Amazon under those providers’ own notices.

Saved products and comparisons remain until you remove the account. Use Account → Delete account to permanently remove the login and private workspace. Related affiliate events are detached from the user and stripped of their session hash; non-identifying product, route, and timestamp fields may remain for aggregate accounting and fraud records.

Kuchloge does not currently enable behavioural advertising or third-party customer analytics. The application diagnostics described above are operational reliability records, not behavioural profiles. If product analytics are enabled later, this notice and the release record must be updated before collection begins.

A public privacy contact must be configured before users are invited.