How API Playground handles data.

When you use the contact form, we collect the name, email address, and message you submit. This information is sent to our workflow endpoint and used to respond to your request, troubleshoot issues, and improve support.

When you use the playground, you may enter URLs, headers, API keys, request bodies, files, webhook URLs, and other request details. You control what you enter and which endpoint receives it.

API Playground sends request details through its proxy so your browser can test HTTP endpoints and display the response. This can include the request URL, method, headers, body, uploaded files, and authentication values that you choose to include.

We use this data to perform the request and return the response to you. We do not intentionally sell API request data or use API keys from your requests for our own purposes. Avoid entering secrets unless they are needed for the endpoint you are testing.

The playground stores recent request history and saved presets in your browser localStorage. This helps you replay requests and keep reusable templates without creating an account.

Because this storage is local to your browser, you can clear it by using the clear history controls in the product or by clearing your browser site data for playgroundapi.com.

We use PostHog to collect product analytics, such as page views, CTA clicks, request sent events, failed request events, template usage, export actions, chat opens, and contact form submission status.

Analytics help us understand what parts of the product are useful, find problems, and improve API Playground. PostHog persistence is configured through localStorage.

If you use the chat or agent features, your messages and relevant request context may be sent to an AI provider so the assistant can generate a response. Do not include passwords, private API keys, or sensitive personal information in assistant messages unless you are comfortable sending that information for processing.

The public API Playground experience does not require login cookies. The blog platform may use a secure admin session cookie for authorized administrators. Browser storage may also be used for theme or interface preferences.

We may use service providers for hosting, analytics, contact workflows, AI assistant processing, and operational infrastructure. These providers process information as needed to deliver and improve the service.

When you send an API request to a third-party endpoint, that destination API receives the request data you provide. The destination service's own privacy policy and terms apply to its handling of that data.

Browser-stored history and presets remain in your browser until you delete them or clear site data. Contact messages may be kept as long as needed to respond, maintain business records, and improve support. Analytics data may be retained according to our analytics provider settings.

You can choose not to submit the contact form, not to use the AI assistant, clear localStorage data in your browser, or limit analytics storage through browser settings and privacy tools.

You can contact us to request access, correction, deletion, or information about personal data associated with your email address.

We design API Playground to reduce friction while keeping request handling clear. Still, no online service can guarantee absolute security. Use caution when testing production credentials, private tokens, customer data, or confidential payloads.

API Playground is intended for developers and general technical users. It is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

We may update this privacy policy as the product changes. When we make changes, we will update the last updated date on this page.