Legal
Privacy Policy
Last updated: July 2026
What we collect
Quey collects only what is necessary to operate the service. When you sign in with GitHub or Google, we store your name, email address, and OAuth identity token so we can identify your account across sessions. When you purchase a plan, Stripe processes your payment details — we never store card numbers or billing data on our servers. We receive a Stripe customer ID and subscription status only.
What the Chrome extension does
The Quey Chrome extension requests these permissions: storage (to save your enabled/color/crosshair preferences locally), activeTab and scripting (to inject the inspection toolbar into the page you are viewing and read the element you select), clipboardWrite (to write captured payloads to your clipboard when you copy), and host access to all URLs so the toolbar can run on any page you choose to inspect — not just quey.dev — since Quey is a tool for building other people's sites. When you select an element, the extension reads that element's DOM structure, computed styles, layout, and (in region-capture mode) a screenshot of the visible tab. None of this leaves your browser automatically: it is only written to your clipboard when you click copy, or sent to a locally running MCP bridge on your own machine when you use the Agent panel. The extension never transmits screenshots, DOM data, or clipboard contents to Quey's servers.
Feedback tool
The toolbar's Feedback tool lets you send a bug report, feature request, or general note directly to us. When you submit feedback, we store the message, the type you selected, the page URL it was sent from, your browser's user-agent string, and — if you're signed in — your account email so we can follow up. This is the only toolbar feature that sends data to Quey's servers by default; everything else (element capture, style edits, clipboard copies) stays local unless you explicitly use the Agent panel with a connected MCP bridge.
Local MCP bridge
If you run the optional @quey/mcp server, captures are sent over localhost only. The MCP server does not forward data to external services unless you configure it to do so (for example, by wiring it to a third-party AI agent). Quey has no visibility into data sent through your local MCP setup.
Analytics and error tracking
We may collect anonymised usage analytics (page views, feature interactions) to understand how the product is used. We do not sell this data. Error monitoring may capture stack traces and request context to help us diagnose bugs. Any error reports are retained only as long as necessary and are not used for advertising.
Data retention
Account data is retained for as long as your account is active. You can request deletion of your account and associated data at any time by emailing us. Stripe subscription records are subject to Stripe's own data retention policies for financial compliance.
Third-party services
Quey uses GitHub and Google OAuth for authentication, Stripe for payment processing, and Convex as a hosted backend. Each of these services has its own privacy policy governing how they handle your data. We choose infrastructure providers that meet reasonable data protection standards.
Your rights
You may request access to, correction of, or deletion of your personal data at any time. To exercise these rights, email us at the address below. If you are located in the EU or UK, you have additional rights under GDPR and UK GDPR, including the right to lodge a complaint with a supervisory authority.
Contact
For privacy questions or data requests, contact us at d58192307@gmail.com. We will respond within 30 days.