What the service handles, and for how long.
Prerender Buddy needs public page URLs and page content to render crawler-readable HTML. This page explains the current implementation, including minimized logs, in-memory cache behavior, support data, and known policy gaps.
This overview complements the Privacy Policy. It is not a data processing agreement.
Implementation reviewed: July 13, 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.
Optional support context
When the Setup Assistant is used, messages and relevant account diagnostics are processed to answer the support request.
Storage and retention
Current application defaults.
Automated cleanup runs on a schedule. Account, site, and workspace records also follow explicit deletion flows.
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
Support conversations
What is retained
Messages, relevant account diagnostics, model, and token usage
Default retention
90 days by default
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 is a functional inventory, not a statement of contractual roles or hosting regions.
- Clerk
- Identity and authenticated sessions
- Railway and PostgreSQL
- API, rendering service, and application records
- Cloudflare
- Managed custom hostnames, DNS/HTTPS validation, and edge forwarding
- Netlify
- Public website and maintained edge/functions integrations
- Stripe
- Subscription billing
- Resend and the support mailbox provider
- Transactional email and support escalation
- OpenAI
- Account-aware support-assistant processing when that feature is used
What is not confirmed here
Provider-side retention, backups, contractual roles, and data-residency regions.
Those details require provider-dashboard, contract, and legal review. They 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