Trust · Trust disclosure
Optional cookies and similar technologies require a clear choice where consent is required.
This overview separates essential technology, preferences, analytics, marketing, and third-party domains, and explains how consent, rejection, withdrawal, and the live cookie inventory should work.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
The legal question is what the technology does.
A label such as essential, analytics, preference, or marketing does not determine the result by itself. The purpose, timing, provider, duration, user request, and whether information is stored on or read from the device determine whether consent is required.
Irish DPC guidance states that consent is normally required for cookies and similar technologies, subject to narrow exemptions for communication and services explicitly requested by the user.
Technology categories.
| Category | Purpose | Consent position | Examples of records to disclose |
|---|---|---|---|
| Strictly necessary | Security, session, authentication, checkout, consent choice | May be exempt when strictly necessary | Name, provider, purpose, duration, domain |
| Preferences | Remember non-essential choices | Consent may be required | Language, display, optional settings |
| Analytics | Measure use and performance | Consent normally required unless a lawful exemption applies | Provider, identifier, events, duration |
| Marketing | Advertising, attribution, profiling, cross-site tracking | Consent required | Provider, purpose, recipients, duration |
| Embedded third party | Video, social, maps, support, external widgets | Depends on storage and user action | Provider domain, trigger, data path |
Consent must be a real choice.
- Do not load non-essential technologies before the required choice
- Keep optional categories off by default
- Do not treat scrolling, silence, or continued browsing as consent
- Make reject and accept choices comparably clear
- Explain each purpose and provider before the choice
- Allow withdrawal or change as easily as consent was given
- Record the consent version and choice only as long as needed
The live cookie inventory controls the detail.
The published Cookie Policy and consent interface should list the current cookie or technology name, provider, domain, purpose, category, duration, and whether it is set before or after a user choice.
A category summary cannot replace a live tag, script, and cookie audit. New plugins, embeds, analytics, payment, access, or support tools can change the inventory.
External platform boundary.
OpenAI controls cookies and similar technologies on ChatGPT and OpenAI domains. Stripe, Authflow.ai, and other external providers control their own domains and may set technology when a user follows a link or enters a provider-hosted flow.
Semantec SEO should not describe another provider's cookies as though they were first-party site cookies.
Change or withdraw a choice.
Use the cookie settings route published on the live site. Browser controls can also block or delete storage, but may affect authentication, checkout, preferences, or other requested functions.
Send a concern to privacy@semantecseo.com with the URL, date, browser, technology name where known, and observed behaviour.
Check the controlling first-party and official sources.
These routes support the current public statement. External platform and legal sources remain subject to their own updates.
Semantec SEO Cookie Policy
Current first-party cookie-policy baseline.
Irish DPC cookie guidance
Official Irish consent guidance.
Irish DPC cookie FAQs
Official cookie information and exemptions.
Move to the page that owns the next question.
Each route has a separate job so company, product, trust, legal, and compliance information does not collapse into one promotional page.
Owned route
Cookie Policy
Operative cookie and similar-technology terms.
Open route →
Owned route
Privacy Policy
Personal-data processing associated with website technology.
Open route →
Owned route
Provider register
External services and provider roles.
Open route →
Owned route
Data retention
Consent and technology record retention.
Open route →
Owned route
GDPR overview
Consent withdrawal and other rights.
Open route →
Owned route
Contact
Cookie and privacy concern route.
Open route →