Is Page Vault safe?

Clean risk

Page Vault identifies signed-in users to PostHog and sends capture URLs and optional cookies to its API.

When the extension popup opens, Page Vault sends a PostHog identify event with the signed-in user's identifier and primary email address. When a user starts a capture, it submits the active tab URL to Page Vault's API and can include site cookies if cookie capture is enabled.

Page Vaultv0.5.2Chrome Web Store
3Risk
Who publishes it

Page Vault - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
Page Vault
Declared legal entity
Page Vault
Registered address
382 NE 191st St Suite 73062, Miami, FL 33179-3899, US
Registered contact
Todd Price

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 0.5.2. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every site you visit

    <all_urls>

  • Store data in your browser

    storage

  • See the address and title of every tab you have open

    tabs

  • Read and change cookies, including the ones that keep you signed in

    cookies

Where it sends data

Destinations our analysis observed Page Vault contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • us.i.posthog.com

    Page Vault sends data to us.i.posthog.com. 24 other extensions we have analysed send data here.

  • api.page-vault.com

    Page Vault sends data to api.page-vault.com. No other extension we have analysed sends data here.

Updated 30 September 2026fendggmofabjinelohmdjcjhniehplik