Apple’s warning about AI agents misusing Full Disk Access sparks a debate over Mac security, privacy, and the potential consequences for developers and users. The MacVoices Live! panel examines Apple’s permission system, the need for more granular controls, and concerns about restricting legitimate applications and developer options. The discussion also questions Mark Zuckerberg’s involvement in drafting the White House’s voluntary AI regulatory accord and whether self-regulation is the best solution to potentially dangerous advances in AI.
App Tracking Transparency is at the center of a new UK lawsuit seeking approximately $2.7 billion (£2 billion), putting one of the most recognizable iPhone privacy features under fresh legal pressure. The claim follows earlier challenges to the tracking system in France, but this action seeks compensation for developers who say Apple imposed unfair restrictions on their businesses while favoring its own advertising services.
Filed on September 3 at London’s Competition Appeal Tribunal, the case represents another dispute over the rules behind the familiar permission prompt. Apple rejects the allegations and maintains that it follows the same App Tracking Transparency requirements as other developers.
The amount being sought is not a fine or an awarded payment. It is the claimants’ estimate of losses, which Apple disputes.
What the App Tracking Transparency Lawsuit Alleges
The action was brought by ATT Collective Action Limited, whose director, Ann Pope, previously led antitrust enforcement at the UK Competition and Markets Authority. Law firm Hausfeld is representing the proposed class.
According to Hausfeld’s announcement of the claim, developers argue that Apple introduced the framework unfairly, without adequate consultation, and applied more burdensome requirements to outside businesses than to its own services.
The complaint focuses partly on consent. It alleges that third-party developers must obtain permission under data-protection law and then secure an additional approval through the iOS tracking prompt. Apple’s advertising services, the claimants argue, operate under a less demanding process.
Developers also contend that the introduction left them insufficient time to adapt business models dependent on advertising.
These are allegations about how the system was designed and introduced—not established findings in this UK case. The claimants’ stated position is that privacy protections should remain compatible with fair treatment of businesses.
Image Credit: AppleMagazine
What the Tracking Prompt Actually Protects
For someone using an iPhone, App Tracking Transparency offers a direct choice about a practice that previously could be difficult to see.
An app may want to connect information about your activity with information gathered through other companies’ apps or websites. That connection can help advertisers build a profile, target advertisements, or measure whether an advertising campaign led to a purchase.
Under Apple’s explanation of the tracking rules, apps must request permission before carrying out the tracking covered by the framework. Choosing “Ask App Not to Track” blocks access to the system advertising identifier and prohibits using other identifying information to perform that tracking instead.
The feature arrived with iOS 14.5 in 2021. It does not remove advertisements, make an app anonymous, or serve as a universal switch for every kind of data collection.
That boundary matters. A retailer remembering purchases made within its own service is not automatically doing the same thing as an advertising company linking activity across unrelated businesses.
The disagreement concerns whether those distinctions, and the consent processes built around them, give Apple an unfair commercial advantage.
Apple Says the Same Rules Apply to Everyone
Apple has responded directly to the lawsuit, defending the feature as a way to give people control over tracking across other companies’ services.
In a statement reported by AFP, a spokesperson said: “Apple is bound by the exact same requirements as all developers under ATT.”
The company also pointed to support for the feature from customers and privacy advocates.
That response challenges the foundation of the developers’ case. Apple presents App Tracking Transparency as a rule based on the type of data activity involved. The claimants argue that its practical operation places competing advertising businesses at a disadvantage.
Resolving that disagreement requires more than comparing the appearance of two permission screens. The underlying data uses, consent requirements, and commercial effects all matter.
Why Free Apps Are Part of the Dispute
Advertising can support both sides of an app business. A developer may sell advertising space inside a free app while also buying advertisements elsewhere to attract new users.
A change to tracking can therefore affect how much an app earns and how confidently its developer can measure spending on promotion.
Consider a small game studio. It needs to know whether an advertising campaign brings in players who keep using the game. If measurement becomes less precise, deciding where to spend the next marketing dollar becomes harder. Separately, advertisers may value the game’s available ad space differently when less information is available for targeting.
That explains the commercial concern without proving the legal claim. Losing revenue after a privacy change does not, by itself, establish that the change was unlawful.
There is also a consumer interest that cannot be reduced to advertising performance. Someone choosing not to be tracked is expressing a preference about personal information, not making a promise to preserve a developer’s previous income.
The difficult question is whether that preference can be protected through a system that treats competing businesses fairly.
France Has Already Examined the Consent Process
The UK action arrives after a separate French competition investigation found problems with the implementation of App Tracking Transparency.
In its March 2025 decision, France’s Autorité de la concurrence distinguished between the legitimate objective of protecting privacy and the way Apple pursued it.
The authority criticized multiple consent requests and differences in treatment between Apple and outside publishers. It also highlighted the position of smaller businesses that lack the extensive first-party data available to large platforms.
Importantly, the French authority did not argue that people should lose the ability to refuse tracking. It said adjustments to the framework could address competition concerns while retaining privacy protections.
That distinction leaves room for changes to wording, consent flows, or implementation without automatically requiring the removal of the feature. The French decision, however, does not determine liability or compensation in the separate UK proceedings.
The Claim Is for Developers, Not iPhone Owners
The official claim website describes a proposed action for UK-based app developers affected since April 2021. It estimates losses across the group rather than offering a fixed payment to everyone who owns an iPhone.
The proposed scope includes developers earning advertising revenue from third-party iOS apps and developers spending money to attract users to those apps. Whether compensation becomes available depends on the proceedings and their outcome.
For U.S. readers, the filing does not announce a change to domestic iPhone settings or create a consumer refund program. There is no reason to grant an app tracking permission simply because its developer objects to the framework.
Businesses following the case should also distinguish registering interest from receiving compensation. The claim website currently invites affected organizations to provide their details; it is not distributing a settlement.
Recent versions of xOS (that is, macOS, iOS, iPadOS, etc) have Data Protection Classes from A to D that get assigned to files and folders.
[…]
The thing is, though, is that these files and folders are inaccessible unless the user is logged in, and the screen is unlocked. A few seconds after the screen locks (or you log out), the keys are purged, and they cannot be read.
[…]
That means the files any application considers to be worth protection cannot be accessed when a backup usually happens.
[…]
You may have noticed that if you had an overnight backup, when you unlock your screen, a copy starts to run. It’s typically quite brief, thanks to ⚡️Turbo Smart Update, but it might surprise you anyway. […] During your overnight copy, SuperDuper kept track of the files that it couldn’t access due to their protection class. And now that it can access them, it’s making sure they get backed up.
This seems like the right thing to do. Time Machine also does it. A backup app should try to make as faithful a backup as possible. I kind of find it annoying, though. Sometimes it can’t do a Turbo Smart Update, and so the backup that should already be done may end up taking another 30 minutes or more. The best thing to do is schedule backups while you’re using your Mac to avoid SuperDuper needing to do such “follow-ups.”
I wrote some code to try to figure out which files I have that are using data protection. Interestingly, the URLFileProtection API seems to not work on macOS. I used the lower level getattrlist() instead. Nanian recommends fcntl(). I didn’t find any protected files that I actually care about, just caches and derived data from Apple’s own apps. But, in theory, Apple or a third-party app could be saving actual user data using data protection.
Apple Health data can now move between the Health app and Google Health on an iPhone. The connection lets Google Health import supported information recorded by an iPhone, Apple Watch, and compatible apps. The latest Google Health update can also send supported Fitbit information to Apple Health.
This two-way connection is useful for people who wear a Fitbit but prefer Apple’s Health app as the central place for viewing activity, sleep, steps, and other wellness information. It also reduces the need for third-party synchronization apps.
The feature requires a recent version of Google Health. Google began introducing support for sending data back to Apple Health with Google Health version 5.05. Because app updates can roll out gradually, the new sharing options may not appear until the latest version reaches your account.
Update Google Health Before Starting
The Fitbit app became Google Health in 2026. Existing Fitbit users should find that the installed app has changed its name and design after updating. Fitbit accounts must also be moved to an adult Google Account to use the redesigned service.
Google says the Apple Health connection requires iOS 16.4 or later. The iPhone must have internet access while the connection is being created.
To check the iOS version installed on your iPhone:
Settings > General > About > iOS Version
Install the latest compatible iOS update if the phone is running an older release.
To look for an available iPhone software update:
Settings > General > Software Update
Next, confirm that Google Health is current. Version 5.05 or later is required for the newer option that sends supported Google Health and Fitbit information to Apple Health.
To update Google Health from the App Store:
App Store > Profile Picture > Available Updates > Google Health > Update
If Google Health does not appear under Available Updates, search for the app manually. The App Store page may show an Update button if a newer release is available.
To find the app directly:
App Store > Search > Enter Google Health > Google Health (Fitbit)
People who previously used Fitbit should sign in with the Google Account connected to their Fitbit information. Creating a different account may produce an empty Google Health profile.
Image Credit: Google
Connect Apple Health Data to Google Health
Connecting the apps allows Google Health to read supported information from Apple Health. This can include data collected by the iPhone, Apple Watch, and other apps that already share information with Apple Health.
To start the Apple Health connection:
Google Health > Connections > Apps and Services > Apple Health > Get Started
Depending on the Google Health version and interface shown on the iPhone, Connections may appear behind the profile icon.
To find Apple Health through the alternative menu:
Google Health > Profile Icon > Partner Apps > Apple Health
Google Health will display a consent screen explaining the connection. Read the information before continuing.
To approve the initial connection:
Sync Google Health With Apple Health > Agree
The iPhone will then display Apple’s health permission screen. This screen lets you decide which information Google Health can read.
To give Google Health access to every supported category:
Apple Health Permission Screen > Turn All Categories On > Allow
You do not have to share every available category. Selecting individual permissions provides more control over sensitive health information.
To share only selected categories:
Apple Health Permission Screen > Select Each Health Category > Allow
Google Health can import supported information such as steps, distance, active energy, exercise records, routes, sleep sessions, sleep stages, heart rate, resting heart rate, heart rate variability, blood oxygen, respiratory rate, body temperature, weight, body fat percentage, water, nutrition information, and some cycle-tracking data.
Available categories depend on the devices and apps connected to Apple Health. An iPhone may provide steps and walking information, while an Apple Watch can contribute heart rate, workouts, sleep, and other measurements supported by the model.
After the permissions are approved, Google Health should confirm that the connection is complete.
To finish the connection:
Google Health Confirmation Screen > Done
New Apple Health information should begin appearing automatically in Google Health. Google has said that imported data can be used across relevant Google Health metrics, although not every external data type is used for every calculation.
To find imported health information:
Google Health > Health > Select a Metric
Google Health may display information from several connected sources together. Its value for a metric can differ slightly from the number shown by Apple Health because the apps may process available data differently.
Send Fitbit Data to Apple Health
Google Health version 5.05 adds the reverse direction that many iPhone and Fitbit users previously lacked. Supported information recorded through Fitbit can now be written into Apple Health.
Before enabling this option, make sure the Fitbit is properly connected to Google Health. Fitbit devices normally synchronize automatically throughout the day when Bluetooth is available and the wearable is near the iPhone.
To check the connected Fitbit:
Google Health > Profile Icon > Devices > Select Your Fitbit
The device page should show the wearable, its battery level, and its most recent synchronization time. Opening Google Health can also prompt a nearby Fitbit to transfer recently collected information.
Once the wearable is updating Google Health correctly, open the Apple Health connection settings.
To open the sharing controls for Apple Health:
Google Health > Profile Icon > Partner Apps > Apple Health
The interface may use Apps and Services instead of Partner Apps on some versions.
To reach the same connection through Apps and Services:
Google Health > Connections > Apps and Services > Apple Health
Follow the prompts for sharing Google Health information with Apple Health. The iPhone may display separate permissions for data that Google Health can read and data that it can write.
To allow supported Fitbit information to appear in Apple Health:
Apple Health Permission Screen > Allow Google Health to Write > Select Health Categories > Allow
Google says supported information can include exercise records, steps, sleep, vitals, and other health data. The exact selection can vary according to the Fitbit model, region, Google Health version, and information stored in the account.
Selecting every category is convenient, but it can create overlapping sources when an iPhone, Apple Watch, and Fitbit record the same type of activity. Choose only the categories you want Google Health to add.
A person who uses a Fitbit mainly for sleep, for example, can allow sleep information while leaving steps disabled. Someone who wears a Fitbit instead of an Apple Watch may prefer to enable steps, workouts, heart rate, sleep, and other supported categories.
Image Credit: AppleMagazine
Check Google Health Permissions
Apple Health keeps permission controls on the iPhone. You can change them after the first connection without deleting either app.
To review Google Health access from Apple Health:
Health > Profile Picture > Privacy > Apps > Google Health
The page shows the categories Google Health is permitted to read or update. Turn off any category you no longer want to share.
Some iOS versions provide the same controls through the Sharing tab.
To find Google Health through the Sharing tab:
Health > Sharing > Apps and Services > Google Health
Turning off a permission stops future sharing for that category. It does not necessarily remove information that has already been written to Google Health or Apple Health.
The Google Health app also provides controls for the connection.
To review Apple Health inside Google Health:
Google Health > Connections > Apps and Services > Connected > Apple Health
If Google Health displays a message that new data types are available, open the connection and approve the additional categories you want to use. Newly supported information is not automatically shared without permission.
Manage Duplicate Health Information
An iPhone, Apple Watch, and Fitbit can record similar information at the same time. Apple Health keeps each source attached to its data and uses a priority order when presenting combined measurements.
You can inspect the sources contributing to a category and choose which one Apple Health should prefer.
To review the sources used for step information:
Health > Search > Activity > Steps > Data Sources and Access
The screen shows the apps and devices that provide step records. If Google Health, an Apple Watch, and the iPhone all appear, you can adjust their priority.
To change the order of step sources:
Health > Search > Activity > Steps > Data Sources and Access > Edit > Drag Sources Into the Preferred Order > Done
Move the source you trust most toward the top. Apple Health generally gives higher priority to sources placed above others when similar records overlap.
Repeat the same process for other categories if their totals do not look right. Exercise, sleep, active energy, and distance can each have their own sources and permissions.
Image Credit: Google
Fix Missing or Delayed Data
Synchronization is not always immediate. A Fitbit first sends its information to Google Health, and Google Health then writes supported records to Apple Health. Bluetooth availability, Background App Refresh, internet access, and battery-saving behavior can affect this process.
Begin by opening Google Health with the Fitbit close to the iPhone. Wait for the device to complete its normal synchronization before checking Apple Health.
If Apple Health information is missing from Google Health, confirm that the connection remains active.
To check the connection status:
Google Health > Connections > Apps and Services > Apple Health
If Google Health displays an error or a request for new permissions, follow the message shown on the screen.
Background App Refresh can help Google Health update when the app is not open.
To allow Google Health to refresh in the background:
Settings > General > Background App Refresh > Google Health > On
Bluetooth must remain available for a Fitbit to communicate with the iPhone.
To confirm that Bluetooth is enabled:
Settings > Bluetooth > Bluetooth On
If the connection continues to fail, disconnecting and reconnecting Apple Health may restore the permission request.
To disconnect Apple Health from Google Health:
Google Health > Connections > Apps and Services > Apple Health > Disconnect > Confirm Disconnect
Disconnecting the service does not automatically remove every permission already stored by Apple Health. Review the Google Health entry in the Health app if you want to remove those permissions as well.
To remove the remaining Apple Health permissions:
Health > Profile Picture > Privacy > Apps > Google Health > Turn Off All
After reconnecting the apps, allow time for new records to appear. Previously stored information may not transfer in exactly the same way as activity recorded after the connection was enabled.
You can inspect an individual entry to confirm whether it came from Google Health, a Fitbit, an Apple Watch, or the iPhone.
To check the source and time of a synced record:
Health > Search > Select a Health Category > Show All Data > Select the Latest Entry
ChatGPT Health is returning with substantially wider access, giving more iPhone users the option to connect information from Apple Health directly to the AI assistant.
The expansion follows a limited test introduced in January. OpenAI is now gradually making the dedicated Health experience available to eligible ChatGPT Free, Go, Plus and Pro users in the United States who are at least 18 years old.
Despite the close Apple connection, this is not a feature created by Apple or built directly into the Health app. OpenAI operates the service through ChatGPT, while Apple Health serves as one of the sources users can voluntarily connect.
Once permission is granted, ChatGPT can examine selected health and fitness information stored on iPhone, including activity, sleep, workouts and other measurements collected by compatible apps and devices. Users can then ask questions about changes over time without manually exporting records or uploading screenshots during every conversation.
Image Credit: OpenAI
ChatGPT Health Reaches More iPhone Users
ChatGPT Health originally appeared as a limited early-access experience for a small group of testers. The expanded rollout replaces that narrow availability with support for eligible adult users across the United States, although OpenAI says access may take several weeks to reach every account.
The feature works on the ChatGPT website and iOS app, but connecting Apple Health requires an iPhone. Users also need a recent version of the ChatGPT app before the Health option appears in the sidebar or More menu.
Apple Health is only one part of the system. ChatGPT can also connect to supported medical-record portals, One Medical and Function Health. Bringing those sources together allows the assistant to answer questions using a broader personal context than activity data alone.
A user could ask how sleep duration has changed across several weeks, whether workout frequency declined after a schedule change or how recent laboratory results compare with earlier tests. ChatGPT can also help organize questions before a medical appointment or summarize changes found across connected records.
Information from third-party fitness services can reach ChatGPT through Apple Health when those apps already share their data with the iPhone database. That may include measurements from platforms such as Garmin, Oura, Whoop, Strava and MyFitnessPal, depending on which categories each service makes available.
Not every proprietary score transfers. An app may calculate its own readiness, recovery or sleep score without writing that exact result into Apple Health. ChatGPT can only use the information made available through the connected source and approved by the user.
After synchronization, health information can inform responses throughout ChatGPT rather than remaining limited to conversations opened from the Health tab. The assistant normally asks for permission before using connected information, and users can also add “@Health” to a prompt when they specifically want a response based on their records.
Image Credit: OpenAI
Apple Health Data Gains a Conversational Layer
The appeal of the integration comes from turning a large collection of measurements into questions expressed in ordinary language.
Apple Health can already organize trends, highlights, medications, laboratory results and activity records. ChatGPT adds a conversational layer capable of comparing those categories or explaining them in a more personalized format.
Someone preparing for an annual physical could ask for a summary of meaningful changes since the previous appointment. A runner might request a comparison between training volume, sleep and resting heart rate. Another user could ask which information deserves discussion with a clinician after receiving new laboratory results.
That does not make ChatGPT a doctor. OpenAI says the feature is intended to support medical care rather than diagnose conditions or recommend treatment. Urgent symptoms and emergencies still require professional assistance.
The distinction is especially important because health data can appear more conclusive than it is. A change in heart rate, sleep or activity may have several explanations that cannot be determined from an iPhone record alone. Wearables can identify patterns, but they do not automatically reveal the medical cause behind them.
ChatGPT may help users notice relationships and prepare better questions. It should not be treated as the final authority on whether a symptom is harmless, whether medication should change or whether professional care is unnecessary.
The service is also read-only. ChatGPT can examine approved Apple Health information but cannot alter the original records stored on iPhone. It cannot add a diagnosis, change a medication list or write new measurements back into the Health app.
Users retain control over which Apple Health categories are shared. Someone may allow access to steps, workouts and sleep while withholding reproductive health, medications or other sensitive information.
That selective approach may be more appropriate than approving every category simply because the option is available. A useful response does not always require a complete health history.
Image Credit: OpenAI
Privacy Becomes the Central Decision
Connecting Apple Health to ChatGPT creates a different privacy relationship from using health features entirely within the Apple ecosystem.
Apple designs the Health app around on-device protections and user-controlled permissions. ChatGPT Health requires selected information to synchronize with OpenAI systems so the company can analyze it and generate personalized responses.
OpenAI says connected Apple Health data, medical records and conversations using that information are not used to train its foundation models or target advertising. The company also applies additional encryption and isolation protections to health information.
Users can disconnect Apple Health at any time. OpenAI says synchronized data from the disconnected source will be deleted from its systems within 30 days.
Previous conversations are handled separately. Information already included in ChatGPT conversation history remains until those chats are deleted, even after the Apple Health connection is removed.
Memory introduces another consideration. Conversations using Health can create memories when ChatGPT memory is enabled, although OpenAI says memories are not generated directly from synchronized health data. Temporary Chat or separate project memory can reduce how much personal context continues across future conversations.
The new Health experience should also not be confused with the existing ChatGPT integration inside Apple Intelligence. Siri and Writing Tools can use ChatGPT for certain requests without requiring the dedicated ChatGPT app or a connected account.
ChatGPT Health is a separate OpenAI service with its own account, permissions, privacy controls and health-data connections. Using ChatGPT through Siri does not automatically give OpenAI access to Apple Health.
That separation gives users a meaningful choice. They can continue keeping health information inside Apple apps, share only selected categories with ChatGPT or connect medical records for a more comprehensive view.
The expanded rollout makes one of the most personal databases on iPhone available to conversational AI. Its usefulness will depend not only on the quality of the answers, but also on whether users understand exactly which information they are sharing and where it goes after leaving the device.
Login
