Your private work is not inventory.

Current release and prepared update

The version currently public in the Chrome Web Store is 0.4. It remains local-only and does not use the two-save Guest/Free boundary, secure account connection, Pro entitlement, or extension public-link flow described below. Version 0.7.0 is prepared for the same Store item, but those new behaviors apply only after Google reviews and delivers that update.

The local browser extension

The prepared version 0.7.0 of Fullary Local Chat Memory runs on chatgpt.com and is separate from the Fullary web workspace and ChatGPT app. It processes visible message structure locally to place controls and return you to a source message. It stores nothing until you explicitly choose a bookmark or Fullary menu action. An ordinary save keeps the chosen message or selected text, role and capture type, conversation title and canonical URL, bounded source locators and fallback excerpts, save time, and local folder only in the encrypted extension vault for that browser profile.

After Google delivers 0.7, the account-free Guest starter and connected Free account each allow exactly two current distinct local saves. Duplicate saves, edits, moves, search, export, return-to-source, and deletion remain available; deletion frees a slot. Existing libraries over the limit are preserved and readable. Pro opens the full local library subject to browser storage limits only while Fullary verifies the current entitlement. Ordinary records are never uploaded or synchronized automatically. The extension sends no analytics or diagnostics and does not sell data, use it for advertising, or train models.

Secure account connection in version 0.7

After Google delivers 0.7, connecting begins only after your click. The extension creates a random device identifier, a one-time secret, a separate acknowledgement secret, and a non-exportable P-256 device key. It sends only the two secret hashes, the public key, device identifier, and bounded device label, then opens an exact Fullary pairing URL. The pairing expires after ten minutes. The approval button stays disabled unless the installed extension proves that the exact request is still in its protected session. After website sign-in and explicit approval, the same extension instance proves possession of the one-time secret and receives a random device-scoped token. The raw one-time secrets stay in session storage; the token is encrypted in the local vault; and the private device key remains non-exportable in extension IndexedDB. Fullary stores hashes rather than raw pairing secrets or device tokens.

Each entitlement request combines the token with a fresh, signed, short-lived device proof, so copying the token and device identifier alone cannot authorize another machine. Device tokens expire after 90 days, can be revoked from the account page, and are checked against the server's current tier before paid local capacity is used. Each account may keep up to ten active browser connections; older revoked or expired connection records are removed after a bounded retention period.

Pairing and entitlement requests never include saved text, titles, folders, searches, exports, source links, ChatGPT content, or existing local records. Connecting does not copy or merge the Guest library into the web workspace. If verification is unavailable, new saves beyond the Free limit fail closed; existing local records remain usable.

Optional public-message links

In version 0.7.0 a signed-in Free, Pro, or Owner creator can choose Create link. Ordinary local saves still never upload or synchronize automatically. Only after the creator previews the exact message, chooses an expiry, reviews the Fullary account and message after sign-in, and explicitly confirms Create link once more does the extension send that one message to Fullary.

Free creators can choose one hour, one day, or one week; Pro and Owner can additionally choose one year or permanent until revoked. The draft is retrievable for up to ten minutes and is bound to the same browser tab and window. Fullary derives a one-way account binding after sign-in, validates the tier and expiry, and screens the content. The published unlisted snapshot contains only the exact reviewed plain text, role, and a server-derived title—not the account, chat URL, folders, projects, locators, surrounding messages, source metadata, or local vault. Anyone with the raw link may view it until expiry or revocation.

Browser permissions

The prepared version 0.7.0 requests browser storage, context menus, and access to chatgpt.com for local tools. Its manifest declares https://fullary.com/api/extension/* for account calls; Chrome technically treats that path as permission for the full https://fullary.com origin. The extension's own network client still rejects every Fullary request except pairing start, pairing claim, and entitlement verification, and isolated page bridges run only on the exact account-pairing and public-link confirmation pages. Its Market pilot button opens the exact https://fullary.com/market page in a new tab without sending saved content, source details, credentials, or billing data; there is no content bridge on that page. It does not request cookies, general browsing history, every-website access, browser identity, payments, downloads, or remote executable code.

Local retention, export, and removal

Extension records remain in that browser profile until you remove individual records, clear the extension's data, remove the extension, or lose the browser profile. You can export them as JSON from the Fullary drawer. The build does not automatically back up or synchronize ordinary records, so removal may be irreversible if you did not export first. Because Fullary receives no server copy, it cannot recover, remotely inspect, or remotely delete a local record.

Device Vault web app

The separate Fullary Device Vault page accepts text you paste or deliberately send through a supported installed web-app Share target. It does not add controls to native ChatGPT apps and does not read their history. A Share-target submission becomes one encrypted local draft; you must review it and press Save before it enters the permanent vault, or you can discard it. Before local storage, the title and body are encrypted with AES-256-GCM using a non-exportable key kept in that browser's IndexedDB. Search decrypts records in memory only while the page is open. The page sends no saved title or body to Fullary's account, database, analytics, marketplace, or device catalog.

Installing the web app is optional. Web Share Target and installation support depend on the browser and operating system. Ordinary records stay only in that installed app or browser profile and do not synchronize. A portable backup is created only when you request one: records are decrypted locally and re-encrypted with a passphrase-derived key before the file is downloaded. Fullary does not receive or retain the backup, passphrase, or recovery key and cannot restore them if they are lost. The service worker caches the Device Vault page for offline opening and intercepts supported Share-target submissions locally so the shared text is encrypted into a single pending IndexedDB draft rather than sent to the website.

Chrome Web Store Limited Use

When delivered, version 0.7.0 uses handled information only for encrypted local save, organize, search, export, return-to-source, secure device entitlement, and the explicitly confirmed one-message sharing flow. Pairing and entitlement never transfer local content. Public-link confirmation sends only one exact reviewed message, role, strict expiry choice, and bounded anti-replay fields, with no source URL, chat title, folders, searches, export, vault, or surrounding conversation. Handled information is not used for personalized advertising, credit decisions, data brokerage, unrelated analytics, or model training.

Fullary's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

What the cloud service collects

Separately from the local extension, the Fullary cloud service stores account identifiers needed to operate your workspace, text and metadata you manually submit to that service, folders and projects you create, relationships you deliberately create among Problem, Attempt, Failure, and Outcome records, subscription state, and limited security and reliability logs. Sign-in is used only to authenticate the account. It does not give Fullary access to ChatGPT conversations, and the cloud service does not scrape, crawl, import, or reconstruct chat history. Unless a section expressly refers to the local extension, the remaining sections below describe the Fullary cloud service.

Marketplace preview and future transactions

The current Fullary Market is a preview and private-draft pilot, not a live marketplace. When a signed-in creator deliberately uses the draft studio, Fullary stores the account-linked stall name, draft title, proposed delivery type, intended USD price, exact-deliverable description, rights confirmation, and timestamps. Drafts are private and cannot be purchased. The pilot does not request seller identity documents, bank details, tax records, buyer data, orders, marketplace payments, commissions, or payouts. Do not place that information in a draft or ordinary support email.

Fullary intends to use Tap Payments for a future Marketplace flow, subject to Tap's contractual, technical, KYC/KYB, category, country, and compliance approval and Fullary's completion of the required legal and product controls. If that flow is activated, Fullary and Tap may process the minimum information needed for seller onboarding and verification, payment and fraud screening, order administration, split allocation, refunds, disputes, chargebacks, reconciliation, and seller payout status. That may include seller identity and business details, ownership and authorized-signatory information, tax or registration information, bank-account evidence, provider account and verification identifiers, buyer contact and billing information, order and delivery records, amounts and currencies, risk results, and support evidence. The activated onboarding screen will identify the secure collection route and applicable controller or processor before documents are requested. Fullary does not receive full payment-card details from a provider-hosted checkout.

How cloud private content is used

Private items are used to provide search, organization, and features you request. Private content is not placed in public discovery, sold to data brokers, or used for advertising.

Cloud sharing and source links

Fullary does not automatically publish private cloud items, create public profiles, or expose a workspace to other Fullary users. A confirmed extension message link or a deliberately created cloud-workspace link stores an immutable snapshot of only the exact text, a title derived from that text, its role label, expiry, revocation state, and irreversibly hashed high-entropy request and URL values. Folder, project, account, conversation, and source-link metadata are not included in the public snapshot. Anyone with the raw URL can view and forward that snapshot until it expires or you revoke it; they can also copy it or take screenshots. Share pages are marked for search engines not to index, but no technical measure can prevent copying or guarantee that every crawler obeys. The public title and a short excerpt may appear in social or messaging link previews. An optional source URL on a private record is stored only as a user-provided bookmark; Fullary does not use it to fetch or copy the linked content. We disclose data only to service providers that help operate Fullary, when you direct us to do so, or when disclosure is reasonably required by law, security, or the protection of rights.

Public-content screening and reports

Before a public snapshot is created, Fullary uses a conservative text screen to reject high-confidence patterns involving sexual exploitation, explicit sexual material, violent threats, hateful incitement, extremist recruitment, authentication secrets, and financial or payment identifiers. The screen does not make private records public and does not replace human review. It may reject legitimate text conservatively; Fullary does not promise it will identify every prohibited variation.

A public-page visitor may deliberately submit a category, bounded description, optional contact email, and confirmation for owner-only review. Copyright or IP reports require a contact email. Fullary stores only a hash of the high-entropy tracking token and returns the raw tracking URL once. Reviewers can see the reported public snapshot and report details, record a decision, and revoke a link. A takedown purges the public title and text; bounded report, decision, internal account-binding, and security metadata may remain for up to 365 days for abuse prevention, appeals, disputes, and legal obligations. Reporter contact details are not shown to the publishing account and are used only to clarify or resolve the report. Privacy requests can be sent through Support.

Operator and contact

Fullary is operated by Modern Science House SPC, Commercial Registration No. 1568033, a company registered in the Sultanate of Oman. Privacy requests may be sent to admin@fullary.com.

Service providers and payments

Fullary uses OpenAI account authentication for the website, Auth0 for OAuth account linking between ChatGPT and the Fullary plugin, and OpenAI Sites infrastructure backed by Cloudflare services. Auth0 may process the verified account identity, authorization subject, and permissions needed to link the plugin to the correct Fullary account; it does not receive a user's Fullary workspace content through this sign-in flow. Paid Fullary Pro subscriptions are sold through Lemon Squeezy as Merchant of Record. Lemon Squeezy processes subscription payment, billing, indirect-tax, invoice, refund, and fraud-prevention information under its own privacy notice. The extension's View Pro action only opens Fullary's pricing page in a new tab; the extension does not receive, read, or store payment-card or billing details.

Lemon Squeezy is not the payment rail for third-party Fullary Market sales. Fullary is evaluating Tap Payments for future marketplace seller onboarding, checkout, split allocation, refunds, disputes, chargebacks, reconciliation, and payouts. No such live transaction flow is enabled today, and naming an intended provider is not a claim of provider approval. If activated, Tap's own notices and the final checkout or onboarding disclosures will also apply. Fullary does not receive full payment-card details from provider-hosted payment pages.

Cloud retention and deletion

We keep account and cloud-workspace data only for as long as reasonably needed to provide Fullary, meet legal obligations, resolve disputes, and protect the service. When a share is revoked or purged after expiry, its public snapshot content is removed and its public URL no longer resolves; limited non-content metadata may remain temporarily for security and abuse controls. You may export or delete cloud-workspace data through account controls. Limited records may be retained where required for security, fraud prevention, billing, tax, or other legal obligations.

International cloud processing and security

Our cloud providers may process data outside your country. We use reasonable administrative and technical safeguards appropriate to the service, but no online service can guarantee absolute security. Do not save credentials, payment-card data, government identifiers, medical records, or other highly sensitive material in Fullary.

Your choices and rights

For cloud account, workspace, and confirmed public-snapshot data, you may use available account controls or request access, correction, export, revocation, or deletion through the Support page. Ordinary local extension records are controlled through local removal, browser-data, and export options; Fullary has no server copy of those ordinary saves to act on. Depending on applicable law, you may also have rights to restrict or object to processing or to complain to a data-protection authority. We may need to verify a request before acting on it.

Changes to this notice

We will update the date shown on this page when this notice changes. If a change materially affects how local extension records or private cloud-workspace content is handled, we will provide additional notice where reasonably possible or legally required.