Infinity Explainer

Privacy policy

Publisher: zylen · Last updated: November 14, 2026

This policy describes the Infinity Explainer plugin in ChatGPT and this public website. The separate, self-hosted version is described below. Infinity Explainer turns explanations into connected cards on a canvas.

Starting with version 2.1.0, you can create a new canvas directly in ChatGPT without signing in to the canvas website, completing OAuth, or approving a website connection. These conversation-created canvases use a separate access credential for each canvas. Existing website account connections remain available separately.

Information handled by the plugin

How information is used and shared

Canvas information is used to create, display, edit, save, reopen, import, and export your canvas. For conversation-created canvases, the access credential and matching canvas identifier authorize subsequent operations. For account-owned canvases, account identity or an approved canvas credential is used to check access. Technical information supports authentication, security, synchronization, and troubleshooting.

The service returns a new canvas's access credential to your current ChatGPT conversation and the embedded canvas interface. They retain it and send it with subsequent tool calls for that canvas. The credential is not placed in URLs or normal displayed canvas or chat text. Anyone holding a valid credential can access the corresponding canvas within its permissions; the canvas identifier alone does not grant access. Keep credentials private. Conversation-created canvases are not automatically added to a signed-in website account's canvas library.

Saved canvases are stored in Cloudflare D1 through ChatGPT Sites. OpenAI processes sign-in, plugin tool calls, tool results, and the conversation in ChatGPT. Selecting text for a question can send that selection and surrounding card text to ChatGPT as context. The plugin receives the arguments supplied to its tools; connecting it does not itself give it unrestricted access to your entire chat history.

When realtime updates are enabled, the update service receives an opaque canvas channel and revision notifications; the canvas text is retrieved separately through access-checked plugin tools. The ChatGPT plugin uses the current conversation to generate your answers and does not independently call a separate language-model API.

Information you choose to post to GitHub Issues is public and is processed by GitHub. Exported files are downloaded to the location you choose and are outside the plugin's storage controls.

Retention and availability

Canvas access credentials expire after 30 days without valid use. Valid use extends that expiry by another 30 days. An optional website pairing request expires after 15 minutes if not approved. Credential expiry or revocation does not itself delete the canvas content or all associated database records.

The current canvas service has no scheduled expiry for saved canvases. Content remains in the active saved canvas until you edit, replace, or delete it, or the service's stored data is removed. There is no promised storage duration, backup service, or guarantee that saved data will remain available.

You can export an importable JSON copy from the canvas interface while the service and your canvas are accessible. Keep your own copies of anything you want to preserve. Revoking access to the plugin does not automatically delete its saved canvas records.

Diagnostic events held only in the interface's memory are lost when that document is discarded. Retention of hosting logs, security records, provider backups, and ChatGPT conversations is governed separately by the relevant provider's policies; deleting a card is not a request to erase those systems.

Your controls and deletion

For conversation-created canvases, keep access within the conversation and embedded interface that hold the matching credential. These canvases and their credentials are not automatically linked to a website account or managed in its access list. If you separately pair an account-owned canvas through the website, you can revoke that paired connection from the website's access management page. Revocation prevents subsequent use of that credential; it does not erase saved content.

You can edit or delete cards in the canvas interface. Deleting cards removes their text and corresponding layout entries from the active saved canvas. Importing a canvas replaces the current saved cards and layout. These actions do not erase copies already exported, posted publicly, or retained in your ChatGPT conversation.

The current plugin does not provide a whole-canvas or account-data deletion tool. Removing every card leaves an empty canvas record and its ownership identifier. Disconnecting the plugin and deleting your ChatGPT conversation are separate actions with separate effects.

For general privacy questions, open a GitHub issue without including personal information. GitHub Issues is public and is not a private deletion-request channel. Do not post canvas contents, account identifiers, passwords, tokens, or other confidential information there.

This website

The public information and policy pages are hosted on GitHub Pages. These pages do not add advertising trackers, analytics scripts, sign-in forms, or canvas storage. GitHub may process request and security information to deliver the website.

Self-hosted use

If you run the open-source app yourself, canvas content and model settings, including any API key you configure, can be stored in your browser's local storage. Prompts and selected context are sent to the model endpoint you select. An optional local MCP server stores canvases and diagnostic traces on its host. You control those installations, files, providers, and their retention; they are separate from the hosted ChatGPT plugin. Clear local storage and remove local files to remove those local copies.

Provider policies

For their own services, see the OpenAI Privacy Policy, Cloudflare Privacy Policy, and GitHub Privacy Statement.

Updates

Changes to this policy will appear on this page with an updated date. Check this page for the current description of the service's data practices.