Last updated: October 30, 2026

This Privacy Policy explains how MindFeast handles information when you visit the MindFeast website at https://mindfeast.life or use MindFeast Android apps, including the apps listed on Google Play as MindFeast: Lock Screen, MindFeast Spelling, and MindFeast Agent Alarm.

MindFeast is designed for parent-managed family devices. MindFeast does not use advertising, does not sell personal information, and does not provide a MindFeast cloud account service.

MindFeast: Lock Screen helps parents create and show learning slides, questions, narration slides, optional AI conversation slides, art, reflection prompts, and gratitude prompts during ordinary device use.

MindFeast Spelling is local-first and does not communicate with a MindFeast server. It uses the microphone for speech recognition through the device or system speech service. When the device is online, the system recognizer may use Google's cloud speech-to-text service, so the app requests internet access. It checks network state to choose between on-device and cloud recognition. The app has no ads or account, and it does not record audio to disk.

MindFeast Agent Alarm is a local-first alarm clock. It schedules and plays a wake alarm you choose on the device. Alarm settings, imported wake audio, picture study images, morning notes, and theme preferences stay on the device. The app does not communicate with a MindFeast server, has no account, and does not include ads or tracking.

An optional local-network agent connection is off by default. If you enable it, a parent-controlled agent on the same trusted Wi-Fi or LAN can send wake audio, pictures, notes, theme, and alarm settings to the app using a bearer token generated on the device. That traffic stays on your local network. MindFeast Agent Alarm does not send app data to MindFeast over the internet. Data leaves the device for an AI agent only when you choose to use this optional connection. The connection uses HTTP on the local network and is not end-to-end encrypted, so use a trusted network, keep the token private, and do not expose the listener to the internet.

Device Security

MindFeast: Lock Screen is an educational lock screen experience. It does not replace Android's built-in device lock, password, PIN, pattern, fingerprint, face unlock, encryption, or other security features. Parents should use Android's system security settings to protect the device and the information stored on it.

Contact

MindFeast Contact: support@mindfeast.life Website: https://mindfeast.life

Website Analytics

The MindFeast website uses Umami Cloud, operated by Umami Software, Inc., to understand website traffic and whether visitors select important outbound links, such as links to Google Play or GitHub.

Umami may process the page visited, page title, referrer, browser, operating system, device type, screen size, language, approximate location, campaign parameters, and events such as Google Play or GitHub link clicks. A link-click event indicates only that the link was selected; it does not tell MindFeast whether a purchase occurred.

According to Umami, its website tracker does not use cookies, fingerprint visitors, or track visitors across websites. Umami uses network and request information, including the IP address and user agent, to derive approximate location and anonymous session metrics. According to Umami, IP addresses are not stored.

Website analytics are separate from the MindFeast Android apps. MindFeast does not send children's responses, locally stored app content, spoken words, or information entered into the apps to Umami.

Analytics information is processed and retained by Umami Cloud according to the data region and service plan configured for MindFeast's account and under Umami's privacy practices.

Information Stored on the Device

MindFeast: Lock Screen stores app information locally on the device so the app can work as a parent-managed learning tool. This may include:

  • Parent-created slides, prompts, questions, answers, hints, accepted answers, informational text, images, and audio.

  • Starter slides and installed slide packs.

  • Which slides are active for a child or device.

  • Basic completion history.

  • Essay responses, narration responses, and gratitude journal responses.

  • AI conversation transcripts, if a parent turns on AI conversation slides, and written answers given when an AI conversation cannot run.

  • App settings, including lock screen settings, remote trigger settings, sync settings, slide creation preferences, the AI conversation slide switch, and the voice setting for AI conversation slides.

  • A local admin PIN hash, if the parent creates an admin PIN.

  • Optional credentials or secrets entered by the parent, such as a Gemini API key, an xAI API key, SMB/local folder sync credentials, and a remote trigger token.

  • Grok sign-in tokens, if the parent uses Sign in with Grok. These are an access token, a refresh token, and the time the access token expires. They are stored encrypted, as described in Sign in with Grok below.

  • The AI provider the parent picks for AI slide creation, Gemini or Grok.

  • A Grok fallback log, if a Grok feature switches from the parent's Grok plan to the parent's xAI API key. Each entry has the time, the feature, and the reason, as described in Sign in with Grok below.

  • A Dropbox sign-in credential, if the parent connects Dropbox. It includes a refresh token and is stored encrypted, as described in Dropbox Sync below.

  • Local purchase entitlement state for installed slide packs.

This information is used to provide the app's core features. MindFeast does not operate its own server to receive or store this information.

Narration slides do not use AI. A narration is stored on the device like an essay response. If the child uses the keyboard's voice typing, that is handled by the device's keyboard, not by MindFeast.

MindFeast Spelling does not record audio to disk. It does not communicate with a MindFeast server.

MindFeast Agent Alarm stores app information locally on the device so the alarm can work offline. This may include:

  • Alarm schedule settings, including wake time, enable state, weekday repeat days, and clock display preference.

  • Imported wake audio and picture study images chosen in the app.

  • Morning notes and note headings.

  • Theme and atmosphere preferences.

  • Optional local-network agent settings, including listen port and an on-device bearer token stored with Android platform encryption where supported.

  • Local purchase entitlement state from Google Play.

MindFeast Agent Alarm does not communicate with a MindFeast server.

Information Shared with Third Parties

MindFeast: Lock Screen only sends information outside the device when a parent uses a feature that requires it or when Google Play services are used.

MindFeast Spelling does not send audio or other app data to a MindFeast server. When the device is online, the system speech recognizer may use Google's cloud speech-to-text service.

MindFeast Agent Alarm does not send app data to a MindFeast server. Outside Google Play Billing, information leaves the device for an AI agent only if you enable the optional local-network agent connection described above.

Google Play Billing

MindFeast uses Google Play Billing for app purchases and one-time slide pack purchases. Google processes payment information and purchase transactions. MindFeast receives purchase status information from Google Play so the app can unlock purchased content. MindFeast does not receive full credit card or bank account information.

AI Slide Creation (Gemini or Grok)

MindFeast: Lock Screen includes optional AI slide creation with Gemini or Grok. Only a parent can use it, from Admin. AI slide creation is off unless a parent connects a provider and chooses to create or regenerate slide content. To use Gemini, the parent saves a Gemini API key. To use Grok, the parent uses Sign in with Grok or saves an xAI API key. If both providers are connected, the parent picks one in Admin > Settings, and MindFeast stores that choice on the device.

When a parent uses Gemini, MindFeast sends the parent-provided API key and slide creation request to Google's Gemini API. The request may include the parent's prompt, style instructions, selected slide type, slide orientation, and any image URL the parent provides for context. If Gemini image generation is used, MindFeast sends an image prompt to Gemini and receives generated image data.

When a parent uses Grok, MindFeast sends the same prompt fields directly from the device to xAI's API (api.x.ai), with the parent's Grok sign-in or xAI API key. If Grok image generation is used, MindFeast sends an image prompt to xAI and receives generated image data. AI slide creation does not send child data, such as a child's answers, essays, narrations, or AI conversation transcripts, to either provider.

Parents should not include private child information in AI slide creation prompts unless they are comfortable sending that information to Google or xAI. Google handles Gemini requests under the terms and privacy practices that apply to the Gemini API and the parent-provided API key. xAI handles Grok requests under the terms and settings of the parent's own xAI account, which MindFeast does not control.

Sign in with Grok

MindFeast: Lock Screen includes an optional Sign in with Grok feature. It lets a parent use their own Grok plan for Grok features instead of an xAI API key. Only a parent can use it, from Admin > Settings > AI accounts. No MindFeast account or server is involved.

When a parent presses Sign in with Grok, MindFeast asks xAI's sign-in service (auth.x.ai) for a one-time code and opens xAI's sign-in page in a browser tab. The parent signs in to their own xAI account on xAI's site and approves MindFeast there. The parent's xAI password is never entered into MindFeast.

MindFeast asks xAI for the openid, profile, email, offline_access, grok-cli:access, and api:access permissions, so xAI's approval page may mention the parent's profile and email address. MindFeast does not read or store the parent's name, email address, or xAI account ID. It stores only the access token, the refresh token, and the time the access token expires. These are encrypted with a key held in the Android Keystore and are excluded from Android cloud backup and device transfer.

Grok features try the parent's Grok plan first. If xAI refuses the plan and the parent has also saved an xAI API key, MindFeast retries that request once with the API key. MindFeast then adds an entry to a fallback log on the device. Each entry has the time, the feature (text conversation, voice conversation, slide text, or slide image), and the reason xAI refused the plan. AI accounts shows the most recent entry. The log is not sent anywhere. It stays on the device until app data is cleared or the app is uninstalled. Signing out does not clear it.

To stop Grok access, press Sign out in AI accounts. Sign out asks xAI to revoke MindFeast's access and deletes the stored tokens from the device. The tokens are deleted even if xAI cannot be reached. If xAI no longer accepts the saved sign-in, MindFeast deletes the tokens and asks the parent to sign in again.

xAI (Grok) AI Conversation Slides

MindFeast: Lock Screen includes optional AI conversation slides that use xAI's Grok. These slides are off by default. Conversation slides are shown only after a parent turns on AI conversations in Settings. Conversation slides use the parent's Grok sign-in or xAI API key. Without either one, the slide offers a written answer instead. The xAI API key is stored encrypted on the device, like the Gemini API key.

When a conversation slide runs, MindFeast sends the parent's Grok sign-in or xAI API key, the slide's parent-written intent, context, and opening question, and the child's typed or transcribed replies directly from the device to xAI's API (api.x.ai). No MindFeast server is involved.

Voice is optional and set separately on each device. When voice is on, a conversation slide runs as a live voice conversation with xAI. The child's voice is streamed from the device's microphone directly to xAI's API for the length of the conversation, along with the parent's Grok sign-in or xAI API key and the slide's intent, context, and opening question, and xAI sends back spoken replies and text transcripts of both sides. MindFeast does not store or record audio. Only the text transcript is stored on the device, like a typed conversation. When voice is off, only text is sent to xAI, and if the child uses the keyboard's voice typing to write a reply, that is handled by the device's keyboard, not by MindFeast.

If the AI cannot run because there is no Grok sign-in or xAI API key, or no internet connection, the slide shows a warning and offers a written answer instead. That answer is stored on the device.

xAI handles this information under the terms and settings of the parent's own xAI account and xAI's privacy policy. MindFeast does not control those terms or settings.

Parents should not include private child information in a slide's intent or context unless they are comfortable sending that information to xAI.

Reporting AI Content

In Admin, a parent can open a saved AI conversation and tap Report to MindFeast on an AI reply. This opens the parent's email app with a prefilled message to support@mindfeast.life. The message contains only that AI reply, a category, an optional note from the parent, and the app version and AI model. It does not include the child's replies or identifiers. Nothing is sent unless the parent sends the email.

If the parent sends a report, MindFeast receives it by email, along with the parent's email address and anything the parent writes. MindFeast uses reports only to improve content filtering and to respond to and handle the reported issue. MindFeast does not sell reports or use them for advertising, and deletes them when they are no longer needed to handle the issue.

Parent-Provided Media URLs

If a parent enters an image URL or audio URL in MindFeast: Lock Screen, MindFeast downloads that file from the URL. The website or server hosting that URL may receive normal network request information, such as the device's IP address.

Local Folder or SMB Sync

MindFeast: Lock Screen can optionally sync slides with a parent-provided shared folder on a home computer or local network file server. When this feature is configured, MindFeast connects to the server information entered by the parent and may upload or download slide files, images, audio, and slide metadata.

MindFeast does not control the parent-provided computer, file server, network share, or any backups of that shared folder.

Dropbox Sync

MindFeast: Lock Screen can optionally sync slides with Dropbox. Dropbox sync is off unless a parent selects Dropbox as the sync source in Admin > Sync and connects a Dropbox account. SMB is the default sync source.

MindFeast can reach only its own app folder in Dropbox, which appears in the parent's Dropbox as Apps/MindFeast. It cannot see or change other files in the account. When a parent presses Connect, Dropbox asks the parent to approve these permissions:

  • files.metadata.read, to list the slide folders and files in the app folder.

  • files.content.read, to download slide files.

  • files.content.write, to export slides to the app folder.

Sign-in uses OAuth with PKCE, through the Dropbox app or a browser. The app contains only a public app key. It does not contain a Dropbox app secret, and the parent's Dropbox password is never entered into MindFeast.

Sync Slides lists the slide folders at the top of the app folder and downloads the files directly inside each one, usually slide.md, images, and audio. It skips hidden folders whose names start with a dot. Sync does not change or delete anything in Dropbox. A sync can remove a previously imported Dropbox slide from the device when that slide is no longer in the app folder and has no local edits. Sync does not overwrite a slide on the device that came from another source, or one with local edits waiting to be exported.

Export to Dropbox is a separate, optional action. It uploads a slide's files to a folder with the slide's name in the app folder. If a file with the same name already exists in that folder, export replaces it. Export does not delete anything in Dropbox.

MindFeast contacts Dropbox only when a parent uses a Dropbox control in Admin (Connect, Sync Slides, Export to Dropbox, or Disconnect) or starts a sync from the optional remote trigger. There is no scheduled background sync.

Slide data moves only between the device and Dropbox. MindFeast does not send Dropbox files, folder names, or account information to a MindFeast server, and does not operate a server for this feature. MindFeast does not sell Dropbox data, use it for advertising, use it to train AI models, or send it to Gemini or Grok. After import, a Dropbox slide works like any other slide on the device, including through the optional remote trigger and Android backup described below.

To stay connected, MindFeast stores a Dropbox credential that includes a refresh token. The credential is encrypted with a key held in the Android Keystore and is excluded from Android cloud backup and device transfer. The app uses it to get short-lived access tokens from Dropbox.

To stop Dropbox access, press Disconnect in Admin > Sync. Disconnect asks Dropbox to revoke MindFeast's access and deletes the stored credential from the device. The credential is deleted even if Dropbox cannot be reached. Disconnect does not delete imported slides from the device or files in Dropbox. Parents can also remove MindFeast's access at any time from the Connected apps section of their Dropbox account settings.

This policy can also be opened in the app from Admin > Settings.

Remote Trigger

MindFeast: Lock Screen includes an optional remote trigger feature. If enabled by a parent, the app runs a small local web control interface on the device so another device on the same local network can trigger or manage slides. The remote trigger uses a token in the local URL and only accepts local or link-local network connections.

MindFeast does not send remote trigger activity to a MindFeast server.

Optional Agent Alarm LAN Connection

MindFeast Agent Alarm includes an optional local-network agent connection. If enabled, the app listens on the device so a parent-controlled agent on the same local network can send wake audio, pictures, notes, theme, and alarm settings. Requests use a bearer token generated on the device and are limited to local or link-local network clients. Traffic stays on the local network and is not sent to a MindFeast server.

The optional connection uses HTTP and is not end-to-end encrypted. Parents should use a trusted network, keep the token private, and should not port-forward or otherwise expose the listener to the internet.

Advertising and Tracking

  • MindFeast does not show ads.

  • MindFeast does not include third-party advertising SDKs.

  • MindFeast does not sell personal information.

  • The MindFeast website uses the privacy-focused analytics described above.

  • MindFeast does not use analytics information for targeted advertising or for cross-app or cross-site tracking.

Children and Family Use

MindFeast is intended to be managed by parents. In MindFeast: Lock Screen, children may interact with slides, answer questions, write essay responses, write narrations, have AI conversations if a parent turns on AI conversation slides, or respond to gratitude prompts. These responses, including AI conversation transcripts, are stored locally in the app so parents can review them.

On a narration slide, the child listens to a parent-provided audio file, listens to parent-written text read by the device's on-device text-to-speech, or reads text on screen. The passage is then hidden, and the child writes a narration by typing or with the keyboard's voice typing.

Children may speak a word to MindFeast Spelling. That speech is handled by the device or system speech service as described above and is not recorded to disk by the app.

MindFeast Agent Alarm is managed by parents. Children may see the morning wake screen, including a picture study and notes a parent or parent-controlled agent has prepared. Those materials are stored on the device.

Parents are responsible for choosing the content shown to their children and for deciding whether to use optional features that send information outside the device, such as AI slide creation with Gemini or Grok, Sign in with Grok, xAI (Grok) AI conversation slides, media URL downloads, SMB/local folder sync, Dropbox sync, or the optional Agent Alarm local-network agent connection. These features are optional and stay off until a parent sets them up.

Permissions

MindFeast uses Android permissions to provide app functionality, including:

  • Display over other apps, foreground service, notifications, and boot startup permissions so MindFeast: Lock Screen can show selected learning slides during ordinary device use.

  • Internet access for optional AI slide creation with Gemini or Grok, optional Sign in with Grok, optional xAI (Grok) AI conversation slides, optional media downloads, Google Play Billing, optional local network sync, optional Dropbox sync, and optional remote trigger features in MindFeast: Lock Screen.

  • Network state access so MindFeast: Lock Screen can check for a connection before an AI conversation slide.

  • Microphone access for optional voice in MindFeast: Lock Screen AI conversation slides, requested from Admin when voice is turned on. Microphone audio is streamed to xAI during a voice conversation and is not stored.

  • Microphone access so MindFeast Spelling can listen for a spoken word through the system speech recognizer.

  • Internet access and network state for MindFeast Spelling because the system recognizer may use Google's cloud speech-to-text when the device is online, and so the app can prefer on-device recognition when offline.

  • Exact alarm, notifications, full-screen intent, foreground service, wake lock, vibration, and boot startup permissions so MindFeast Agent Alarm can schedule and deliver a wake alarm, including audio playback while ringing.

  • Internet access and network state for MindFeast Agent Alarm so Google Play Billing can work and so the optional local-network agent listener can accept connections when a parent enables it.

MindFeast uses these permissions for app functionality, not for advertising or tracking.

Security

MindFeast is designed to keep family content local by default.

For MindFeast: Lock Screen, the local admin PIN is stored as a one-way hash, not as plain text. Sensitive settings such as SMB passwords, Gemini API keys, xAI API keys, and remote trigger tokens are stored locally in encrypted form where supported by Android. The Dropbox credential, including its refresh token, and the Grok sign-in tokens are encrypted with a key held in the Android Keystore. The AI provider choice and the Grok fallback log contain no credentials and are stored without encryption. MindFeast excludes its settings DataStore, including the Dropbox credential, the Grok sign-in tokens, the AI provider choice, and the Grok fallback log, from Android cloud backup and device-transfer extraction rules.

For MindFeast Agent Alarm, the optional agent bearer token is stored locally with Android platform encryption where supported. App backup is disabled so credentials, imported audio and pictures, and notes are not exported through ordinary Android backup.

No method of storage or transmission is perfectly secure. Parents should protect the device, choose an appropriate admin PIN, restrict any Gemini or xAI API key they create, sign out of Grok on a device they no longer use, secure any local network file shares they configure, and treat any Agent Alarm bearer token like a password on a trusted network.

Android Backup and Device Transfer

Android and Google services may provide app backup, restore, or device-transfer features depending on the user's device settings and Google account configuration. MindFeast: Lock Screen excludes its settings DataStore from Android cloud backup and device transfer, but other app data may be handled by Android backup or transfer mechanisms according to Android and Google settings. This other app data includes saved AI conversation transcripts, essays, and narrations, which are stored in the app database. MindFeast Agent Alarm disables app backup so its local settings, credentials, and imported media are not included in ordinary Android cloud backup.

Data Retention and Deletion

MindFeast keeps local app data on the device until it is deleted by the parent, removed by app features, cleared through Android system settings, or removed by uninstalling the app.

Parents can delete essay responses, narration responses, AI conversation transcripts, and gratitude journal entries in MindFeast: Lock Screen. In MindFeast Agent Alarm, parents can clear imported wake audio, restore the default picture, and clear notes in the app. Parents can also remove app data by using Android's app storage controls or by uninstalling the relevant MindFeast app. Uninstalling MindFeast Agent Alarm deletes its settings, credentials, and imported audio and pictures on the device.

If a parent syncs slides to a shared folder or exports slides to Dropbox, copies in that shared folder or in Apps/MindFeast must be managed or deleted separately by the parent. Disconnecting Dropbox asks Dropbox to revoke MindFeast's access and deletes the stored Dropbox credential from the device. It does not delete slides already imported to the device or files in Dropbox. If a parent sends prompts or other information to Gemini, that information is handled by Google under the terms and privacy practices that apply to the Gemini API and the parent-provided API key. Information sent to xAI by AI slide creation or AI conversation slides is handled by xAI under the terms and settings of the parent's own xAI account, as described above. Signing out of Grok asks xAI to revoke MindFeast's access and deletes the stored Grok tokens from the device. It does not clear the Grok fallback log, which is removed when app data is cleared or the app is uninstalled.

MindFeast does not provide cloud accounts, so there is no MindFeast account to delete.

Website analytics information is retained by Umami Cloud according to the data region and service plan configured for MindFeast's account.

Changes to This Policy

MindFeast may update this Privacy Policy as the website or app changes. If the policy changes, the updated version will be posted at:

https://mindfeast.life/privacy

Questions

Questions about this Privacy Policy can be sent to:

support@mindfeast.life