Metaenga Cookie Policy
Version: 0.2
Last updated: 28 July 2026
Effective date: On publication
This Cookie Policy explains how Metaenga, Inc. (“Metaenga”, “we”, “us” or “our”) uses cookies and similar technologies on metaenga.com, Metaenga web applications and other online services that link to this Policy (together, the “Online Services”).
Metaenga, Inc. is a Delaware corporation with a registered address at 1111B South Governors Avenue, Dover, Delaware 19904, United States.
This Policy should be read with our Privacy Policy. A customer-specific service may use a more restrictive cookie and analytics configuration under an enterprise agreement.
1. What cookies and similar technologies are
Cookies are small text files stored on a browser or device. Similar technologies include:
- browser local storage and session storage;
- software development kits and mobile identifiers;
- pixels, tags and web beacons;
- scripts that read device or browser information;
- local application databases used by browser or native software.
Cookie and ePrivacy rules may apply even where the information is not directly identifying. Where a technology processes Personal Data, our Privacy Policy also applies.
Local VR session storage is described in the Privacy Policy, the applicable EULA and any enterprise DPA. It is not used for advertising and is not controlled through the public website’s Cookie Settings interface.
2. Your choices
Except for technologies that are strictly necessary to provide a feature you request, Metaenga will not activate non-essential cookies or similar technologies until you give the required consent.
Our consent interface is intended to let you:
- accept all optional technologies;
- reject all optional technologies with the same level of ease;
- choose separately between preference, analytics and advertising categories;
- change or withdraw your choice at any time through the permanent Cookie Settings link.
Withdrawing consent does not affect processing that occurred lawfully before withdrawal. Essential technologies cannot be disabled through our preference tool because the requested service may not function without them, although you may still block them through your browser.
Your choice is stored for up to 12 months unless:
- you delete your browser storage;
- we materially change the technologies or purposes;
- applicable law requires us to ask again sooner.
3. Categories we use
| Category | Purpose | Consent position |
|---|
| Strictly necessary | Security, fraud prevention, authentication, session continuity, load balancing, requested checkout or form functionality, and recording your privacy choices | Used without optional consent only where legally exempt and necessary for the feature requested |
| Preferences | Language, interface and accessibility choices that are not essential | Activated with consent where required |
| Analytics | Measuring visits, performance and usability; identifying errors; understanding how public pages are used | Activated only after analytics consent where required |
| Advertising and social media | Measuring campaigns, cross-site advertising, audience creation or social-media tracking | Activated only after separate consent; not used to profile enterprise learners |
We do not use enterprise learner results, pass/fail records or detailed training events for advertising or cross-site profiling.
4. Current technology and provider register
The table below describes the technologies that Metaenga currently uses or supports. The consent interface shown on the relevant Online Service is the operational source for the exact cookies, domains and current durations.
| Provider / technology | Typical purpose and data | Category | Typical duration |
|---|
| Metaenga first-party session and security technologies | Login/session state, authentication flow, tenant routing, fraud prevention, security events | Strictly necessary | Session or the minimum period needed for account security |
| Metaenga consent record | Selected cookie categories, policy version and choice timestamp | Strictly necessary | Up to 12 months |
Metaenga language preference, including NEXT_LOCALE where used | Remembers the language selected by the visitor | Preferences | Up to 12 months |
| Google reCAPTCHA, where a protected form is requested | IP address, browser/device information, page and interaction signals used to distinguish abusive traffic from legitimate requests | Strictly necessary only where the protected feature is explicitly requested and the configured use meets the legal exemption; otherwise consent is required | Set by Google according to its service configuration |
| Google Tag Manager | Delivers tags according to Metaenga’s consent configuration | Strictly necessary only if configured solely to operate consent controls without optional tracking; otherwise it and its optional tags are gated by the applicable consent | Depends on the container and tag delivered |
| Google Analytics, if shown as enabled in Cookie Settings | Page and interaction information used to measure public-site usage and performance | Analytics | As shown in Cookie Settings |
| Hotjar, if shown as enabled in Cookie Settings | Public-site usability, interaction and diagnostic information | Analytics | As shown in Cookie Settings |
| Stripe or another displayed payment provider | Checkout security, fraud prevention, payment-session continuity and payment processing when a user starts a purchase | Strictly necessary for requested checkout | Determined by the payment provider |
| Metaenga browser local storage | Consent state, interface state and technically necessary browser application data | Strictly necessary or Preferences, depending on purpose | Session or until cleared, as shown in Cookie Settings |
The mere presence of Google Tag Manager does not mean that every possible Google or advertising service is enabled. Optional tags must follow the consent category assigned to their actual purpose.
If Metaenga enables a new non-essential provider or materially changes a purpose, we will update this Policy and the consent interface before or when the change takes effect.
5. Public website and authenticated services
Public-site analytics are separate from enterprise learner processing.
Metaenga’s default enterprise position is:
- no advertising cookies in learner training flows;
- no use of learner results for marketing;
- analytics in an authenticated customer environment only where required to operate, secure or support that environment, or where the applicable customer has approved an optional tool;
- a customer-specific deployment may disable optional analytics entirely.
Some authentication, identity, headset, app-store, payment or customer integration providers operate under their own terms and privacy notices. They may set necessary technologies when you choose to use their feature.
6. Third parties and international transfers
Third-party technology providers may receive online identifiers, device/browser information, IP addresses and interaction data for the purposes described above.
Metaenga reviews the role of each provider and uses contractual and transfer safeguards where required. Depending on the provider and service configuration, information may be processed outside your country, including in the United States. More information is provided in the Privacy Policy and applicable enterprise DPA.
Provider certifications apply only to the provider and certified service scope. They are not Metaenga certifications.
7. Browser controls, Do Not Track and Global Privacy Control
Browser settings may let you block or delete cookies. Blocking strictly necessary technologies can prevent login, checkout, language or security features from working.
Some browsers send “Do Not Track” signals, but there is no single universally accepted technical standard for those signals. Metaenga uses the Cookie Settings tool as the primary way to record consent choices.
Where applicable law requires Metaenga to recognise an opt-out preference signal, such as Global Privacy Control, we will treat the signal as an opt-out request for the relevant browser or device. A recognised signal does not replace a separate opt-in where consent is required.
8. Changes to this Policy
We may update this Policy to reflect a change in technology, law or our Online Services.
The date above shows the latest revision. If a change materially affects an existing choice, we will request a new choice where required.
9. Contact
Questions about this Policy or Metaenga’s privacy practices can be sent to:
Metaenga, Inc.
Attention: Privacy
1111B South Governors Avenue
Dover, Delaware 19904
United States
Email: privacy@metaenga.com
