Security & privacy

Your API keys

• Encrypted at rest. Keys are encrypted with AES-256-GCM before they're stored. They're never kept in plain text.
• Server-side only. Keys are used exclusively on the server to call your provider's API. They are never sent to the browser and never exposed in the app.
• Validated, not stored blindly. A key is checked against the provider before saving, so an invalid key is rejected up front.

Read-only access

Metricneed only reads data — it never creates charges, issues refunds or modifies anything in your provider account. Where your provider supports it, we recommend creating a read-only or restricted key (for example a Stripe restricted key with read access to Core resources, or a Polar token scoped to read products, orders, subscriptions, customers and refunds).

Data isolation

Your data lives in a normalized database with row-level security per account, so each account can only ever read its own connections, customers, subscriptions and transactions.

Revoking access

You're always in control: delete a connection in the app to stop Metricneed using that key, and revoke the key itself in your provider's dashboard whenever you like. Because access is a key you issued, you can cut it off at any time.

For how each provider's key is created, see the connection guides.