DadGPTPrivacy, without vague promises
The current plugin is skills-only. It has no DadGPT-operated server, analytics endpoint, account system, or API connection in the conversation path. OpenAI still processes your conversation as part of ChatGPT.
No publisher chat dashboard
There is no technical endpoint in this release through which DadGPT’s publisher receives ordinary chat messages.
The data path
“The publisher cannot see it” is not the same as “no company processes it.” These are separate privacy boundaries.
Your message, attachments, account context, and any enabled ChatGPT features are handled in the ChatGPT environment.
The plugin contributes instructions and reference material that shape how the model should respond.
OpenAI’s systems process the exchange according to your plan, settings, applicable policies, and available product controls.
The current release has no remote MCP server or publisher API. The publisher therefore receives no copy through DadGPT.
Protect yourself
Use roles or initials when a real name, employer, address, or case number is not needed.
Do not paste passwords, recovery codes, private keys, bank details, or authentication tokens.
Check memory, history, training, and temporary-chat options in your own ChatGPT settings.
Revisit OpenAI’s current privacy information instead of relying on an old screenshot or promise.
This project does not add analytics or advertising trackers to the website. The hosting provider may still process ordinary technical request data needed to deliver and secure the site under its own policies.
DadGPT cannot override OpenAI’s terms, privacy policy, or account controls. Those official documents are the source of truth for ChatGPT’s handling of your data.