Fenix Privacy Policy

Effective: October 1, 2026 · Fenix is developed by Leo Đogani.

This policy explains what information Fenix processes, why it is used, when it may be sent to service providers, and how you can control or delete your data.

Information you choose to provide

How Fenix uses data

Fenix uses this information to authenticate your account, generate AI responses, provide voice and research features, recall memories you explicitly saved, protect the service from abuse, diagnose failures without storing message bodies in application observability logs, and operate account and security controls.

AI and infrastructure providers

To provide requested features, relevant content may be processed by service providers that operate parts of Fenix. These include OpenAI for AI responses, web research, image analysis, transcription, speech and realtime voice; Google Gemini for bounded independent review in applicable advanced/Deep flows; Anthropic (Claude) and DeepSeek only when an applicable comparison/advisory feature is configured and invoked; ElevenLabs only when configured for a requested voice feature; Supabase for authentication, account data, saved memory and server functions; and Render for application hosting. Fenix may change or add processors as the service evolves; this policy should be updated before materially different data use is introduced.

Fenix does not sell personal data and does not use chat content to serve advertising.

Chat, attachments and voice

Ordinary Fenix chat transcripts are not intentionally persisted as a conversation archive in the Fenix application database. Recent context is sent as needed to generate a response. PDF and text attachments are read for the requested turn; images may be sent to the configured AI provider for analysis. Voice audio may be sent to the configured AI provider for transcription or realtime conversation. Provider-side processing and retention are also governed by the applicable provider agreements and data controls.

Security and technical data

Fenix uses HTTPS for production app and provider connections. Provider and administrator credentials are kept server-side, authenticated account data is scoped through Supabase Auth and row-level access controls, and privileged creator actions require separate short-lived verification. Application observability is designed not to store request bodies or authorization headers.

Fenix uses limited technical information to secure the service and prevent automated abuse. Application rate limiting stores opaque, non-reversible subject digests, operation names, timestamps and counters rather than chat content, access tokens, email addresses, API keys, raw IP addresses or raw user-agent strings. Hosting, authentication and network providers may independently process connection metadata required to operate their services.

Retention and deletion

Your account profile and memories are retained while your account exists unless you delete individual memories sooner. Fenix provides a self-service account deletion flow that removes the authentication account, Fenix profile, saved memories and user-linked Fenix community content. Active refresh-token sessions are revoked as part of deletion. Infrastructure or service providers may retain limited security, operational or backup records for the periods required by their systems, contracts or applicable law.

Your controls

Privacy questions

For privacy or data questions, contact the verified developer support contact published with Fenix in the app store. Account deletion can be started directly from the link below without first contacting support.

Changes to this policy

If Fenix materially changes the data it collects, how it uses data, or the service providers that process data, this policy will be updated and its effective date changed.

Delete account / data Return to Fenix