> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cr3dentials.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# How Cr3dentials Works

> How Cr3dentials uses zkTLS and zero-knowledge proofs to verify data from web-based platforms without exposing login credentials or raw data.

Cr3dentials uses **zkTLS** to run private, tamper-proof verifications directly from web-based platforms. zkTLS stands for zero-knowledge Transport Layer Security. It lets users generate a proof of what they see during a secure HTTPS session without revealing the full content of that session.

This means users can prove facts like revenue, activity, or account ownership from dashboards like YouTube Studio or Shopify Admin without exposing their login credentials or sharing raw data.

## The three parties

<AccordionGroup>
  <Accordion title="Verifier" icon="building">
    The verifier is the organization requesting the verification. This could be a lender, fintech platform, marketplace, or any service that needs to validate user claims before providing access to capital, services, or opportunities.

    The verifier defines:

    * **What needs to be proven**, such as revenue, payout consistency, or account age.
    * **Which platforms are acceptable.**
    * **How much data they want to see**, using Cr3dentials' selective disclosure feature:
      * Full details, such as exact income values and payout history.
      * Specific data points, such as account creation date or monthly average.
      * Binary thresholds only, such as whether a user earns more than \$5,000 per month.
  </Accordion>

  <Accordion title="Applicant" icon="user">
    The applicant is the person being verified. They receive a secure link to complete the verification. From there, they choose a supported platform, connect their account, and approve the session.

    Cr3dentials runs locally in their browser and handles everything without routing data through centralized servers. Users never share login credentials with Cr3dentials. They stay in full control of what is verified and can optionally store encrypted access tokens for future sessions.
  </Accordion>

  <Accordion title="Data Sources" icon="database">
    Data sources are the platforms the applicant connects to, such as social media accounts, e-commerce and accounting tools, payroll, and banking.

    Cr3dentials loads these dashboards in a secure browser environment and extracts the required data using zkTLS. Instead of returning the raw data, Cr3dentials generates a zero-knowledge proof that the information on the page satisfies the verifier's conditions.
  </Accordion>
</AccordionGroup>

## User flow

The user journey is short.

<Steps>
  <Step title="Verifier initiates a request">
    The verifier initiates a verification request and shares a unique link with the applicant.
  </Step>

  <Step title="Applicant opens the link">
    The applicant clicks the link and is redirected to the Cr3dentials appclip or mobile app.
  </Step>

  <Step title="Applicant connects a platform">
    The applicant selects the platform they want to verify, logs in, and authorizes data access.
  </Step>

  <Step title="Cr3dentials generates a proof">
    Cr3dentials fetches the required data in a secure zkTLS session and generates a proof.
  </Step>

  <Step title="Proof is delivered">
    The zero-knowledge proof is automatically sent to the verifier once verification is complete.
  </Step>
</Steps>