Effective August 23, 2026

Webhook Reliability API data handling

A concise description of what the API receives, processes, retains, and does not promise.

Request processing

  • The service processes the JSON body needed to perform the requested operation.
  • The application code does not intentionally write request bodies to a database, file, analytics service, or application log.
  • The service does not call third-party endpoints and does not request passwords, access tokens, private keys, or production credentials.
  • Responses are generated during the request and are not intended as durable storage.

Infrastructure processing

  • Netlify hosts the function and may process request metadata under its own privacy and security terms.
  • When accessed through RapidAPI, RapidAPI proxies the request and may process account, subscription, usage, request, and billing metadata under its own terms.
  • Do not submit secrets, regulated records, personal data, or information you are not authorized to process.

Service boundaries

  • Outputs are deterministic development helpers, not a security audit, compliance certification, legal opinion, or guarantee that an external operation is safe.
  • Consumers remain responsible for the target provider's current retry, rate-limit, privacy, idempotency, and authorization requirements.
  • Availability and response timing are subject to hosting and marketplace infrastructure.

Questions and deletion requests

Because the application does not intentionally persist request bodies, it normally has no stored payload record to delete. For questions about this service, email jblaz6335@gmail.com. Account and billing records held by Netlify or RapidAPI are governed by those providers.