Privacy policy

Effective October 29, 2026

This policy explains what data the Pagewing Chrome extension ("Pagewing") and its website handle, and why. Pagewing is published by Ahmed Gamal ("we", "us"). Questions: tool@appzlr.com.

The short version

• Before the extension sends anything to your Pagewing account, it shows you what it will send and why, and asks you to agree by pressing "Continue" (in the side panel, or on our sign-in page). Until you do, nothing from it reaches your account. If that list changes, the extension shows it again and holds everything back until you agree to the new one.
• Bookmarks never leave your computer (if you turn on searching inside bookmarked pages, the text of those pages is kept in your account), and screen recordings only do when you share one. Notes stay in your browser unless you turn on notes sync, which keeps them in your account so you can use them on our website and in your other browsers. Screenshots and PDFs you edit in Pagewing stay in your browser; with a paid subscription, screenshots are also kept in your Pagewing cloud and you can save PDFs there.
• Our server only stores what's needed to run your account, your plan (and any free trial it had), your subscription, the counts behind the free plan's limits, and what you create, save or sync in the tools (such as short links, tab sessions, templates, reminders, tracked time, synced notes, Read later articles with your highlights, AI writer history and tracked emails; each is listed below), a short record of the free-plan limits and paid features your account runs into and of its upgrades (see "Upgrade records" below), plus, only if you turn it on, a daily count of how often you use each tool.
• When you create an account on our website, we keep where your first visit to it came from: the name of the site that sent you (like chatgpt.com, never the page's address), any campaign tags in the link, the page you landed on, and, if you answer the welcome page's optional question, where you heard about Pagewing. It shows us which places bring people to Pagewing. It stays with us and isn't shared with anyone.
• Our website uses Google Analytics to count visits. The extension has no third-party analytics. Counting which tools you use is off unless you turn it on, and even then it only reports which tool you used, never what you used it on.
• When we run ads, our website uses Google's and Meta's ad tags to measure them. If you reach it from one of our ads on Google or Meta (Facebook, Instagram), the website remembers that ad click, and if you then create an account, subscribe or move up to a higher plan, our server tells that ad platform, so we can see which ads work. Meta is also told when any account is created on our website, without your name or email. Nothing the extension handles is ever part of this.
• The AI writer only sends text when you ask it to write something: your request and the text it works on go to our server and to Anthropic, which runs the AI model, to write the answer. Anthropic doesn't train on it and deletes it within 30 days. Your results are kept in your Pagewing history unless you turn that off. Shared recordings are named the same way: the start of a recording's transcript goes to Anthropic to suggest its title, unless you turn AI titles off, and on Pro the transcript goes to write its summary, chapters and action items, unless you turn AI summaries off.
• We don't sell data, show ads in Pagewing, or track the pages you visit with the extension.

Your agreement in the extension

The extension asks before it sends anything. When you press Sign in in the side panel, it first says what goes to your Pagewing account and why, with "What's synced" opening the full list, tool by tool, and a link to this policy. Pressing "Continue" records your agreement in that browser and opens our sign-in page; "Not now" leaves everything as it was. If you start signing in on our website instead, the sign-in page shows the same summary and list, with the same "Continue". Until you agree, the extension sends nothing that carries your sign-in, and it doesn't take the sign-in at all. Two kinds of collection aren't needed for any tool to work and are off unless you turn them on in the extension's Settings → Privacy: counting which tools you use and video speed's time-saved stats. Each browser keeps its own agreement and switches. When we change what the extension sends, it shows the new list in the side panel and sends nothing to your account from that browser until you agree again (or sign out). Settings → Privacy → "What's sent" shows the list at any time.

Data that stays on your device

• Page access. Pagewing can run on the pages you visit so it can scroll them and capture screenshots when you ask it to. It measures and scrolls the page locally, and reads its text locally to show it in the teleprompter when you ask. It doesn't collect, store or transmit page content, except text you choose to send to the AI writer (see "AI writer" below).
• Screenshots and screen recordings are created in your browser. Screen recordings you save to your computer go to your Downloads folder and are never uploaded unless you share them later; recordings you share, and videos you upload to your Pagewing library, are uploaded (see "Shared recordings" below). Screenshots you edit open in the Pagewing website in the same browser and are kept in that browser's storage; with a paid subscription they're uploaded to your Pagewing cloud instead (see "Screenshots" below), unless you choose "Save to Downloads" in the extension. Your recent screenshots are also kept in the browser's own storage so the side panel can list them. When you record, Chrome asks you what to share. The recording only includes what you choose, plus your microphone and camera if you turn them on. The camera and microphone are only used on the recorder's own page, while you preview or record.
• PDFs. When you open a PDF in Pagewing, the extension downloads it from the site you're viewing (as Chrome's own viewer would) and hands it to our website's PDF editor in the same browser. Viewing, annotating, signing, organizing, compressing and converting PDFs to Word, Excel, PowerPoint, images or text all happen in your browser, and your files and saved signatures are kept in the browser's own storage until you remove them. The extension notes which of your tabs show a PDF (from the file type) so it can offer to open it; that stays on your device. If you turn on "Open PDFs from websites in Pagewing", PDF links open in our editor instead of Chrome's viewer.
• Bookmarks are read and changed with Chrome's bookmarks API, on your device. The bookmark manager page on this website works through the extension in the same browser: your bookmarks go from the extension to that page and back, and are never sent to our servers. When you run a link check (by hand or on a schedule you turn on), your browser contacts each bookmarked site directly to see if it still responds; when you ask for a saved copy of a dead page, it asks the Internet Archive's Wayback Machine about that one address. Tags and notes you add to bookmarks, and each page's preview image and description (read from the page when you save it, or when you load previews in the manager), are kept in the extension on your device. We aren't involved and see none of it.
• Searching inside bookmarked pages (Premium) is off until you turn it on. While it's on, the extension in each browser where you're signed in downloads each bookmarked page the way a signed-out visitor sees it (without your cookies or sign-ins, and never private or local addresses such as your router or intranet), finds the article in it on your device with the same reader as Read later, and sends us the page's address, its bookmark title and the article. Our server keeps the address, title and up to the first 20,000 characters of the page's plain text (no images or layout), for up to 20,000 pages, only so you can search them in the side panel and the bookmark manager. Your bookmarks themselves, their folders, tags and notes still stay in your browser. Deleting a bookmark deletes its page's text; turning the feature off deletes all of it, and so does deleting your account.
• Open tabs and auto-save. Tabs & sessions reads the address and title of your open tabs on your device to list, search and tidy them. Its auto-save snapshots of your open windows, and recently closed tabs (only if you allow it), are kept in Chrome's extension storage on your device and never uploaded unless you choose to keep one as a session.
• Read later on web pages. The extension runs on the pages you visit so you can highlight text there and see your highlights again. On each page it only checks, on your device, whether its address is one of your saved pages with highlights; it doesn't read a page's text, or send anything about it, until you save the page or highlight something on it (see below). The side panel's Read later tab gets the list of addresses you've saved from your account and checks the open tab against it on your device, so it only asks our server about a page you've already saved. To put a check on the Pagewing button when a tab's page is already saved, the extension keeps that list of addresses on your device and checks each tab against it there; you can turn the check off in Read later's settings. Your Read later settings are kept in the extension on your device.
• Notes you write in Pagewing, and the stopwatch's state, are kept in Chrome's extension storage on your device, and uninstalling Pagewing deletes them there. Notes are only uploaded if you turn on "Sync notes to your Pagewing account" (see below); the stopwatch's state never is.
• Video speed runs on the pages you visit, on your device: it changes how fast their video and audio play, and how the picture looks if you ask it to. Its settings, site rules and shortcuts are kept in Chrome's extension storage on your device, and synced to your account while you're signed in (see below). It never records which videos or pages you watch: for the time-saved stats, only if you turn them on, it adds up how long things played, per site name. When you turn on volume boost or pitch for a tab, Pagewing captures that tab's sound (Chrome shows its capture icon on the tab) and plays it back louder or at the pitch you chose. That sound is processed on your device as it plays and is never recorded, stored or sent anywhere; the capture stops when you turn them off, close the tab or it loads another page.
• Page marker. What you draw and write on a page with the page marker is kept in the extension's own browser database on your device, with that page's address and title, so your marks come back when you open the page again. It's never uploaded, unless you take a screenshot of the page and choose to keep it in your Pagewing. You can delete or export these marks from the side panel, and uninstalling Pagewing deletes them.
• Typing on web pages. To notice when you type a template's shortcut in a text box, Pagewing looks at the few characters just before your cursor, on your device. What you type on web pages is never sent anywhere (unless you send it to the AI writer yourself). A template that uses {{clipboard}} reads your clipboard only when you choose that template, to fill it in; what it reads stays on your device.
• Text recovery. So a refresh, a crash or an expired session can't lose your words, Pagewing keeps what you type into text areas and editors on web pages (and one-line boxes, if you turn that on), with the page's address and title, in the extension's own storage in your browser. It is never uploaded: our website's Text recovery page reads it through the extension in the same browser. Password, card number and one-time-code boxes, code editors and private (incognito) windows are never saved. Drafts are deleted after 7 days on the free plan and 90 days on Premium, and you can turn it off, turn off any site, or delete everything in the side panel.
• The new tab page of earlier versions. Pagewing no longer has a new tab page. Its settings, shortcuts and to-dos that earlier versions synced to your account are deleted from our servers, and the extension deletes its own copy and any background photos from your browser when it updates.
• Cleaning browsing data. When you use the cleaner, Pagewing asks Chrome to delete the data you picked, on your device. It doesn't read that data or send it anywhere. Your choices, protected sites and the log of recent cleanups are kept in Chrome's extension storage.
• Settings such as scroll speed, recorder options and your recent recordings list, and the scripts you save in the teleprompter, are kept in Chrome's extension storage.

Data we receive and store

• Account. You sign in on our website with Google or with an email and password. Sign-in is run by Google Firebase Authentication, under Google's privacy terms; we never see your password. We store your account ID, email address, whether it's verified, and the name and profile picture link your sign-in provides, plus when you first signed in and when you were last active.
• Connected browsers. When you sign Pagewing in, the website gives that browser its own sign-in token. We store a scrambled (hashed) copy of the token, a name for the browser such as "Chrome on Windows", and when it was connected and last used, so you can see and disconnect your browsers on your account page.
• Subscription. Subscriptions are sold through Paddle, which acts as the merchant of record. When you subscribe, we send Paddle your account's email address and name so checkout opens with them filled in. Paddle collects your payment and billing details, handles tax, and emails your receipts, underits own privacy policy. We store the subscription's number, your customer number with Paddle, the number of your first payment, the subscription's status and its renewal or end date, and any pause, discount or plan change you take. While a checkout is open we keep which plan and price it's for, for 90 days. Your card details never reach us. Our pricing page loads Paddle's script for every visitor, to show prices in your currency, which Paddle works out from your IP address.
• Upgrade records. To learn which free-plan limits and paid features lead people to upgrade, our server keeps a short record with your account when it turns down something because your plan doesn't include it (which limit or feature, its tool, and how many times that day), when our website shows you an upgrade prompt or you follow it, when you open your account page from an upgrade button in the extension (the button puts the limit or feature in the page's address), when you open checkout (and for which plan), and when your account is created and your subscription starts, moves to a higher plan, renews or ends, each with the time. It never includes what you were saving or doing, or any page's address or content, and the extension sends nothing extra for it: these are requests our server answers anyway. We look at them only as totals, and each record is deleted a year after it's made.
• Welcome page counts. Right after it's installed, the extension opens our welcome page. That page counts the visit once, and our server counts an account later created in the same browser, both only as a number per day: no account, browser, address or other identifier is sent or kept with them. To tell that the sign-up came after the visit, the page keeps the visit's date in your browser's local storage, sends it along with the website's requests until you're signed in, and then stops. The counts are deleted after a year.
• Cancelling. When you cancel your subscription on your account page, we ask why. We keep your answer with your account and plan: the reason you pick, anything you choose to write, the offers we showed you (a pause, yearly billing, a cheaper plan or a discount) and whether you took one or cancelled. If you write about a missing feature or a problem, it also goes to our contact inbox so we can answer you by email. We use these to improve Pagewing and look at them as totals, and delete each one, and its copy in our inbox, two years after it's made. A pause, discount or plan change you take is made through Paddle, like any other change to your subscription.
• Short links. When you shorten a link, the extension sends us that URL and any custom alias you typed, and a title for the link (the page's title when you shorten the tab you're on, which you can change). While the shortener's address field follows the tab you're on, that address stays on your device: it's only checked against the links already shown. An address you type into the field is sent as you type, to show whether you already have a short link for it. We store the URL, the title, the short code, the account that created it, when it was created, a click count and when it was last clicked, plus any tags, expiry date, off switch and device and country redirects you set (each redirect's devices or countries and the address it sends them to). When someone opens a short link, we add one to the click count, note the time and redirect them; if the link has device or country redirects, the kind of device and the country Cloudflare reports for the visit decide where it goes, and aren't kept beyond the totals below. For the link's stats we also add one to a daily total for the website that sent them (its domain only, never the full address), the country Cloudflare reports for the visit, the kind of device (computer, phone, tablet or bot) and which redirect sent them, if any. Those are totals only: we don't record who clicked, their IP address, browser details, city or the page they came from. To keep short links from leading people to phishing or malware, our server may look up the address you shorten (and a new address you give an existing link) in Google's Web Risk service, which checks it against Google's list of unsafe sites. Only the address is sent, never who you are. Anyone can report a short link on our report page; we keep the report (the link, the reason, what they wrote, their account ID if they're signed in, and an email address only if they typed one) for two years, to review it.
• API keys. On Pagewing Pro you can make keys for our API on your account page. We store each key's name, when it was made and when it was last used, and a one-way hash of the key, never the key itself (it's shown to you once). Requests made with a key do what the same change would do on the website, under your account. Deleting a key, or your account, removes it.
• Templates. The text templates you create (name, shortcut, folder and text) are stored with your account, so you can manage them on our website and use them in every browser you sign in to. We also store when each was created and changed, and how many times and when it was last inserted. Each browser keeps a copy so it can insert them instantly. Deleting a template deletes it from our server.
• Tab sessions. When you save tabs in Tabs & sessions (or keep an auto-save), we store each session's name, your note and star, the names you give its windows, the address, title, pinned state and tab group (name and color) of every tab in it, and the links and notes you pin to it (its workspace), with when it was saved, changed and last restored. This lets you restore it in any browser you sign in to and manage it on our website. If you turn on a share link, anyone with that link can see the session's name, note, tabs, pinned links and notes (never your name or email) until you turn it off. Deleting a session deletes it from our server.
• Video speed. While you're signed in, the extension syncs its video speed settings to your account so you can manage them on our website and share them between your browsers: the all-sites speed, presets, switches, keyboard shortcuts and site rules (each a site name or address pattern you typed, such asyoutube.com/shorts/*, with its speed and picture settings). Only if you turn on the time-saved stats ("Count the time video speed saves me", off until you turn it on), it sends, per day and site name (such as youtube.com), how many seconds of video and audio played and how long that took. It never sends page addresses, titles or what you watched. We keep the stats for 400 days. Each browser has its own switches for both in the extension (Video speed → Sites → Sync, and Settings → Privacy for the stats), and "Delete from my account" on the Video speed page deletes both from our server.
• Read later. When you save a page (from the side panel, a shortcut or the right-click menu), or highlight text on a page that isn't saved yet, the extension reads the article on your device and we store, with your account: its address, title, site name, author, publication date, a short excerpt, the address of its lead image, and the article's text as cleaned-up HTML. Images are never copied to our server; the reader loads them from the article's own site, without telling that site which page you're on. Saving a link from the right-click menu has the extension fetch that page (without your cookies) to read it. We also store each highlight's text, color, a little of the text around it (so it can be found again) and your note, and per article its tags, whether it's archived or a favorite, how far you've read and when. This is kept for everyone signed in, on the free plan too, so you can read and export it on our website from any browser. Importing a list from Pocket, Omnivore or Instapaper stores the links, titles, tags and highlights in that file. Deleting an article deletes it and its highlights from our server. When you ask Read later for an article's summary, ask a question about it or ask it to explain a passage (on our website or in the side panel), or turn on summaries for new saves, the article's title, site name, author and text (up to about 120,000 characters) and your question or passage go to Anthropic, which runs the Claude model, to write the answer. Under its commercial terms Anthropic doesn't use it to train its models and deletes it within 30 days. We keep the summary and your questions and answers with the article until you delete them or the article. Listening to an article uses your browser's own voices; some of them (marked "online") are run by your browser's maker, which then gets the text being read.
• Notes, only if you turn on sync. Notes sync is off until you turn it on, in the Notes tab of the side panel or on the Notes page of our website. Then the notes in that browser are uploaded once, and every change after that, so you can write and organize them on our website and see them in your other browsers: each note's text, when it was created and last edited, whether it's pinned, its folder, and the address and title of the page it's about when it has one, with that page's author, site name and publish date (read from the page's own metadata when you make the note or press Cite, so you can cite it; you can edit them). Turning sync on in one browser doesn't upload the notes of your other browsers; each one has its own switch. A note you move to the trash is deleted from our server 30 days later, and one you delete for good is deleted right away (a marker that it was deleted is kept for 30 days so your other browsers delete it too). "Delete synced data" on your account page deletes every synced note from our server at once and turns sync off; the notes in your browsers stay. Turning sync off in a browser stops it sending changes.
• Reminders. The reminders you set (their text and notes, time, time zone, repeat, list, and the address and title of a page, only when you attach one) are stored with your account, with a short history of when each rang, was snoozed or done, so they ring in every browser you sign in to and you can manage them on our website. Each browser keeps a copy of your upcoming ones so it can show the notification on time. If you have a paid subscription and turn on email for a reminder, we send it to your account's email address through Resend, our email provider; you can turn reminder emails off at any time from the link in every email. Deleting a reminder deletes it from our server.
• Email tracker. When you send an email from Gmail with tracking on, the extension adds a tiny invisible image and, if you track link clicks, points its links at our link host (link.appzlr.com), which forwards the reader to the real address. We store that email's subject, its recipients' names and addresses, the address it was sent from, the tracked links' addresses, Gmail's ID for the conversation and when it was sent, never the message itself. When the image loads or a link is clicked we store the time, which mail app asked (such as Gmail or Outlook), and only when the reader's own device asked directly, its device type, operating system and approximate city and country. We don't store IP addresses: we keep a scrambled (keyed hash) form of the sending browser's address for the first minutes after sending, to tell your own views apart from your readers', and delete it within about a quarter of an hour. A hit that arrives before its email is registered is kept for at most a day with only the details above and the same scrambled form of its address. When Gmail shows you your own tracked email, the extension tells us so that view isn't counted. To spot replies it looks at the senders of messages in threads you open and at Gmail's unread feed in your browser; only the fact that a reply came is sent. Opens and clicks are kept for a year; deleting a tracked email, or "Delete all tracking data" on the Email tracker page, deletes it all. Emails only to yourself, and any email with an address from your never-track list among its recipients, are never tracked, and each compose window can turn tracking off.
• AI writer. Nothing is sent until you ask the writer for something: pressing Write after typing its trigger (// by default) in a text box, picking a rewrite for text you selected, pressing Draft reply in Gmail or Outlook, choosing it from the right-click menu, or writing in the side panel or on the AI writer page. Then we receive what you asked (your instruction, the tone, length and language you picked, and the saved prompt or writing voice you chose), the text it works on (the text you selected, up to about 3,800 characters of the text already in the text box, or for Draft reply the email thread shown on the page), the answer it gave before when you press Try again, and the page's title and address. We send all of that to Anthropic, which runs the Claude model that writes the answer, as our service provider, except the page's address: Anthropic gets only the site's name. Under its commercial terms Anthropic doesn't use it to train its models and deletes it within 30 days, unless it's flagged for breaking Anthropic's usage policy or the law requires keeping it. The answer comes back to you and only goes into the page when you press Insert or Replace. Password, card number and one-time-code boxes, code editors and the sites you tell it to leave alone are left alone, from the right-click menu and the shortcut too. With history on (the default), each result is kept with your account (the request with its tone, length and language, up to 4,000 characters of the text it worked on, the answer, the site's name and the page title) so you can find and reuse it; you can delete any or all of it on the AI writer page, and turn history off there or in the extension. With history off, the extension keeps your last 20 results in that browser only. Drafts you write on the AI writer page, saved prompts and writing voices are stored with your account until you delete them. We count how many AI requests you make each day, for the plan's daily limit. We never log what you send outside your own history.
• AI fields in templates. A template can have a part the AI writer fills in (written {{ai: …}}). Only when you press Write next to it, or Insert with it still empty, we receive its instruction, the template as you filled it in so far (with the values of its other fields), the page's title and address, and, if you tick "Let AI fields read the text selected on the page" in the side panel, the text selected on the page. We send that to Anthropic to write the part, on the same terms as the AI writer above (the page's address goes as the site's name only). The answer is shown to you first, you can change it, and it's not kept: AI fields have no history. Each one counts as one of the AI writer's daily requests.
• Time tracker. The time you track (each entry's description, start and end, project, task, tags, whether it's billable, and the address of the page you started it from, only when you start it from a page) and your projects, clients, tags, rates, targets, favorites and time settings are stored with your account in our database, so every browser you sign in to and our website show the same timer, timesheets and reports. Each browser keeps a copy of the last two weeks so the side panel opens at once and works offline. Idle detection uses Chrome's idle state on your device (active, idle or locked) only to ask whether to keep time you were away; it isn't sent to us. If you turn on the Start timer buttons for work apps (Jira, Trello, GitHub, GitLab, Asana or Linear; all off until you do), the extension reads the open issue's key and title on those sites only, and sends them with the page's address only when you press the button, as that entry's description and link. Invoices you make on the Time tracker page (Pro) are stored with your account: the details you type in for yourself and your client, the lines, tax, discount and notes, their status, and which entries they bill. Deleting an entry, a project, an invoice or "Delete all time data" on the Time tracker page deletes it from our server.
• Focus mode. Your focus settings (the sites on your block and allowed lists and in your block sets, their schedules and allowances, the pause screen's message and lengths, the friction setting, and when a focus or strict session ends) are stored with your account, so you can edit them on our website and every browser you sign in to blocks the same sites. To pause a site, the extension checks each address you open against your lists on your device; it doesn't send us the pages you visit. What you type or pick on the pause screen (an intention, a feeling) stays in that browser. For the sites focus mode stops, and only those, it counts per day how often the pause showed, how often you turned back or went in, and the minutes you chose, and sends those counts to your account for the stats on our website. We don't receive the pages, titles or times of those visits. You can clear the stats on the focus page at any time, and we delete them after a year.
• Shared recordings. Only when you choose "Share link" in the screen recorder (a paid subscription feature), the recording is uploaded to your Pagewing cloud while you record, with a still frame from it as its preview picture, its title, length, size and picture size, and when it was made. Anyone with its link can watch it on our website unless you set a password (we keep only a one-way hash of it) or an expiry date, and can download it unless you turn downloads off. If you trim or cut it on the Recordings page, an edited copy is made in your browser and stored with it, and the link plays only that copy; removing the edits deletes the copy. Deleting a recording on the Recordings page or in the recorder deletes the video, its details, its transcript and everything viewers left on it from our storage. The recording's sound is transcribed on our servers by Cloudflare Workers AI (Cloudflare hosts Pagewing, and doesn't use what it transcribes to train AI models), and the transcript is kept with the recording as its captions. A new recording is named after the tab it shows: while it records, the recorder notes which tab is in front (in your browser only) and, when it stops, uses that tab's title as the recording's title (you can turn this off in the recorder). Once the transcript is ready, unless you turn AI titles off on the Recordings page, the start of the transcript (about the first 4,000 characters), its language, the recording's length and that tab title are sent to Anthropic, which runs the Claude model, to suggest a better title; under its commercial terms Anthropic doesn't train on it and deletes it within 30 days. A title you typed is never replaced, unless you ask for a suggestion yourself. On Pagewing Pro, unless you turn AI summaries off on the Recordings page, the parts of the transcript you didn't cut (up to about 100,000 characters, with their times), its language, and the recording's title and length are also sent to Anthropic, on the same terms, to write a summary, chapters and action items, which are kept with the recording until you edit, remove or delete it. Viewers of the link see the summary and chapters unless you hide them. Also on Pro, the logo, name, links and button you add to your share pages are stored in your account and shown to everyone who watches your shared recordings; the logo is a public image, and removing it deletes it.
• Watching a shared recording. When you play a recording someone shared with you, we count the play and how much of the video you watched, so its owner sees views and how far people got. If you're signed in to Pagewing, the owner also sees your name (or "Pagewing user" if your account has no name; never your email), your photo, and when and how much you watched; if you aren't, a random ID kept in your browser lets us count you once, and the owner only sees a number. Comments and emoji reactions you leave are shown to everyone who can watch the recording, with your account's name and photo, or the name you typed as a guest; you can edit or delete your comments, and the owner can delete them too. When you comment or react as a guest, we keep a scrambled (keyed hash) form of your IP address with it for at most two hours, to limit how much one address can post; nobody sees it. Reports you send go to the Pagewing team, with your account ID if you're signed in and the email you type, if any, and are kept for two years.
• PDF cloud storage. Only when you save a PDF to your Pagewing cloud (a paid subscription feature), we store the file, its name, size, page count and when it was saved or changed, so you can open it on any browser you sign in to. Deleting it in the PDF app deletes it from our storage.
• Screenshots. With a paid subscription, when you capture a screenshot with "Edit in Pagewing" on (the default), press Edit on one in the side panel, or save one to the cloud on the website, we store the image, the page's title and address, the kind of capture, its size, a small preview, your edits (shapes, text, crop and background) and the finished image, so you can edit, find and download it on the website from any browser you sign in to. Screenshots can show whatever was on your screen, so blur or crop anything private, or switch the extension to "Save to Downloads" to keep captures on your computer only. Deleting a screenshot on the website deletes it from our storage.
• Shared screenshots. Only when you make a share link for a screenshot (a paid subscription feature), anyone who has the link can see the finished image, its name (or the page's title when you haven't named it), your name and photo as they are on your account (never your email) and when you took it, on a Pagewing page, until the link expires or you turn it off. The captured page's address isn't shown. You choose how long the link works, and can add a password (we keep only a scrambled form of it) or turn downloads off. We count the link's views and keep when it was last viewed, with no details about who viewed it. Chat apps that preview links fetch the image too. People can report a shared screenshot to us; a report's message, the reporter's account ID if they're signed in and an email only if they typed one reach our team only, and are kept for two years.
• Sending screenshots to Slack and Jira. Only when you connect Slack or Jira on the Pagewing website (a paid subscription feature) and send screenshots there. Connecting signs you in to Slack or Atlassian, which gives Pagewing access to your account there; we keep that access (encrypted), your Slack workspace's name or your Jira sites' names and addresses, and when you connected. When you send, the screenshots, your message or the issue's summary and description, and the page's title and address go through our server to Slack or Jira and are posted there as you; we don't keep a copy. We read your Slack channel names and your Jira projects, issue types and matching issues only to fill in the send dialog. What you send is then kept by Slack or Atlassian under their own terms. Disconnecting on the website deletes the access we kept (and asks Slack to revoke it).
• Messages to us. When you send a message from the side panel's Feedback & support tab or our contact page, we store the topic, subject, what you wrote, the tool it's about, the address we should reply to, your plan at the time and when you sent it, with your account, and from the extension its version and an ID for the browser it was sent from, so we can read it and answer you by email. You can choose to include the page you're on and your browser and system (such as "Chrome 141 · Windows"); both are off until you tick them, and otherwise we don't receive them. Messages are deleted two years after you send them.
• Why you removed Pagewing. When you remove the extension, Chrome opens a page on our website that asks why, in one optional question. Its address carries the extension's version and the day it was installed, nothing else. If you answer, we store the reasons you picked, the tool it's about, what you wrote, the email address you give (only if you want a reply), the version, the install day and the country our hosting provider reports for the request. It isn't linked to your account, and we don't store your IP address.
• Feature requests. When you send a request from the side panel's Feedback & support tab, we store what you wrote, the kind of request, the tool it's about, the extension's version, an ID for the browser it was sent from and when you sent it, with your account, so we can read it, plan what to build and show you its status. For a bug report you can choose to include the address of the page you're on; otherwise we don't receive it. If you aren't signed in, the tab opens an email to us instead.
• Tool usage, only if you turn it on. Counting is off until you turn on "Count which tools I use" in the extension's Settings → Privacy, separately in each browser. Then, while you're signed in, Pagewing tells our server when you use a tool: start autoscroll, take a screenshot, draw on a page, start a recording, save a PDF result, add or export bookmarks or run a link check, save or restore a tab session, start a note, insert a template, start the stopwatch or timer, see focus mode's pause screen, change a video speed setting, save a page or highlight to Read later, create a short link, set a reminder, track time, track an email, ask the AI writer for something, restore text you typed, or clean browsing data. We keep one number per tool per day (UTC) for your account, for example "Screenshots: 4 on 2026-10-18". We don't receive the page, URL, file, note or anything else the tool was used on, or the time of day. You can see this month's counts on your Pagewing home page. We use them to show you your usage and to understand which tools people rely on, so we know what to improve.
• Announcements. When the side panel shows one of our announcements (news or an offer), it tells us that the announcement was shown, clicked or closed, once you've agreed to the extension's list. It's sent without your sign-in, and we only keep a total for each announcement.
• Signed-in hint. When you sign in on our website, it sets a first-party cookie (tbx_in=1) so its pages can show "Open Pagewing" instead of "Account" in the header. It holds no account details, our server doesn't read it, and signing out removes it. Otherwise it expires 30 days after your last signed-in visit.
• Website analytics. Our website's public pages (not the extension, and not the pages where you sign in, connect the extension, pay or use your tools) use Google Analytics for Firebase to understand how people find and use it: pages viewed, the site that referred you, your approximate location (country or city, from your IP address), browser and device type, and visit times. Google Analytics sets cookies in your browser to tell visits apart and processes this data underGoogle's privacy policy. We only see aggregated reports. We don't send it your account details, and we don't use it for advertising.
• Advertising measurement. When we run ads, our website's public pages (not the extension, and not the pages where you sign in, connect the extension, pay or use your tools) load the Google Ads tag and the Meta Pixel. They set cookies and tell Google and Meta which of those pages you visit, so they can measure our ads and may show our ads again to people who visited. The Meta Pixel also tells Meta when someone creates an account on our website, so our ads can reach people who signed up but haven't subscribed; on the pages without the tags this is one request that carries only our site's name and an event ID made from a hash of the account ID, and no Meta script runs there. If you arrive from one of our ads, the link carries a click identifier (such as gclid or fbclid) and campaign tags (such as utm_campaign). The website keeps these in a first-party cookie for 90 days. If you then sign in or create an account on our website (which is also how the extension signs in), we save them with your account, together with your browser's user agent and IP address at that sign-in, the address of the page you signed in on (without anything after a "?") and, if the Meta Pixel ran, Meta's own browser cookies (_fbp and _fbc). When that account is created, when it first subscribes and when it first moves up to a higher plan, our server reports the event to the platform the ad came from (Google through its Data Manager API, Meta through its Conversions API): the click identifier, the event and its time, the amount paid for a subscription or added by the new plan, your browser's user agent and IP address, and a one-way SHA-256 hash of your email address and of your account ID, which the platform uses to match the event to the ad click; the event's ID is made from that hash too. Meta also gets the sign-in page's address and its two cookies. Our server doesn't report accounts that didn't come from one of our ads. Google and Meta process this under their own privacy policies (Google,Meta).
• Where you came from. Every page of our website notes the first visit in your browser that came from another site or carried campaign tags (utm_source, utm_medium,utm_campaign, utm_term, utm_content): the referring site's name only (such aschatgpt.com or google.com, never the address of the page that linked here), those tags, the page you landed on and when. A first visit with neither is noted as a direct visit, which a later visit from another site or with tags replaces. The welcome page that opens after you install the extension also asks, optionally, where you heard about Pagewing; your answer is noted the same way. All of this stays in your browser's local storage. When you sign in on our website (which is also how the extension signs in), the sign-in that creates your account saves it with the account, and an answer you give later is added once; after that it doesn't change. Sign-in, payment and our own pages are never counted as where you came from. We use it only to see which sites, searches, AI assistants and campaigns bring people to Pagewing and which of those accounts go on to subscribe, as counts on our admin page. It isn't sent to Google, Meta or anyone else, and it's kept for every visitor alike, since it never leaves our own service. Clearing this site's data in your browser removes what's noted there.
• Server logs. Like any website, our hosting provider briefly keeps standard request logs for security and reliability: each request's address (which includes words you type into a search box on our website), its time and your IP address. Our own log lines can carry your account ID when something goes wrong, never what you wrote. We use them only to fix problems and stop abuse.

How we use it

We use this data only to provide Pagewing's features: running your account and plan, checking your subscription, serving short links, showing you your tool usage and deciding which tools to improve, understanding how the website is used, and replying when you contact us. Pagewing's use of information complies with theChrome Web Store User Data Policy, including the Limited Use requirements. We don't sell or transfer user data to third parties, except to Google Firebase to sign you in and measure website visits, to Google and Meta to measure our own ads (see "Advertising measurement" above), to Paddle to sell and manage subscriptions and show prices in your currency, to Cloudflare, which hosts the service, your PDF cloud storage, your screenshots and your shared recordings, to Resend, which delivers the reminder emails you ask for (your email address and that reminder), to Google Web Risk, which checks the addresses you shorten against its list of unsafe sites (the address only), to Slack or Atlassian when you send screenshots there (what you send; see "Sending screenshots to Slack and Jira" above), to Anthropic, which runs the AI model behind the AI writer, Read later's summaries and answers, and the titles of shared recordings (only the request and text you send the writer, the articles you ask Read later about with your questions, and the start of a shared recording's transcript; see "AI writer", "Read later" and "Shared recordings" above), to MongoDB, whose Atlas service stores our database (everything this policy says we keep with your account or on our server, apart from files, which Cloudflare stores), and to jsDelivr, which serves the video converter's code to your browser when you convert or edit a video on our website (like any website it sees your IP address). We don't use it for advertising, other than measuring our own ads as described above, which never includes data the extension handles, and we don't use it for creditworthiness or lending, and we don't let people read it except where needed for security, to comply with the law, or with your permission (for example, a support request or a feature request you send us).

How long we keep it

• Short links and their click stats stay until you delete them in the Shorten tab or on the Short links page, which removes them from our server.
• Articles and highlights in Read later stay until you delete them, on any plan, and so do their AI summaries and questions. Anthropic deletes what Read later sends it within 30 days.
• Time entries, projects, clients, tags and invoices stay until you delete them, on any plan.
• AI writer history stays until you delete it (the newest 2,000 results; past that the oldest unstarred ones are deleted), and nothing new is kept while history is off. Drafts, saved prompts and voices stay until you delete them. Anthropic deletes what the writer sends it within 30 days, longer only if it's flagged for breaking its usage policy or the law requires.
• Reminders stay until you delete them (done ones too, until you clear them). Resend keeps a record of each email it sent for its own limited retention period.
• PDFs in your cloud storage, screenshots and shared recordings in your account stay until you delete them, while a paid subscription covers them. If it ends, they're deleted 30 days later; until then you can still download or delete them, and the PDF app, Screenshots and Recordings pages show the date. While a subscription is paused they're kept, but you can't add new ones. A recording whose upload never finished (the browser closed mid-recording) is deleted after a day.
• Screenshots and PDFs kept in your browser stay there until you delete them or clear the site's data; we never receive them.
• Synced notes stay until you delete them. Notes in the trash are deleted 30 days after you trash them, and "Delete synced data" on your account page deletes them all at once.
• A connected browser's record is deleted when you disconnect it or sign Pagewing out, or after 90 days without use, when that browser is signed out.
• Answers to the "why did you remove it" question are deleted two years after you send them.
• Tool usage counts are kept with your account and deleted along with it.
• Google Analytics keeps website visit data for the retention period set in our Analytics settings (14 months at most).
• Where your first visit came from, and where you said you heard about Pagewing, are kept with your account and deleted along with it.
• The ad click cookie expires 90 days after you land. An ad click saved with your account is kept with the account and deleted along with it; what Google and Meta keep is set by their policies.
• Your account is kept until you ask us to delete it. Deleting it deletes everything this policy says we keep with it, including your cloud files, comments you left on shared recordings and Firebase's sign-in record. Subscription records are kept as long as tax and accounting law requires, and Paddle keeps its own under its policy.

Your choices and rights

You can turn tool counting and video speed's time-saved stats on or off at any time in the extension's Settings → Privacy. You can delete short links, your cloud PDFs, your screenshots and your synced notes ("Delete synced data" on your account page) at any time. To see, correct or delete the other data we hold about you, emailtool@appzlr.com. from the email address you sign in with, so we can find your account. Uninstalling Pagewing removes the settings it kept in this browser. To keep your visits out of Google Analytics, block cookies for this site or use Google'sopt-out add-on. If your browser sends a Global Privacy Controlsignal, our website doesn't load the ad tags or save the ad click cookie, so nothing about you is reported to Google or Meta. Blocking cookies for this site also stops the ad click from being saved with your account. You can also manage ads inGoogle's My Ad Center and Meta's ad preferences.

Children

Pagewing isn't directed at children under 13, and we don't knowingly collect their data.

Changes

If we change this policy, we'll update the date at the top of this page. If a change is significant, we'll also mention it in the extension's release notes. If we change what the extension sends to your account, the extension shows you the new list and sends nothing more from that browser until you agree to it.