r/OpenAI • u/curiousinquirer007 • 22h ago
Discussion Why I will not use Dots: Insufficient visibility and controls for privacy and info separation.
TL;DR: I won’t use Dots without inspectable, selectively deletable memory and explicit controls over cross-domain sharing. I also need architectural transparency to assess privacy risks and manage quality over time. Until then, hard pass.

----------
An always-on agent sounds like great idea for someone doing one clearly defined kind of work and using it for that work. What about (the vast majority of) users that use AI across various domains in professional and personal life?
What someone tells their life advice AI about their mistress is none of their work assistant AI’s business. Their legal counselor AI, healthcare adviser AI, dating coach AI, therapist AI, and dietitian AI should not automatically share context just because they serve the same person.
Yet, OpenAI currently provides a single dot that can retain information from conversations and connected apps for as long as you keep it, without letting us inspect, edit, or delete individual memories. That is a lot of trust to ask for across completely different parts of someone’s life.
Could some overlap help serve the user better overall? Sure. Then let the user choose which information crosses the boundary, for what purpose, and for how long.
Otherwise, deeply personal information can enter persistent state we cannot audit, and we're supposed to trust that it won’t resurface in unrelated work or reach an external service? Without enforceable boundaries, a single know-everything Dot sounds like a privacy nightmare waiting to happen, even if you don't exactly hold state secrets.
And yes, ChatGPT has "Memory". It also has controls to review and delete saved memories and turn memory off. I have turned it off, for example. That choice is precisely the point.
Also, privacy and cybersecurity used to be a bolt-on during early internet days, but it's long since they've become first-class citizens in any serious app, with security being built-in from the start.
Permission should be denied by default, with clear user control. Access to one part of a user's life should not quietly become permission to use it every other part indefinitely. How about narrow, role-specific permissions, with default expiration and easy revocation? What happened to minimizing attack surface, blast radius, and unnecessary information-sharing? An internal action check is not the same as preventing an unrelated task from receiving sensitive information in the first place.
(Some of these are fancy-sounding cybersecurity language but they're pretty standard in pre-AI web apps, from your banking to your Cloud productivity suites).
-------
Also important: what happened to letting us understand the architecture itself?
There is documentation about persistent notes, selected context, and delegation, but I still lack a sufficiently clear end-to-end picture. Where do the components run? Where are the LLMs, what does the harness do, and where does persistent state live? What enters each inference? Who or what decides? What is the compaction policy?
What happens after I’ve used this thing for a year?
Context size used to mean degradation over time, and “Lost in the Middle” showed that information can be present in context without being used reliably. Compaction and handoffs try to address this in modern agents but raise another problem: information loss.
Still, with enough public documentation about how Codex handles this (and how agentic harnesses work in general), I've been able to research these (often with GPT's help), because it changes how I work: when to branch or start fresh, how to structure multi-agent delegation, when to restart against the same project directory, and how to check a summary against preserved original context.
Voice is another good example. Knowing GPT-Live separates live conversation from backend work helps distinguish an immediate response from the analysis arriving later. Understanding the system helps me not be put off by the shallowness of the front LLM and wait for intelligence to come from the back-end model's reasoning — with managed expectations given the lossy handoff process.
Yet, so far I've been able to find very little about what Dots actually look like in terms of harness and persistence architecture.
Without more info about Dots, I have not idea what user-side QA looks like, and what the failure modes are. I'd need equivalent understanding to get sustained quality from Dots comparable to a frontier reasoning model working with carefully assembled context.
LLMs may be closed, but before I'm comfortable jumping on the Dots train, I'd want a documented deployment, data-flow, and persistence architecture; enforceable boundaries between domains; inspectable and selectively controllable memory; and guidance on managing long-running context without losing essential information.
With that, I could assess where it belongs and how to use it well. Until then, as much as I like checking out new tech, hard pass for me.
Disclaimer: this post was drafted using my original draft and multiple iterative drafts with GPT-6-Astra (Pro) and myself, with final draft edited and approved by me.
cc: u/tibo-openai

