Christensen Capital Integrations

Privacy Policy

Last updated: September 13, 2026

This policy describes how Christensen Capital integrations handle information when a user connects a supported third-party service. Each integration may also provide additional, service-specific details.

Information we access

We access only information authorized by the user through the third-party provider's permission process. The exact categories depend on the integration and the permissions granted.

How information is used

Authorized information is used only to provide the requested integration, including retrieval, analysis, and user-directed automation. We do not sell connected-service data.

Credentials and authorization

We do not request third-party account passwords. Supported connections use the provider's authorization process. Application secrets remain in server-side configuration and are not exposed to the browser.

Storage and retention

Retention depends on the integration. The current Oura development version does not persist Oura access tokens, refresh tokens, or retrieved Oura data. This policy will be updated before persistent storage is enabled.

Oura integration

Depending on the permissions granted, the Oura integration may access profile information, daily summaries, heart-rate data, workouts, tags, sessions, and daily SpO₂ data. That information is used only for the user-authorized workflow.

Your choices

You may decline requested permissions or revoke a connection through the third-party provider where supported. See the support pagefor assistance with access or deletion questions.