Cookie Policy

Effective date: 9 October 2026

This Cookie Policy explains how Wikisio uses cookies and related technologies on wikisio.com. It should be read with our Privacy Policy. Cookies are small text files stored by a browser; related technologies can include pixels, tags, local storage, scripts, and identifiers. They can be set by Wikisio (first-party) or by a provider whose service is used on a page (third-party). A technology’s name and lifetime may change when we update services, and some providers use more than one mechanism. This page describes the services and configuration we have observed; it is not a live inventory of every cookie on every visitor’s device.

Why cookies and similar technologies are used

These technologies can help a site deliver a page, remember a setting, protect a form, measure site performance, understand aggregate use, and request or measure an advertisement. They may distinguish a browser from another browser or remember activity over time. A cookie does not necessarily identify you by name. However, online identifiers and associated browsing information can be personal information under some laws, especially when combined with other data. Advertising and analytics providers may process identifiers under their own policies and settings.

Technology categories on Wikisio

Essential delivery and security: The hosting stack and security or content delivery services may use cookies, request identifiers, or other signals to deliver requested pages, balance traffic, prevent abuse, or troubleshoot. The site may not function reliably if essential browser capabilities are disabled. A provider’s security signals may be processed even when an analytics cookie is blocked.

Analytics and audience measurement: Wikisio uses Google Analytics 4 through Google Site Kit. The configured Google tag excludes logged-in WordPress users. Analytics technologies can help count page views, understand engagement, identify referral sources, and compare broad device or browser patterns. Google Analytics may use cookies or other identifiers, depending on Google’s product behavior, the visitor’s location, and our settings. We also load Cloudflare Web Analytics for performance and traffic measurement. Cloudflare says its Web Analytics does not track individual end users across customer properties and does not collect personal data for its analytics metrics; Cloudflare’s separate security or delivery products can process technical request data to operate and protect the site.

Advertising: Selected Wikisio pages have Google Ad Manager publisher tags. These tags can request available inventory and may involve Google or other demand partners, measurement tools, and browser technologies. Such technologies can support ad delivery, frequency capping, fraud prevention, conversion or impression measurement, and personalized or non-personalized ad choices, subject to the applicable settings and consent. Google explains that it and its partners can use cookies for advertising and that prior visits may inform which ads are shown. A tag request does not guarantee a filled ad. Some placements may display no advertisement, and blocking cookies can change the available demand or reporting.

Site functionality and tools: PDF conversion and other browser tools may use scripts and temporary browser storage to process a user’s interaction or keep state while the tool operates. A file upload is not itself a cookie, but a tool may use network requests to perform its function. Avoid submitting confidential or sensitive documents. The processing purpose and provider can depend on the tool and its current implementation; a browser’s developer tools can show the technologies active during a particular session.

AdSense status and distinction from Ad Manager

At the time this Policy was reviewed, Google Site Kit reported that AdSense was not linked and that account and site setup were incomplete. We therefore do not represent that AdSense is approved or currently serving ads. The observed publisher tags are Google Ad Manager tags, which are separate from proof of AdSense approval. If the advertising configuration changes, we will update the policy and the site’s user choices as appropriate. The appearance or absence of an ad does not by itself confirm the status of an account.

Consent, regional requirements, and your choices

Some cookies may be essential to provide a requested service; other analytics or advertising technologies may require consent depending on your location and the applicable law. If a consent banner or privacy control is shown, you can use it to accept or reject optional categories and revisit those choices where the control permits. You can also use your browser to block or delete cookies, clear site data, limit cross-site tracking, or browse in a private session. Browser controls are usually found in privacy or security settings. Each browser and mobile system offers different controls, and deleting a cookie can remove a saved preference or sign you out.

At the time of review, we did not verify a live Google-certified CMP or IAB Transparency and Consent Framework flow on Wikisio; Google Site Kit’s consent-mode setting was not enabled. This means the policy is not a consent interface and does not prove that regional consent signals are implemented. Google requires publishers to use a Google-certified CMP integrated with the IAB framework when serving personalized ads to users in the EEA, UK, and Switzerland. We must configure an appropriate certified consent flow before serving personalized ads in those regions, or ensure the ad request is handled in a permitted way. If your consent choice is required by law, do not rely on this text alone in place of an interactive choice.

Google offers separate controls for ad personalization and account privacy. You may be able to turn off personalized advertising in Google’s controls, and you can review Google’s explanation of ad cookies. Your choice may reduce personalization, but it does not necessarily prevent all ads, disable measurement, or delete information already held by a provider. Cookie blocking can also affect frequency capping, fraud detection, and aggregate reporting.

Third-party providers

Google services may set or read technologies when their tags run. Google and advertising partners control their own systems and may update their identifiers, domains, retention, and options. Cloudflare supports delivery, security, and Web Analytics features. We do not control every provider cookie or browser storage item, and the list a visitor sees can vary by region, consent, browser, page, ad availability, and provider changes. For provider-specific details, use their current privacy notices and settings: Google advertising technologies, Google Privacy Policy, and Cloudflare Privacy Policy.

Managing cookies in common browsers

Most current browsers let you review cookies stored by a site, remove selected or all cookies, block third-party cookies, or clear data when the browser closes. Look in the browser’s Settings or Preferences under Privacy, Security, Cookies, or Site Data. Mobile browsers may also provide tracking protection or app-level privacy controls in the device settings. Instructions vary by product version, so consult the browser’s own help pages. If you use several browsers or devices, a preference on one device may not carry to another. A private browsing window usually removes some local data when closed, but it does not make a visit invisible to websites, employers, networks, or service providers.

Do Not Track and similar signals

Browsers may send signals such as Do Not Track or Global Privacy Control. The meaning and legal effect of those signals vary by jurisdiction and service. The site’s current configuration has not been verified as honoring every signal across Google, Cloudflare, ad partners, and site functionality. Where a signal is legally recognized, we will handle it as required by applicable law and provider capability. You can also use a visible consent control, Google’s ad settings, and browser controls where available.

Retention and security

Cookie duration can range from the length of a browser session to a period set by a provider. The website does not promise one universal lifetime for all cookies. Providers may retain information under their own schedules, and browser deletion removes local copies but may not delete server-side records already created. We use reasonable measures to limit unauthorized access, but no internet transmission or stored data is guaranteed fully secure.

Children, changes, and contact

Wikisio is a general audience information service, not a site designed to collect information from children. Parents or guardians who have a concern about a child’s use may contact us. We may revise this Policy when site features, advertising settings, provider technology, or legal requirements change; the date at the top will be updated. Questions about cookies and privacy can be sent to [email protected]. Include the page and browser involved, but do not send passwords, identity documents, or sensitive records by email.

For a particular session, your browser’s cookie and storage panel is the best way to inspect what was actually placed on your device. The categories above are a plain-language explanation of the purposes of our observed integrations, not a guarantee that every visitor receives every technology or that every provider uses the same data for the same period.