Royalada Cookie Policy
This Cookie Policy explains how Royalada LLC (“Royalada”, “we”, “our”, or “us”) uses cookies, browser storage, pixels, tags, scripts, SDKs, and similar technologies in connection with our websites and services. This Cookie Policy should be read together with our Privacy Policy.
Simply put: This policy explains which cookies and similar technologies may be used, why they are used, who provides them, and how long they last.
1. Cookies and Similar Technologies We Use
Royalada may use cookies and similar technologies for website functionality, security, advertising, lead generation, customer engagement, analytics, reporting, fraud prevention, and consent management. Where required by law, non-essential cookies and similar technologies are used only with consent.
Our role. On websites and applications operated by Royalada, Royalada acts as the data controller for the technologies described in this policy. On publisher or customer websites and applications that integrate Royalada services (including the Hood Web SDK and Royalada advertising services), Royalada generally acts as a processor or service provider on behalf of the publisher or customer, who remains responsible for its own cookie notice, consent collection, and Consent Management Platform. Requests relating to cookies or personal data on a publisher’s website should in the first instance be directed to that publisher; Royalada will assist the publisher in responding as required.
2. Royalada Website Cookies
The table below lists cookies and similar technologies that may be used on Royalada websites.
| Category | Name / Pattern | Storage Type | Purpose | Expiry | Consent |
|---|---|---|---|---|---|
| Strictly necessary | _opc.uid | sessionStorage | Random session ID used to group events during one browser session. | Session; reset after 30 minutes of inactivity or day change | No — exempt |
| Strictly necessary | _opc._let | sessionStorage | Last event timestamp used to expire the session. | Session | No — exempt |
| Strictly necessary | _ocpsh | Cookie | Non-identifying flag set only after the visitor accepts web push, used to avoid duplicate prompts across subdomains. Exempt as strictly necessary for a service explicitly requested by the visitor (ePrivacy Directive Art. 5(3)). | 180 days or until permission is revoked | No — exempt (service explicitly requested) |
| Functional | _opc.userConsent | localStorage | Stores consent choices so they can be respected. | Until cleared | No — required to respect the visitor’s choice |
| Functional | _opc.m_<id>.* | localStorage | Message/modal frequency capping, dismiss state, A/B variant, do-not-show flag. | Per campaign settings / until cleared | Depends on campaign |
| Analytics | _opc.uid | localStorage | Persistent first-party visitor ID, only if analytics consent exists. | Up to 12 months; deleted on consent withdrawal | Yes, where required |
| Analytics | _opc.utm_* | localStorage | Campaign attribution parameters. | Up to 12 months; deleted on consent withdrawal | Yes, where required |
Note on _opc.uid. The same name is used for two different items with different scope and purpose: the sessionStorage entry is a short-lived session ID that exists only for the duration of a single browser session and is strictly necessary for the service to function, while the localStorage entry is a persistent visitor ID that is created only with analytics consent and is deleted when consent is withdrawn.
3. Royalada Advertising Services
Royalada advertising services may use scripts, pixels, tags, iframes, server-side logs, and similar technologies to deliver advertisements, measure impressions and clicks, prevent invalid traffic, report campaign performance, and support advertising services.
Royalada’s Display SDK does not set cookies, does not use localStorage, sessionStorage, IndexedDB, or similar browser storage, and does not create or read its own identifier.
Advertisements displayed through Royalada services may include third-party advertising content, creatives, iframes, pixels, tags, scripts, partner SDKs, or synchronization URLs provided by advertisers, demand partners, measurement providers, or other advertising partners. These third parties may use their own cookies, pixels, tags, identifiers, or similar technologies on their own domains, subject to applicable law, consent requirements, and their own privacy and cookie policies.
Where permitted by law and valid consent or another required legal basis exists, Royalada may support partner synchronization or cookie matching. This may allow an authorized advertising partner to match a publisher-provided or Royalada-side identifier with the partner’s own advertising identifier for advertising delivery, measurement, attribution, frequency management, fraud prevention, or similar permitted purposes. Partner synchronization is initiated only where the applicable consent signal (including the IAB TCF TC String, where the TCF applies) establishes consent for Purpose 1 (storing and/or accessing information on a device) and the relevant advertising purposes for both Royalada and the partner concerned.
If required consent or another valid legal basis is not available, personalized advertising, partner synchronization, third-party advertising cookies, and similar activities are not enabled, and advertisements may instead be delivered in a contextual or non-personalized way.
IAB Europe Transparency & Consent Framework (TCF)
Royalada supports the IAB Europe Transparency & Consent Framework (TCF) and reads and honors the TC String provided by the publisher’s Consent Management Platform. Royalada is not currently registered on the IAB Europe Global Vendor List (GVL) and does not represent itself as a registered TCF vendor; Royalada intends to seek GVL registration.
Where the TCF applies, Royalada processes personal data in connection with advertising only where the TC String communicates a valid legal basis for the applicable purpose. Upon registration, the following purposes, legal bases, and retention periods will correspond to Royalada’s GVL registration record:
| TCF Purpose / Special Purpose | Legal basis | Retention |
|---|---|---|
| Purpose 1 — Store and/or access information on a device | Consent | For the lifetime of the relevant cookie or identifier as disclosed in this policy |
| Purpose 2 — Use limited data to select advertising | Consent or legitimate interest, as signaled | [●] days |
| Purpose 3 — Create profiles for personalised advertising | Consent (only where personalized advertising is enabled) | [●] days |
| Purpose 4 — Use profiles to select personalised advertising | Consent (only where personalized advertising is enabled) | [●] days |
| Purpose 7 — Measure advertising performance | Consent or legitimate interest, as signaled | [●] days |
| Purpose 10 — Develop and improve services | Consent or legitimate interest, as signaled | [●] days |
| Special Purpose 1 — Ensure security, prevent and detect fraud, and fix errors | Legitimate interest | [●] days |
| Special Purpose 2 — Deliver and present advertising and content | Legitimate interest | [●] days |
Server-side advertising logs (impressions, clicks, invalid-traffic signals) are retained for [●— e.g., 90 days], after which they are deleted or aggregated.
| Category | Name / Technology | Provider | Purpose | Domain / Origin | Expiry |
|---|---|---|---|---|---|
| Advertising delivery | display.js | Royalada / technology provider | Delivers and measures advertisements. Does not set cookies or browser storage. | Publisher site / Royalada service domain | No browser storage |
| Third-party advertising content and partner technologies | Creative, iframe, pixel, tag, script, partner SDK, or synchronization URL | Advertiser, demand partner, measurement provider, or other advertising partner | Advertising delivery, measurement, attribution, synchronization, frequency management, fraud prevention, or similar permitted advertising purposes. | Third-party / partner domain | Set by the relevant third party |
Simply put: Royalada’s own Display SDK does not store cookies or identifiers in the visitor’s browser. Ads served through Royalada may include third-party advertising technologies, and partner synchronization may occur only where permitted by law and consent choices. Royalada honors IAB TCF consent signals; it is not yet a registered IAB Europe Global Vendor List vendor.
4. Royalada Lead Generation and Customer Engagement Services
Royalada may use browser storage and similar technologies to support lead forms, on-site messages, web push, analytics, communication preferences, and customer engagement services.
The Hood Web SDK does not set tracking cookies. It may set one non-identifying first-party cookie only after a visitor accepts web push, and otherwise uses first-party browser storage under a single _opc key.
| Category | Name / Technology | Provider | Purpose | Domain | Expiry |
|---|---|---|---|---|---|
| Strictly necessary | _ocpsh (cookie) | Royalada / technology provider | Non-identifying flag set only after web push is accepted, used to avoid duplicate prompts or registrations across subdomains. Exempt as strictly necessary for a service explicitly requested by the visitor (ePrivacy Directive Art. 5(3)). | Publisher registrable domain | 180 days or until permission is revoked |
| Strictly necessary | _opc.uid in sessionStorage | Royalada / technology provider | Random session ID used to group events within a single browser session. | Publisher origin | Browser session; reset after 30 minutes of inactivity or day change |
| Strictly necessary | _opc._let in sessionStorage | Royalada / technology provider | Timestamp used only to expire the session ID. | Publisher origin | Browser session |
| Functional | _opc.userConsent in localStorage | Royalada / technology provider | Stores visitor consent choices so they can be respected on later pages. | Publisher origin | Until cleared by visitor |
| Functional | _opc.webpush_dismissals in localStorage | Royalada / technology provider | Counts web push prompt dismissals to avoid repeated prompting. | Publisher origin | Until cleared by visitor |
| Functional | _opc.push in localStorage | Royalada / technology provider | Indicates that web push was accepted on a specific subdomain when per-subdomain mode is used. | Publisher origin | Until unsubscribed or cleared |
| Functional / message control | _opc.m_<id>.* in localStorage | Royalada / technology provider | Stores on-site message/modal counters, last shown timestamp, do-not-show flag, or A/B variant. | Publisher origin | Per campaign settings; session or until cleared |
| Analytics — consent required where applicable | _opc.uid in localStorage | Royalada / technology provider | Persistent first-party visitor ID used to recognize returning visitors on the same website. | Publisher origin | Up to 12 months; deleted on consent withdrawal |
| Analytics — consent required where applicable | _opc.ttl in localStorage | Royalada / technology provider | Expiry timestamp for the persistent visitor ID. | Publisher origin | Same as _opc.uid |
| Analytics — consent required where applicable | _opc.utm_* in localStorage | Royalada / technology provider | Stores campaign attribution parameters from the landing URL. | Publisher origin | Up to 12 months; deleted on consent withdrawal |
5. Third-Party Cookies and Partner Technologies
Advertisements, partner promotions, measurement services, fraud prevention services, communication services, demand partners, and other third-party partners may use their own cookies, pixels, tags, identifiers, or similar technologies.
These technologies are controlled by the relevant third party, not by Royalada. The name, purpose, domain, and duration of such cookies or similar technologies are determined by the relevant third party and may change over time.
Where third-party technologies are used for personalized advertising, targeted advertising, measurement, attribution, partner synchronization, affiliate tracking, or similar activities, they are subject to applicable consent and privacy requirements.
Where required by law, these third-party partners are disclosed through the applicable Consent Management Platform, vendor list, partner list, privacy notice, or cookie notice used on the relevant website, application, or service.
Further information about the third parties involved in a specific service, website, or campaign — including the identity of recipients of personal data where required by applicable law — is available on request at [email protected].
| Partner category | Technology type | Purpose | Domain | Expiry |
|---|---|---|---|---|
| Advertising and demand partners | Cookies, pixels, tags, identifiers, or similar technologies controlled by the partner | Advertising delivery, measurement, attribution, synchronization, frequency management, or fraud prevention where permitted | Partner domain | Set by partner |
| Measurement and attribution partners | Pixels, tags, postbacks, cookies, or similar technologies controlled by the partner | Campaign measurement, conversion tracking, reporting, or attribution | Partner domain or service domain | Set by partner |
| Fraud prevention and traffic quality partners | Cookies, pixels, tags, identifiers, server-side signals, or similar technologies controlled by the partner | Fraud prevention, invalid traffic detection, abuse prevention, and service security | Partner domain or service domain | Set by partner |
| Communication providers | Provider identifiers, delivery events, tracking pixels, or similar technologies controlled by the provider | Message delivery, delivery status, unsubscribe handling, and engagement measurement | Provider domain or service domain | Set by provider |
| Affiliate and referral partners | Affiliate links, tracking IDs, pixels, cookies, postbacks, or similar technologies controlled by the partner | Referral tracking, commission calculation, attribution, or conversion measurement | Partner domain | Set by partner |
Third-party partners may also process personal information under their own privacy policies and cookie policies when individuals interact with their websites, advertisements, services, or technologies.
Simply put: Some advertising, measurement, fraud prevention, communication, or affiliate partners may use their own cookies or similar technologies. Those technologies are controlled by those partners, not by Royalada. Where required, they are shown through the relevant consent tool or vendor list, and you can always ask us who is involved.
6. Consent and Choices
Where required by law, non-essential cookies and similar technologies are used only with consent.
Publishers, customers, and business partners using Royalada services are responsible for providing appropriate cookie notices, operating a suitable Consent Management Platform where required, and making relevant consent and privacy signals available to Royalada.
Royalada respects supported consent and privacy signals, including:
- IAB TCF — where the IAB Europe Transparency & Consent Framework applies, Royalada reads and honors the TC String provided by the publisher’s Consent Management Platform, and processes data only for the purposes and legal bases it communicates (see Section 3).
- IAB GPP — Royalada supports the IAB Global Privacy Platform, including the TCF EU section and the applicable US National and US state sections, where technically supported.
- Global Privacy Control (GPC) — where US state privacy laws apply, Royalada treats a valid GPC signal as a request to opt out of the “sale” or “sharing” of personal information and of targeted advertising, as defined by the applicable law.
You may manage cookies and similar technologies through the consent banner or preference center on the website or application you are using, browser settings, device privacy settings, unsubscribe links, opt-out tools, or by contacting the relevant website operator or Royalada.
Withdrawing consent is as easy as giving it: you can change or withdraw your choices at any time by reopening the cookie settings or preference center link on the relevant website. Withdrawal applies going forward and does not affect the lawfulness of processing before the withdrawal.
Simply put: Some cookies are necessary. Others need consent where the law requires it. Publishers and partners must collect consent where required, Royalada respects supported consent signals, and you can change your mind at any time via the cookie settings link.
7. Changes to This Cookie Policy
Royalada may update this Cookie Policy from time to time to reflect changes in our services, technologies, providers, or legal requirements. When we update this Cookie Policy, we will revise the “Last Updated” date.
8. Contact Us
If you have questions about this Cookie Policy, contact us at:
Royalada LLC Dragise Misovica 163A, 32000, Cacak, Serbia Email: [email protected]