Privacy
This page covers what Ghostwriter sends to the model and the photo libraries, what it never sends, and what it keeps in your database.
What is sent, and where
Nothing is sent anywhere until someone in the panel asks for it: by starting a piece, writing a guide, asking for kinds or ideas, asking for suggested edits, or using the image button. Content to revisit, the link index and Finish this page's checks never send anything. Ghostwriter sends no analytics and doesn't phone home.
To the writing provider (Anthropic, OpenAI, Google or OpenRouter, whichever is chosen, on your own account, or the gateway you set). With OpenRouter, every request, images included, passes through OpenRouter on its way to the model's company, and OpenRouter's privacy policy applies too:
| When | What is sent |
|---|---|
| Writing or editing a piece | The voice guide, the kind's brief, guidance and checklist, the answers to the brief, the conversation, the form's fields (names, labels, helper text, hints, options), and up to six example records as YAML |
| Filling in a brief | The kind's questions, the person's reply (a working title and notes) or the plan idea, the titles of recent records, and after Try again the brief they didn't take |
| Linking a new draft to your pages | The draft, the voice guide, and the title, address, type and short summary of the records most likely to fit (from resources given ->publicUrlUsing()) |
| Suggest edits | The record's text as it is in the form, the voice guide, what the free checks found, and the titles and summaries of a few related records. The double-check gets the same page and the suggestions |
| Write it for me, Write around it, Write another | The field or sentence, and the page's own text around it |
| Writing the voice guide | The text of up to 24 published records |
| Changing the voice guide | The guide and your request |
| Suggesting or learning kinds | Titles and openings of up to 60 published records; for learning, the chosen examples in full |
| The content plan | Titles and the first lines of up to 150 records per resource (published or not), the voice guide, the kinds and the plan |
| The image style guide | Small copies of up to ten images per resource |
| Finding photos | The text of the block and page, small copies of images already used in that place, and thumbnails of the photos found |
| Making an image | The same text and images, your direction, and any image of your own you add (to the image provider) |
| Search title and description, with a first draft or Try again | The draft, the record's title and the resource's name |
| Suggest links in Finish this page | The record's text as it is in the form, and the title, address, type and short summary of the records it could link to |
| Comments: Apply | Your comments, the blocks they're on, the conversation and the current draft |
Records are read through the resource's own query, so only what the resource would list is ever read, scoped to the current tenant. A resource's records are only read for someone its policy lets list them (viewAny), and Model it on lists only records they may view.
To the photo libraries: search words go to Openverse, and to Unsplash, Pexels or Pixabay when their keys are set. Choosing a photo downloads it and, for Unsplash, tells Unsplash it was used. Only the search words are sent, never record content. Paid stock libraries get the same, plus the licence request when someone licenses a photo.
To Shutterstock, when it's set up: your search words, the photo you preview or license, and, when someone who manages Ghostwriter connects the account, the sign-in Shutterstock asks for on its own site.
To each service in Connections, on Check & save: one small test call with the key just pasted (a list of one model, or a search for one photo).
To other sites: only if Check links to other sites once a week is on, a HEAD request to each address your records link to, once a week. See Content to revisit.
What is not sent
- API keys, except each to its own service
- records beyond the samples listed above
- user details: names and email addresses stay in your app. A shared conversation's "Started by" names are shown in the panel, not sent.
Each provider's terms
How long a provider keeps what it's sent, and whether it may train on it, depends on its terms and your account. On paid API plans, Anthropic, OpenAI and Google don't train on API data by default. Gemini's free tier is different: Google may use what's sent to improve its products. See Google (Gemini, and images).
What is kept, and where
Everything is kept in your database, in the ghostwriter_ tables (see Where things are kept):
- Conversations in
ghostwriter_sessions: the brief, every message with who sent it, the draft, and who started and last changed each piece. Delete rows from that table to clear them; nothing else depends on old ones. - Photo requests in
ghostwriter_states, with the user who made each one. Made images not yet used wait on thelocaldisk underghostwriter/imagesand are cleared after a day. - The guides, kinds and plan, in their own tables.
- Reviews and their decisions in
ghostwriter_edit_reviews, with who made each decision and when. Suggestions nobody acted on expire after 14 days; decisions are kept as the page's history. - An index of your records (titles, summaries, paragraphs, public addresses) for Suggest edits, Content to revisit and links to your pages, in the
ghostwriter_index_andghostwriter_revisit_tables. It's rebuilt from your records, so it can be emptied at any time and refilled withphp artisan ghostwriter:revisit --full. - The stock image ledger, in
ghostwriter_stock_imagesandghostwriter_stock_usages. Licence records are never deleted.
Logs hold retries and failures, with the provider and the error, never keys (see Logging).
API keys are read from the environment when they're needed, and never shown. Your keys stay on your site. Ghostwriter sends them only to the provider you chose, never to us.
Keys set up in Connections are kept in the ghostwriter_credentials table, encrypted with your APP_KEY, per workspace, and never shown again (only their last four characters). If APP_KEY changes, they can no longer be read: set them up again. Keys in .env aren't affected. See Connections.