Notifications
What Foxl can notify you about, how each category works, and where to turn them on or off
Foxl can tell you when long-running work finishes, so you do not have to sit and watch it. Every notification is opt-out per category, and nothing is sent unless the work you started actually completed.
Where to control them
On mobile, open Settings > Notifications. The screen shows one row per category plus the current permission state, and a link into the operating system's own settings when permission has been denied at the OS level (no in-app toggle can grant that for you).
Notifications require two things to be true: the operating system has granted Foxl permission, and the category is enabled. If you never see a notification, check the permission state at the top of that screen first.
The categories
| Category | Default | Fires when |
|---|---|---|
| Chat replies | On | A response finishes while you are away from the app |
| Scheduled tasks | On | A scheduled run completes |
| Code tasks | On | A coding task is ready for review, merged, or fails |
| Notes transcripts | On | A transcript, summary, or report finishes while you are away |
| Product updates | On | New features and release highlights |
| Promotions and tips | Off | Occasional offers - opt-in only |
Everything useful defaults to on because it is low-volume and follows an action you took. Only marketing is opt-in: it is never sent unless you explicitly enable it.
Chat replies
A reply can take a while on a hard question, and if you leave the app before it lands there is nothing on screen to tell you it did. This fires only when you were away when the response completed - if you watched it stream, you already know.
Tapping the notification opens that conversation.
Notes transcripts
Transcribing an imported recording takes roughly as long as the audio, so the natural thing is to start it and put the phone down. This category covers a finished transcript, and also the AI results that follow it - the summary and the coaching report, which are the slowest steps because they read the whole transcript. Tapping it opens the note that finished.
A summary you watched appear on screen does not notify you; only one that landed while you were elsewhere.
Because Notes does its transcription work on the device rather than on our servers, the app itself reports completion. If you force-quit Foxl mid-import, the import stops with it and no notification is sent.
Code tasks
A Foxl Code task runs on its own and can take minutes. This fires when the task reaches a state that wants your attention: a pull request ready for review, a merge, or a failure.
Promotions and tips
The only category that is off unless you turn it on, and the only one not caused by something you did. If you enable it, you will hear from us at most once every 30 days - that limit is enforced on our side, not a promise about intent.
What you receive depends on which parts of Foxl you use and how long you have been here, so the message is at least relevant. That grouping is based on counts and dates - your tier, when you signed up, when you were last active, whether you have used Notes or Code. It never involves the contents of your messages, transcripts or files.
You will not hear from us in your first week, whatever your settings say.
Requirements
Notifications are delivered to the mobile app. The desktop app uses your operating system's own notification centre for local events and does not need any of this; the web app has no push notifications.
Your phone registers itself with Foxl once, the first time you run the app and grant permission. That registration is tied to your account, so notifications follow you across devices signed in to the same account, and signing out on a device stops that device receiving them.
Privacy
Notification text contains only what you need to recognise the event - a conversation title, a note name, a task title. The body of a message, the contents of a transcript, and any file content are never included in a notification payload.