Keyring Network | Docs
  • INTRODUCTION
    • About Us
    • Our Solution
    • Use Cases
  • USER GUIDE
    • 1. Choose a Policy
    • 2. Onboard
      • Keyring Connect
      • Keyring Pro
    • 3. Create a Credential
    • FAQ
      • What is my onboarding status?
      • How to manage multiple entities?
      • What is Keyring's business model?
      • How to create credentials x-chain?
  • INTEGRATION STEPS
    • 1. Create a Policy
      • Connect Policy Builder
    • 2. Integrate to User Flow
    • 3. Permission smart contracts
  • PROTOCOL GUIDE
    • Sandbox
      • Keyring Connect
      • Keyring Pro
    • Data Flow
      • Data Collected
      • Data Storage
    • Smart Contracts
  • RESOURCES
    • Links
    • Get in Touch
    • Brand Assets
    • Data Policies
  • Onboarding Requirements
    • Keyring Pro
      • FalconX
    • Keyring Connect
Powered by GitBook
On this page
  • User Compliance Data
  • Usage Analytics Data
  1. PROTOCOL GUIDE
  2. Data Flow

Data Collected

Keyring processes and stores two main types of data defined below.

User Compliance Data

Definition: Datapoints collected from users as part of onboarding, including Personally identifiable information (PII).

Use of data: Used for the core purpose of our solution. Keyring does not share any PII or data outside of its core use case and never sells it. At a User’s request, Keyring may also use the contact information provided upon onboarding to keep them updated on their onboarding status.

Usage Analytics Data

Definition: Data points collected from Users’ usage of Keyring, such as cookies or anonymised website usage data.

Use of data: Used in a range of ways to improve user experience on the Keyring’s interface, including keeping users signed in, and understanding how they use our app and website for internal analytics.

What types of cookies are used?
  • Strictly necessary cookies. These are cookies that are required for the operation of our website. These essential cookies are always enabled because our website won’t work properly without them. They include, for example, cookies that enable you to log into secure areas of our website.

  • Analytical or performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it.

  • Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).

PreviousData FlowNextData Storage

Last updated 7 months ago