Cookie Policy

Last updated: 20 September 2026

This policy describes cookies and related technologies used on The Indic Journal. The publication is operated from Sweden. For questions, contact contact@theindicjournal.com. Our Privacy Policy explains the wider handling of personal information.

Use the Cookie settings control on this website to reopen the consent panel. Choose Reject optional cookies to withdraw optional consent, or choose categories and save your preferences. The banner also offers Accept optional cookies. Essential functions remain available when you reject optional cookies.

The current banner presents opt-in choices worldwide, including to visitors in Sweden and other EU/EEA countries. Continuing to browse, scrolling or closing a notice is not agreement to optional tracking. If the settings control does not appear, reload the page, check whether a browser extension is blocking it, or contact us. Browser controls provide an additional way to block or remove stored data.

How cookies work · Categories · Names and lifetimes · Browser controls

A cookie is a small value that a website asks your browser to store and return on later requests. Some expire when a browsing session ends; others remain until their expiry date or until you delete them. First-party cookies use this website’s domain. Third-party cookies are associated with another provider.

Related technologies include local or session storage, pixels, embedded frames and scripts. A third-party request may reveal an IP address and browser information even without setting a cookie. Consequently, optional script loading matters as well as cookie storage. Server logs needed to deliver and protect the website are explained in the Privacy Policy.

Necessary / functional

These support a service you request: signing in, maintaining account security, validating a submission session and remembering consent choices. They are not used as permission for unrelated marketing. Blocking necessary cookies in your browser can prevent login, submission or the storage of a cookie decision.

Preferences

Optional preferences can remember choices that are convenient but not essential. Where offered, these are controlled separately in the panel. Some signed-in editor settings relate specifically to an account function you request. A category appearing in the panel does not mean every page sets a cookie in that category.

Statistics

Google Analytics is used to understand visits and interactions with our content after statistics consent. Its identifiers help distinguish visits and sessions; the information can include visited pages, referrals, browser or device details and approximate location. Our configured loader excludes signed-in users and turns off Google signals and advertising-personalisation signals.

Marketing and external features

Where advertising is enabled, Google and its partners may use identifiers to serve and measure advertising, prevent invalid activity and, according to the applicable consent and settings, personalise ads. Optional media or other third-party features can also involve provider tracking. Rejecting these technologies may leave a video or other feature unavailable until you choose to enable it. An ordinary external link does not require consent simply to be displayed; following it takes you to another provider’s website.

The entries below distinguish our configured consent and submission controls from standard service cookies that depend on the features you use. A suffix such as [hash] or [id] varies by installation or user. Provider defaults are identified as defaults, not a claim that every listed cookie has been observed on your device. Browser restrictions can shorten these lifetimes.

Consent preferences: Complianz

Names: cmplz_functional, cmplz_preferences, cmplz_statistics, cmplz_marketing, cmplz_policy_id and cmplz_banner-status, as applicable. Purpose: remember category choices, the policy version and banner status. Type: first-party, necessary consent records. Configured lifetime: up to 365 days; a new choice or policy change can replace them. These records do not themselves permit a refused analytics or marketing category.

Guest article submissions

Name: tij_guest_session. Purpose: a random browser token used to validate the guest submission form and limit abuse. Type: first-party, necessary when using the guest submission feature. Configured lifetime: one day. It is not an advertising identifier. The form itself has a shorter validity period and may require refreshing.

WordPress login and account settings

Names: wordpress_test_cookie, wordpress_logged_in_[hash], wordpress_sec_[hash] and wp-settings-[id] / wp-settings-time-[id], where applicable. They test cookie support, authenticate a session or remember editor preferences. They are first-party. The cookie test lasts for the session. WordPress normally uses a two-day authentication period, or fourteen days with “Remember Me”; session-cookie behaviour, logout and security settings can end access sooner. Editor preference cookies normally last up to one year. See WordPress’s cookie documentation.

Comment convenience

If a comment form offers to remember your details and you choose it, comment_author_[hash], comment_author_email_[hash] and comment_author_url_[hash] can store the details you entered to save retyping. These are first-party convenience cookies, normally retained for about one year under WordPress defaults. Leave the form’s remember-details option unchecked if you do not want them.

Google Analytics

Names: _ga and _ga_[measurement-id]. Purpose: distinguish browsers and maintain session information for audience measurement. Category: statistics, requiring opt-in in our setup. They are normally first-party cookies even though Google processes the analytics data. Provider default: up to two years, subject to configuration and browser limits. See Google’s Analytics cookie information. Device-cookie expiry does not specify how long analytics reports are retained on a server.

Advertising and embedded-provider cookies

These depend on whether the service loads, your choices, region and provider settings. Google documents examples including advertising cookies such as IDE and id on third-party domains, with a stated lifetime of thirteen months in the EEA, UK and Switzerland and twenty-four months elsewhere. This is a provider example, not confirmation that those cookies are currently present on every page here. Consult Google’s current cookie descriptions for names, functions and lifetimes, and the relevant provider notice before enabling an external feature.

A full inventory can vary between a public article, login, submission form and a consent-enabled embedded service. Contact us if you find a cookie or request that is not explained here; include its name and the page URL, but never its authentication value.

4. Consent, refusal and withdrawal

Our consent manager is configured to hold optional Analytics and advertising scripts until the relevant choice is granted. Rejecting optional categories should not stop ordinary reading or essential account functions. Accepting one category is not acceptance of every category, and consent to cookies is not a newsletter subscription or permission to publish a submitted article.

Your choice is saved in that browser. Another browser, device, private session or deletion of site data may require a fresh choice. You may also see the panel again when the recorded choice expires or the configuration materially changes.

Withdrawing consent prevents future optional processing controlled by that choice; it does not retrospectively undo lawful earlier processing. Reload after changing settings so a page already open can apply the new state. To remove cookies that remain on your device, use browser controls as well. We cannot delete another website’s cookies directly, and the banner is not a substitute for a request about information already held by a provider.

Your browser can show cookies and site storage, delete them and block some or all future storage. Blocking third-party cookies alone may not block first-party Analytics cookies, while blocking all cookies may break sign-in and guest forms. Browser privacy signals and tracking protection add safeguards but do not replace checking your saved category choices.

Google users can also review My Ad Center. These Google settings do not automatically change your consent decision on The Indic Journal. Likewise, rejecting cookies here does not change preferences you previously gave directly to another site.

6. Policy updates and concerns

We may revise this page as services or configurations change. The update date is shown above. A policy description does not authorise new optional tracking without the required choice. If you suspect a non-essential service loaded after rejection, tell us the page and approximate time so we can investigate.

Email contact@theindicjournal.com. You can also read Swedish cookie guidance from PTS and use the privacy-rights contacts in our Privacy Policy.

Footer Menu