1. Information We Collect
We collect information that you provide directly to us, including:
- Account information (email address, name) via Clerk authentication
- API endpoint configurations, canvas data, and transformation settings
- Usage analytics and API call metrics
- Payment information (processed securely through Stripe)
2. How We Use Your Information
We use the information we collect to:
- Provide, maintain, and improve our visual API builder
- Process subscription payments and manage your account
- Enable real-time collaboration features
- Process AI assistant requests to help build your APIs
- Send technical notices and support messages
- Monitor usage to enforce plan limits
3. Third-Party API Response Retention
When a published endpoint successfully calls its upstream APIs, API Funnel retains the most recent successful response so it can be served as a stale fallback if all of that endpoint's upstream APIs become unavailable at request time. Specifically:
- One response is stored per published endpoint, and it is overwritten on every new successful call. This is not a rolling log or history, there is no accumulation of past responses.
- The stored response is only ever served as a fallback if it was fetched within the last 10 minutes. Older stored responses are simply unused until the next successful call overwrites them.
- There is no separate expiry or scheduled purge for this stored response. It is deleted when the account that owns it is deleted; it is not automatically deleted when you remove or unpublish an individual canvas or endpoint.
- Each published endpoint has its own setting to disable this fallback cache (on by default). Turning it off stops future storage and immediately deletes any response already stored for that endpoint. If your upstream API's license or your own compliance requirements prohibit retaining its response data, turn this off for that endpoint before publishing it, or contact us to discuss your requirements.
This is separate from the optional, per-input-node response caching feature (a performance cache with a configurable expiry that you opt into per node). The retention described here is on by default for published endpoints, and configurable per endpoint as described above.
4. Data Security
We implement appropriate technical and organizational measures to protect your personal information. All data is transmitted over HTTPS, and your canvas data is isolated per user account.
5. Your Rights
Regardless of where you are located, you have the right to:
- Access: request a copy of the personal information we hold about you
- Portability: export your canvas and endpoint configurations at any time via OpenAPI export
- Erasure: request deletion of your account and the data associated with it
- Manage your subscription at any time
To exercise any of these rights, contact us via the Support page.
6. Contact Us
If you have questions about this Privacy Policy, please contact us via the Support page.
