Kazım Akgül · Paddle Toolkit
Privacy Policy
Last updated: September 29, 2026
This policy explains how Kazım Akgül handles information in Paddle Toolkit, a skills-only plugin for ChatGPT and Codex, and when you contact me for product support. I publish Paddle Toolkit independently. It is not affiliated with or endorsed by Paddle.
In brief: Paddle Toolkit has no publisher-operated backend. The plugin does not send prompts, files, code, or Paddle account data to me, and it does not include publisher analytics or telemetry. When you use ChatGPT or Codex, the platform processes the information you provide under its own terms and privacy policy. If you connect a Paddle tool, your requests go directly to the selected Paddle service through your client.
Information I receive
Installing or using the packaged skills does not create an account with me or automatically give me access to your conversations, workspace files, prompts, Paddle credentials, or Paddle account. I receive information only when you choose to send it for support, for example through email or a GitHub issue. This may include your email address or GitHub username, the support request, and any files or other information you choose to attach.
The Paddle Toolkit website is hosted on sapienx.app by Vercel. When you visit this policy page, Vercel may process technical request information such as your IP address, browser and device details, requested URL, and request time for hosting, security, and diagnostics. See Vercel's Privacy Notice.
How information is used
- Support messages are used to understand, respond to, and resolve the request.
- Website request information is processed by the hosting provider to deliver and secure the site.
- I do not use information from Paddle Toolkit for advertising or sell it.
Services that process information directly
Paddle Toolkit is an instruction package, not a service that proxies tool calls. Depending on the features you choose to use, information is handled directly by these providers under their own terms and privacy practices:
- OpenAI: ChatGPT or Codex processes your prompts, files, and tool interactions. See the OpenAI Privacy Policy.
- Paddle: If you connect its live or sandbox MCP server, Paddle receives requests and data needed to provide the selected account tools. Live access uses Paddle OAuth; sandbox access uses a sandbox credential configured in your MCP client. See Paddle's Privacy Policy.
- Kapa.ai: If you separately choose to use Paddle's documentation MCP, documentation questions are sent to the MCP service hosted by Kapa.ai. See Kapa.ai's Privacy Notice.
- GitHub: If you open a support issue, the information you post is handled by GitHub and may be publicly visible. See GitHub's General Privacy Statement. Do not post API keys, passwords, webhook secrets, or private customer data in an issue.
I do not receive information sent directly to these providers through your client. Their own policies govern their processing and retention.
Retention
I retain support correspondence only as long as reasonably needed to respond, resolve the request, and maintain necessary operational or security records, unless a longer period is required to address a legal claim or comply with law. Public GitHub issues are stored and managed by GitHub; Vercel's handling of website request logs is governed by its own policies. I do not retain plugin prompts, workspace contents, or Paddle tool requests because the plugin sends those directly to the platform or service you select.
Your choices and requests
- You can use the code and guidance skills without connecting Paddle account tools.
- You can stop using or uninstall the plugin, and disconnect a Paddle MCP server in your ChatGPT or Codex settings.
- For a support request you sent directly to me, contact me to request access, correction, or deletion. Requests about data held by OpenAI, Paddle, Kapa.ai, GitHub, or Vercel should be sent to that provider.
- Before posting publicly, remove credentials, personal data, and confidential code from issue text and attachments.
Security and changes
Do not share Paddle credentials in chat or public support issues. Store credentials using the protected credential controls provided by your MCP client. I may update this policy when the plugin or its data practices change; the date above shows when it was last revised.
Contact
For privacy questions or requests about information I receive, email info@sapienx.app or use the Paddle Toolkit support issues.