Privacy Policy

Privacy at a glance

• Fork history and conversation snapshots are stored locally in your browser using Chrome extension storage.
• We do not persist or log ChatGPT conversation content on our backend.
• When you submit a Fork or Apply request, the relevant conversation context is sent to our backend for in-memory processing and then to OpenAI to generate the requested result.
• OpenAI may retain submitted API content for abuse monitoring for up to 30 days unless stronger account-level retention controls apply.
• Google Cloud Run may retain standard request metadata such as IP address, URL, user agent, status, and request/response sizes, but observed logs do not contain conversation bodies.
• Exported fork-history JSON files remain on your device and are managed by you.

1. What ChatGPT Fork accesses

ChatGPT Fork runs on chatgpt.com and reads the parts of the ChatGPT page needed to provide the fork feature. When you create a fork, the extension may capture:

• the selected assistant response block and related source metadata;
• the user and assistant conversation transcript up to the selected message;
• ChatGPT conversation and message references used to associate local fork history with the correct conversation; and
• fork messages, titles, timestamps, model metadata, and apply status created while you use the extension.

The extension does not intentionally access ChatGPT cookies, passwords, payment information, browser history, geolocation, arbitrary browser tabs, or files/images you upload to ChatGPT.

2. Local storage

ChatGPT Fork stores conversation snapshots, source text, fork history, fork messages, timestamps, titles, model metadata, and apply status locally in chrome.storage.local. We do not receive this locally stored content unless you actively submit a Fork or Apply request.

The extension may also store limited interface state locally and cache a Google OAuth access token in chrome.storage.session for the current browser session.

You can delete individual forks, clear fork history, export fork data, or import previously exported fork data. Clearing fork history removes fork-thread data but may not remove separate authentication session state or interface preferences.

3. What happens when you submit a Fork or Apply request

When you submit a Fork or Apply request, ChatGPT Fork sends the relevant selected content and conversation context to the ChatGPT Fork backend so the request can be processed.

Depending on the action, the request may include:

• a fork identifier;
• selected source text and source type;
• the relevant parent conversation transcript;
• the fork conversation transcript; and
• your current question or requested apply action.

ChatGPT conversation references and message IDs used to organize local fork history are not included in the normal AI request payload.

4. Our backend does not persist conversation content

We do not persist or log ChatGPT conversation content on our backend. Submitted request bodies are processed in memory only for the time needed to complete the request. The backend does not use an application database or filesystem to store prompts, conversation transcripts, or generated responses.

5. OpenAI processing

After a Fork or Apply request reaches the ChatGPT Fork backend, the context needed to generate the requested result is sent to the OpenAI API.

The backend uses the OpenAI Responses API with store: false, which disables Responses application-state storage. OpenAI may still retain API content for abuse monitoring for up to 30 days unless stronger account-level data-retention controls apply. OpenAI's independent retention and processing practices are governed by OpenAI's applicable policies and account settings.

6. Google sign-in and authentication

ChatGPT Fork uses Google OAuth for identity verification and requests OpenID and email scopes. The OAuth access token is sent to the ChatGPT Fork backend and verified with Google.

The backend may temporarily hold the access token, Google account subject identifier, and optional email address in memory for authentication, rate limiting, and concurrency controls. This information is not written by the application to a persistent database.

7. Applying content back to ChatGPT

When you choose Apply to main chat, ChatGPT Fork inserts the generated apply text into the ChatGPT composer and submits it to ChatGPT. That content is then handled by ChatGPT under OpenAI's applicable terms and privacy practices.

8. Hosting and operational logs

The ChatGPT Fork backend is hosted on Google Cloud Run. Our application logs limited operational metadata such as request ID, HTTP method, path, status, and duration. It does not intentionally log request bodies, response bodies, authentication tokens, conversation text, email addresses, or request headers.

Google Cloud Run may independently retain standard request metadata such as IP address, requested URL, user agent, HTTP method, protocol, status, request/response sizes, and latency. Observed Cloud Run logs do not contain conversation request or response bodies. The currently observed request logs use Google's default logging retention of approximately 30 days.

9. Third parties that may receive data

• Google OAuth — identity verification.
• Google Cloud Run / Cloud Logging — backend hosting and standard operational request metadata.
• OpenAI API — processing submitted Fork and Apply context to generate results.
• ChatGPT — receives text you choose to submit back to the main conversation.
• Google Chrome — provides extension storage, identity APIs, and Chrome Web Store distribution.

10. Analytics, advertising, and sale of data

ChatGPT Fork does not include runtime analytics or telemetry SDKs, advertising trackers, fingerprinting, behavioral advertising, or data-broker integrations. ChatGPT Fork does not sell or rent user data.

Chrome Web Store publisher analytics, if provided by Google, are generated by the Chrome Web Store platform and are separate from the extension's own runtime behavior.

11. Exported data

If you export fork history, the resulting plaintext JSON file may contain conversation text and fork messages. The exported file remains on your device and is managed by you. We do not automatically upload exported files to our backend.

12. Your controls

• Delete individual forks.
• Clear stored fork history.
• Export fork history.
• Import previously exported fork history.
• Sign out of the extension.
• Disable or uninstall the extension through Chrome.

13. Security

OpenAI API credentials are kept on the server and are not included in the browser extension bundle. ChatGPT Fork does not intentionally read or store your ChatGPT cookies, passwords, or payment credentials.

14. Changes to this policy

This policy may be updated as ChatGPT Fork changes. Material changes will be reflected on this page with an updated effective date.

15. Contact

Privacy questions can be sent to support@northboundsoftwaregroup.com.