Privacy Notice

How Panther Hook fits into the data flow

Panther Hook handles account and service data needed to operate, secure, support, and bill for the service. When a customer sends lead or submission data into Panther Hook, the customer generally decides why the data is collected and how it will be used, while Panther Hook processes it to provide the configured service.

Customers are responsible for the notices, permissions, lawful basis, and other obligations that apply to the lead data they collect and send through Panther Hook.

Data the service processes

Depending on how the service is used, Panther Hook may process account email and authentication identifiers; workspace and team membership; customer configuration; form definitions; submissions and lead fields; attribution data such as UTM values and click IDs; integration configuration; billing references; hashed IP identifiers, user-agent, timestamp, abuse-prevention and security metadata; coarse country code supplied by the Cloudflare edge; derived browser family, operating-system family and device category; and service logs.

Secure production file intake uses bounded upload grants and private object storage. When a customer enables and uses file uploads, Panther Hook processes uploaded file content and related metadata as part of that customer's submission workflow.

Lead context and location

Lead context uses coarse request metadata. Panther Hook does not persist a visitor's raw IP address for this feature and does not derive or store precise latitude, longitude, city, postal code, or GPS location. The browser is not asked for geolocation permission. Country is a best-effort two-letter code supplied by the trusted Cloudflare edge, while browser, operating system, and device category are derived from the received user-agent.

How data is used

Data is used to authenticate users, provide workspace and lead-management features, persist and route submissions, operate webhooks and customer-configured integrations, prevent abuse, troubleshoot failures, support billing, secure the service, and maintain bounded operational history.

When a customer configures form consent evidence, a submission may also retain the consent status or choice, configured consent text and version, capture timestamp, and related source-page or privacy-policy references.

Authentication

If you sign in with Google or GitHub, Panther Hook uses the provider identifier and verified email information needed to authenticate or link your account. OAuth access tokens used only to complete sign-in are not retained after the identity lookup is complete.

Service providers and customer-directed destinations

Panther Hook uses infrastructure, database, authentication, email-delivery, and billing providers to operate the service. The current provider list is published on the Subprocessors page.

Customer-directed integrations such as Zapier, Make, Google Sheets, Slack, Telegram, and Discord receive submission data only when a customer configures and uses the relevant destination. Those destinations may have their own privacy terms.

Retention and deletion

Automatic submission-retention cleanup is active. Each workspace uses its configured retention period within the plan maximum. Expired primary submission records are deleted automatically, and attached file objects are removed through the bounded private-R2 cleanup lifecycle.

Self-service workspace and account deletion are available in the product. The deletion flow removes the relevant primary application records and stored file objects covered by that flow. Deleting an individual workspace does not cancel the account subscription; deleting the Panther Hook account cancels its active paid subscription first. Provider backups, recovery history, security records, and service logs may follow separate bounded lifecycles, so deletion is not represented as instantaneous removal from every provider system or backup.

Privacy and data-subject rights

Depending on the law that applies to you and the circumstances, you may have rights such as access, correction, deletion, restriction, portability, objection, or withdrawal of consent where consent is the applicable basis. These rights are not identical in every jurisdiction and may be subject to legal exceptions.

For account or service-data requests, contact support@pantherhook.com. If your request concerns lead or submission data collected by a Panther Hook customer, you may need to contact that customer as the organization controlling the collection and business use of the data.

Cookies and browser storage

Panther Hook currently uses essential authentication and security cookies plus local browser storage for product preferences and workspace state. The current frontend does not include optional advertising or analytics trackers. See the Cookie & browser storage notice for details.

Security

Panther Hook applies technical and operational safeguards described on the Security page. No security measure eliminates every risk, and Panther Hook does not claim certifications or service levels it has not obtained or published.

Contact

General privacy requests and questions can be sent to support@pantherhook.com.