Chapter 24
Privacy and Security
You write something that belongs to you. This chapter tells you where your texts live, what Goethe Write does with them and what it does not do, who can see them, and how keys are kept. It has four parts:
In short: Your projects stay where you save them. Text goes to a provider only when you ask Goethe for something, with your own key, without going through a Goethe Write server. Nothing is sent in the background. This is also stated in Settings ▸ Privacy.
Where your texts live
The project file
A project is one file with the extension .lexwrite. In the Finder it looks like a document; in truth it is a package, a folder that macOS treats like a file. Inside it are:
| Part | Contents |
|---|---|
| project.json | The outline, the details of characters and places, the project’s settings (including the House Rules for Goethe), the comments, the Goethe log if you turned it on, and the state of the window (where your cursor stood) |
| texts/ | Each text as a file of its own |
| files/ | The Research files (PDFs, images) |
| snapshots/ | Your snapshots |
The settings of this device (window sizes and preferences, for example) do not go into the file; they go into this Mac’s own store.
You decide where the file lies. You choose the place when you save, and you move it with File ▸ Move Project…. Goethe Write sends the file nowhere. If you put it in a folder that another service syncs (iCloud Drive, say), what that service does applies to this copy.
Important: If you pass on the project file, you pass on everything in it: the texts, the Research files, the snapshots, the comments, the house rules and the Goethe log. If you need a copy without some of that, duplicate the project and delete it there, or export only what is needed (see Chapter 14).
Automatic saving and versions
macOS saves your project continuously by itself. You find earlier states under File ▸ Revert To: Last Saved and Browse All Versions…. More in Chapter 15.
The backups
In addition, Goethe Write makes backups. They always run; there is no switch for them:
- when you close the project,
- every 30 minutes while you work (and only if something has changed),
- right away when you choose File ▸ Backups ▸ Back Up Now.
Each backup is a ZIP file of the whole project, named after the project and the time. It lies in a folder per project. Under Settings ▸ Backups you set:
- How many backups stay. The newest ones stay; you choose from 3 to 50 (default: 10). Older ones go to the Trash.
- Show in Finder opens the backups folder on this Mac.
- Second Location: a folder for a second copy of every backup, such as on an external drive. If the location can’t be reached for a while (drive disconnected), the next backup catches up on the missing copies.
With File ▸ Backups ▸ Browse… you look at a project’s backups. You can Open as Project the whole backup (it opens as a separate, locked project) or Restore single texts: that puts a copy next to the current text, and the current text stays as it is.
Important: A backup is a complete image of the project, with everything that is in the project file. Keep it the way you would keep the project file.
More on backups and getting things back in Chapter 15 and Chapter 25.
The program’s folder
Goethe Write keeps its own things in the program’s “Application Support” folder, under the name Goethe Write: the backups (in the subfolder Sicherungen), your own templates, Goethe’s logs (in the subfolder Goethe-Protokolle) and the mirrors of other Macs’ projects (in the subfolder Goethe Link). In addition there are copies for the preview in the Finder (Quick Look) in the “Caches” folder; they are made again when needed.
You open the backups folder easily with Settings ▸ Backups ▸ Show in Finder, and the logs folder with Settings ▸ Privacy ▸ Show in Finder (when the log is turned on).
Another Mac’s project: the guest mirror
If you open another Mac’s project as a guest with File ▸ Open Project from Network… (see Chapter 17), your Mac makes a copy of it, the mirror. It lies in the program’s Goethe Link folder. The following applies:
- It is a copy for working along. The project belongs to the Mac that shares it (the host).
- Your Mac makes no backups of the mirror. The host’s Mac does that.
- A mirror is never saved by itself and opens only through a session as a guest. If you open it another way (for example from the recent documents), it is a copy to read.
- A mirror may grow to about 2 gigabytes at most.
- You delete it like any file when you no longer need it. The host’s project is not affected.
What lies where: an overview
| What | Where | Who can reach it |
|---|---|---|
| Your project | Where you save it | Whoever has access to that file |
| Backups (ZIP) | In the program’s Sicherungen folder, optionally a second location | Whoever has access to your Mac or the second location |
| Goethe log | In the project file and as a text file in the Goethe-Protokolle folder | as above |
| Your API keys | In this Mac’s keychain | Only this program, while the Mac is unlocked |
| Mirror of someone else’s project | Goethe Link folder | Whoever has access to your Mac |
| Settings of this device | In this Mac’s store | This program |
Encryption and keychain
You don’t have to understand any technology for this. Here is what the app does and what you get from it.
The keychain
The keychain is macOS’s vault for passwords and keys. Goethe Write stores there:
- Your API keys for Goethe (one per provider, if you have set up several). They are never in a file, a log, a setting or an error message. After saving, the app shows only a hint like “•••• 4F2a,” the last four characters. The key can be read only while your Mac is unlocked, and it is never synced with other devices. For a custom server, the key is tied to its address and goes only there.
- The device keys of Goethe Cloud and the keys of the projects that are shared. They stay only on this device: they are not in the iCloud keychain, and they do not come along in a backup you restore on another device. Where a key is stored, only its label stands there, never its content.
You can see the entries in the Keychain Access app under the names “com.lexxington.goethe” (API keys) and “com.lexxington.goethe.cloud” (cloud).
Removing a key: Settings ▸ Goethe, then Remove… at the provider. The key is deleted from the keychain; at the provider it stays valid, so revoke it there too if you don’t want it any more.
Tip: An API key is like a credit card the provider charges. Share it with no one. If you suspect it has fallen into the wrong hands, revoke it at the provider and create a new one.
Goethe Link: encrypted between devices
With Goethe Link, Macs, iPads and iPhones work on the same project (see Chapter 17). This is protected without your setting anything up:
- Encrypted connection. Texts and names travel over the network only encrypted. Anyone who records the traffic sees only unreadable noise.
- No name on the network. On the network your Mac appears under a neutral name such as “Goethe-7F3A,” new with every start. Your name, your Mac’s name and the project’s name go only inside the encrypted connection.
- Pairing with a comparison. You pair a new device only while you have Pair Device… open (two minutes). Both devices show six digits that you compare. If they match, the device belongs. Several wrong attempts in a row block pairing for a while. Comparing is only needed the first time.
- Read first, write later. A new device can only read at first. It may write only once you switch on May Write for that device and that project. A paired device gets a project only if you allow it for that project.
- One writes, the others read. Only one person writes in a text at a time. That protects against conflicting changes. What a guest types is never lost silently: if it is refused, it stays as “not delivered” so that you decide.
- Disconnecting a device. With Disconnect you end a connection; with Unpair your Mac forgets the device.
So that devices on the same network can find each other, macOS asks whether Goethe Write may use the local network. The system explains: “Goethe Write uses it to find iPhone, iPad and other Macs on the same network to work on a project together, and to reach your own AI server on the local network, such as Ollama or LM Studio.” If you don’t allow it, no device finds your Mac (System Settings ▸ Privacy & Security ▸ Local Network).
Coming soon: Sharing over the internet (not just on the same network) needs a service of Goethe Cloud called the “relay.” The app is prepared for it; the service is not in operation yet. If it can’t be reached, the app says so honestly: “The internet service is not reachable right now. Goethe Write keeps trying; in the same network it works without it.” Invitation links are meant for this: they work once and for seven days, whoever opens one joins without comparing digits, and you can withdraw them. So send such a link only to the person you mean. More in Chapter 17.
Read links: the key is only in the link
With a read link (in the sharing window under Read in a Browser), others can read your manuscript and your screenplays in any browser, also on Windows and also while your Mac is off. This is how it is protected:
- Your project lies in Goethe Cloud only encrypted. The service keeps encrypted data and nothing else.
- The key is only in the link, in the part after the “#,” which a browser never sends to a server. Whoever has the link can read; without the link the state is unreadable.
- Send the link only to the people who should read. Whoever has it reads.
- Comments from the browser also wait encrypted until your Mac fetches them. You can set whether readers may comment (“Readers may comment”).
- The new state follows after every save, at most every two minutes.
Note: Read links need the Goethe Cloud service. If it can’t be reached, the app tells you. (See also Chapter 18.)
What Goethe and the provider see
The short answer
| Who | What they see |
|---|---|
| You, on your Mac | Everything |
| Goethe Write (program and team) | Neither your keys nor your texts for Goethe. Goethe Write runs no server that Goethe requests pass through. |
| The provider you chose | Only what you send with a request to Goethe (see below), and only after you have allowed it. Its privacy policy applies there. |
| Your own server on this Mac | What Goethe sends, but it does not leave the Mac. |
What goes to the provider
When you ask Goethe for something, this goes to the provider:
- Goethe’s instructions (its role and principles), plus your house rules and your own instructions.
- The passage in question, or the text, folder or project, depending on how far you let Goethe read (about 60,000 characters at most).
- The sources you explicitly include (about 40,000 characters at most).
- Brief project details (title, synopsis, characters and places), if “Send Project Details” is turned on (about 4,000 characters at most).
- Your request.
Nothing goes out in the background. There is no secret request. More in Chapter 16.
Permission
Before text goes to a provider for the first time, Goethe asks you, once per provider (for a custom server: per address). The question says what goes, to whom, and that the provider applies its own rules. With Don’t Allow, nothing goes out. You can withdraw at any time: Settings ▸ Privacy (or Settings ▸ Goethe ▸ Privacy) shows which provider you allowed and when, with the button Withdraw Permission. If you turn “Send Project Details” back on later, Goethe asks again.
With Google Gemini in the free tier, Google may use inputs and responses to improve its services, and people may read along. For confidential texts, use only a paid account. OpenRouter passes the request on to the provider of the chosen model, whose terms also apply.
Locks: what Goethe never sees
With Entry ▸ Hide from Goethe you make texts and folders invisible to Goethe. What is hidden never goes to the provider: neither as material nor as a source nor in the project details. A hidden folder hides everything below it. More in Chapter 16.
Tip: If you have a brief with client data, hide it before you ask Goethe anything for the first time.
The log: knowing what Goethe did
With Keep a Log (Settings ▸ Privacy), Goethe writes down every applied result: when, with which model, what was asked, what happened. For every changed text there is a checksum of its wording before and after. The wording itself is never in it. The log lies in the project file and as a text file on this Mac, and it is off by default.
No usage data
The page Settings ▸ Privacy states: your projects stay where you save them. Text goes to a provider only when you ask Goethe for something. Nothing is sent in the background, and the app collects no usage data.
A problem report contains no project text
Help ▸ Report a Problem… prepares a message to hello@lexxington.com in your mail program. It holds the version of Goethe Write, the system of your Mac and the language of the interface, plus three questions that you answer. It never contains text from your project, and no file is attached. Goethe Write sends nothing by itself: you read the message and send it yourself. What you add or attach besides is your decision. More in Chapter 25, section "The developers".
Notice and contact
Who makes Goethe Write
The window Goethe Write ▸ About Goethe Write shows the app’s icon, the name, “German Software,” the version and:
- Developed by Nami Shams and Team
- © 2026 ICSL FZE, Sharjah. All rights reserved.
Goethe Write is a product of ICSL FZE, Sharjah. As the window says, the copyright in the software lies with this company.
Your Goethe Cloud account
For Goethe Cloud there is an account that you create and manage in the browser at account.goethecloud.com. You sign in with your email address: the page sends you a six-digit code that is valid for 10 minutes, and you need no password. There is also Sign in with Apple. On the page you can:
- choose the language of the page and of the emails,
- sign out, or sign out on all devices,
- delete your account (this deletes your Goethe Cloud account and signs you out everywhere; your documents on your Mac are not touched, and it cannot be undone).
The page also says: “Goethe Cloud is not open yet. Today this page creates your account, so it is ready when the service opens.” More on the subscription and the account in Chapter 18.
Privacy policy, support and terms
At the bottom, the account page links to these pages:
| Page | Address |
|---|---|
| Website | https://goethecloud.com/ |
| Privacy | https://goethecloud.com/privacy/ |
| Support | https://goethecloud.com/support/ |
| Terms | https://goethecloud.com/terms/ |
Note: These addresses stand as they are on the account page. If they change, the links there apply.
In the app, Help ▸ Privacy Policy opens the privacy policy of Goethe Write in your browser (the page goethecloud.com/privacy). It says there, in the language of the law, what this chapter says in plain words.
Contact and help
- Help in the application: Help ▸ Goethe Write Help (that is this manual).
- Support: the support page above, or an email to hello@lexxington.com. Help ▸ Report a Problem… prepares it for you, with version and system but without text from your project.
- Privacy: Help ▸ Privacy Policy.
- Problems with Goethe, connections, import or export: Chapter 25.
- Questions about the subscription through Apple: in Goethe Write ▸ Goethe Cloud… and in your settings at Apple (see Chapter 18).
Note: This manual describes what the application does today. What is planned appears in a box labeled Coming soon. That is not a promise of a date.