Last updated: November 10, 2026
Grabify processes captured content locally. Grabify's servers do not receive your captures.
Captured images, annotations, notes, PDFs, and PowerPoint files are processed on your device. In-progress sessions and named Library collections are stored in the extension's local browser database so they can be reopened. Source titles, sanitized source URLs, dates, and detected slide numbers are saved locally with captures. Source details are included in PDF or PowerPoint only when you choose Include sources. Captured content leaves your device only when you explicitly enable and use an optional export integration or connect an AI assistant.
Record mode: Chrome's display-sharing picker lets you choose the browser tab, window, or screen to record and whether available system or tab audio is included. Recording chunks are held only in page memory, assembled on-device, and downloaded locally as a WebM file when you stop. Grabify does not upload Record-mode video or audio to its servers, and optional export integrations do not receive a recording automatically. The file leaves your device only if you later choose a separate sharing or upload action.
Grabify does not continuously log your browsing history, include third-party advertising trackers, build an advertising profile, sell personal information, or sell captured content.
Stripe handles card and bank information. Grabify does not receive or store those payment credentials.
Captures and recoverable sessions are stored in the extension's local IndexedDB database. Preferences, capture settings, local funnel events, and non-sensitive integration configuration are stored in local Chrome extension storage. Sensitive integration values—including webhook URLs, custom headers and fields, Airtable tokens, and Cloudinary upload presets—are held only in Chrome's in-memory session storage. They are not written to local or sync storage and must be re-entered after Chrome restarts or the extension reloads. License status, usage counters, the one-time review-credit grant, and a random device identifier created for voluntary feedback may be stored through Chrome sync. Websites cannot read these extension storage areas. Local funnel events are not sent to Grabify.
AI assistants (optional): When you pair the separately installed local assistant companion and connect a page, Claude Desktop or ChatGPT can request captures, visible readable text, tables, and PNG/PDF exports from that selected page. The companion listens only on 127.0.0.1, uses separate private browser and assistant credentials, and does not allow the assistant to choose another tab. Chrome asks for local helper access when you first connect; later connections reuse that permission. Navigation, closing Grabify or the connection dashboard, and Disconnect end the active page connection. Previously returned results remain available to your assistant until the companion's 30-minute retention expires (cleanup runs while the helper is running and on its next startup); exports saved separately remain until you remove them. Companion files and credentials are stored in an owner-only folder on your device. ChatGPT uses a separately configured OpenAI Secure MCP Tunnel. Data you request through either assistant is processed under that provider's terms and privacy policy; Grabify servers do not receive it. Assistant exports use Grabify's normal export limits and branding, and do not invoke Airtable or webhook automation. The browser keeps up to four prepared export files on this device for recovery without a second credit deduction. They expire after 30 minutes and are cleaned up on the next use; End session removes the prepared files. Small accounting receipts can remain until expiry to prevent duplicate deductions.
These transfers occur at your direction and are governed by the destination provider's terms. Integrations are disabled by default.
Stripe processes checkout and subscriptions. Vercel hosts the Grabify API. Upstash stores operational records for licenses, purchases, credits, and voluntary feedback, plus historical referral records created by older versions. If owner email alerts are enabled, Resend receives short excerpts of voluntarily submitted reports and private inbox links; page URL fields, contact addresses, browser details, device identifiers, and captures are excluded from alerts. Google Chrome sync may sync small extension records through your signed-in Chrome profile. Google Forms may host the optional uninstall-feedback form.
Grabify does not sell data or transfer it for advertising, credit scoring, or purposes unrelated to capture and export, licensing, billing, user-requested support, security, and service reliability.
Permissions when needed: In Chrome Web Store version 1.26.34 and later, clipboard writing, media downloads and broader website access are optional. Grabify explains the purpose before asking Chrome to grant access when the related feature needs it. Basic toolbar capture uses activeTab. Skipping a request keeps existing work, and the action can be tried again later. Earlier versions may request these permissions at installation.
Media downloads: When you choose Find media or open Media from a page's panel, Grabify scans that page's top-frame media elements and direct file links. Choosing Download with Grabify from an image, video, or audio context menu scans only that media's accessible frame and selects the exact clicked source. The source tab and frame are revalidated before downloading. Discovered URLs remain in Chrome's in-memory session storage, with a 30-minute authorization window; clicked-media handoffs use opaque identifiers and do not place media URLs in the workspace address. Previews and downloads request files from the source host. MP3 and still-image conversion run locally in a private extension worker, omit cookies, and reject redirects. Original-download handling differs by edition, as described below. Media and conversions are not uploaded to Grabify or optional integrations. Active jobs continue when the Media panel or tab closes; you can reopen Media to check progress or cancel. Job metadata stays in bounded in-memory session storage (up to 40 records; terminal records expire after 30 minutes). Closing Chrome or reloading the extension can interrupt unfinished jobs. Browser-based direct scans exclude YouTube sources. Other protected media, raw blob URLs, and unsupported segmented streams are excluded.
Pasted media links and X posts: Find media can check a pasted direct file URL using a HEAD request or a small range probe. For a public X post, Grabify sends its post ID to X's public embed service and reads the available progressive MP4/image URLs from X's media CDN; this can resolve the underlying files when a page player uses a blob URL. These lookups omit cookies and referrers, reject redirects, and do not extract account credentials or access private posts. Resolved URLs remain in bounded in-memory session caches, with authorization expiring after 30 minutes. They are not added to the workspace address, synced, or sent to Grabify. Raw blob URLs and protected or unsupported segmented streams remain unsupported. YouTube links are supported only in the separate local edition described below.
Chrome Web Store edition: Original media downloads fetch the source without site cookies or credentials, reject redirects, and are limited to 32 MiB (33,554,432 bytes). Chrome saves the resulting local file and records it in its download history. Sources requiring sign-in, redirects, or larger files are unsupported. YouTube and the native helper are not included in this edition.
Separate local edition: Original media downloads use Chrome's source access rules and usual download history. This local edition includes YouTube downloading through an explicitly installed native messaging helper. Opening Media or its setup guide checks the helper connection locally without contacting media sites. When you paste a YouTube video link or choose its download action, the helper requests public metadata and source files from YouTube. yt-dlp handles source retrieval and FFmpeg merges MP4 or creates MP3 on your device. The helper does not read browser account cookies or saved credentials, access private/restricted/protected/live videos, or upload media to Grabify. Native messaging is restricted to configured extension origins; no local HTTP server is opened. Output saves to your local Grabify downloads folder, and temporary files are removed on cancellation or connection closure. Closing the Media panel does not disconnect an active helper job; reopen it for progress and cancellation. Native downloads use the helper’s progress display and are not added to Chrome’s download history.
Grabify (Chrome Web Store developer: mreiffy) is the seller of Pro subscriptions and credit packs. For purchase or billing support, contact Grabify at mreiffy@gmail.com. Google distributes the extension through the Chrome Web Store but is not the seller, payment processor, or billing-support provider for these purchases. Stripe processes payments for Grabify.
Monthly and annual Pro subscriptions automatically renew at the price and billing interval shown at checkout until canceled. Cancel before the next renewal through Manage Subscription in the extension, which opens the Stripe customer portal, or email Grabify support. Cancellation stops future renewals; Pro access ordinarily continues through the end of the paid billing period.
Credit packs and other digital purchases, including subscription charges already processed, are final and non-refundable except where required by applicable law. For a duplicate charge, incorrect amount, or other billing error, email mreiffy@gmail.com with the purchase email and charge details so Grabify can investigate.
Full Page capture is included in Free. Normal export limits and branding still apply.
You may capture and export only content you own or are explicitly authorized or otherwise legally entitled to copy. Grabify does not grant access rights or permission to copy content and must not be used to bypass paywalls, DRM, login restrictions, or other access controls, or where a website's terms or applicable law prohibit copying.
You can disable integrations at any time in Grabify settings and remove local extension data through Chrome. To request access to or deletion of server-side information associated with a purchase, license, feedback submission, random device identifier, or historical referral record, email mreiffy@gmail.com. Include the relevant identifier so the record can be located.
Grabify's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.