Website inspection and capture
Inspection and editing run in your browser after you activate UIGrab. Normal UI capture serializes the selected elements or page, including text, design properties and image content, and writes an encoded representation to your clipboard. UIGrab does not upload these normal toolbar captures to its licensing backend. When you paste into Figma, Figma processes that content under its own terms and privacy practices.
Screenshots are captured locally. Download and copy operations place files on your device or content on your clipboard. Captures may include private information present on the page. Capture only content you are authorized to use, and avoid capturing passwords, financial information or other sensitive material. The packaged extension does not automatically capture based on website URL parameters.
Optional external requests
When you use translation, selected website text and the target language are sent to Google Translate. Font selection can request a font family and font resources from Google Fonts. These providers also receive ordinary network request information. Do not translate sensitive text unless you are comfortable sharing it with that provider.
Asset operations may request media from the website’s media hosts. Where additional access is necessary, UIGrab requests permission for that origin. Responsive previews reload the current website inside a frame, so the website receives those requests and may use its existing cookies. Preview temporarily removes framing restrictions and the frame’s full Content Security Policy for the current website in that tab; top-level page and unrelated frame-host headers are not changed.
Local extension data
The extension stores trial timing, an installation identifier, an optional restoration license key and a short-lived verified entitlement cache in Chrome’s local extension storage. Editor and toolbar preferences use local browser storage associated with the inspected website. UIGrab does not provide a cloud capture library. Clearing extension data removes local activation information; an existing customer can restore using their license key.
Purchases and verification
The licensing backend processes an installation identifier, Dodo payment and customer identifiers, purchase email, purchase and license status, purchase time and verification time. License keys are sent over HTTPS for verification and represented in UIGrab’s database by a keyed cryptographic digest, not plaintext. Pro ownership is determined by verified backend purchase records, not local storage alone. A verified cache provides temporary offline access.
Payments are handled by Dodo Payments under its own terms and privacy practices. UIGrab receives verified transaction and license events needed to provide Pro access. UIGrab does not store payment-card details. Pro is a one-time purchase with no recurring billing.
Hosting, security and support
The UIGrab website uses Vercel Web Analytics to measure page visits, traffic sources and aggregate browser, device and location information. Analytics does not use tracking cookies. Page URL query parameters and fragments are removed before events are sent, so checkout identifiers in those parts of the URL are not included. We do not send license keys, form contents, captured website content or extension activity as analytics events.
Our hosting and infrastructure providers, including Vercel and Supabase, may process IP address, browser details, route, timestamp and security logs. The backend uses hashed request-address identifiers for rate limiting. Support messages contain information you choose to send. Never send payment-card details or publish your license key.
We use this information to deliver the service, verify and restore purchases, prevent abuse, answer support requests and diagnose failures. UIGrab does not include application analytics tracking of captures or browsing history. Dodo credentials and database service credentials remain server-side.
Retention and deletion
Local data remains until you clear it or remove the extension. Purchase records may be retained for accounting, fraud prevention and legal obligations. Operational logs and rate-limit records are retained only as needed. To request access or deletion where applicable, use the contact page.
Changes
We may update this policy when the product, providers or legal requirements change. The date above identifies the current version.