Privacy

Last updated 13 October 2026

Who is responsible

MastermindStack is operated by Archer Futura Technologies AB, a company incorporated under the laws of Sweden with its registered office in Stockholm, Sweden, the controller of the personal data described here. Questions and requests: contact@modelgraphx.com.

What we collect and why

• Your account. Your name, email address and how you sign in, so you can have an account and reach your projects. Sign-in is handled by our authentication provider, Clerk. We never see your password.
• Your work. The projects you create: manuscripts, revisions, images, captions, book covers and published editions; and the templates you keep for yourself, with every version of each and the Word file a template's look comes from. We store them to provide the service to you and use them for nothing else. A template you keep for your company is one of its documents, kept in its register as other company documents are. If you keep a Vault, the text and images of your projects are also written to a folder you choose on your own computer, outside our systems. A change you suggest in a project, rather than make, keeps the name your account shows and the time you made it in the project's text, in its revisions and in the Word file made from it, until it is accepted or rejected; one the chat suggests is marked as Claude's. A comment on a project's text keeps the name your account shows, the time, and the words it is on, with the replies to it and whether it is resolved, for as long as the project is kept; it is written into the Word file made from the project. A Word document you bring into a project keeps its comments the same way, with the names and times its file gives; a comment the chat writes, once you approve it, is marked as Claude's and signed with the model that wrote it: its name, its provider, the model's exact identifier, when, and what it did, the same signature the words a model writes carry, in Write and in the Word file made from the project. Its charts, SmartArt, text boxes, equations and embedded objects are kept as they are in its file, each with the project as a small Word file of its own, and go back into the Word file made from the project.
• A project’s materials. What you add to a project’s Materials, as what it is written from, is kept with the project: files you upload (in a private store, under the project), the addresses of web pages with the date you read them, references to documents of your company’s register (the register keeps the documents themselves), and notes, each with the details for citing it that you give or that a file says about itself (its title, author and year). You and the people you share the project with can open them; its owner and editors change them. Removing a material removes it, and its file when no other material of the project keeps the same file; deleting the project removes them all.
• A document’s figures. To show what each document of a project is in figures (its pages, slides, sheets, sections or lines, its words, characters and pictures, and the chunks a review reads it in), your browser measures the file once and keeps the numbers for you, by the file’s fingerprint (its SHA-256), so it is not read again to be counted. Only the numbers are kept, never any of the file’s text; they are yours alone, at most 20 000 files’ worth, the oldest measured going first. Measuring a document of your company’s register reads its file as opening it does.
• Spelling. The spelling of what you write is checked in your browser, with dictionaries the app loads from our site; none of your text is sent anywhere to be checked. A word you add to your dictionary is kept with your account, with its language, so every project of yours takes it; only you can see your words, at most 10 000, and you remove one in a project’s Settings. A word you ignore is forgotten when you leave the app.
• A review. A review project keeps what it reviews and how: which of your projects, which version of a register document, and the files and web pages you give it, kept as they were (a file in the same private store as materials; a web page as its text, with its address and the time it was read). To read a web page, our server fetches that address on the public internet once, when you add it; it never reads addresses inside a private network. Each finding is kept as written, with the name of whoever found it and when, and each decision about it likewise, with its reason; neither is ever changed. You and the people you share the review with can read them; whoever found a finding may withdraw it while it is open. A reviewer you invite sees only the findings they made themselves; you and the review’s editors see them all. When a project or a register document is reviewed, a copy of the version reviewed is kept with the review, so the reviewers you invite can read it. A returned copy you read into a review is kept with it, and its comments and tracked changes become findings under the names they carry. The review’s report is its own text, a revision like any other, naming who made it. A sign-off is kept as made, with the name of whoever signed it off, the time and the verdict, and so is a reopening, with its reason; neither is ever changed. When you send the accepted findings back to a project, they go into a new revision of it as suggestions and comments under the names of whoever found them; to a register document, as its next working version. Reviewed copies are made in your browser and kept nowhere; a copy you make to send out for review is kept with the review as it was sent, so what comes back is read against it. A kind of review you make is kept as yours, in versions that are never changed, with who made each version; one an administrator keeps as the company’s is read by the company’s members. A review keeps a copy of the version of each such kind it uses, which the people it is shared with read. When you ask Claude to draft a kind, your description and the text of a reference document you choose go to the provider of the model you choose; the document itself is not kept. When you ask Claude to suggest a review’s scope, the beginning of the text of each thing reviewed and the names and descriptions of the kinds of review on offer go to the provider of the model you choose; nothing is chosen or kept until you use the suggestion and save the scope. The documents a review is held to (a standard, a specification, a design basis) are kept with it as its subjects are; when Claude reviews, the parts of their text most related to what it reviews go with the request to the same provider, and a finding keeps which of them it rests on and where. With “Read the figures too” on, for the kinds of review that look at figures, a PDF reviewed goes whole to the same provider, and a Word file’s or a project’s pictures go as small images with their captions; nothing more is kept. A long document is read whole first into a short map of what it defines, states and refers to, made by the same provider from the same text; the map goes with each part’s review and is not kept. Deleting the review removes its findings, decisions and sign-offs; what was sent back stays with the project or document it went to.
• Voices you keep. A voice you write or make your own (its name, what it is for, how it sounds in words, its rules, what it was made from) is kept with your account, with every version of it, until you delete it; only you can see it. A project records which voice it is written in and its version. A voice in the manner of a writer or public figure describes their manner in our own words and holds none of their text. When you learn your own voice from your writing, the writing you choose is measured in your browser and not kept: the voice keeps what it counted (such as sentence length and how often you ask questions) and the names of the projects, register documents and files it was learned from, never the texts. A voice you export is a file on your computer; one you import is read in your browser and kept only when you save it. In a project written in a voice, each suggestion of the chat or the writing agent that you accept or reject is kept for that voice, so it can offer you rules learned from your decisions: whether you accepted it, the words it would remove and add, who suggested it and the project. Only you can see them; they change no voice unless you keep a rule, and they are removed when you choose Forget my decisions or delete the voice.
• Projects you share, and projects shared with you. When you share a project, we keep the email address you invite, the role you give (editor or commenter), your name as the invitation shows it, the project’s title at the time, and when the invitation was accepted, withdrawn or declined. Only the person whose own account carries that address can accept it. Someone who accepts is kept as a member, with the name their account shows: you see their name, address and role; they see the names and roles of everyone who has the project, but not anyone’s address. If you started the project from a template of your own, they can read that template as the project uses it. A member sees the project’s text, its revisions, pictures and comments; what they write, suggest and comment is kept in the project with their name. An address with no account yet is sent an invitation to make one by Clerk, our sign-in provider. Removing someone, or their leaving, ends their access; what they wrote stays in the project’s history, as yours does.
• Your conversations with the chat, if you use it. What you write to the chat, its answers, what it found and read for you, the changes it proposed and whether you approved them, and the drafts it wrote, kept with your account so you can come back to them. A conversation started from a project's Write (its Agent) is kept with the name of that project, so it opens again where you left it; it is still yours alone, even on a project shared with others, and stays yours if you leave the project. Only you can see them. Deleting a conversation deletes it with its drafts.
• Your company's documents, if your company keeps its document register here. The documents its members add, with their versions, who they came from or went to, and a record of who did what and when, downloads included. Every member of the company can read them, and its administrators decide what is issued, withdrawn or voided. The record cannot be changed, so it can show what happened to each document. When a member uses suggested details, the proposal and what the member kept or changed are recorded, so later suggestions improve. When someone outside the company sends a document back with comments, markings or changes, a review round keeps what they did in the file and who in the company decided what about it, and only the document's owner and the company's administrators can see it. A member who keeps a Vault gets copies of the company's documents in a folder they choose on their own computer: each copy is recorded as a download, and the copies themselves are outside our systems.
• Your public page, if you make one. The address and name you choose, the publications you put on it and any share image you choose as a link preview are shown to anyone who visits the page, in its RSS feed and in link previews on other sites. Nothing is public until you publish it; taking a publication down stops it being shown. We keep a record of when you published and took down each publication. We do not record who reads your page.
• Accounts you connect, if you do. When you connect LinkedIn, Bluesky or Mastodon to post from MastermindStack, we keep the account's identifier and name and the access the platform grants us, encrypted with a key held apart from the database. We use it only to publish the posts you write and schedule, and we send the platform only those posts. Disconnecting deletes it and cancels posts still waiting to go there, and for Mastodon also withdraws the access at your server; you can also withdraw it from the platform's own settings.
• How your posts do. For each Bluesky or Mastodon post made here, we read its public counts (likes or favourites, reposts or boosts, replies and quotes) from Bluesky's public service or from the post's own Mastodon server, every 15 minutes on the first day and every 6 hours after, for 30 days, and keep the latest counts while your account exists, to show you how the post is doing. LinkedIn shares no post figures with us. We record nothing about the people who read your posts or your pages.
• Technical records. Our hosting and database providers record technical details of requests, such as IP address, browser and time, to run the service and keep it secure.

We process your account, your work and your company's documents to perform our agreement with you (the terms), the record of who did what in a company's register for the company's legitimate interest in showing what happened to its documents, technical records for our legitimate interest in running a secure service, and optional browser preferences only with your consent. We do not sell your data, use it for advertising, or train AI models on your work.

Who processes it for us

• Clerk: accounts, sign-in and company memberships, and the invitation to make an account sent to an address you share a project with.
• Supabase: the database and file storage holding your projects and your company's documents, in the European Union (Frankfurt, Germany).
• Vercel: hosting of the website and its server functions.
• Anthropic or OpenAI, as you choose: when you write with the agent, what it writes from goes to the provider of the model you choose (Anthropic for Claude, OpenAI for its models): the project’s title, what you say it is for, the materials you tick (their text, or a PDF whole, and small copies of the pictures in them) and the project’s voice. They process it on our behalf, in the United States, to write the plan and the slides or sections (for a text, its template’s headings and guidance and what you have written go too); the model’s name is kept with what it wrote, and what it writes cites the materials it rests on. When you have the text rewritten in the project’s voice, the words of the sections you tick go, a section at a time, with the voice, to the provider of the model you choose; what comes back are suggestions in Write, each with the model’s name, which you accept or reject. When you have part of the text revised through the chat, the paragraphs it is about (the words you selected, a section or the whole text), what you asked, and the materials it names go, a section at a time, to the provider of the model you choose, and what comes back is suggestions in Write in the same way. A new project made from a conversation keeps copies of the materials you choose from the project it is made from, in the same private store, as that project’s materials are kept. The first time the agent plans from a long material (one too long to send whole), it reads the whole of it, a few pages at a time, to the provider of the model you choose, which records what it says (its claims, figures, terms and names, each with the material’s own words and where they are); that fact sheet is kept with the project’s material, for the version read, and the people the project is shared with can read it as they can the material. It goes when the material or the project goes, or when you forget it, and a copy of the material takes it along. Writing from such a material, the model is given its fact sheet in place of its text: the whole sheet to plan, and for each section the facts that bear on it, each with where it is. Its owner and editors see a material's fact sheet in its project's Documents step, and can have it read again or forget it there. Once the agent has written a report, a book, an essay or an article, an editor reads what it wrote as one piece, unless you switch it off: the paragraphs written, the plan and the materials go to the provider of the model you chose, and what comes back are its suggestions and its comments, kept as yours are, signed with the model. When you ask for a picture to be made for a slide, the description you write, with the deck’s and the slide’s titles, goes to OpenAI’s image model; a picture you take is kept with the project’s materials, marked with the model that made it. When you ask Claude to review a review project’s subjects, the text of each subject you tick (in parts), the kinds of review with their checklists, and the review’s criteria go to the provider of the model you choose, which returns findings; the model’s name is kept with each finding.
• TypeSafe, Anthropic and OpenAI: when a member adds a document with suggested details, its text (or, for a PDF, the file) is sent to them to propose its details. They process it on our behalf, in the United States.
• Anthropic: when you use the chat, what you write, the conversation so far and what the chat reads for you from your projects (the project open in Write as it stands there, changes not yet saved and suggestions included, and a project's comments: their words, who wrote them and when, and their replies), their materials (the text of their files, page by page; a web page's address and your note on it, not the page itself), your templates and your company's documents, and, when you ask it to write a project, the plan the writing agent made for it (its sections or slides, what each says and the materials it rests on), and, in Write, the words you have selected there and the titles of the materials ticked for the agent, are sent to Anthropic to write its answers; on a project written in a voice, that voice (its name, how it sounds and its rules) goes with each request, so the chat's drafts and suggestions are in it; when you ask the chat to describe your own voice, the writing you chose for it is sent with the request; when you ask it to blend voices, the voices you chose (their names, shares, portraits and rules) are sent with it; and when you ask it to learn from your decisions on a voice's suggestions, or to score how closely a project keeps to its voice, those decisions (the words removed and suggested), or the project's text with the app's measure of it, are sent with the request. It processes them on our behalf, in the United States.
• Anthropic: when a member asks for a draft or a review in a review round, the text of the document under review and of the returned copy, with its comments and markings, is sent to Anthropic to draft assessments, wording and answers, and to review the document for law and wording. It processes it on our behalf, in the United States.

Each processes data on our behalf under its data processing terms. Where a provider handles data outside the EU and EEA, the transfer relies on the safeguards those terms provide, such as the EU Standard Contractual Clauses.

What we keep in your browser

There are no analytics, advertising or tracking cookies. You can change your answer at any time with Privacy choices; declining removes the remembered appearance settings.

How long we keep it

Your account and your projects are kept while your account exists. You can delete a project yourself at any time: Delete project removes it at once with its revisions, its publications, its cover, its page, its materials and their files, and any posts still waiting to go out, and a copy of it saved in your browser. Delete template removes one of your own templates at once with all its versions, and its Word file when no other template of yours uses it. Posts already made on another platform stay there until you remove them on that platform. When you ask us to delete your account, we delete it and your projects within one month. Technical records are kept by our providers for their standard retention periods.

A company's documents belong to the company, not to the member who added them. They are kept at least as long as its register's retention rules say, for example ten years after an agreement ends, and removed after that only on the company's decision. A document is withdrawn or voided, never simply deleted. The record of who did what stays with the documents, under each member's account identifier, also after the member leaves the company or deletes their account.

Your rights

You can ask for a copy of your personal data, have it corrected, deleted or restricted, receive it in a portable form, object to processing based on legitimate interest, and withdraw consent at any time. Write to contact@modelgraphx.com; we answer within one month. You can also complain to a data protection authority, such as the one where you live; in Sweden that is Integritetsskyddsmyndigheten (IMY), imy.se.

Changes

If this policy changes, we update this page and its date. A change in what we ask your consent for will ask you again.