Keep your projects and website data protected while Pixy fits safely into your existing workflow.
The project key px_ is public and only names the project. The browser approval pxt_ is the one that grants editing, and it exists in that browser, for that site, alone. The agent key px_sk_ is your agent's private credential. Reading your HTML gets a stranger the project's name and nothing more.
Very. Approving https://acme.com does not approve staging.acme.com or localhost:3000, and your laptop and your phone are two approvals. Each lasts 180 days from its last use, so a browser you stop designing on lapses by itself.
Regenerate key on the project card. It mints a new project key and drops every agent key, every browser approval and any connected page. Your pages, edits and tasks survive, but every deployed tag needs replacing.
No. We never capture, copy or store them. The editor runs in your browser on your site, and only the record of what changed leaves it. Nothing on our side fetches a page, which is why localhost and sites behind a login work at all.
No. Your agent runs on your own machine under your own provider account, and Pixy is the relay between the two. We send your work to no model and run none of our own.
None, and no third-party analytics or trackers. Even the fonts are served from our own server. See the Privacy Policy.
There is not. You type your email, we send a six-digit code that is good for ten minutes, and the code signs you in. A new address becomes an account on the same screen.