Privacy Policy

RelayFox stores webhook requests sent to URLs you create, including the request method, path, query parameters, provider-supplied headers, body, content type, size, and source IP. Platform credentials and internal infrastructure headers are filtered and are not intentionally stored.

If you create an account, RelayFox stores your account identifier, email address, plan, endpoint settings, team membership, and hashed CLI token records. RelayFox never stores the plaintext value of a CLI token after it is shown to you.

Data is used to receive and display webhooks, stream them to the RelayFox CLI, replay requests when instructed, manage accounts and subscriptions, prevent abuse, provide support, and understand aggregate product usage.

Anonymous and Free endpoints expire after 24 hours. Pro endpoint URLs are permanent while active, and captured request history is retained for up to 30 days. Aggregate product events are retained for up to 180 days. Deleting an endpoint removes its captured request history. Operational backups may take additional time to expire.

RelayFox relies on Vercel for hosting and analytics, Neon for PostgreSQL, Clerk for authentication, Polar for subscription checkout and tax handling, and Resend for transactional email. These providers process only the data required to provide their services under their own terms.

Vercel Web Analytics provides privacy-focused aggregate traffic and product-event measurement. RelayFox does not intentionally put webhook payloads, endpoint IDs, email addresses, or CLI tokens into analytics events. Authentication and checkout providers may use cookies required for their services.

You can delete endpoints from their settings. To request account deletion, data access, correction, or another privacy action, email support@relayfox.dev.

Webhook URLs are secrets. Do not send passwords, payment card data, private keys, medical data, or other regulated data to RelayFox unless you have independently confirmed that your use is lawful and appropriate.