What the service handles, and for how long.
See what Prerender Buddy fetches, stores, caches, minimizes, and retains across rendering, AI Visibility, content, Agent, and AI Ads workflows.
On this page
Overview
Technical data overview
Prerender Buddy processes public-page and workspace data to provide website Health, crawler activity, controlled AI Visibility monitoring, generated content drafts, Agent assistance, and eligible AI Ads workflows. This page explains the current implementation, including minimized logs, in-memory cache behavior, product records, provider involvement, and known policy gaps.
This overview complements the Privacy Policy. It is not a data processing agreement.
Implementation reviewed: August 2, 2026.
Public page content
The renderer fetches the configured public URL, loads public page resources, and captures the resulting HTML.
Minimized render logs
Durable render logs omit query strings and fragments and keep operational fields for a limited period.
AI Visibility evidence
When configured, Prerender Buddy stores controlled prompts and provider responses, including answer text, source and citation relationships, run context, tracked brand aliases, and tracked or detected competitors. These observations come from configured provider API runs; they are not private consumer conversations.
Content, Agent, creative, and Ads records
Content workflows can store generated article drafts and the workspace evidence used to prepare them. Agent and support workflows process conversations and relevant account or site context to answer the request.
AI Ads workflows can store uploaded or generated creative assets, copy and creative variations, proof results, provider account identifiers, encrypted provider credentials, connection state, and imported performance records such as impressions, clicks, spend, currency, and reporting dates. A saved or exported creative is not proof that an ad is live.
Storage and retention
Current application defaults.
Automated cleanup runs on a schedule. Account, site, and workspace records also follow explicit deletion flows. No retention period is stated here for AI Visibility evidence, generated article drafts, Agent conversations, creative assets, Ads connections or credentials, or imported performance records because those defaults have not been fully verified.
Scheduled cleanup Documented defaults
Record What is retained Default retention
Record
Site and workspace configuration
What is retained
Domain, origin URL, setup mode, status, and cache settings
Default retention
Until the site, workspace, or account is deleted
Record
Render logs
What is retained
Page origin and path without query or fragment, bounded user agent, cache result, duration, status, and timestamp
Default retention
30 days by default
Record
Rendered HTML cache
What is retained
Rendered public page HTML, final URL, status, and timestamp in process memory
Default retention
Normal-read TTL up to 7 days; expired entries leave through reads, eviction, clearing, or restart
Record
Usage records
What is retained
Fresh-render quantities and quota notification delivery records
Default retention
400 days by default
Record
Free-tool analytics
What is retained
Tool, hostname, outcome fields, source, and allowlisted metadata
Default retention
90 days by default
Record
User-created public reports
What is retained
Public URL without credentials, query, or fragment; dated technical metrics and issue summaries; no raw HTML or page excerpts
Default retention
90 days by default, or earlier when deleted by the creator
Record
Product funnel analytics
What is retained
Consent-based page paths and pseudonymous account milestones; no tested URLs, site domains, or email addresses
Default retention
Managed in PostHog according to the configured project retention settings
Record
Interaction analytics
What is retained
Consent-based page, browser, device, click, scroll, pointer-movement, heatmap, and privacy-masked reconstructed interaction data
Default retention
Clarity recordings are normally retained for 30 days; selected or favorited recordings may remain for up to 9 months
Record
Support conversations
What is retained
Messages, relevant account diagnostics, model, and token usage
Default retention
90 days by default
Record
Email preferences
What is retained
Marketing opt-in, consent source and time, policy version, unsubscribe time, and provider synchronization state
Default retention
Until account deletion; the opt-out record remains to enforce the preference
Record
Administrative audit records
What is retained
Administrative action and target identifiers
Default retention
365 days by default
Default periods describe Prerender Buddy application records. Provider-side backups and legal retention may follow separate terms.
Important cache detail
Logs and cache treat URLs differently.
Durable render logs remove query strings and fragments before storage. The process-local HTML cache currently uses the exact requested URL as its key, so query parameters can produce separate cached entries.
Do not place credentials, session identifiers, personal data, signed private resources, or sensitive state in URLs sent through crawler rendering. Keep personalized and authenticated pages outside the render path.
The cache is not durable or shared across renderer instances. Entries can disappear through expiry, capacity eviction, explicit clearing, or process restart.
Service providers
Systems visible in the implementation.
This functional inventory links to current provider documentation. A provider may act as a processor, subprocessor, or independent controller depending on the service and data involved.
Clerk
Identity and authenticated sessions
Railway
API, rendering service, PostgreSQL, and application records
Cloudflare
Managed custom hostnames, DNS and HTTPS validation, and edge forwarding
Netlify
Public website, functions, and maintained edge integration
Stripe
Hosted checkout, subscription billing, invoices, and payment administration
Resend
Transactional email, support escalation, and consented marketing email delivery
Hostinger
Support and business email mailbox hosting
OpenAI
AI Visibility, Agent, support-assistant, and applicable content or creative generation processing when those features are used
PostHog Cloud US
Consent-based web analytics and pseudonymous product-funnel milestones
Microsoft Clarity
Consent-based heatmaps and privacy-masked interaction recordings
Better Stack
Public endpoint availability checks and incident response
Better Stack monitors public Prerender Buddy endpoints only. Its incident tooling stores monitor responses and may capture a screenshot when a failed response has a non-empty body. Authenticated customer pages and private account URLs should not be added to those monitors.
What is not confirmed here
Account-specific regions, provider retention settings, and contract acceptance.
PostHog and Microsoft Clarity may process analytics data in the United States. Other actual deployment regions and account-level retention settings require provider-dashboard confirmation and are not inferred from source code.
Customer controls
Delete sites, revoke API keys, or use the account deletion flow.
Some provider-side records, including billing and delivered email, may follow the provider's own legal or operational retention rules.
Related technical boundaries