Omlet Docs
BlogChangelogAsk the CommunityContact Sales
  • Get started
    • What is Omlet?
    • CLI & Dashboard
  • Omlet for VS Code
  • CLI & Dashboard
    • CLI
      • Your first scan
      • Set up your dashbard
      • Future scans
      • Ensure data accuracy
      • Config file
        • Exports configuration
        • Mapping aliases
        • Excluding certain components & files
        • Tutorial: Config file
      • Custom component properties
        • CLI hooks
        • Tutorial 1: Team/code owner usage
        • Tutorial 2: Package version tracking
        • Other example scripts
      • Set up regular scans
      • CLI commands
        • init
        • analyze
        • login
    • Analytics
      • Popular charts
      • Create custom charts
      • Save charts to dashboard
      • Share charts and dashboards with your team
      • Download chart data
    • Components
      • Search and filter components
      • Component tags
      • Dependency Tree
      • Props tracking
    • Workspace & Account
      • Invite team members
      • Renaming projects
      • Update your email address
      • Access your billing details & invoices
  • Security
    • Security in Omlet
    • Data collection
  • Help
    • Pricing
    • FAQs
      • How detection works?
      • Monorepo support
      • How to delete scans?
      • Omlet vs. React Scanner
      • Working with multiple workspaces
    • Troubleshooting
      • Debugging CLI issues
      • Some components aren't detected
      • API failed or timeout
      • Are you behind a proxy?
      • Troubleshooting Git errors
Powered by GitBook
On this page
  • How is the data collected for Omlet?
  • What data is collected for Omlet?
  • Where is the data stored for Omlet?
  1. Security

Data collection

How is the data collected for Omlet?

Omlet never collects, stores or upload your code. The scanning process is always done locally using the Omlet CLI available for download via NPM. Only metadata is collected.

As a user, you have full control over what code Omlet will scan by choosing which repository it should scan. You also have the option to limit scanning to certain files or directories.

What data is collected for Omlet?

Regarding metadata, Omlet collects:

  • Function names related to frontend code

  • File paths of where the functions are defined

  • Where the functions are called from

For troubleshooting purposes, other metadata we collect are:

  • IP address of the user who uploads the data

  • Node.js version

  • OS type/version

  • URL to the git repository and current branch name

Omlet CLI has an option to generate the output locally which you can use to inspect the data. You can do this by running:

npx @omlet/cli analyze --dry-run 
yarn dlx @omlet/cli analyze --dry-run 
pnpm dlx @omlet/cli analyze --dry-run 

This will generate a local file omlet.out.json with the scanned output that is normally uploaded to Omlet's Web app. When using --dry-run, the results are never uploaded.

Where is the data stored for Omlet?

The metadata collected is uploaded to Omlet's backend hosted on AWS (S3) and MongoDB. We only use this data to provide the service directly to you.

Last updated 4 months ago

If you have further questions, please .

contact us