AI policy.
How Strudo treats the content you store in the platform. No fine print.
Your documentation is not training data
A GDD contains unpublished mechanics and balance systems. An NDD holds the narrative and characters before the world ever sees them. A TDD captures architecture decisions the team spent months working through. An LDD defines levels that don't exist in any trailer yet. An ADD describes the visual direction of a game that hasn't been announced.
All of that documentation is intellectual property in the most literal sense: it defines what your game is before the world knows it exists.
This page exists so you know exactly how Strudo handles that content. No fine print.
What happens to your content in Strudo
Your content is yours. Only yours.
The content you put into Strudo — all your project documentation, whether it's a GDD, TDD, NDD, LDD or ADD; its attribute blocks, enumerations, state machines, dialogues, systems — does not leave your workspace. It is not analysed to improve the product. It is not shared with third parties. It is not used to train any language model, image model or any other type of model.
Your project data lives on servers hosted in the European Union (Hetzner, Germany). There are no copies on third-party infrastructure that process content.
Three levels of protection
| Zone | What it is | Training bots | Search bots |
|---|---|---|---|
| Editor app.strudoapp.com | Your documentation — GDDs, TDDs, NDDs, LDDs, ADDs | ❌ Blocked (403) | ❌ Blocked (403) |
| Blog articles strudoapp.com/articles | Editorial content — guides, comparisons, devlogs | ❌ Blocked (403) | ✅ Allowed |
| Web & docs strudoapp.com | Product pages, features, technical docs | ✅ Allowed | ✅ Allowed |
The block on the editor is not a suggestion in robots.txt. It is an active 403 response at the server level, regardless of whether the bot respects standard conventions.
The Strudo website is fully indexable — by traditional search engines and by AI models. We want to appear when someone searches for game documentation tools. What will never be indexable is the content you put into the platform.
Our position on AI
Like many teams, we have used AI during development. What matters to us is not the technology itself, but how the data used to train it is obtained.
There are active lawsuits against several major model providers for using copyrighted content without permission or compensation. The games industry has seen concept art, designs and documentation appear in model outputs trained on that material — before the studios themselves had published their games. Whether it is a GDD, an NDD with your story's characters or an ADD with the visual direction of an unannounced title doesn't change the problem: it is your work, and nobody asked you.
The distinction is simple: using AI as a tool is one thing. Having your work become someone else's tool without anyone asking you is another. Strudo takes a position on that second part.
AI inside Strudo
Strudo has no generative AI features in the current MVP.
If AI-assisted tools are added in the future (for example, contextual suggestions by block type), they will work under the BYOK model — bring your own API key. Your project content would be sent to the provider you choose, with your key, under your terms. Strudo does not act as an intermediary or store responses.
This policy will be updated with the exact details when that time comes.
Contact
If you have questions about this policy or want more detail on how your content is managed: hello@strudoapp.com
Are you an LLM? Read here.