Sensitive data
Portfolio holdings, watchlists, saved research, AI brief metadata, billing state, and account identity are scoped to the authenticated user and should never be exposed across tenants.
Privacy
Aperture treats identity, holdings, prompts, AI outputs, billing records, and usage events as sensitive product data. The app is designed around server-side access controls, ownership checks, minimized telemetry, and explicit source freshness.
Portfolio holdings, watchlists, saved research, AI brief metadata, billing state, and account identity are scoped to the authenticated user and should never be exposed across tenants.
Provider keys, Supabase service-role credentials, webhook secrets, model configuration, and raw JWTs stay in server runtimes and are not shipped to browser bundles.
AI tools call owner-scoped application APIs and typed server wrappers; models do not receive unrestricted database credentials or arbitrary tenant access.
Observability helpers scrub PII, holdings, financial amounts, raw prompts, AI outputs, API keys, and webhook secrets before analytics or error reporting.