SuppyHQ

What SuppyHQ can touch in Stripe and Polar.

SuppyHQ needs to know who paid you. It doesn't need your money. So it asks for the least it can, and this page lists all of it.

Stripe

You connect Stripe with the SuppyHQ app, from its page in the Stripe App Marketplace or the Connect button in SuppyHQ. There's no key to paste. Stripe shows six permissions, all Read, and you accept them on Stripe's screen:

Nothing on the list charges, refunds, or changes anything. There's no webhook to create either: Stripe sends the app's events to SuppyHQ by itself.

Take it back

Uninstall SuppyHQ in Stripe: Settings, then Installed apps. SuppyHQ then can read nothing more. Disconnect in Integrations makes SuppyHQ forget its token, but only Stripe can uninstall the app. Customers it already imported stay.

Polar

You connect Polar with OAuth 2, through Polar's own sign-in. There's no key to paste, and SuppyHQ never sees your Polar password. It asks for five permissions, the fewest it can work with, and you approve them on Polar's screen:

Nothing on the list charges, refunds, or changes a product.

Why it needs webhooks:write

The first import reads your past orders. After that, Polar tells SuppyHQ about each new order, refund and plan change through a webhook. That's how a new buyer shows up with their plan, and how a failing payment goes on top.

This permission lets SuppyHQ create that webhook and keep its signing secret, which proves an event came from Polar. You set up nothing, and it deletes the webhook when you disconnect.

Polar has no narrower permission, so the token could change other webhooks in your organization. SuppyHQ only creates and deletes its own. It can't charge or refund.

Take it back

Disconnect in Integrations. SuppyHQ deletes the webhook it made and revokes its token. Customers it already imported stay.

How they're kept

Keys and tokens are encrypted where they are stored. Incoming payment events are checked, and a fake one is dropped.

The rest is on the security page.