Privacy Policy

Who we are

Publisher / controller: AgentRender (product site: agentrenderapi.com).

Contact: hello@agentrenderapi.com (subject prefix [AgentRender Support]).

Data we collect

• Waitlist fields you submit (email, intended use, plan interest, expected renders, notes, MCP preference).
• Account email for demo or paid access, including the email used at Stripe checkout.
• API keys we issue — we store key identifiers and status; secret key material is stored hashed or otherwise protected for authentication. Full keys are shown to you at issuance and are not re-displayed in plaintext afterward when feasible.
• Render request metadata: URL submitted, timestamps, endpoint, HTTP/status outcome, approximate size, plan/quota counters, and related operational fields.
• Render receipts: receipt identifiers, content hashes, viewport/format parameters, and timestamps returned for agent audit trails and retained as needed for security and billing.
• MCP tool call metadata when using remote MCP (tool name, timing, auth result, and similar operational data).
• Support emails and related correspondence.
• Payment confirmation data from Stripe (Stripe processes card details; we receive confirmation and billing email, not full card numbers).

MCP tool inputs and outputs

Remote MCP at https://api.agentrenderapi.com/mcp uses the same API key authentication as REST (Authorization: Bearer).

• Inputs may include public URLs you ask to render and tool parameters you supply.
• Outputs returned to the client fall into these categories:
  • screenshot — image bytes or image payloads (e.g. PNG/JPEG/WebP) plus receipt/metadata;
  • pdf — PDF bytes or PDF payloads plus receipt/metadata;
  • extract — structured JSON such as title, meta, main text, and links.
• We do not intentionally retain full page HTML or full render binaries longer than needed to fulfill the request and operate the service securely.

What we do not sell

We do not sell personal data. We do not sell waitlist emails, account emails, API usage profiles, or render metadata to third parties for their marketing.

How we use data

• Fulfill renders and return outputs to you or your MCP/REST client.
• Issue, authenticate, rotate, and revoke API keys.
• Billing and subscription management via Stripe.
• Customer support and operational communications.
• Abuse prevention, security monitoring, SSRF protections, and quota enforcement.
• Improve reliability and product quality (including aggregated metrics).

Retention

• API keys: while the account is active; revoked or deleted when access ends or upon feasible deletion requests.
• Usage logs, receipts, and render metadata: retained as needed for security, billing, and abuse prevention, then deleted or aggregated.
• Waitlist data: until you ask us to remove it, or until no longer needed for access provisioning.
• Support correspondence: as reasonably needed to resolve issues and maintain records.

Subprocessors

• Stripe — payments and subscriptions.
• Fly.io — API hosting and render compute.
• Cloudflare — Pages hosting, DNS, and CDN for the marketing site.
• Formspree — waitlist form delivery when the waitlist form is used.
• Resend (and/or Google/Gmail as applicable) — transactional and support email.

Security

• TLS for site and API traffic.
• Treat API keys as secrets — do not paste them into public chats or repositories.
• Public-URL orientation with network protections that may block private/internal targets (SSRF defenses).

Your rights

Contact hello@agentrenderapi.com to request access to or deletion of waitlist or account email data where feasible. We may need to verify your request.

Children

AgentRender is not directed to children under 13. We do not knowingly collect personal information from children under 13.

Changes

We may update this page from time to time. The “Last updated” date will change when we do. Continued use of AgentRender after an update constitutes acceptance of the revised policy.