You saved it.
Know where it lives.

The current local browser-extension build stores the selected text and source details only in extension storage for the current browser profile. Open the Fullary drawer in ChatGPT to see, search, reopen, or delete those local records, or choose Export JSON to make a backup.

The local record is not uploaded to Fullary, does not appear on Fullary.com, and does not become a native ChatGPT bookmark, Library item, or Project. The original message remains in its original ChatGPT conversation under ChatGPT's own history rules.

Without leaving ChatGPT, open the Fullary drawer on the right. It lists the saved date, source role, chat title, folder, and text excerpt. Its search box searches the extension records in this browser profile. Selecting a result reopens the original conversation and makes a best-effort return to the source message.

No. The browser extension's local library and the Fullary cloud vault are separate. Fullary.com and Fullary's MCP/ChatGPT app can work with cloud records that you deliberately submit to that service, but neither can see the extension's local records. There is no automatic sync, cloud backup, or silent transfer between them in the current preview.

Yes. The extension places a Fullary bookmark icon beside visible user messages and visible ChatGPT answers. Choose the bookmark for a one-click local save, right-click it to choose a local folder, or select part of a message and use the Fullary browser context menu. Each explicit action saves only that message or selection.

No. A Fullary record is a separate local copy of only the material you chose. Deleting it from the drawer does not alter the original ChatGPT message. Likewise, deleting or losing the original conversation may prevent Fullary from reopening its source, but it does not automatically remove the local saved copy.

No. The current 0.4 release and prepared version 0.7.0 store nothing until you explicitly use a trusted Fullary bookmark or menu action. Neither silently imports your conversation history. Ordinary saves stay encrypted in this browser profile and make no automatic server upload or sync. After Google delivers 0.7, only its separate public-link flow—previewing one exact message, choosing its expiry, reviewing the Fullary account and message after sign-in, and confirming Create link once more—can send that one message.

After installing the browser extension, open or reload ChatGPT in that browser profile and start a normal conversation. When the conversation has a durable ChatGPT URL, a bookmark appears when you point to or focus a supported visible message. Use the fixed Fullary button, its browser-toolbar icon, or Alt+Shift+F to open the local drawer.

Open the old conversation on chatgpt.com and reload the page once if the extension was installed while that tab was already open. Fullary adds controls to supported messages currently rendered on the page. It does not require you to attach the MCP app, and it does not bulk-import other conversations.

It can add its local controls to supported conversation pages rendered on chatgpt.com, including conversations reached through ChatGPT Projects or Work. It saves only the message you deliberately choose; it does not receive the whole Project, its files, or its other chats.

No. Drawer search covers only messages or selections you deliberately saved with the extension in the current browser profile. It does not search unsaved ChatGPT history. Open an older conversation and save the specific message if you want it in the local library.

The current local extension uses deterministic text matching across locally saved message text, chat titles, folders, and source roles. It is not semantic or fuzzy AI search, it does not search material you never saved, and it does not include records held separately in the Fullary cloud vault.

No. A local Fullary folder organizes extension records inside one browser profile. It does not create, modify, read, or synchronize a native ChatGPT Project. Fullary cloud projects are also separate organizational containers in the optional cloud workspace.

After Google delivers version 0.7, no account is needed for its two-save Guest starter. Search, folders, export, return-to-source, and deletion work for those local records in this browser profile. The current public 0.4 release remains local-only and does not yet use that plan gate. Install the reviewed build only from Fullary's official Chrome Web Store listing. A Fullary sign-in is required to connect the extension, use the two-record Free web workspace, verify Pro, or deliberately publish a one-message public link. Connecting does not upload existing local records. See the Guest, Free, and Pro path.

Yes. Open Fullary's current Chrome Web Store listing. The public release is currently version 0.4: it remains local-only and does not yet use the two-save account tiers. Google controls when the prepared version 0.7.0 update becomes available. After it arrives, Guest and connected Free each allow exactly two current local saves, while Pro opens the full local library subject to browser storage limits. Ordinary saves stay encrypted in this browser profile and never upload or synchronize automatically. The separate Fullary MCP/ChatGPT app may have a different public-review status.

You do not need an account for the current local-only 0.4 release or, after Google delivers 0.7, for its two-save Guest starter. Sign in to open the separate two-record Free web workspace and—under 0.7—to connect this browser, verify Pro, or deliberately create an extension public link. The 0.7 connection uses a short-lived one-time approval and a revocable device token; it sends no saved text. The MCP/ChatGPT cloud service also requires sign-in.

Fullary.com provides account, profile, billing, plan, privacy, help, and support pages, plus optional cloud-workspace workflows such as structured Problem, Attempt, Failure, and Outcome records and controlled snapshots. The website and MCP app can open the same verified cloud workspace. They do not open, search, or synchronize the extension's local drawer.

The current preview separates data by browser profile, not by ChatGPT or Fullary account. Different ChatGPT accounts used in the same browser profile share the same local Fullary library. Use separate browser profiles for account separation. Cloud accounts remain separate and should never share credentials.

Yes, through a separate explicit flow in the prepared version 0.7.0 after Google delivers it; the current public 0.4 release does not provide this flow. A signed-in Free, Pro, or Owner creator previews one exact message, chooses its expiry, reviews the Fullary account and message after sign-in, and confirms Create link once more. Only after the final confirmation is that one message sent to Fullary.

The exact reviewed message becomes a revocable unlisted snapshot after safety checks. Free can choose one hour, one day, or one week; Pro and Owner can additionally choose one year or permanent until revoked. The link appears in the same authenticated account's Sharing section, while anyone with the raw link can view it without signing in. It excludes the chat title and URL, folders, projects, account details, surrounding messages, source locators, and the rest of the encrypted local vault.

No. It is intentionally absent from public listings, but it is still forwardable. Anyone who receives the URL can view and share that selected snapshot until it expires or you revoke it. Never put material in a snapshot that its recipients should not see.

Open the snapshot and choose Report this snapshot. Select a reason, describe the exact concern, and save the one-time tracking URL Fullary returns. Reports enter an owner-only review queue and do not automatically disclose the reporter or remove a link. The reporting page explains takedowns, owner appeals, copyright notices, retention, and urgent-safety escalation.

No. Copy the URL when Fullary creates it. Fullary stores only an irreversible hash of the link token, so the original URL cannot be reconstructed later. You can still see its status and revoke it from the Sharing section of your workspace.

Local extension records stay inside that browser profile and have no public URL. Cloud records belong to the authenticated Fullary account unless you explicitly create a separate cloud snapshot link. Neither installing the extension, selecting Save, nor signing into the cloud service publishes anything or grants bulk access to unsaved ChatGPT history.

The website Free account allows exactly two private web records now. After Google delivers the pending Chrome 0.7 update, Guest needs no account and keeps exactly two current local messages; connected Free has the same local limit. Pro then opens the full local extension library subject to browser storage limits, raises the private web safety cap to 10,000 records, and adds larger organization and advanced progress features. The current public 0.4 extension remains local-only and does not yet use these account tiers. No plan automatically uploads or synchronizes local content. See the Pricing page for the complete contract.

Subscriptions are managed on Fullary.com, not inside ChatGPT. Free activates when you first sign in. After a successful Lemon Squeezy checkout and verified webhook, Pro activates for that Fullary account. To use it in the extension, approve this browser through the short-lived pairing page. The server then checks the current tier on use; the device token can be revoked. Saved content remains local and is never sent during connection.

Use the extension drawer to search, reopen, delete, and export local records as JSON. Use the separate Fullary web workspace to edit cloud records, move them between cloud folders, manage or revoke cloud snapshots, export cloud account data, and delete cloud records. Actions in one surface do not automatically change data in the other.

In the cloud workspace, deleting a cloud folder removes that container but leaves its records as unfiled items. Local extension folders are separate; current local records remain controlled through the extension drawer and browser-profile storage. A cloud-folder action never changes a local folder or record.

No. Subscription cancellation and data deletion are separate safeguards. If an account has an active subscription, cancel that subscription before completing account deletion.