How this policy applies
BrandInk Media ("BrandInk," "we," "us," or "our") uses website technologies to operate and secure our site, remember choices, understand website performance and, where enabled, measure marketing campaigns. This policy applies to brandink.media.
01
What cookies are
A cookie is a small text file that a website stores on your browser or device. Cookies can remember information between page visits or later sessions, such as language choices, consent preferences or a randomly generated identifier.
Cookies may be set directly by BrandInk (first-party cookies) or by another organisation whose service appears on our website (third-party cookies). Some cookies expire when you close your browser, while others remain for a defined period unless you delete them earlier.
02
Cookies and similar technologies
In addition to browser cookies, our website may use pixels, tags, scripts, local storage, software development kits or similar technologies. These tools may recognise a browser or device, record an event, help prevent fraud, measure website use or connect an enquiry with a marketing campaign.
In this policy, we use the word “cookies” to cover cookies and these related technologies unless the context requires otherwise.
03
Categories we may use
Strictly necessaryAlways active
Support security, network management, form protection, load balancing and saved consent choices. The website may not work correctly without them.
FunctionalOptional
Remember preferences or support enhanced features, such as embedded content, chat, scheduling or personalised website settings.
AnalyticsOptional
Help us understand visits, traffic sources, page interactions, technical performance and aggregate usage so we can improve the website.
AdvertisingOptional
Help measure campaigns, attribute conversions, limit repeated ads and, where enabled, support relevant advertising on third-party platforms.
Consent standardWhere required by applicable law, functional, analytics and advertising cookies are not activated until you make a relevant choice. Strictly necessary cookies do not require consent where they are essential to provide a requested website function.
04
Cookie and technology register
The table below describes the types of technology BrandInk may use. Exact cookie names and lifetimes can vary by configuration, browser and provider. BrandInk should update this register whenever a new website plugin, analytics product, advertising pixel, embedded service or consent platform is activated.
| Provider / feature | Category | Purpose | Typical duration |
|---|
| BrandInk / WordPress / hosting | Strictly necessary | Website delivery, security, form operation, traffic management and technical preferences. | Session to 12 months, depending on function. |
| Cookie consent platform | Strictly necessary | Stores whether you accepted, rejected or customised optional cookies. | Commonly 6–12 months. |
| Google Analytics, if enabled | Analytics | Measures website visits, engagement, traffic sources and conversion events. | Depends on BrandInk's configured retention and cookie settings. |
| Google Ads, if enabled | Advertising | Measures advertising conversions and may support campaign optimisation or remarketing. | Varies by cookie, consent and provider configuration. |
| Meta Pixel, if enabled | Advertising | Measures actions following Meta advertising and may support audience or campaign optimisation. | Varies by cookie, consent and provider configuration. |
| Embedded media, chat or scheduling, if enabled | Functional / analytics | Displays external content or provides communication and booking features. | Varies by the independent provider. |
Implementation check requiredThis register is written conservatively because the current production configuration has not been technically audited in this document. Before publishing, compare it with the cookies shown by the active consent plugin and browser developer tools, then add or remove providers as necessary.
05
Third-party providers
Optional website tools may be provided by independent organisations such as Google, Meta, video platforms, scheduling providers, live-chat providers or social networks. When enabled, those organisations may receive device information, cookie identifiers, IP address, page details, event information or other data described in their own privacy notices.
Third parties control their own technologies and may process data in other countries. We encourage you to review their privacy and cookie information before enabling optional features. A link or embedded service does not mean BrandInk controls the provider's independent data practices.
06
How to manage consent
Where our cookie banner is active, it should provide equally understandable options to:
- Accept All optional categories;
- Reject Non-Essential cookies while keeping necessary functions active; and
- Manage Preferences by category before optional technologies load.
You may change or withdraw a previous choice using the “Cookie Settings” or similar control displayed in the website footer or banner. Withdrawal does not make earlier processing unlawful, but it should stop future optional cookie activity covered by that choice.
Website setup noteThis HTML page explains cookies but does not itself block scripts or save consent. A compatible WordPress consent-management plugin must be configured separately to control Google Analytics, Meta Pixel and other non-essential tags.
07
Browser and device controls
Most browsers let you view, block or delete cookies through privacy or site settings. You may also clear stored website data, use private-browsing modes or restrict third-party cookies. Settings vary by browser and device, so consult the browser provider's current help pages.
Blocking all cookies may cause forms, preferences, security controls or embedded features to work incorrectly. Browser deletion may also remove your saved cookie-consent choice, which means the banner can appear again.
08
Global Privacy Control and Do Not Track
Some browsers or extensions send privacy preference signals such as Global Privacy Control (GPC) or Do Not Track. Where applicable law requires BrandInk to recognise GPC as an opt-out of the sale or sharing of personal information, we will treat a valid signal accordingly for the browser or device sending it.
There is no universally adopted response standard for every Do Not Track signal. We will update our practices as recognised standards and legal requirements develop.
09
How long cookies remain
Session cookies normally expire when you close your browser. Persistent cookies remain until their stated expiry date or until you delete them. Similar technologies may retain data according to the settings of the relevant tool.
BrandInk aims to limit cookie duration and related data retention to what is reasonably necessary for the stated purpose. Provider-controlled periods may change, so the active consent platform and provider documentation are the most current sources for exact lifetimes.
10
Personal information and international processing
Cookie data can include or be linked with an IP address, device and browser details, approximate location, page activity, referral source, campaign information or a pseudonymous identifier. Depending on context and applicable law, some of this information may be personal information.
BrandInk and its service providers may process information in India, the United States, Canada or other countries. For more information about purposes, disclosures, safeguards, retention and privacy rights, please read our Privacy Policy.
11
Changes to this policy
We may update this Cookies Policy when our website, providers, technologies or legal obligations change. The revised version will appear on this page with a new “Last updated” date. If a material change requires a fresh choice, we may display the cookie banner again.
12
Contact us
For questions about cookies, consent preferences or privacy on this website, contact:
BrandInk Media
Email: connect@brandink.media
Website: brandink.media/contact
Please include “Cookie Privacy Request” in your subject line and describe the browser, device and relevant website page if you are reporting a technical consent issue.
