The Anthroposophy AppThe Anthroposophy App

AI statement

Where AI touches your content

AI touches what members put on my app in one place only, and that is the reading of newsletters: a file sent through the Upload button in the sidebar, or a newsletter emailed to the app, is read by Mistral AI, a company in France, which lists the events and articles printed in it. Adding a picture to a post, or posting in a group in the ordinary way, sends nothing to AI at all.

A reader may also ask for a page in another language, in which case the text of that page is sent to Google’s translation service, although translation is switched off at present.

Every post, comment, event, group and message on my app is put there by a person, and moderators review every report that is made.

Private groups

I have set up private groups so that Claude, the AI I used to write my app’s code, cannot read what is posted in them, and neither a private group nor a direct message appears on any public page. Sensitive material that you do not want AI to touch therefore belongs in a private group, and it should not be sent through the Upload button.

Public pages

Anything a member posts publicly can be read by anyone, as is the case on any website. AI companies run programs that collect public web pages in very large numbers to train AI models, and this applies to every public website, mine included.

AI is also already part of the tools most people use every day. Gmail, for instance, uses AI to filter the mail that passes through it, and now builds Google’s Gemini AI into the inbox. Someone who wanted none of their work to touch AI would really have to stop using services such as Gmail, and stop uploading anything to the internet at all.

How the app is built

I wrote the code for my app with Claude, an AI made by the company Anthropic, and Claude maintains and updates the app at my direction. Building it this way has kept its costs near zero.

Claude can see the code, the layout of the database, and the public pages that any visitor can see. Whenever Claude asks to read from the database, the answer it gets back is a bare count of rows, and so the posts, events, messages, names and email addresses held there are never shown to Claude. Furthermore, a check that runs before each of Claude’s commands refuses any other way of reading the database. That check works by matching the wording of commands, so it recognises a command written in the ordinary way, and a standing rule that Claude reads no member’s content covers the rest.

Why Upload uses AI

Many groups already put a great deal of work into their newsletters. Upload lists the events and articles in a newsletter for them, and nobody then has to type each study group, talk and festival into a form a second time.

Limits on Upload

  • Copying: an article taken from a newsletter is reproduced word for word, and Mistral AI is instructed not to summarise, translate or rewrite it, nor to invent a venue or any other detail that the newsletter does not print.
  • Dates: the dates and times of events are worked out by my app’s own code under fixed rules, and an event whose date cannot be read with certainty is held back for a person to check before anyone is shown it.
  • Instructions: Mistral AI is told that a newsletter is information only, and that any words in it that look like instructions are to be treated as ordinary text and ignored.
  • Privacy: the file goes to Mistral AI together with any covering email text and the dates needed to read it, with no member’s name, email address or account details attached. On my app’s Mistral AI account, as its settings were on 26 September 2026, the use of these files to train Mistral’s models is switched off, and nothing is kept once the file has been read.

The privacy policy names every service that receives members’ information.