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 extension adds controls to visible ChatGPT messages, but it does not store a message until you explicitly use a trusted Fullary bookmark or menu action. It does not silently import your full conversation history. Ordinary saves make no server upload. In the separate 0.5.2 candidate, only a second trusted confirmation on Create link can send the one reviewed message for publication.

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.

No. Ordinary local saving, search, folders, export, and return-to-source have no Fullary sign-in, subscription, or card requirement; records belong to the browser profile. Install the reviewed build only from Fullary's official Chrome Web Store listing. A Fullary sign-in is required for the separate cloud workspace and for deliberately publishing a one-message public link. It is never required for ordinary local saving. The extension-to-account page keeps the optional cloud path clear.

Yes. The reviewed browser extension is available from Fullary's verified official Chrome Web Store listing. The public build provides local bookmark, folder, search, source-return, and JSON export tools; it does not publish links or synchronize the local vault. Install only from that listing. The separate Fullary MCP/ChatGPT app may have a different public-review status.

You do not need one for ordinary local saving, search, folders, export, or return-to-source. A Fullary sign-in is required for the separate website and MCP/ChatGPT cloud service and when you deliberately create an extension public link. After sign-in, the same approved draft resumes automatically; the resulting /s/ link can be viewed in any browser without signing 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, in the separate version 0.5.2 candidate. A signed-in Free, Pro, or Owner creator can review one exact message, choose a duration, and confirm Create link. This candidate has not yet been submitted or approved for public Chrome Web Store distribution.

The exact reviewed message becomes a revocable unlisted snapshot after safety checks. One week is the default and the longest Free duration; Pro and Owner can also choose one year or permanent until revoked. Fullary validates the preset and computes the expiry on the server. 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 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.

These plans describe the separate Fullary cloud workspace and MCP workflows, not the local-only Chrome extension build. Cloud Free activates automatically after sign-in, is not a timed trial, and needs no card. It includes private cloud saving and search, up to five folders including the starter folders, three private projects and progress maps, a Basic Return-to-Work Brief, and three active seven-day links. Pro raises those limits and adds the Advanced Brief beta and Failure Finder beta. See the Pricing page for the current contract.

Subscriptions are managed on Fullary.com, not inside the Chrome extension or ChatGPT app. Free activates automatically when you first sign in to the web workspace. After a successful Lemon Squeezy checkout and verified webhook, Pro activates automatically for that same Fullary account. Current Free and Pro plans apply to the web workspace and connected ChatGPT app; they do not unlock or synchronize the local-only Chrome extension.

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.