Privacy at KitsuWire.

Privacy choices

On the first visit, KitsuWire asks visitors to choose whether optional analytics and advertising technologies may be used. Necessary storage remains active because it is required to remember security and site preferences such as theme, the fox cursor setting and the privacy choice itself. Visitors can reopen the privacy controls at any time using the Privacy settings link in the footer.

Website access

Technical information such as IP address, browser information and request timestamps may be processed by the hosting and reverse-proxy infrastructure to securely deliver and operate the website. Infrastructure access logs are separate from KitsuWire's application analytics.

First-party analytics

KitsuWire's application analytics runs only after a visitor enables Analytics in the privacy controls. When enabled, KitsuWire creates a random first-party visitor identifier and a random session identifier. These identifiers are used to estimate page views, sessions, new and returning visitors and content performance. The visitor identifier is stored for up to 180 days, while the session identifier is refreshed for up to 30 minutes of activity.

The application analytics database stores the visited path, an article slug when applicable, the external referrer hostname when available, the pseudonymous visitor and session identifiers, and the event time. It does not intentionally store the visitor's IP address, account identity, email address, browser fingerprint or user-agent as part of application analytics. Browser Do Not Track signals are respected. If Analytics is disabled again, the first-party analytics identifiers are removed from the browser. Historical pseudonymous page-view records remain subject to the configured analytics retention period, designed to default to 180 days.

Advertising

KitsuWire is designed so advertising is shown on eligible article pages rather than the homepage. Advertising consent is separate from analytics consent. The Google AdSense loader remains inactive when no AdSense publisher ID is configured and, when a valid publisher ID is configured, it is loaded only after the visitor enables Advertising in the privacy controls. Provider-specific consent and policy requirements must be reviewed again before live advertising is enabled.

Newsletter

When a visitor submits the newsletter form, KitsuWire stores the normalized email address, signup source, request time and double-opt-in status in PostgreSQL. New addresses remain inactive until a confirmation link is successfully used. Confirmation tokens are stored only as cryptographic hashes. Brevo is the intended primary transactional delivery provider when configured and may process the recipient address and confirmation link for delivery. Unsubscribed addresses are marked so they are not included in the active recipient list.

Your rights

The production notice must identify the responsible operator and provide the applicable contact details, legal bases, retention information, processors and data-protection rights for the final deployment. The Imprint page is supplied from private server configuration rather than hard-coded personal data in the source repository.