Privacy
Measure useful actions, not personal browsing profiles.
This notice covers loke.dev and related projects that send aggregate events to loke.dev, including Shuffleworks and FlareCheck.
Last updated: 7 August 2026.
Who operates these sites
Loke operates these personal projects from Sweden. Questions, objections, and privacy requests can be sent through the contact page or tohi@loke.dev.
Infrastructure and security logs
The sites use Cloudflare for hosting, delivery, security, and Worker execution. Like other web infrastructure, Cloudflare receives network information needed to deliver a request, such as an IP address, user agent, requested URL, and security metadata. Some of that information may appear temporarily in infrastructure logs according to the Cloudflare account settings and retention terms.
Aggregate site and event analytics
Loke.dev uses Muro Analytics for basic page-view reporting. Its browser script keeps a random visitor ID in local storage for up to 24 hours and a random session ID in session storage. These IDs are used to group visits, not to identify you by name.
Page-view requests may include the page path, referrer, UTM campaign values, screen size, device type, browser, operating system, and a timestamp. The browser script does not send an email address, account ID, advertising identifier, or raw IP address. The analytics endpoint can still receive normal network information needed to deliver the request.
The sites may also use Cloudflare Web Analytics and a separate custom event collector for approved actions. Those events can include a site, page path, placement, target, campaign label, and count, such as a successful command copy, a tool action, a completed shuffle, or an outbound partner click. The custom event collector does not set a cookie or use local storage.
Affiliate and outbound links
Some product links pass through a short loke.dev redirect. The redirect records the product and link placement before sending the browser to the provider. A commission-capable link is disclosed separately under theaffiliate and editorial policy.
Contact messages and error reports
A contact message contains the name, email address, and message supplied by the sender. Resend processes the email delivery so the message can be answered. When error monitoring is configured, Sentry may process technical diagnostics needed to investigate failures. Do not put secrets or sensitive personal information in a contact message.
Service providers and external sites
Current infrastructure and operational providers may include Cloudflare for delivery, security, and analytics, Muro Analytics for page-view reporting, Sanity for published content, Resend for contact email, and Sentry for error diagnostics. Following an external or affiliate link makes the destination provider responsible for its own processing under its privacy notice.
Retention and choices
Aggregate application events are kept only as long as they are useful for product and affiliate measurement. Analytics Engine currently has a three-month data window when enabled. Muro Analytics retention follows the provider's service and account settings. Infrastructure logs follow provider and account retention settings. Contact messages are retained only as needed to respond, maintain reasonable records, or meet a legal obligation.
You can block browser analytics requests using browser privacy controls. You may also ask about access, correction, deletion, restriction, or objection through the contact details above. A request may require enough information to locate the relevant record; anonymous aggregate events cannot normally be connected back to a particular visitor.