Privacy Policy

When you sign in, we process account information such as your email address, name and profile picture provided by your sign-in method. When you use chat, we process your messages, Phoenix responses, files, images, audio and videos you choose to submit, personalization settings and memories associated with your account. Uploaded videos, including their visual and audible content, are sent through Phoenix AI Amber for analysis with the existing multimodal service and saved privately with saved conversations. Video analysis requires a signed-in strong-model conversation and uses workspace AI credits. Private projects can include instructions, extracted source text, related chats, study cards, quizzes, progress and editable documents with revision history. Project PDF reading happens on your device; extracted text is saved and used for the selected project.

Signed-in conversations are saved so you can return to them. Guest chat is not saved as conversation history in an account, but its messages are processed to generate responses. This does not mean that service providers perform no processing or keep no operational logs.

Text extraction from PDFs and supported images, including scanned PDF pages, runs on your device. The extraction software and Arabic/English recognition data are downloaded from Phoenix when needed. Extracted text may then be sent as part of your chat request or saved in a private project. Recognition can make mistakes; review the original before relying on extracted content.

We use information to authenticate users, operate chat, save conversations, process attachments, personalize responses, provide memory, and perform search, generation and connected-service tasks when those features are used. Interface preferences (such as theme, language, seasonal appearance and haptic feedback) and some session information are stored in your browser. If you choose a gender in Account settings, it is saved with your account and used only to address you with the correct grammatical form in replies and notifications.

Unsent text drafts are stored locally on the same device, separately for each account and conversation, including guest drafts. They can survive navigation, restarts and signing out and back into the same account. They are not cloud-synchronized drafts, do not preserve attachments, and are not retained for temporary chats. Text is sent to Phoenix when you submit it, not merely when it is saved as a draft. Clearing browser or app storage can remove drafts and interface preferences. Account separation is not device encryption: anyone with access to your device or browser storage may be able to read locally stored text.

If you enable notifications, we store the push subscription information needed to deliver reminders and proactive messages, and the browser may refresh that subscription in the background so delivery continues while the app is closed. Notification content may appear on your device screen. You can revoke notification permission in your browser or device settings, and signing out removes that device’s subscription from your account.

The Android app uses Firebase Cloud Messaging and stores a device messaging token associated with your signed-in account for delivery. Reminder notifications can offer a Done action. This action sends a random, limited-purpose token to our servers to mark that reminder completed, without opening the app. We store the token's hash, its expiry and whether it was used. Anyone with that token can complete only the linked reminder until it expires; do not share notification action data.

Optional proactive topics, message mood and goals are saved with your account and can inform proactive messages and follow-ups. These features do not independently monitor your surroundings or other apps. Memory records may include the originating conversation/message and update time so saved facts can be reviewed; they remain associated with the signed-in account.

If follow-ups are enabled, while a saved conversation is open the app periodically tells our servers that it is in use, so Phoenix can tell when you leave a topic. Phoenix may then review recent messages of that conversation, your name, gender and enabled memories to decide whether a short follow-up is useful; finished or minor topics are skipped. Proactive and follow-up messages are limited per day, respect quiet hours, and can be turned off in Settings.

The device permissions screen checks microphone and notification status only when you open it or press a button; checking the microphone does not record or send audio. Vibration feedback runs only on your device.

Signing in with Google is optional. Phoenix requests only your basic Google profile (name, email address and profile picture) to create and identify your account. Phoenix does not access your Google Calendar, Gmail, Drive or any other Google service data.

Phoenix’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google profile information is not used for advertising, sold, or used to train AI models.

You can revoke Phoenix’s access at any time in your Google account settings.

Phoenix provides hosting, authentication and storage using external infrastructure services. Signed-in strong chat models, image requests, live voice calls and signed-in voice typing use Phoenix AI Amber; guest chat, guest voice typing, Flash and proactive check-ins use a separate processing path, identified in the technical processing details below. During live calls, call audio streams directly to the voice provider and transcripts pass through Phoenix servers to answer you; calls are not saved as chats. Weather questions send the city name or rounded location you choose to Open-Meteo. Built-in everyday lookups send only needed search terms, city/country, date or currency codes to public reference services such as Al Quran Cloud, Islamic App, AlAdhan, Frankfurter, TheMealDB, Open Library, TVmaze, Google News RSS and Wikipedia. YouTube results open as a search link on YouTube. If you connect Spotify, Phoenix stores an encrypted Spotify sign-in token for your account and sends playback commands and searches to Spotify; you can disconnect anytime. Phone actions (alarms, calendar events, maps, WhatsApp, dialing) run on your device only after you tap confirm. Provider quotas and policies apply, and provider processing may include operational retention under their terms.

Spotify authorization requests access to playback state, currently playing information and playback control. Phoenix retains an encrypted refresh token associated with your account to obtain short-lived access tokens. Disconnecting removes the stored Phoenix connection; you can also revoke access in Spotify. Disconnecting does not erase records already held by Spotify.

Supported Android builds can send your explicitly requested playback commands to the installed Spotify app through Spotify App Remote after Spotify authorization. Music playback and audio remain in Spotify; Phoenix does not download or rehost the music. Only freshly requested, account-bound commands can run automatically, not commands from reopened or shared conversations. The Spotify account signed into the device app handles playback; use the same account as the connected Phoenix service. Signing out or disconnecting in Phoenix stops its remote connection, but does not necessarily stop music already playing in Spotify.

Chat attachments are processed by the provider selected for the actual chat request; this is distinct from image generation or editing through Phoenix AI Amber. Strong-model video analysis uses that service and may include both scenes and audio. Voice typing sends the recorded audio for transcription through Phoenix AI Amber when signed in and to Groq for guests. The resulting text enters the composer; voice typing is separate from a live call or read-aloud.

Live voice sends microphone audio directly to Google using a short-lived session credential. Your personalization, saved memories when enabled, and recent chat context may be used for the call. Live transcripts also pass through the Phoenix relay and may be forwarded to the response service for call context and action proposals. Captions are displayed temporarily and are not automatically saved as chat history; this does not imply that providers keep no operational records. Ending the call, closing it, or hiding the tab stops microphone capture and playback.

During live calls, Phoenix can prepare reminder or goal proposals. They are not stored as reminders or goals unless you press the visible confirmation button. Confirmed actions are saved in your own account; cancelling or ending the call discards unconfirmed proposals.

When a signed-in user selects read-aloud, response text is sent in sequential portions through Phoenix AI Amber to Google's speech service and audio plays progressively as it arrives. This does not require microphone capture. Cancelling playback stops the current request where possible but cannot retract text already sent to a provider. Guest read-aloud uses the device's speech service, whose processing depends on the browser and operating system. Android image sharing sends only the images you explicitly choose to share into Phoenix; the home-screen widget opens a new conversation and does not expose saved conversation content.

Information needed to fulfill your request may include conversation context, attachments and information retrieved from connected services. Provider processing and retention are subject to their applicable terms and policies. We do not guarantee that all providers retain no data or operational logs. Processing may take place outside your country.

Saved conversations are associated with your account. If you choose to share a conversation, anyone who obtains its sharing link may read its content. Avoid sharing personal information.

Media is stored in a private bucket. New delivery URLs require short-lived capabilities verified against the file owner's account or an active shared conversation referencing that file. Anyone with an active conversation share link can request its shared media. Delivery requests are rechecked and request private no-store caching; previously downloaded or cached copies cannot be recalled. These safeguards are not an absolute guarantee of security.

Project source text is split into owner/project-scoped searchable page excerpts. Semantic search indexes missing or changed source excerpts in the selected project and independently saved personal memories through Phoenix AI Amber using Gemini Embedding 2. Searches send the query to the same service. Indexing and searching use running credits; lexical retrieval remains available when semantic search is unavailable. Saved-memory search is disabled when memory is off or the conversation is temporary. Deleted conversations and unsaved facts are not reconstructed through semantic search. Recognition confidence is a quality signal, not a guarantee of accuracy.

When connected, Tavily receives search terms through Phoenix's server to retrieve public web excerpts and source URLs. Private project files are not sent to Tavily. Search queries can themselves contain personal information; avoid sensitive queries. Tavily's processing and retention terms apply.

Long conversations may use bounded history and private extractive continuity summaries linked to the original thread. Summaries are incomplete reference material, not automatically saved personal facts. Memory capacity is separate from the smaller relevant set used in a response. API admission and notification delivery attempts may store hashed request scopes, timestamps and status, not audio or message bodies.

Successful changes to memories, reminders, projects, source files, documents and settings, and conversation creation, deletion and sharing changes, generate private audit records containing only your account ID, resource type and ID, action and time. These records do not copy messages, memory text, file contents, emails, IP addresses or credentials. Other accounts cannot read your audit records, and application clients cannot create, edit or delete them. Failed or denied attempts are not recorded in this change log.

Application diagnostics use redacted errors and per-request measurements such as a random request identifier, elapsed time and outcome. These operational logs are separate from the private change log. Hosting and service providers may separately process network metadata, including IP addresses, under their policies. We do not specify a uniform retention period for all provider diagnostics.

Conversations, memories, files and settings are retained as needed to operate the service and restore your data. We currently do not specify a uniform automatic deletion period. You can delete conversations from the chat list and delete or disable memories in Settings. Disabling memory stops its use and saving, but does not delete existing memories or conversations. Temporary signed-in chats do not save conversation history or use saved memories; explicitly requested image or reminder actions may still process or save their own data. You can export account records and revoke shared links in Settings, and delete projects and their study documents. Deleting a project leaves its conversations outside that project.

Saved memories are separate from conversation history. Deleting a source conversation does not automatically delete a fact independently saved as memory; delete that memory separately in Settings. An explicit request not to save a fact prevents personal-memory capture, but does not delete the message from an ordinary saved conversation. Once that conversation is deleted, Phoenix must not claim to retrieve its deleted unsaved contents. Memory search and responses can be incomplete or inaccurate.

The Account export downloads a JSON copy of your conversation and message records, memories, settings, projects and source records, documents and revisions, study progress and reminders. It is not a complete backup: it does not download original stored media files, device-local drafts, private audit records, connected-service credentials or third-party logs. Media references in exported records are not a guarantee of lasting access to their files.

There is currently no in-app button to delete your entire account. To request account, file or other data deletion, contact the developer below. We may need to verify account ownership. Deleting a conversation record does not mean that all associated files, cached copies or third-party logs are immediately deleted. Signing out is not deletion of locally stored drafts. Content-free audit records remain after the related item is deleted and follow the same data-request process; there is currently no automatic audit deletion period.

We may update this policy when features or data processing change. The latest revision date appears at the top of this page. Review this policy before connecting a new service or submitting sensitive information. Contact us with questions about your rights or how your information is processed.

Developer: Abdullah Sherify. For questions or data deletion requests, contact the email below. Identify your account email, but do not send passwords or sign-in codes.

Email: sherify@phoenixai.chat

Official website: get.phoenixai.chat — find app information and the Android download link there.

Phoenix AI Amber is the name used for the AI service within Phoenix, not a claim to own independent foundation models. This service operates through Lovable AI Gateway and the actual model and voice providers; data needed to fulfill your request is sent to them as described in this policy. The service name does not change the data processors or their terms.

Hosting, authentication and storage are provided through Lovable Cloud. Guest chat, guest voice typing, Flash and proactive check-ins use the developer’s Groq account. Earlier sections of this policy identify other services that receive your data according to the feature you use.