FAQ

Straight answers on product scope, pricing, and billing

This FAQ avoids marketing ahead of the codebase. Billing, integrations, and report claims are written to match the current application behaviour.

FAQ

Public answers that match the current product

The FAQ is intentionally conservative. It only promises what the application already supports or what the billing flow explicitly implements.

View full FAQ

Who is ITK for?

ITK is built for agencies and client teams that need to manage multiple reporting relationships without losing control of access, integrations, or billing.

Which integrations are publicly supported today?

The public site only claims support for Meta, Google, Shopify, and WooCommerce because those are the integrations represented in the current application code.

Is this a public self-serve platform or a private beta?

The product is credible enough to present publicly, but some commercial flows still behave like an early production private beta. The public copy is written to match that reality.

Do you store arbitrary HTML from public report editing?

No public claim is made around editable raw HTML. The current reporting model is built around structured sections and rendered output.

Billing FAQ

Pricing and billing questions

Is there a free trial?

There is no advertised automatic trial on paid plans. Use the free tier where it is available, or start directly on a paid plan.

How do I manage a paid subscription?

Once billing is live on your account, plan changes and cancellations can be handled through the billing portal.

What happens after Stripe Checkout?

Stripe returns you to account setup so you can finish creating or activating your ITK account.

What if a plan is not available for online checkout yet?

If a plan or billing cycle is not published for self-serve checkout, you can still start account setup and we can enable it separately.

What security claims are made publicly?

The platform uses authenticated access controls and tenant-aware data boundaries. This public pricing page does not promise sector-specific compliance regimes that are not evidenced in the codebase.