Privacy,
in plain sight.

PixelRecord handles website content to create the screenshot you request. That capture work happens locally in your browser. This policy also explains the limited data used by pixelrecord.app, its optional launch waitlist, and PixelRecord Pro purchases.

Effective: October 27, 2026

Captured page content
On your device
Extension analytics
None
Extension account
Not required
Waitlist email
Resend
Pro buyer email
Kept with license

The extension does not upload your screenshots or captured page content.

Capture, stitching, editing, clipboard copy, and PNG/PDF export run inside Chrome on your device.

1. Scope

This Privacy Policy covers the PixelRecord Chrome extension (the “Extension”) and the website at pixelrecord.app (the “Website”). In this policy, “PixelRecord,” “we,” “us,” and “our” refer to the operator of the PixelRecord product.

The Extension and Website have different data flows. The Extension processes captures locally. The Website is hosted by Cloudflare, the optional waitlist uses Resend to send and manage email, and PixelRecord Pro is sold through Stripe or Lemon Squeezy, which process payments as Merchant of Record.

2. Data the Extension handles

Google considers screenshots and website content to be user data even when they are processed only on a user’s device. When you explicitly start a capture, PixelRecord handles the following information to provide the capture and editing features:

  • Rendered website content: the visible pixels of the page, which can include text, images, form values, personal information, or other sensitive material visible in the selected tab.
  • Page details: the current page title and URL, used to identify the capture and suggest an export filename.
  • Layout details: document and viewport dimensions, device pixel ratio, scroll positions, and the location of fixed or sticky elements, used to scroll and stitch the page correctly.
  • Your edits: crop bounds and annotations such as pen strokes, highlights, arrows, rectangles, and text that you add in the editor.

The Extension uses this information only to capture the tab you selected, assemble and display the screenshot, preserve your in-progress edits, and create the copy or export you request. It does not continuously monitor tabs or read your general browsing history.

Free allowance and Pro license

The free plan includes seven captures per calendar month. The Extension counts successful captures on your device; the count is never sent to PixelRecord. If Chrome sync is turned on, Chrome also keeps the count in your browser profile so it stays consistent across your signed-in browsers.

If you enter a PixelRecord Pro license code, the Extension sends that code and a random identifier created for this browser installation to pixelrecord.app. We use them to check the code, limit the number of browsers where a code is active, and return a signed license that the Extension verifies on your device. While Pro is active, the Extension renews the license with pixelrecord.app every few days, sending only that signed license. If pixelrecord.app no longer lists the browser as activated, the Extension sends the stored code and browser identifier once more to activate it again. These requests never include screenshots, page content, URLs, or annotations.

For each license, we store a one-way hash of the code, how many browsers it may be used on, and optional expiry and revocation dates. For a purchased license, we also store the buyer’s email address and order reference with it, as described in Pro purchases. For each activated browser, we store its random identifier, when it was activated, and when it last renewed. When a code is already active in as many browsers as it allows, records of its browsers that haven’t renewed for 30 days are deleted so another browser can take their place. To slow down code guessing, we also keep a one-way hash of the requesting IP address with a count of recent activation attempts; these counters are deleted within about a day.

3. Local processing, storage, and deletion

Screenshot tiles are captured through Chrome, stitched locally, and stored with the page title, URL, capture metadata, crop, and annotations in the Extension’s private IndexedDB storage. This temporary storage lets the editor open the result and keep in-progress edits available on the same device.

Each capture is assigned a 24-hour expiration time. Expired captures are removed the next time the Extension’s cleanup process runs, so deletion may occur after—not exactly at—the 24-hour mark if the Extension is inactive. You can remove local Extension data sooner by removing PixelRecord from Chrome; Chrome developer tools can also clear the Extension’s private storage.

The Extension also keeps its random browser identifier, the monthly capture count, and any Pro license code with its signed license in Chrome’s extension storage, so the license page can show the code and the Extension can activate it again. They remain until you remove the license or remove PixelRecord from Chrome; a count kept in Chrome sync remains in your profile.

Files you download and images you copy to the clipboard are then controlled by your device, browser, operating system, and any application where you save or paste them. PixelRecord cannot delete those copies for you.

What is not sent

The Extension has no account system, cloud screenshot storage, extension analytics, telemetry, advertising, or remote capture service. PixelRecord does not receive your screenshots, page content, URLs, annotations, or exported files. The only requests the Extension makes to PixelRecord are the license activation, renewal, and removal described above.

4. Chrome permissions

PixelRecord requests the narrow permissions needed for its current capture workflow:

activeTab
Gives temporary access to the tab you choose after you click the PixelRecord toolbar button.
scripting
Runs the capture script in that tab so PixelRecord can measure, scroll, capture, and restore the page.
offscreen
Provides an Extension-owned document where screenshot tiles can be combined with a local canvas.
clipboardWrite
Copies the finished PNG to your clipboard only when you choose the copy action.
storage
Keeps the monthly free-capture count, a random browser identifier, and any Pro license in the Extension’s own storage.

The Extension does not request permanent access to every website, browsing history, cookies, or clipboard contents.

5. Website, launch waitlist, and purchases

Ordinary Website requests

The Website is hosted on Cloudflare. When your browser requests a page, Cloudflare may process ordinary request data such as your IP address, browser and device information, requested URL, and request time to deliver, protect, and operate the Website. PixelRecord does not currently place analytics or advertising scripts on the Website and does not set its own tracking cookies.

Links from the Website to the Chrome Web Store carry a campaign tag (utm_source, utm_medium, utm_campaign) that names only the kind of page the link was on, such as a guide or the home page. When you open the Web Store listing, Google can use it to count aggregate installs per source in the Web Store’s own analytics, under Google’s privacy policy. The tag contains no personal data, and the Website itself does not read it back, store it, or send it anywhere.

Waitlist email

If you choose to join the waitlist, we use the email address you enter to send a confirmation message and, after you confirm, PixelRecord launch and early-access updates. Joining the waitlist is optional and is separate from using the Extension.

The Website sends the address to Resend for email delivery. The confirmation link contains an encrypted token rather than a plain-text email address and expires after seven days. After confirmation, the address is added to a PixelRecord contact segment in Resend. The PixelRecord Worker does not maintain a separate subscriber database.

We keep a confirmed waitlist address until you unsubscribe, ask us to delete it, or the launch and early-access update program ends. Resend or Cloudflare may retain limited records for longer where needed for security, delivery suppression, legal compliance, or dispute resolution under their own terms.

Pro purchases

PixelRecord Pro is sold through Stripe (Stripe Managed Payments) or Lemon Squeezy, which act as Merchant of Record. They collect your payment details, billing information, and email address at checkout and handle payment, tax, and receipts under their own privacy policies. PixelRecord never receives your card or other payment details.

When a payment completes, the reseller notifies pixelrecord.app with the order’s identifiers, payment status, and the email address you entered at checkout. We use that email address to send your license code through Resend, and to help with support, refunds, and lost codes.

We store the buyer’s email address and the order reference (a Stripe Checkout Session and payment ID, or a Lemon Squeezy order ID and number) with the license, along with when the order was recorded and when the license email was sent. If the purchase is refunded or disputed, the reseller tells us and we mark the license as revoked. We do not add buyers to the waitlist or send them marketing email because of a purchase.

We keep these records for as long as the license exists and as needed to handle support, refunds, disputes, and legal obligations. You can ask us to access, correct, or delete the email address stored with your license; the reseller keeps its own order records under its own terms.

6. Service providers and sharing

We use a limited set of providers to operate the Website, waitlist, and Pro purchases:

  • Cloudflare hosts and secures the Website, runs the waitlist and license endpoints, and stores license and activation records in its D1 database. See Cloudflare’s Privacy Policy.
  • Resend (Plus Five Five, Inc.) sends waitlist confirmation, update, and license code emails, and stores confirmed waitlist contacts. See Resend’s Privacy Policy.
  • Stripe sells PixelRecord Pro as Merchant of Record through Stripe Managed Payments and processes payments, taxes, receipts, refunds, and disputes. See Stripe’s Privacy Policy.
  • Lemon Squeezy sells PixelRecord Pro as Merchant of Record for orders placed through its checkout. See Lemon Squeezy’s Privacy Policy.

We do not send captured page content or screenshots to any of these providers. We do not sell personal information, share it with data brokers, or use it for personalized or interest-based advertising. We may disclose limited information when required by law or when reasonably necessary to protect the security and integrity of the service.

These providers may process information in countries other than your own. Their privacy notices describe their locations, safeguards, and subprocessors.

7. Chrome Web Store Limited Use

PixelRecord’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Data handled through Chrome permissions is used only to provide the Extension’s disclosed, user-facing capture and editing features. It is not transferred for advertising, credit assessment, data brokerage, or unrelated purposes, and it is not made available for people to read because it is not transmitted to PixelRecord.

8. Your choices and rights

  • You decide when the Extension gets temporary access by starting a capture.
  • You can delete locally stored capture data by removing the Extension; Chrome developer tools can also clear its private storage.
  • You can remove a Pro license from a browser on the Extension’s license page, which deletes that browser’s activation record from our database.
  • You can choose not to join the waitlist without affecting the Extension.
  • You can unsubscribe from update emails or contact us to request access to, correction of, or deletion of your waitlist address.
  • You can contact us to request access to, correction of, or deletion of the email address stored with a purchased license.

Depending on where you live, privacy law may provide additional rights such as restricting or objecting to processing, withdrawing consent, obtaining a portable copy, or complaining to a local data protection authority. We may need to verify a request before acting on it.

9. Children

PixelRecord is a general-purpose productivity tool and is not directed to children under 13. We do not knowingly use the Website to collect personal information from children under 13. If you believe a child has joined the waitlist, contact us so we can remove the address.

10. Changes to this policy

We may update this policy when PixelRecord’s features, providers, or legal obligations change. We will post the revised policy here and update the effective date. If a change materially affects how the Extension handles user data, we will disclose it before publishing the affected version.

11. Contact

Questions or requests about this policy can be sent to PixelRecord at hello@pixelrecord.app.