--- title: How Prerender.io handles your data and privacy description: Learn what data Prerender receives, stores, and encrypts. Covers visitor data handling, cookie management, and encryption for requests and cached HTML. --- [Skip to content](https://docs.prerender.io/docs/how-prerender-handles-your-data-and-privacy#main-content) ![prerender-logo](https://docs.prerender.io/hs-fs/hubfs/logo.png?width=100&height=75&name=logo.png) Open main navigation Close main navigation - [Contact us](mailto:support@prerender.io) [Contact us](mailto:support@prerender.io) How can we help you? - There are no suggestions because the search field is empty. 1. [Knowledge Base - Prerender.io](https://docs.prerender.io/docs?hsLang=en) 2. [How Prerender.io works](https://docs.prerender.io/docs/how-prerender-io-works?hsLang=en) May 22, 2026 # How Prerender.io handles your data and privacy ## What Prerender.io sees, what it stores, and how your data is protected — from the first crawler request to the cached response. ### TL;DR Prerender.io only receives the URL of the page you want rendered—it never accesses your website visitors' private data, cookies, or authentication headers. Traffic between your servers and Prerender.io is encrypted via TLS, and each page renders in a fresh, isolated browser instance with no data carried over from previous renders. --- ![request-data-flow](https://docs.prerender.io/hubfs/Request%20Flow.svg) --- ### What Prerender.io receives When an AI crawler or search engine bot visits your site, [Prerender's integration](https://docs.prerender.io/docs/how-does-prerender-work?hsLang=en) intercepts the request and identifies whether it comes from a crawler or a website visitor. If it's a crawler, Prerender receives one piece of information: the URL of the page to render. Prerender.io does not receive: - Personal data or visitor identifiers - Cookies or session tokens - Authentication headers - IP addresses of your website visitors Prerender.io can only access content that is already publicly visible on your website — the same content any unauthenticated website visitor would see. It does not bypass authentication or connect to your internal systems. You can verify this in Prerender's open-source [GitHub repositories](https://github.com/prerender). --- ### What Prerender.io stores **User-Agent strings** Prerender.io stores the `User-Agent` string sent with each request. This string identifies the type of crawler that initiated the request — for example, GPTBot or Googlebot — but does not identify any individual person. **Your server's IP address** Prerender.io stores the IP address of the server that requests rendering. This is used for rate limiting and blocking malicious requests — not for tracking or profiling. See [IP addresses](https://docs.prerender.io/docs/22-ip-addresses?hsLang=en) for the full list of Prerender's IP ranges. **Rendered HTML** Prerender.io caches the rendered HTML of each page. This cache contains only content that is already publicly accessible on your website — nothing that a website visitor could not access without Prerender. **Cookie handling** Each page renders in a new, isolated browser instance. Prerender does not carry cookies or any stored data between renders — every render starts from a clean state. --- ### How your data is encrypted **Traffic between your servers and Prerender** All requests between your servers and Prerender's rendering service travel through a TLS-secured channel. TLS (Transport Layer Security) is the same encryption standard used by HTTPS. **Rendering requests to your website** Prerender.io prioritizes HTTPS when fetching your pages for rendering. If your web server does not support HTTPS, Prerender degrades the connection to HTTP to complete the render. > ⚠️ If your site does not serve content over HTTPS, rendering requests will use an unencrypted HTTP connection. This request flow involves only Prerender's rendering servers and your website — no personal data is transmitted. **Cached HTML at rest** Rendered HTML stored in Prerender's cache is not encrypted at rest. However, the cache contains only publicly accessible content — equivalent to what any unauthenticated visitor would see. Prerender's internal systems are isolated from the public internet, and cached data is only reachable through encrypted communication channels. ℹ️ If your security review requires encryption at rest, contact [`support@prerender.io`](mailto:support@prerender.io) to discuss your requirements. --- > 💬 **Still need help?** > If you have questions about Prerender's data handling, security posture, or compliance requirements, our support team can help. > → Contact us at [`support@prerender.io`](mailto:support@prerender.io) --- #### Related articles - [How does Prerender.io work?](https://docs.prerender.io/docs/how-does-prerender.io-work?hsLang=en) - [Certificates](https://docs.prerender.io/docs/certificates?hsLang=en) - [IP addresses](https://docs.prerender.io/docs/22-ip-addresses?hsLang=en) - [Multi-factor authentication](https://docs.prerender.io/docs/multi-factor-authentication?hsLang=en) - [How Prerender.io works](https://docs.prerender.io/docs/how-prerender-io-works?hsLang=en) - [Getting started](https://docs.prerender.io/docs/getting-started?hsLang=en) - [Integrations](https://docs.prerender.io/docs/integrations?hsLang=en#main-content) - [Prerender.io officially maintained integration](https://docs.prerender.io/docs/integrations?hsLang=en#prerender-io-officially-maintained-integration) - [Bubble](https://docs.prerender.io/docs/integrations?hsLang=en#bubble) - [FAQ](https://docs.prerender.io/docs/integrations?hsLang=en#faq) - [Get Found on AI & Search](https://docs.prerender.io/docs/get-found-on-ai-search?hsLang=en#main-content) - [Google Search Performance](https://docs.prerender.io/docs/get-found-on-ai-search?hsLang=en#google-search-performance) - [Troubleshooting](https://docs.prerender.io/docs/troubleshooting?hsLang=en) - [Billing & Account](https://docs.prerender.io/docs/billing-account?hsLang=en#main-content) - [Plans & Subscriptions](https://docs.prerender.io/docs/billing-account?hsLang=en#plans-subscriptions) - [Renders, Usage & Limits](https://docs.prerender.io/docs/billing-account?hsLang=en#renders-usage-limits) - [Payments & Invoices](https://docs.prerender.io/docs/billing-account?hsLang=en#payments-invoices) - [Account Access & Security](https://docs.prerender.io/docs/billing-account?hsLang=en#account-access-security) [![Chill listening crop-3](https://docs.prerender.io/hs-fs/hubfs/logo-1.png?width=24&height=24&name=logo-1.png "Chill listening crop-3")](http://prerender.io) 304 S. Jones Blvd #1205, Las Vegas, NV 89107 [mailto:support@prerender.io](mailto:support@prerender.io) Copyright © 2025, Prerender.io