Privacy Policy

How ContinuForge collects, uses, stores and shares data across the Chrome extension, website and account service.

Last updated: August 10, 2026.

Short version. ContinuForge processes ChatGPT content and ContinuForge Memory locally for its browser features. Chat or Memory content is not sent to ContinuForge servers merely because the extension is installed, a ChatGPT page is open, or material is saved to Memory. User-selected material is transferred to ChatGPT/OpenAI only when the user explicitly starts a feature that requires that transfer.

1. Scope and operator

This policy applies to the ContinuForge Chrome extension, the ContinuForge website and ContinuForge account/API services. ContinuForge is an independent product and is not affiliated with or endorsed by OpenAI or Google.

Service operator: Individual Entrepreneur Aleksei Sergeevich Vakhrushev, Registration No. 323330000025760. Privacy and deletion requests: support@continuforge.com. Additional legal information is available on the Legal and Terms pages.

2. Collection, use and storage overview

Collection

ContinuForge collects only the account, license, service and limited analytics data described below. ChatGPT page content and ContinuForge Memory content are normally collected into local browser storage for the requested extension function rather than into ContinuForge servers.

Use

Data is used to provide the requested ContinuForge features, authenticate accounts, enforce Free/Pro and device/transfer limits, deliver service email, process payments, prevent abuse, secure and diagnose the service, and measure product/reliability events described in this policy.

Storage

Chat/Memory working content is stored locally in Chrome extension storage/IndexedDB unless the user explicitly sends selected material to ChatGPT/OpenAI. Account, license, payment, referral and limited analytics/service records are stored in ContinuForge server infrastructure as described below.

3. ChatGPT content processed locally

ContinuForge runs on supported ChatGPT pages and may read or process content that is already available in the page in order to provide user-facing features such as Continue, search, labels, Explorer/navigation, export, anti-lag and related interface functions.

This processing happens in the browser. ChatGPT conversation content is not sent to ContinuForge servers merely because the extension is installed or operating on a ChatGPT page. ContinuForge does not claim to automatically identify project goals, accepted or rejected decisions, important files or unresolved questions unless a specific released feature explicitly does so.

4. ContinuForge Memory: what is collected and stored

ContinuForge Memory is user-initiated. A Memory item is created only after the user explicitly chooses a ContinuForge context-menu action or another Memory control.

Selected text

the selected text;
the source page URL;
the page title;
the capture timestamp;
technical length/truncation metadata when applicable.

Saved web page

page URL and title;
page language;
canonical URL, when the page provides one;
meta description, when the page provides one;
a limited HTML snapshot and page text;
capture timestamp and technical truncation metadata.

Saved image

the image itself;
the image URL when available;
source page URL and title;
alt text when available;
image dimensions and technical capture metadata;
capture timestamp.

Memory metadata is stored in Chrome extension local storage, while larger Memory payloads such as page snapshots and images are stored locally in the extension's IndexedDB storage. Saving an item to ContinuForge Memory does not upload its content to ContinuForge servers. When saving an image, the browser may request the selected image from its source host; if direct retrieval is not available, ContinuForge can create a local crop of the visible image instead.

5. Build Memory Document — Pro

Build Memory Document — Pro combines user-selected ContinuForge Memory items locally into one generated file/package for the requested workflow. Only the Memory items selected by the user are included.

The generated file/package is created locally in the browser. Creating it does not send its contents to ContinuForge servers. When the user explicitly sends it to ChatGPT, the selected material is transferred to ChatGPT/OpenAI as part of that requested action.

6. Transfer to ChatGPT / OpenAI

ContinuForge transfers user-selected content to ChatGPT/OpenAI only when the user explicitly starts a feature that requires that transfer. Examples can include a selected Memory item, a Build Memory Document file/package, a selected file, a continuation package or other material the user chooses to send through a supported ContinuForge workflow.

That content is then processed by ChatGPT/OpenAI under OpenAI's own terms and privacy rules. See OpenAI Terms & Policies. ContinuForge does not control OpenAI's subsequent processing.

7. Account and authentication data

If you create or use a ContinuForge account, ContinuForge may process:

email address and account/user ID;
password during registration or login;
preferred language;
account creation, email-verification and login timestamps;
access, refresh, session and verification tokens or token hashes;
referral code and referral state when used.

The password is sent to the ContinuForge API over HTTPS for registration/authentication. The backend stores a password hash, not the original plaintext password. The website may use a secure session/refresh cookie. The extension stores its refresh token in extension local storage and keeps the short-lived access token in extension session storage.

8. License, device and transfer/referral data

To provide Free/Pro access, device limits, licenses, Continue counters and referrals, ContinuForge may process and store:

installation ID;
device/browser name supplied by the extension;
extension/app version;
plan, subscription/license status and expiry;
device activation, last-seen and revocation timestamps;
base, used and referral transfer counters;
referral code, attribution, qualification and credit state;
hashed IP signals and device/installation signals used for referral abuse prevention.

For referral qualification, the service can also store the registration User-Agent and pseudonymous HMAC-based IP hashes as anti-abuse signals. These records are not used for advertising profiling.

9. Product and website analytics

ContinuForge uses limited first-party analytics to understand service use, acquisition, reliability and feature adoption. Depending on the event, a record may contain an event ID, event name, extension version, language, site path, broad feature category, Memory object type, destination category, or counts of selected Memory items by type.

Examples include page views, download/registration events, memory_save, memory_send, and Build Memory Document open/create/paywall events. Website acquisition events may include limited first-touch parameters such as UTM source/medium/campaign/content, ContinuForge referral lead code, referring-site domain and landing path.

The analytics implementation does not accept ChatGPT conversation text, Memory text, saved-page HTML, images, Build Memory Document generated content or the URL of a saved Memory page as analytics-event content. For approximate unique-visitor counts, the backend can derive a pseudonymous HMAC visitor hash from the request IP address and User-Agent; the analytics event record does not persist the raw IP address or raw User-Agent in that visitor field.

10. Server and security logs

When the website or extension contacts ContinuForge infrastructure, hosting/network/application systems may process standard request data such as IP address, User-Agent, request time, requested endpoint/path, HTTP status and error/security information. These data are used for service operation, security, diagnostics, rate limiting, abuse prevention and incident investigation. Operational server logs are separate from the privacy-limited product analytics described above.

11. Payments

Payment-card or bank details are entered into the payment provider's checkout, not into the ContinuForge extension. The current site identifies Robokassa for supported checkout flows. ContinuForge may receive transaction metadata needed to verify payment and activate Pro, such as provider/payment event ID, status, amount, currency, user/account association and provider response data required for reconciliation or disputes.

The ContinuForge extension does not store your bank-card number. Recurring billing applies only when the checkout explicitly presents it and the user separately agrees to it.

12. Who data may be shared with

OpenAI / ChatGPT

Receives only user-selected material when the user explicitly starts a ContinuForge action that sends content to ChatGPT.

ContinuForge infrastructure

Hosting, network, application and database infrastructure processes account, license, service, analytics and request data needed to operate and secure the website/API. Chat/Memory content is not sent to the ContinuForge API merely because it is processed locally.

Beget mail infrastructure

ContinuForge is currently configured to use Beget SMTP infrastructure for service email. Beget may therefore process the recipient email address and the service-message data needed to deliver email verification, account/service notices or support mail.

Payment provider

The payment provider processes the payment information required for checkout. Card details are handled by that provider rather than the ContinuForge extension.

Law, security and abuse prevention

Information may be disclosed where required by law or when reasonably necessary to investigate fraud, security incidents or abuse, or to protect users, ContinuForge or others.

ContinuForge does not sell user data. ContinuForge does not transfer user data to advertising networks or data brokers and does not use extension user data for personalized, retargeted or interest-based advertising.

13. Data retention

Local extension data

ContinuForge Memory and other local extension state remain in the browser until the user deletes them, clears the extension/browser data, or removes the extension in a way that removes its local storage. Browser behavior can vary, so users who require deletion should use the ContinuForge delete controls and/or Chrome's extension-data controls.

Account and service data

Account-owned operational data is retained while the account is active and as needed to provide and secure the service. Some categories can be retained longer where necessary for payment/accounting records, fraud prevention, security, disputes or legal obligations.

14. Deletion

To request deletion of a ContinuForge account, email support@continuforge.com. When an account deletion is processed, active account-owned state such as sessions, licenses/grants, device activations, transfer balances/ledger, referral state, profile and subscription state is removed. Payment and analytics records may be retained in de-linked form where necessary for accounting, security, disputes or legal requirements. A limited hash of an unexpired email-verification token may temporarily remain until the original token expiry so a recreated account can complete the same mailbox proof; this does not restore the deleted account's sessions, licenses, devices, transfers or profile.

Local Memory items are deleted by the user from ContinuForge or by clearing local extension data; account deletion on the server does not by itself reach into Chrome and erase local browser storage.

15. Security

ContinuForge uses HTTPS/TLS for the public website and API. Authentication secrets are not published. Passwords are stored as hashes rather than plaintext. Locally stored ContinuForge Memory is not published by ContinuForge. No service can promise absolute security, and users should not send passwords, session tokens or payment-card details to support.

16. Chrome permissions and host access

The permissions used by ContinuForge 1.1.140 are described in detail on the Chrome permissions page. They include storage, contextMenus, activeTab, scripting, alarms, webRequest and declarativeNetRequest, together with limited host permissions for ChatGPT/OpenAI, ContinuForge and OpenAI file-delivery domains.

17. Chrome Web Store Limited Use

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

Extension user data is collected, used or transmitted only as necessary for ContinuForge's disclosed single purpose and related operation, security, reliability and measurement.
Web browsing activity is accessed only where required for a user-facing feature initiated or used by the user.
User data is not sold.
User data is not transferred to advertising platforms, advertising networks, data brokers or information resellers.
User data is not used for personalized, retargeted or interest-based advertising.
User data is not used to determine creditworthiness or for lending.
ContinuForge personnel do not obtain access through ContinuForge servers to locally stored ChatGPT/Memory content. If a user voluntarily sends specific material to support, that material may be read only to handle the support/security request or as otherwise required by law.

Chrome Web Store policy information: Limited Use and Handling Requirements.

18. Changes and contact

If ContinuForge materially changes how extension user data is collected or used, this policy will be updated and the change will be disclosed as required. Questions, privacy requests and deletion requests: support@continuforge.com.