Know what
you’re connecting.
Indie handles useful—and sometimes sensitive—information about your apps. Here is the practical version of what goes where.
You choose the signals you send.
The Events API receives the fields your server sends. Keep messages focused on what an operator needs to act. Do not put passwords, API keys, card numbers or private documents into an event body.
Purchase and customer history can contain names, email addresses, amounts and transaction identifiers. Think about who should see those records before connecting a project.
An app credential belongs on a server.
Indie project keys are for server-side use. Store them in an environment or secret store, never in frontend JavaScript or a public repository. Revoke a key if you no longer use it or suspect it has been exposed.
Stripe webhook signing secrets verify incoming messages. The Connect Stripe flow uses scoped authorization and stores its access and refresh tokens encrypted on the backend. Customers do not paste full Stripe account API keys into Indie. This OAuth connection remains in testing.
Card details do not belong in an operations dashboard.
The Stripe import retains the purchase identifiers, captured amount, currency, refund amount and selected customer details needed for history. It does not keep card details, billing addresses, payment-method objects or the complete raw charge response.
Other event integrations are under your control. Avoid sending unnecessary personal information and do not assume arbitrary custom text has been stripped of secrets for you.
A widget needs less access than the full app.
The widget uses a scoped, read-only summary credential. Its summary does not include customer details or incident descriptions, and it cannot change your projects.
Notification preview preferences let you limit what appears on the lock screen. Device settings still control what iOS displays and plays.
Disconnecting and deleting do different things.
Disconnecting Stripe stops syncing and removes the locally stored authorization tokens. Existing purchase history remains. To revoke the app permission at Stripe too, remove Indie from your installed Stripe apps.
Owned-workspace exports include retained commerce and monitoring records, including unassigned Stripe purchases. They exclude credentials and are data exports, not restorable server backups. Account deletion removes the account and applicable owned workspaces, subject to billing and ownership checks.
The formal version
This page explains the product’s data behavior in practice. The privacy notice and terms are the formal commitments, and support explains how to make a request. No security certification or availability guarantee is claimed here.
Read the privacy notice