Privacy Policy

Schematic-inator is a self-hosted, open-source Discord bot — there's no single shared service it runs as. Anyone can deploy their own instance with their own Discord bot token. This policy describes what the bot's code does with data when it runs; if you invite an instance you don't control to your server, its operator is responsible for how they run it.

When you use the /schematicinator slash command or the "Schematic-inator!" message command, the bot receives — via Discord's own API — the diagram script text or attached .d2 file you provide, plus the interaction metadata Discord includes with every command (your Discord user ID, and the channel and server IDs), so it knows where to send the reply.

Your script is compiled and laid out entirely locally using the D2 library, then rasterized to a PNG locally using resvg. Nothing is sent to Terrastruct (D2's maker) or any other third-party rendering service. The rendered image is posted back to the channel as a reply attachment.

The bot does not write diagram scripts, rendered images, or interaction metadata to a database or disk. Everything exists only in memory for the duration of a single render (capped at 20 seconds) and is discarded once the reply is sent or the request fails.

If a render fails, the error reply may echo back a snippet of your own script — for example, a D2 syntax error pointing at the offending line. That's shown only to you in Discord; it isn't logged or stored by the bot.

Operational logs (e.g. "bot is running", a failed message delivery) may be written to the host's log stream for debugging. These logs don't include diagram script or file contents.

The only external services involved are Discord's API (to receive commands and post replies) and, if you use the file-attachment option, Discord's own CDN (to download the .d2 file you uploaded to Discord). No analytics, tracking, or third-party data-sharing is used.

This bot isn't directed at children and doesn't collect any personal profile data — only the diagram content and interaction metadata described above, handled the same way regardless of age.

This policy may be updated if the bot's behavior changes, such as adding persistence or logging. Check this page for the current version.

Questions about this bot's data handling: jebbkaizer@rocketmail.com