ChatGPT Computer History Privacy

You can now ask ChatGPT what you were doing across apps and websites on your Mac, then turn that trail into a recap, a found document, a draft timesheet, or a reusable workflow. For a team already paying $20 per user each month for ChatGPT Business on annual billing, that creates a serious chance to absorb work-recall and process-capture jobs into an existing seat. The trade is privacy: raw interaction events stay temporarily on the Mac, OpenAI processes them to make summaries, and the resulting local memory files remain unencrypted until you clear them.

The short answer on privacy

ChatGPT Computer History is private by choice, not private by architecture. It is off by default, starts only after each person opts in, and lets you restrict the apps and websites that contribute. It does not record screenshots, screen video, microphone input, system audio, or private-mode browsing.

It still captures sensitive material. The event stream can include clicks, typing, keyboard shortcuts, app switches, and context macOS exposes through Accessibility. OpenAI processes those events on its servers to generate memories. OpenAI says it does not retain the temporary event files after processing unless required by law and does not use those event files for training. The generated memories come back to the Mac as readable, unencrypted Markdown files that remain until you delete them.

That distinction matters. This is closer to a detailed flight recorder than a security camera. It does not keep a movie of your screen, but it can still reconstruct which controls you touched, what you typed, which app you moved into, and what work context surrounded those actions.

What ChatGPT Computer History actually is

Computer History turns activity from approved Mac apps and websites into a time-ordered set of summaries and memories that ChatGPT and Codex can use. You can ask what you were doing before a break, refer to a document the way you remember it rather than by filename, prepare a standup recap, or turn a repeated workflow into a skill or automation.

It replaces the Chronicle research preview, but it is a rebuilt system. Chronicle used screenshots. Computer History records interaction events and periodically condenses them into text.

The privacy model has five distinct stages:

The last row is easy to miss. OpenAI says the temporary event files used for summarization are not used for training. But when a future chat uses a memory, relevant memory content and interaction events may become chat context. That chat content may help improve OpenAI models if your account's Data Controls allow it. Turning off Improve the model for everyone keeps conversations in your chat history while stopping their use for model training.

The business math changes before the workflow does

Computer History can remove the need to buy a separate experiment, but it does not automatically replace a mature time tracker or documentation platform.

OpenAI's current pricing puts Business at $20 per user per month with annual billing, or $25 monthly. Pro starts at $100 per month, while Enterprise is quote-based. Computer History is included only for Pro, Business, and Enterprise users, not Plus users.

Now compare the adjacent budget lines. Memtime's annual Basic plan for automatic time tracking is $14 per user per month. Scribe Pro Team is $13 per seat per month annually, with a five-seat minimum. A ten-person team that already has ChatGPT Business could therefore pilot passive work recall and raw workflow capture before adding $270 per month in separate Memtime and Scribe seats.

Do not cancel either tool on this math alone. Computer History does not promise exact billable durations, project-code exports, polished SOP layouts, version control, or compliance records. The practical decision is to run a narrow pilot against one real workflow. If the timeline produces useful raw material, buy or build only the missing last mile.

For a broader view of where this sits in the product, the current ChatGPT review covers the surrounding plans and use cases.

How to turn it on without making a privacy mess

The safest default is an allowlist, not a cleanup project. Start with only the sources needed for one low-risk workflow.

1. Confirm eligibility. Computer History currently requires the ChatGPT desktop app on macOS, an eligible Pro, Business, or Enterprise plan, and Memories. It is unavailable through an API key or Amazon Bedrock, and it is not currently offered in the EEA, Switzerland, or the United Kingdom.
2. Separate admin access from personal consent. A Business or Enterprise administrator first grants access to an eligible role. That does not activate the feature. Every member still has to opt in.
3. Choose only the sources you need. Under Computer History permissions, use Include only these apps and Include only these websites for the pilot. Exclusions are useful later, but a short allowlist makes the initial data boundary visible.
4. Pause around people and sensitive work. OpenAI advises turning collection off during communications with other people unless they gave prior express consent. Health, financial, legal, HR, password, and personal apps should stay outside the first pilot.
5. Inspect before you trust. After a work session, open the History timeline, read every summary, reveal a memory file in Finder, and test deletion. You can clear the last 10 minutes, hour, day, all history, or a recent app session. Clearing also deletes memories created from those events and cannot be undone.
6. Set the future-chat rule. Decide whether chats may use local memories and whether those chats may contribute to later memories. Review Improve the model for everyone under ChatGPT Data Controls separately.

Computer History does not require Screen Recording permission. If setup asks for broad permissions that do not match the documented flow, stop and recheck the app, plan, workspace role, and current OpenAI instructions.

The seven use cases, ranked by who profits first

1. Client-service teams reconstruct billable work

An agency strategist or independent consultant often ends the day with fragments spread across Slack, documents, browser research, and deliverables. Computer History could identify those sources and produce a draft account of what happened in sequence. The operator then maps the work to client codes and confirms the time rather than rebuilding the day from memory.

The payoff is fewer missed entries and less non-billable admin. The boundary is precision: use the output as a draft, never as an automatic invoice or payroll record.

2. Operations leaders turn repeated work into a reusable process

An operations manager can complete a recurring launch, reporting, or content-publishing workflow with collection enabled only for the necessary tools. If Computer History notices a repeated pattern, its timeline can suggest a skill or automation. The manager reviews the sequence, adds the decisions the event log could not know, and publishes the approved process.

This attacks the same budget line as workflow-documentation software. It pays when the expensive part is getting a busy expert to recall every step, not when the company already has excellent, maintained SOPs.

3. Product and engineering leads create cleaner handoffs

A product lead who moves between a spec, issue tracker, Slack thread, prototype, and release note can ask for a recap of the day's work and the decisions still open. Computer History can use the timeline to locate the relevant source, then ChatGPT or Codex can read that source directly when permitted.

The payoff is less reconstruction at standup and fewer links lost between tools. The summary is context, not the source of truth. The issue, document, or repository still owns the final decision.

4. Founders recover fuzzy recent work

A founder may remember that a pricing assumption appeared in a document reviewed yesterday but not remember its title or folder. Computer History is designed for that kind of human reference. The founder asks for the planning document they were looking at, verifies the source, and continues from the exact place they stopped.

This pays by shortening search across a fragmented stack. It is most useful for recent work, not as a permanent company archive.

5. Account teams prepare follow-ups from the actual work trail

An account manager can use a tightly limited set of approved sources to reconstruct which proposal, internal thread, and deliverable were touched before a client follow-up. ChatGPT can turn the verified trail into a checklist of unresolved actions.

The payoff is continuity when several accounts move at once. The privacy requirement is strict: pause during client calls unless everyone has given prior express consent, and exclude communications that do not belong in the history.

6. Researchers preserve the route to a conclusion

A market researcher can let selected browser sites and document apps contribute while working through a question. Later, the timeline can help find the sources used and reconstruct the order in which the thesis changed.

The payoff is faster return to an unfinished investigation. It does not make a citation true. Every quoted number and conclusion still needs verification against the original source.

7. Workspace administrators run a policy pilot before rollout

An Enterprise administrator can grant access to one low-risk role without turning the feature on for anyone. In Business, an administrator can keep the pilot narrow because workspace access still does not opt anyone in. One volunteer enables it, uses a narrow allowlist, reviews the local memories, tests clearing, and documents what appeared that the policy team did not expect.

The payoff is a real control decision rather than a debate based on the feature name. This is the right first use for a regulated or privacy-sensitive company.

Three products worth building around Computer History

1. A local privacy guardrail, the strongest opportunity

Build a local-only audit tool that scans Computer History's Markdown memories as untrusted data, flags likely health, financial, credential, client, and personal information, and produces a guided remediation list. The buyer is a security-conscious individual, a small-company IT lead, or an Enterprise pilot owner who needs proof that the allowlist is behaving as intended.

The demand signal is unusually sharp for a new feature. ChatGPT privacy settings gets about 170 Google searches a month, is up 27% year over year, and carries a $72.63 CPC. The high top-of-page bid reaches $57.50. DataForSEO's ChatGPT citation check returned no cited domains for that job, so there is not yet a settled source layer answering the new Computer History questions.

The smallest sellable version is a signed Mac utility or local Codex skill that reads the documented memory directory, treats every line as content rather than an instruction, categorizes exposure, and links each finding to the exact file and the manual setting the user should change. It should never upload the scan.

The catch is severe: a privacy scanner becomes another program with access to sensitive local files. Offline operation, a transparent ruleset, and prompt-injection resistance are the product. OpenAI could also add native redaction or policy reports, so the durable edge has to be auditability across more than one AI memory system.

2. A human-approved timesheet assistant

Build a local workflow that maps Computer History summaries to client and project codes, asks the worker to confirm gaps and durations, then exports a draft CSV for the billing system. Agencies, lawyers, consultants, and fractional operators pay when incomplete time capture turns directly into lost revenue.

AI time tracking gets about 170 Google searches a month with commercial intent and a $19.65 CPC. People ask AI assistants for it about 59 times a month. Memtime charges $14 per user per month on its annual Basic plan, which proves buyers already pay for passive reconstruction.

The MVP needs a project-code mapping file, a local parser for recent memories, a review screen, and one export format. The catch is accuracy. Computer History is not documented as a precise clock, so the product must draft and ask, never auto-submit billing or payroll.

3. A governed workflow-to-SOP compiler

Build a review layer that turns a repeated Computer History workflow into a versioned SOP, asks the process owner to supply missing decisions, redacts sensitive context, and routes the result for approval. The buyer is an operations team that wants living documentation without asking every expert to narrate a clean demo.

Workflow documentation software gets about 90 Google searches a month, is up 27% year over year, and has keyword difficulty 0. People ask AI assistants about workflow documentation roughly 100 times a month. Existing products reinforce the budget: Tango Pro Team costs $15 per user per month annually, while Scribe Pro Team costs $13 per seat with a five-seat minimum.

The MVP is a local skill plus a lightweight approval and version-history service. The catch is competition from the platform itself, because Computer History already suggests skills and automations. The product earns its place through governance, redaction, ownership, review dates, and distribution, not through basic step extraction.

Limits and the honest take

Computer History is useful, but it is not a harmless memory switch.

• It is narrow in availability. It currently needs the macOS ChatGPT desktop app, Memories, and a Pro, Business, or Enterprise plan. There is no API-key or Bedrock route, and several European regions are excluded.
• No screenshots does not mean no sensitive data. Typing and accessibility context can still expose names, messages, figures, searches, and document details.
• Local does not mean encrypted. The generated Markdown memories remain readable on the filesystem and are not encrypted by Computer History.
• Temporary does not describe every artifact. Event files last up to 48 hours, but generated memories last until you clear them.
• Server processing still happens. OpenAI summarizes temporary events on its servers, even though it says it does not retain those event files after processing unless legally required and does not train on them.
• Later chats have their own data rule. Once a memory enters a future chat, model-improvement use follows that account's ChatGPT Data Controls.
• Observed content can attack the observer. OpenAI explicitly warns that content in apps and websites can increase prompt-injection risk.
• It is not an audit system. Do not use summaries as payroll evidence, a legal archive, an employee-surveillance record, or a substitute for consent.

The right buyer is someone whose main cost is reconstructing recent work. The wrong buyer needs exact time, defensible records, broad employee monitoring, or zero server processing.

Is ChatGPT history confidential?

Computer History gives you opt-in, source, pause, review, and deletion controls, but it can still contain confidential material. Temporary events are processed by OpenAI to make memories, and generated memories are unencrypted local Markdown. Treat the feature as sensitive work data, not as a private vault.

Does ChatGPT know your browsing history?

Computer History starts only after you turn it on and records interaction events from websites you allow. Private-mode browsing is never included. It does not capture a screen recording, but allowed-site events and exposed context can still reveal what you did there.

Can my employer see my ChatGPT history?

OpenAI's Computer History documentation says Business and Enterprise administrators control access to the feature, while each person controls opt-in and local history. It does not state that granting access gives an administrator a viewer for an individual's Computer History. A company-managed Mac can have separate device, security, and retention controls, so check the employer's policy before enabling it.

Should I delete ChatGPT history?

Delete a Computer History item when it contains material you did not intend to keep, and change the app or website permission so the source does not contribute again. Clearing removes the relevant events and memories and cannot be undone. If the content entered a later chat, review that chat and your Data Controls separately.

How do I make my ChatGPT private?

For Computer History, keep it off until you have a specific job, use an include-only source list, pause around communications and sensitive work, inspect the resulting memory files, and turn off Improve the model for everyone if you do not want eligible chats used for model improvement. Those controls reduce exposure, but they do not turn the feature into an offline encrypted system.

Your Monday move

Enable Computer History for one volunteer and one low-risk workflow, allow only three necessary sources, run it for one workday, inspect every generated memory, and clear the test. Record whether it found a document, recovered billable work, or captured a reusable process that the team would otherwise have reconstructed manually. Expand only when that benefit is worth the data boundary you observed.

If you want that pilot turned into a governed workflow for your business, I can build the automation with you.