No analytics or session recording
No product analytics tool, no heatmap, no session replay. Nobody is watching a recording of you using the software, and there is no third party script collecting behaviour on this site.
Legal
Everybody outside this business who touches data on the hosted service, what they do, and what they can see. It is a short list, and two entries on it are still placeholders because the hosting and email providers are not finally chosen.
Data processing addendumPrivacy policy
A self hosted install has no sub-processors at all, unless you configure a language model key of your own.
Where an entry says placeholder, it means the decision has not been made and this page will be updated with the real name, the region and the date before anybody is charged.
| Who | What they do | What they can see | Region |
|---|---|---|---|
| Hosting provider, placeholder | Runs the servers, the database and the disk the uploads folder sits on | Everything, in the sense that any host can technically reach the data on its own machines | To be named before launch |
| Email delivery provider, placeholder | Sends account email: receipts, password resets, service notices, and replies to forms | Email addresses, names, and the content of messages sent through the site | To be named before launch |
| Stripe, through Paid Memberships Pro | Processes card payments and stores payment methods for recurring billing | Your billing details, your card, the amount and the plan. Never the content of your twins. | United States and Ireland, per Stripe's own terms |
| Language model provider, optional | Answers the three optional calls: extraction of prose the rules could not parse, rewriting a finished brief, and Ask | Only the text described on the language model page, and only when a key is configured. No files. | Depends on the provider configured |
Paid Memberships Pro is a WordPress plugin running on the same server rather than a third party service, so it is not itself a sub-processor. It is named here because it is the route by which card details reach Stripe, and people ask.
Not on the list
Each of these is a category of vendor commonly found in a SaaS stack. None is used here, and if one is ever added it will appear above with thirty days of notice.
No product analytics tool, no heatmap, no session replay. Nobody is watching a recording of you using the software, and there is no third party script collecting behaviour on this site.
No pixels, no remarketing tags, no conversion trackers. This is why there is no cookie banner: there is nothing to consent to.
Support is email to a person. There is no ticketing tool with a copy of your data in it, and no chat widget loading a third party script into the application.
Form submissions are a row in this site's own database. They are not sent to an enrichment service to be matched against a firmographic profile.
Errors are written to the server log on the host. That is worse for debugging and better for privacy, and it is an honest description of where things stand today.
Backups are whatever the hosting provider runs. When that is chosen, the retention and the region will be named here.
Adding or replacing a sub-processor is a change worth being told about, so the process is fixed rather than discretionary.
An emergency replacement, for example a hosting provider failing, may happen faster than thirty days. In that case notice goes out as soon as the change is made, with what happened and why, and the same objection right applies afterwards.
If you self host, none of this affects you. Your sub-processors are your host and, if you configure one, your language model provider.
Two WordPress plugins on your own hosting, no outbound calls unless you configure a key, and nobody in the middle. The installation guide is written for somebody who has installed a plugin before and nothing more.