Way one: functions the app declares
The first way is the one a developer builds on purpose. Through AppFunctions, part of the Android platform with a Jetpack library alongside, an app publishes selected features as individual functions. The library writes them into a schema the operating system indexes, and a caller with the right permission, which Google says can be an agent, another app or an assistant such as Gemini, can find a function and run it. Google calls the result Android MCP and says the same functions can feed the system's proactive features too. It needs Android 16 or later; as of May 2026 the Gemini side was still a closed preview for selected testers. A remote MCP server run from the app's own backend is the cross-platform alternative. Google's advice is that encrypted content or sensitive data held on the device should use the local path.
For a health app, each declared function is a sentence that belongs in the privacy policy. A function that creates a water entry is a sentence about input, like a widget. A function that returns this week's medication status is a sentence about output to a reader who is neither the user nor us. Keeping the route on the device settles where the data travels, not who reads it. What Linnea's privacy policy says about Android names Health Connect, sign-in, purchases and notification delivery as services Google provides under its own terms, and the Linnea page lists an app shortcut, a Quick Settings tile and reminders as ways to log. On the Android side, neither names an agent, an assistant or a function registry. Nothing we have published says what, if anything, Linnea declares to the system. As with Siri, the sentence is missing, and we would rather say so.
Way two: the screen itself
The second way needs no cooperation from the app. Google describes Computer Control as an Android API still to come, one that lets an assistant preloaded by the device maker carry out tasks in other apps through their user interface. The assistant holds a privileged permission and asks for a session covering up to six apps. The first time it tries, the system shows the user a dialog asking whether the assistant may automate the apps it has named. If the user agrees, the system runs those apps on a background virtual display, much as casting does; the assistant launches them, takes screenshots, decides what to do, and sends taps, swipes and typed text, handing control back to the person for steps such as confirming a transaction. The developer page is explicit that a target app needs no changes; the assistant navigates by analyzing screenshots, and may choose to limit which apps it automates. In the blog post's words, agents can fall back to this route "without requiring any app-side integration". The page describes no switch on the app's side, and we looked for one.
This is the way that turns screen design into a data flow. Whatever the app shows, an authorized assistant can read: for a health log, the medication list, the meals, the glucose readings, everything the person sees. End-to-end encryption, which keeps Linnea's health records unreadable to us, does nothing here, because the screen is where the person reads them. The permission sits with the user, where it belongs, but it is granted to an assistant for a session rather than set per app in Settings, and the app is not asked. So the sentence this way calls for is about a reader, not a route: on a phone with such an assistant, software the user authorizes may see what the user sees and act as the user would. Linnea's policy does not contain that sentence. It is the one we would add first, because, as Google documents the framework, it would be true of any app on the device, integrated or not.
Way three: notifications and chips
The third way is quieter. Alongside tasks a person asks for, the intelligence system offers what Google calls proactive assistance: suggestion chips on the lock screen, in notifications, on the keyboard and inside apps. For a health app the notification is the surface that matters. Linnea's policy says our notifications carry only fixed text or a signal to update, never your health information, and the Linnea page says reminders show a fixed message, never a medication name or dose, while notifications on Android show counts and status only. A lock screen is the obvious reason for rules like these. They now also bound what a proactive layer can learn from a Linnea notification: that a medication, supplement or water reminder fired, not which one or how much. The keyboard and in-app chips work on what you type and what is on screen, which brings us back to the second way.
What a policy should say on Android
Three sentences follow, and only one is in Linnea's policy today. For declared functions: name them, say whether each writes an entry or reads one out, or say there are none. For the screen: say that an assistant the user authorizes may read and operate the app in a session, and that the app has no switch for it, if that is still true when the API ships. For notifications: say what they carry. Linnea's policy does the third. The first two are what we would most like our own policy to gain once the facts settle; one API is upcoming and the other in preview. Until then we will not let "on your device" stand in for them. Apple's switch is per app, in Settings; Google's, as documented, is a dialog when an assistant first asks. Both leave the switch with the user; neither tells the person what is behind the door. That part is the app's to say.
Linnea's privacy policy draws its lines feature by feature. If an Android line is unclear to you, tell us which.
Linnea provides organizational and informational tools only; it does not provide medical advice, diagnosis, or treatment. Always consult a qualified health professional for medical decisions. Android, Google Play, Gemini and Health Connect are trademarks of Google LLC, referenced for identification only; Arctura Technologies Inc. is not affiliated with or endorsed by Google. The Android intelligence system, AppFunctions and Computer Control are described from Google's published developer documentation as read on 9 November 2026; that documentation describes Computer Control as upcoming and the AppFunctions integration with Gemini as a private preview, and availability varies by device, manufacturer and region. Siri is a trademark of Apple Inc., referenced for identification only.
Sources
- Android Developers Blog, "What's new in intelligent apps at the Android Developer Summit", 5 November 2026: developer.android.com/blog/posts/android-intelligence-system-in-app-agents-ads
- Android Developers, "Connect your app to the Android intelligence system": developer.android.com/ai/intelligence-system
- Android Developers, "Android Computer Control": developer.android.com/ai/computer-control
- Android Developers, "Overview of AppFunctions": developer.android.com/ai/appfunctions
- Apple Support, "About iOS 27 Updates", iOS 27.2 section (Excluded Apps): support.apple.com/en-us/149076
- Linnea Privacy Policy, version 3.3 (effective 9 November 2026), sections 1, 2, 6 and 9: arcturatech.com/linnea/privacy.html
- Linnea for iPhone, Apple Watch and Android, product page (logging entry points on Android; reminders and notifications): arcturatech.com/linnea/