Scope
This policy explains how Cryptic Labs LLC ("Cryptic," "we," "us," or "our") uses cookies and similar technologies when operating webpages and features of the RNS.ID online platform (the "Platform") that link to this policy.
This policy covers technologies used by Cryptic for Platform-level processing. Products and services made available through the Platform are not necessarily provided by Cryptic. A product provider or another party may use additional technologies for its own processing under an in-context notice or its own privacy and cookie documentation.
It should be read with the RNS.ID Privacy Notice.
Technologies Covered
The term "cookies" in this policy includes:
- browser cookies;
- local storage and session storage;
- pixels, web beacons, and conversion tags;
- scripts and software development kits;
- device or browser identifiers; and
- similar technologies that store, read, or transmit information from a browser or device.
Some technologies are set by Cryptic through the Platform. Others are provided by companies that supply analytics, advertising, communications, security, payment, wallet, or other functionality to Cryptic or to the applicable product provider.
Our Categories
| Category | Purpose | Can Be Disabled in Cookie Settings? |
|---|---|---|
| Strictly Necessary | Authentication, security, fraud prevention, network operation, consent records, and features you expressly request | No, but browser controls may block them and prevent the site from working |
| Performance and Analytics | Measure visits, diagnose performance, understand feature use, and improve the Platform | Yes |
| Functional | Remember settings and provide enhanced features such as language, chat, or wallet preferences | Yes, unless a specific technology is necessary for a feature you request |
| Advertising and Targeting | Measure campaigns, attribute referrals or ads, limit repetition, and personalize or evaluate advertising | Yes |
We use technologies that are not strictly necessary only as permitted by applicable law and your available choices.
Platform Storage Inventory
The following table describes material first-party browser storage identified in the current Platform application. A key may be created only when you use the related feature.
| Storage Key or Group | Type | Category | Purpose | Typical Retention |
|---|---|---|---|---|
rns-token | Local storage | Strictly Necessary | Maintains an authenticated session | Until logout, replacement, expiration enforced by the service, or browser storage is cleared |
rns-cookie-policy | Local storage | Strictly Necessary | Records that the Cookie Settings interaction was completed | Until the choice is replaced or browser storage is cleared |
rns-accept-list | Local storage | Strictly Necessary | Stores selected cookie categories | Until the choice is replaced or browser storage is cleared |
rns-last-activity-time | Local storage | Strictly Necessary | Supports session-security and inactivity controls | For the active account session or until browser storage is cleared |
rns-kyc-sign, rns-kyc-token | Local storage | Strictly Necessary | Supports an identity-verification workflow expressly requested by the user | Until removed by the workflow or browser storage is cleared |
rns-lng, rns-lng-set-by-user | Local storage | Functional | Remembers language and whether the language was selected by the user | Until changed or browser storage is cleared |
rns-login-email | Cookie | Functional | Remembers the email entered for sign-in convenience | Browser session unless removed earlier |
rns-active-wallet | Local storage | Functional | Remembers the wallet selected for a supported feature | Until changed or browser storage is cleared |
rns-referral-code | Local storage | Functional / Advertising and Targeting | Attributes a referral when the user follows a referral link or chooses to participate | Until used, removed by the service, or browser storage is cleared |
| Product workflow keys | Local or session storage | Strictly Necessary or Functional | Preserves temporary Platform state for an offering, redemption, document, or checkout workflow requested by the user; this does not identify Cryptic as the provider of the underlying offering | For the workflow, until removed, or until browser storage is cleared |
The exact names used by a feature may change when the application is updated. Cookie Settings will present the categories currently available on the device.
Third-Party Technology Inventory
The current Platform deployment is configured to use the following browser-facing providers. Optional providers must not load until the applicable choice or other lawful basis is available.
| Provider / Deployed Identifier | Category | Purpose | Information That May Be Collected | Activation |
|---|---|---|---|---|
Google Analytics (G-K6M48X3BL0) | Performance and Analytics | Site and feature measurement | Device, browser, IP-derived location, page, referral, event, and identifier data | After analytics permission where required |
Google Ads (AW-10839746782) | Advertising and Targeting | Conversion measurement and campaign attribution | Device, browser, page, referral, conversion, and advertising identifier data | After advertising permission where required |
Meta Pixel (597354976119191) | Advertising and Targeting | Campaign measurement, attribution, and audience functions | Device, browser, page, event, referral, and advertising identifier data | After advertising permission where required |
X Tag (oee0f) | Advertising and Targeting | Campaign measurement and attribution | Device, browser, page, event, referral, and advertising identifier data | After advertising permission where required |
CNZZ (1281364334) | Performance and Analytics | Site traffic measurement | Device, browser, IP-derived location, page, referral, event, and identifier data | After analytics permission where required |
Hotjar (3374438) | Performance and Analytics | Usage analytics and experience diagnostics | Device, browser, page, interaction, session, and identifier data, subject to configured suppression rules | After analytics permission where required |
Salesmartly (project_142743_148055_1728366165) | Functional | Customer chat and support | Device, browser, page, chat, contact, and interaction information | When the user requests chat or permits functional technologies, as applicable |
These providers may set their own cookies or storage with provider-controlled names and retention periods. The production Cookie Settings interface must show the current provider, purpose, category, and storage duration based on a verified production scan. Provider practices are also subject to their own privacy documentation.
Other embedded product, payment, verification, wallet, or security technologies may be activated when you request the related feature. Such technologies may be operated by Cryptic, by a service provider processing information for Cryptic, or independently by the applicable product or transaction provider. Where those technologies access a browser or device, the applicable product flow, Cookie Settings, or third-party notice will provide additional information as required by law. Their presence in the Platform does not mean that Cryptic provides the underlying product.
Your Choices
Cookie Settings
You can use Cookie Settings on the Platform to:
- accept or reject Performance and Analytics technologies;
- accept or reject Functional technologies that are not necessary for a requested feature;
- accept or reject Advertising and Targeting technologies; and
- change a previous choice.
Strictly Necessary technologies cannot be disabled through Cookie Settings because they support core operation, security, consent records, or a feature you request.
Browser and Device Controls
Most browsers allow you to view, delete, or block browser storage. If you delete stored preferences, Cryptic may ask for your choices again through the Platform. Blocking authentication, security, or workflow storage may prevent parts of the Platform from working.
Browser-Based Opt-Out Signals
Where required by applicable law, Cryptic treats a legally valid browser-based opt-out preference signal, such as Global Privacy Control, as a request to opt out of applicable sale, sharing, or targeted-advertising activity for that browser and device.
Some browsers also offer a legacy "Do Not Track" setting. Because there is no uniform standard that defines how websites must interpret that setting, Cryptic does not treat the Do Not Track setting by itself as a Cookie Settings selection.
Advertising Controls
You may also use controls offered by your browser, device, or advertising providers. Those controls operate independently from Cookie Settings on the Platform.
Consent Records
We may store the date, category selection, policy version, region or consent regime, and a limited device or account identifier to honor your choice and demonstrate compliance. Consent can be withdrawn prospectively. Withdrawal does not make prior processing unlawful.
Moving a mouse, scrolling, closing a banner, or continuing to browse is not treated as affirmative consent where affirmative consent is required.
Updates
We may update this policy when technologies, providers, purposes, or legal requirements change. The published version will show its effective date. Material changes may cause Cookie Settings to request a new choice.
Contact
Questions about this policy or Cryptic's use of cookies and similar technologies through the Platform may be sent to:
Cryptic Labs LLC
Email: [email protected]
