Page memory
Web Recall user-triggered page fetcher
Last updated: September 2, 2026
Web Recall can revisit a limited set of public pages from browser history only after the person using the Mac selects a Chrome or Edge profile and explicitly confirms that one run.
Not an automatic web crawler
A historical page-memory run does not start when Web Recall, a browser, or an extension starts. Each confirmed run is limited to eligible public HTTPS pages from the selected browser history. Safari History and Firefox are not included in this feature.
Web Recall skips HTTP pages, private or local addresses, sensitive URLs, login-required or blocked pages, sites excluded by the user, and destinations that fail its safety checks.
Identity and robots.txt
The fetcher uses the WebRecall product token. Its user agent includes the app version and this public information URL. Before rendering a page, Web Recall checks /robots.txt, preferring rules for WebRecall and otherwise using applicable * rules.
A publisher can block this fetcher with:
User-agent: WebRecall
Disallow: /
Or permit only a selected area:
User-agent: WebRecall
Disallow: /
Allow: /public/
Requests come from the consenting person's Mac and ordinary internet connection. Web Recall does not operate a fixed crawler IP range or claim reverse-DNS verification. Robots rules express publisher preferences; they are not an access-control or authorization mechanism.
Privacy and page handling
Web Recall does not import browser cookies, login sessions, saved credentials, or website authentication. Each page uses a fresh, nonpersistent browsing context. Authentication challenges, popups, media permissions, and unapproved destinations fail closed.
Only cleaned page text and the minimum source facts needed for local search and run recovery are saved on the person's Mac. Page bodies are not uploaded to Web Recall servers or an AI provider merely to build page memory. Normal run progress and reports use aggregate counts and timing rather than page bodies, URLs, titles, or browser profile paths.
Bounded request policy
- At most 100 pages in one explicitly confirmed run.
- At most two page renderers in total and one active page per origin.
- At least 750 milliseconds between starts for the same origin.
- At most five validated HTTPS redirects.
- An eight-second page deadline and no automatic retry.
The user can pause or cancel a run, exclude sites, delete captured page content, and separately delete private run records in Web Recall Settings.
Publisher and support contact
For a publisher request or product question, email [email protected].