Last updated 23 September 2026

Privacy policy

StoryRoom Queue for ChatGPT runs inside your own browser. It has no server of its own, no account and no analytics. One optional feature, email notifications, involves a third party, and only if you turn it on.

StoryRoom Queue for ChatGPT is an unofficial browser extension. It is not affiliated with, endorsed by, or connected to OpenAI.

Summary

Nothing the extension reads is sent anywhere except to ChatGPT, in the conversation you selected, as a message you asked it to send.

The single exception is email notifications. They are off until you switch them on and supply your own Resend API key, and even then your story text is not what gets sent. What the mail contains is set out below.

What the extension handles

Project files you choose

When you select a configuration file, its contents, meaning the project ID, chunk text and prompts, are read in the browser and stored in the extension's local storage so a run can resume after the popup closes.

Prompts sent to ChatGPT

The extension types the prompt from your configuration into the ChatGPT composer in the tab you selected and presses Send. It sends nothing else, and nowhere else.

Responses from ChatGPT

It reads the text of the assistant's reply in that conversation to check it against your configuration. When a reply arrives as a generated .json file, it retrieves that file's contents from ChatGPT so the result can be checked and stored. Accepted results are kept in the extension's local storage.

Your ChatGPT session

To retrieve a generated file, the extension runs a request in the ChatGPT page itself, using the session already signed in to that page, to ChatGPT's own address. Any credential involved stays inside that page for the duration of that request. The extension does not read, copy, store or transmit your password, session cookie or access token.

Files saved on request

Files are written to your download folder only when you turn on Also save each result file to disk, or when you click Export results.

Email notifications

This feature is off by default. It stays off until you open the extension's settings page, enter a Resend API key of your own, set a sender address and add at least one recipient. If you never do that, nothing in this section happens and no request is ever made.

What is sent, and to whom

When a project finishes, or when a run stops after its retries are exhausted, the extension sends one message to Resend (api.resend.com), the delivery service, which then mails your recipients. Resend is an independent company and its own privacy policy and terms apply to that account, which is yours, not ours.

The message contains:

  • the project title, or its project ID when no title is set;
  • whether the run completed or failed;
  • the link to the ChatGPT conversation it ran in;
  • the date and time;
  • a short note on the outcome, up to 700 characters. For a completed run this is a count of accepted chunks. For a failed run it is the validation errors, which can quote small fragments of the reply that was rejected.
  • the sender name, sender address and recipient addresses you configured.

Your chunk text, your prompts and your accepted results are not sent. The templates are yours to edit, so if you add other content to one, that content goes too.

Your Resend API key

The key is stored in this browser profile under chrome.storage.local, exactly like the rest of the queue. It is held in the extension's background worker and is never exposed to the content script running on ChatGPT pages, never sent anywhere except to Resend as that request's authorisation, and stripped out of any error message the extension displays or logs. Use a key restricted to this purpose, and revoke it in Resend if you stop using the feature.

Turning it off

Clear the enable switch on the settings page, or clear the key. Removing the extension deletes the settings with everything else.

What the extension does not do

  • It does not transmit any data to the developer.
  • It does not use analytics, tracking, advertising or fingerprinting.
  • It does not sell or share data with anyone.
  • It contacts no third party at all, other than Resend when you have switched email notifications on and configured them yourself.
  • It does not read pages other than chatgpt.com and chat.openai.com.
  • It does not collect names, email addresses, passwords, payment details, location or browsing history.

Where the data lives, and removing it

Everything is stored locally by Chrome, on your computer, under chrome.storage.local. It is not synced to any account. You can delete all of it at any time with Clear saved queue in the popup, or by removing the extension. Files you explicitly exported or saved remain in your download folder until you delete them.

Permissions

Each permission the extension requests, and why:

  • storage, unlimitedStorage: keep the queue and accepted results locally, so a run survives closing the popup. Results can be large.
  • scripting: start the extension's own page script in the ChatGPT tab, rename a conversation, and retrieve a generated result file.
  • downloads: write the export you requested and, if you enabled it, save result files. Also used to discard a download started only to obtain a file's address.
  • alarms: wake the extension periodically so a run in a background tab keeps progressing.
  • clipboardWrite: copy a result to your clipboard when you press a copy button.
  • Access to chatgpt.com, chat.openai.com and *.oaiusercontent.com: the pages the extension works in, and the address ChatGPT serves generated files from.

Children

The extension is not directed at children and collects nothing from anyone.

Changes

If this policy changes, the date above will change with it, and the updated policy will be published at the same address.

Contact

Questions about this policy: be.tools9x@gmail.com.