QR Studio privacy policy
Last updated: November 3, 2026 · Applies to QR Studio for ChatGPT and iplugin.dev/qr
QR Studio is published and operated by Trustflow (iPlugin). This policy explains what the plugin processes, why, where it goes, and the choices you have. It applies to the QR Studio MCP service at https://iplugin.dev/qr/mcp, the studio interface, and the local version when you run it on your own computer.
1. What QR Studio does
QR Studio turns the content you choose into a QR code and lets you style it with presets, colors, shapes, gradients, and an optional center logo. You can save designs during a session and export a PNG or SVG file. QR Studio does not create an account, does not sell data, and does not use advertising trackers; it collects first-party anonymous usage statistics.
2. Information the plugin processes
- QR payload. The text you ask to encode: a URL, plain text, Wi-Fi network name and password, contact card fields, email address and message, phone number, coordinates, or calendar event details.
- Design settings. The preset, colors, dot and corner styles, gradient, background, margin, error-correction level, shape, size, and logo choice.
- Logo image. If you upload a logo, the image is processed to place it in the center of the QR code. Built-in marks and initials monograms are generated locally in the interface.
- Design names and library metadata. The name you give a design and the time it was created or changed.
- Export files. The PNG or SVG you ask the plugin to render.
- Technical records. Standard web-server and service logs such as request time, path, response status, IP address, and user agent, used for security, reliability, and abuse prevention. The plugin does not intentionally log the contents of QR payloads.
- Preferences. The interface may keep your chosen language and theme in browser local storage. On the desktop, the local version stores designs under
~/.iplugin-qr.
3. Why we process it
We process this information to render the QR code you requested, keep the design library for the current ChatGPT session, produce export files, show a live preview, keep the service secure and reliable, and respond to support requests. We do not use QR payloads or logos to train models, build profiles, or target advertising.
4. Session isolation and storage
The hosted service keeps each MCP session in a separate library directory. A design created in one session is not shown in another session. The server stores design JSON under a session-specific directory on the plugin host and writes exported files to a shared export directory with a random file name. The service does not require an account, so it does not know your name or email unless you send it in a payload or a support message.
Session libraries and export files are intended for short-lived use. The operator removes session data and exports older than seven days; a deployment or restart may also clear them earlier. Exported file URLs contain a random identifier rather than a design name, but anyone who has a URL can open that file until it is removed. Do not encode secrets you would not put in a URL or a printed QR code.
If you use the local version, designs and exports stay on your computer under ~/.iplugin-qr and are not sent to iplugin.dev unless you explicitly connect the remote MCP server.
5. Who receives data
Requests go to the plugin host at iplugin.dev and are part of your ChatGPT conversation, so OpenAI processes the conversation under its own policies. The hosting provider processes network requests and logs to run and protect the service. We do not sell personal information or share it with advertising networks. We may disclose information if required by law or to protect the service and its users.
6. Legal bases
Where the GDPR or similar law applies, we rely on performance of the service you requested (rendering and exporting the QR code), our legitimate interests in securing and improving the service, and consent where required. You can withdraw consent for optional processing at any time; this does not affect processing that already happened.
7. Your choices and rights
You can delete a saved design in the studio, ask the model to call qr_delete, clear browser site data for the language and theme preference, or delete the local ~/.iplugin-qr directory. Because the hosted service has no account, we may not be able to identify you in logs; we will explain what we can and cannot do. You may have rights to access, correct, delete, restrict, or object to processing, to data portability, and to complain to a supervisory authority. Email micromvp@gmail.com with the subject “QR Studio privacy request”. Do not send passwords or access tokens.
8. Security
We use HTTPS for the public MCP endpoint and the website, keep the service behind a reverse proxy, isolate session libraries, and restrict administrative access. No method of transmission or storage is completely secure. Please avoid encoding passwords, private keys, or other secrets in a QR code that you share. If you believe you found a vulnerability, email micromvp@gmail.com with reproduction steps and do not access other users’ data.
9. Children and international use
QR Studio is a general-audience design tool and is not directed to children under 13. Requests may be processed in countries where the hosting provider operates. Where required, we use appropriate safeguards for international transfers.
10. Retention
Session designs and exports are removed after seven days or earlier on restart or deployment. Web-server logs are retained for a short operational period. Support emails are kept only as long as needed to resolve the request and meet legal obligations. Local files remain until you delete them.
11. Changes and contact
We will update this page and its date when our processing changes. Material changes will be communicated through the product page or support page. Privacy questions, access or deletion requests, and security reports: micromvp@gmail.com. Product: https://iplugin.dev/qr-studio.html. Data deletion: https://iplugin.dev/qr-studio-data-deletion.html.
Anonymous usage statistics
The upgraded widget stores a random UUID v4 in browser localStorage under iplugin.analytics.id.v1 and sends it to first-party iPlugin endpoints for daily active-user counts and MCP event attribution. The server stores a SHA-256 hash scoped to this plugin. Counts use the Asia/Shanghai day. This browser identifier is not an account or verified person; clearing storage and using other devices or partitions can create additional identifiers.
For each parsed MCP request, analytics retain an event ID, plugin, method, allowlisted tool name, success/error/notification outcome, duration, timestamp, optional UUID hash and hashed opaque game, puzzle or design context. We do not include tool arguments or returned content, boards, puzzle answers, QR contents, prompts, account details, IP addresses or User-Agent in these analytics. Requests without a UUID association remain unattributed. Context binding is best effort, not proof of identity or ownership.
Events and context mappings are deleted after 400 days. Daily plugin-scoped activity hashes are retained separately until deletion is requested; daily counts are calculated from those hashes. Statistics use our own service at iplugin.dev, with no advertising platform. Browser storage or network restrictions can prevent collection without blocking core functionality. Old published UI resources retain their original behavior until the upgrade is installed.
Clear plugin browser/site data to reset the local identifier. This does not erase server analytics. To request deletion of associated records, contact micromvp@gmail.com with this plugin name and your anonymous UUID before clearing storage; without that identifier we cannot reliably identify the corresponding hash.