6 min read<\/p>\n
On 13 August 2026, OpenAI described Computer History for the ChatGPT Mac app in its release notes. The feature can track selected app and website activity within ChatGPT and Codex. It will remain unavailable in the EEA, the United Kingdom and Switzerland for the time being.<\/strong><\/p>\n Key Takeaways<\/p>\n Related<\/span>Shadow AI is becoming a governance headache for CIOs<\/a> \/<\/span> AI Regulation: Up to 3 Percent of Corporate Revenue<\/a><\/p>\n What is Computer History?<\/strong> Computer History is an optional feature in the ChatGPT macOS app. It records interaction events from selected apps and websites so that ChatGPT and Codex can build on them. Screenshots, screen recordings, microphone input and system audio are not included. The feature is disabled by default and currently unavailable in the EEA, the United Kingdom and Switzerland.<\/p>\n The announcement appears in the release notes rather than a keynote. OpenAI describes Computer History as an optional feature of the ChatGPT Mac app: ChatGPT and Codex can reference selected activity from apps and websites so users can pick up where they left off without re-explaining every detail. That sounds convenient. For a DACH organisation, it raises a governance question: pulling the activity history of selected apps into a language model pulls working context across device boundaries.<\/p>\n That\u2019s where the conflict begins. US teams can test the context gain. European and Swiss teams cannot, according to OpenAI. When a vendor promises a unified AI workflow, a single feature delivers two speeds.<\/p>\n OpenAI sharply limits the scope. Computer History records interaction events. The notes explicitly exclude screenshots, screen recordings, microphone input and system audio, as well as private browsing. Users can pause the feature, select which apps and sites to include, and review or delete timeline entries.<\/p>\n This is less than a full screen recording and more than a chat history. An interaction event can reveal which app someone was using, which sites were open and how a session should resume. Once it can be tied to an individual, it becomes employee data. The legal category does not depend on whether a screenshot exists in a folder.<\/p>\n Two boundaries remain open because OpenAI does not address them in the notes. Which exact event fields are generated is not specified. Nor is it clear how long the timeline is retained on OpenAI\u2019s side. Teams preparing to pilot the feature later in the EEA will need to clarify both points in the contract and in their record of processing activities-before the first admin flips the switch.<\/p>\n The control architecture is clearer than the data scope. Computer History is disabled by default. OpenAI lists Pro, Business, and Enterprise as intended tiers. In ChatGPT Business, a workspace admin must grant access before members can decide. In Enterprise, admins can assign access based on roles. After that, the individual opt-in remains with each person.<\/p>\n This is a practical operating model. It separates three levels: who may see the feature at all, who may enable it for themselves, and which apps and sites may appear in the timeline. For DACH companies, this becomes the template once the regional block is lifted. For now, it mainly serves as an inventory aid. Users in the US or other available regions running ChatGPT Business or Enterprise on Mac already need a written admin policy; without it, the local admin decides ad hoc.<\/p>\n The note in the release is clear and concise: Computer History is currently unavailable in the EEA, the UK, and Switzerland. OpenAI provides neither a reason nor a timeline. Anyone speculating \u201cbecause of GDPR\u201d or \u201ccoming in autumn\u201d is guessing. The only reliable information is the regional boundary itself.<\/p>\n For governance purposes, this boundary suffices. An AI workflow that pulls context from the device only works where OpenAI enables it. DACH teams stay limited to chat and file context, while US teams can additionally leverage app history. That skews comparability: a New York Codex session starts with more prior knowledge than a Munich one. When measuring productivity, you\u2019re comparing two different tools.<\/p>\n The second consequence lies in shadow-AI risk. The regional block lowers the chance that someone in Frankfurt enables the feature secretly, but it doesn\u2019t eliminate the risk that the same person uses a foreign account or travels to an enabled region. OpenAI does not describe this workaround. A clear internal usage policy for corporate devices and accounts remains essential-especially since the notes label the exclusion as \u201ccurrently.\u201d<\/p>\n Once Computer History arrives in the EEA, this isn\u2019t just an IT update. Interaction events from work apps can reveal behavior and performance. In Germany, co-determination under \u00a7 87 para. 1 no. 6 Works Constitution Act (BetrVG) typically applies because the technical system can monitor behavior or performance. This isn\u2019t a preemptive judgment of OpenAI. It\u2019s the standard situation for tools that log work context.<\/p>\n Data protection follows the same path. Purpose, legal basis, retention periods, data processing agreements, and the question of who is the controller must be in place before the admin enables roles. A data protection impact assessment is likely required because the processing is systematic and involves personal data in the workplace. In Switzerland, the revised Data Protection Act (nDSG) applies analogously to employee personal data. In the UK, the exclusion remains explicitly stated in the notes despite Brexit.<\/p>\n In practice, this means: the time until a possible EEA launch belongs to preparation, not waiting. Take inventory of which Macs use ChatGPT or Codex for work. Ban private pro-accounts on company devices outright. Put contract questions to OpenAI in writing: event fields, retention, storage location, training exclusion, admin logs. Draft a works agreement now-not after the rollout email.<\/p>\n The decision in DACH today is threefold. First: Computer History stays out of the EEA, UK, and Switzerland. Second: where it runs, it belongs under admin policy and app whitelisting, not under individuals. Third: productivity comparisons between regions remain unreliable as long as only one side can use the computer context.<\/p>\n Being transparent about this defuses the debate. The comfort gain is real once the feature arrives. The cost is a new class of work context within a US model. OpenAI has set the switch to default off and admin first-that\u2019s the usable line. The organization only needs to translate it into roles, devices, and a works agreement-and until then, honestly admit that DACH doesn\u2019t yet have that lever.<\/p>\n OpenAI, ChatGPT Release Notes dated 13 August 2026, confirmed in Business and Enterprise notes. Help Center text status: 16 August 2026.<\/p>\n OpenAI excludes screenshots, screen recordings, microphone input, and system audio from Notes. Only interaction events from selected apps and websites are stored. Private browsing remains unaffected.<\/p>\n<\/details>\n According to OpenAI, Computer History is currently unavailable in the EEA, UK, and Switzerland. An opt-in is not provided for these regions, as stated in the Notes.<\/p>\n<\/details>\n Technically, yes. Organizationally, no. Business and Enterprise plans require an additional admin policy, an app whitelist, and clear guidelines for company devices.<\/p>\n<\/details>\n If this feature becomes available in Germany, co-determination under \u00a7 87 Para. 1 No. 6 BetrVG is likely required. Technical systems capable of monitoring behavior or performance typically fall under this provision.<\/p>\n<\/details>\n OpenAI does not provide a date in the Notes. Only the current exclusion of the EEA, UK, and Switzerland is confirmed. Internal preparations can still begin now.<\/p>\n<\/details>\n More from the MBF Media Network<\/p>\n\n
What Computer History on the Mac actually stores<\/h2>\n
Admin approval determines access before opt-in<\/h2>\n
\n\n
\n \nTier<\/th>\n OpenAI\u2019s description<\/th>\n What the organization must define<\/th>\n<\/tr>\n<\/thead>\n \n Pro, Business, Enterprise<\/td>\n Feature available, disabled by default<\/td>\n Which plans and devices are in scope<\/td>\n<\/tr>\n \n Business \/ Enterprise<\/td>\n Admin grants access, then individual opt-in<\/td>\n Which roles may see the toggle<\/td>\n<\/tr>\n \n EEA, UK, Switzerland<\/td>\n currently excluded<\/td>\n How international teams maintain a single workflow<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n EEA, UK and Switzerland remain excluded for now<\/h2>\n
Works Council and Data Protection Take Priority Over the Pilot<\/h2>\n
International Teams Need a Split Rule<\/h2>\n
Frequently Asked Questions<\/h2>\n
Does Computer History record the screen?<\/strong><\/summary>\n
Can employees in Germany enable this feature?<\/strong><\/summary>\n
Is the default-off setting sufficient for governance?<\/strong><\/summary>\n
Does the works council need to be involved?<\/strong><\/summary>\n
When will Computer History be available in the EU?<\/strong><\/summary>\n