Privacy policy

One document for every Spintax product — the browser extension, Studio, the WordPress plugin, the editor packages, the n8n node, the engine libraries, this website, the playground, the MCP server and the Telegram bot. It says what each one touches, what leaves your device, and what we hold. Mostly the answer is: nothing.

Effective 24 August 2026. The date moves when the products change, not when the wording is polished.

Privacy in one sentence

Spintax products run on your own machine, your own server or inside your own account, and what you write in them stays there. There is no account to create, no sign-in, no licence check, no analytics and no database of your content on our side — for most of what follows there is nothing here to leak, sell or hand over.

Three things genuinely leave your device, each because you asked for it: an opt-in news check in the browser extension, the text you hand to Spintax Studio's optional AI connection, and whatever you type into the Telegram bot. Each is described below in its own section.

What this policy covers

It also covers future Spintax products released under the same model, unless one of them ships a policy of its own.

What we never do

• We do not sell or rent your data. For nearly every product there is no data on our side to sell.
• No advertising profiles, ad targeting or cross-site tracking.
• No third-party analytics or tracking SDK — not in any product, and not on this website. There is no Google Analytics, no Plausible, no pixel, no session recorder.
• We do not use your content to train models. Where a product can send text to a model, it is a model you chose, on your account, and the sentence above is about us, not about that provider — whose own terms then apply.
• No accounts. Nothing here asks you to register, and nothing phones home to check a licence.

The browser extension — Spintax Outreach Assistant

The extension helps you do outreach by hand: one recipient at a time, a template rendered for that recipient, pasted into the page when you press the button. It is not a mailer, not a CRM and not a scraper — it never submits a form for you.

What it stores

Everything you create — campaigns, imported rows (names, e-mail addresses, websites and any other column you brought), templates, profiles, the outcome journal, field-mapping recipes and files you uploaded — is stored locally in your browser, in IndexedDB and extension storage. It never leaves your device unless you export a backup yourself.

What it reads on web pages

Only after you press Fill — or a keyboard command you assigned — on a page you granted access to, the extension reads the structure of the form on that page (field names, labels, types) to decide where each of your variables goes, and writes your text into those fields. It does not read page content otherwise, does not run on pages you did not permit, and never submits anything.

Network

The extension has no server of ours behind it and no analytics. By default it makes no network requests at all. One optional feature is the exception: publisher news, which, once you switch it on with the bell in the panel header, fetches the public feed at https://301.sh/posts.json about every six hours to tell you about a new article. The request carries no identifiers and nothing about your work. It is off until you turn it on, and the notifications permission is requested at that moment and given back to the browser when you turn it off.

The "Open in…" buttons

Two buttons hand a prompt to an assistant: Open in ChatGPT opens chatgpt.com in a new tab, and Open in Claude Desktop opens the Claude desktop application. In both cases the prompt travels in the URL, the extension says so in the line above the buttons, and you still press Send yourself over there. The extension itself transmits nothing — it opens a link. What you then send to that service is governed by that service's policy, not ours. If a prompt is too long to fit an address (8,000 characters for ChatGPT, 14,000 for Claude Desktop) the buttons disappear rather than truncate it silently, and Copy prompt remains. A click also copies the prompt to your clipboard and records in the local journal that a hand-off happened — the fact, not the text.

Permissions

• storage, unlimitedStorage — keep your lists and settings on your device.
• activeTab, scripting and host access you grant in the moment — fill the form on the page you chose.
• clipboardWrite — copy a message. The extension cannot read your clipboard: clipboardRead is deliberately not requested.
• alarms, and optional notifications — the opt-in news check, requested when you enable it and removed when you switch it off.
• The queue panel sits beside the page rather than in a popup that closes on the first click. On Chromium that is the sidePanel permission, added automatically by the build tool together with the panel entry point; on Firefox it is the sidebar_action manifest key, which is not a permission at all and appears in no permission prompt.

Your control

Settings → Backup exports a ZIP of everything; Delete all data removes it. Uninstalling the extension deletes its storage with it.

Spintax Studio (Windows)

Studio is an offline desktop application: no account, no sign-in, no telemetry, no analytics, no crash reporting. We have no way to know you installed it. Its one exception is an optional AI connection — off until you turn it on — which sends the text you hand it to a model endpoint you choose, on your own account and your own key, where the key is stored in the Windows Credential Manager on your machine and goes nowhere else.

Studio is published with its own, more detailed policy, and that is the authoritative one for the application: spintax.studio/privacy.html. It is not restated here, because two copies of one policy drift apart.

Spintax for WordPress

The plugin runs inside your own WordPress installation. Your templates and the content it produces live in your own database, on your own server. The plugin makes no outbound HTTP request — no update ping of ours, no usage report, no call home of any kind — so nothing about your site reaches us. WordPress.org counts plugin downloads and active installs; those aggregate numbers are all we can see, and they say nothing about you.

The editor packages — VS Code and Sublime Text

Both are syntax definitions: they colour spintax in your editor and nothing more. They run no code of ours, make no network request and collect nothing. The Visual Studio Marketplace and Package Control publish install counts to us in aggregate, the same way any package registry does.

The n8n node

n8n-nodes-spintax runs inside your own n8n instance and renders templates there, in process, using the same engine as everything else. The data flowing through your workflow stays in your workflow; the node sends nothing anywhere.

The engine libraries

@spintax/core (npm), spintax/core (Packagist), spintax-core (PyPI), Spintax.Core (NuGet), the Object Pascal engine and the ZennoPoster and OpenCart integrations are libraries: they take a string, return a string, and perform no input or output of their own. No network, no files written behind your back, no telemetry. The package registries count downloads, as registries do.

This website

spintax.net carries no analytics, no tracking pixels and no advertising, and sets no cookies. Your browser keeps two or three small things on your own device, in localStorage: the theme you picked, the language you picked and — on the playground — your current draft. Nothing about them is sent anywhere.

Search runs in your browser. The site search is a static index; your query is matched against index files your browser downloads, so it never becomes a search request to a server of ours, and we cannot see what you looked for.

Hosting logs are real, and they are not ours. The site is served by Cloudflare Pages, and the Russian version at ru.spintax.net by GitHub Pages. Like every web host, both record ordinary request data — IP address, user agent, the URL requested, the time — under their own privacy policies. We do not build anything on top of those logs; we have no analytics layer, and we do not join them to anything.

The playground

Everything on /play/ happens in your browser: the engine is a script your browser downloaded, and your template is never uploaded. Your current draft is saved on your own device so the page survives a reload.

A share link is the one exception, and it is worth understanding. When you build a link to share a template, the template itself is encoded into the URL. That means two things: anyone who has the link has the template, and — unlike the rest of the playground — the URL travels to the server and appears in the ordinary hosting logs described above. Do not put anything confidential into a share link.

The MCP server and WebMCP

The hosted MCP server at spintax.net/mcp lets an AI agent validate, render and analyse a template. It is a small edge function with no database and no key-value store attached: the template arrives in the request, is processed, and the answer goes back in the same response. Nothing is written down, and there is nothing to write it to. The request itself passes through Cloudflare's ordinary edge logging, as any HTTP request to any site does.

WebMCP is the same set of tools exposed to an agent running inside your browser on any page of this site. It executes locally in the page and sends nothing anywhere.

The local alternative, @spintax/mcp run with npx on your own machine, makes no network request at all — the private option if a template must not leave your computer.

The Telegram bot

@spintaxnetbot validates and renders templates in a chat. Two honest points about it:

• You are on Telegram. Anything you send the bot goes through Telegram first and is governed by Telegram's own policy. We receive the message content in order to answer it.
• The bot keeps no database. It is a stateless service: there is no key-value store and no table behind it, and the only state it keeps is inside its own reply in your chat — which is why deleting that message ends it. It does not build a profile of you, and it does not store what you sent after the reply is delivered.

One command is different. /draft asks a model to write a template from your brief, so the brief you typed is sent to Cloudflare's Workers AI for that answer and is processed there under Cloudflare's terms. Nothing about it is stored on our side. The rest of the bot's commands touch no model at all.

Storage, retention and your control

• Because everything is stored on your device or in your own account, you control it: deleting it in the product deletes it, and uninstalling takes the rest.
• The extension exports a full backup as a ZIP, and clears everything with one button.
• We hold no server-side copy of your content, so there is nothing on our side to retain or to delete — beyond any message you send us yourself, which we keep only as long as the conversation needs.

Third parties

Using these products puts you in touch with platforms we do not run, each under its own policy: the stores that distribute them (Chrome Web Store, Edge Add-ons, Firefox Add-ons, the Microsoft Store, the Visual Studio Marketplace, Package Control, WordPress.org, npm, Packagist, PyPI, NuGet, the n8n community registry), the hosts that serve this site (Cloudflare and GitHub), Telegram, and any AI endpoint you point a product at. This policy describes what our software does; it does not describe those platforms' practices, and it cannot promise anything on their behalf.

Your rights

Depending on where you live you may have the right to access, correct, delete, export or object to the processing of your personal data. Because these products are built so that your data stays on your device or in your own accounts, most of it is already directly under your control — we cannot produce a copy of what we never received.

Where we do hold something about you — a message you sent us, for example — you can exercise those rights by writing to us through the contact page. We do not sell personal information.

Children

These are tools for site owners, marketers and developers. They are not directed at children, and we do not knowingly collect personal data from anyone, of any age.

International

The products run wherever you run them; this website is served from a global network, and the Russian version from a separate host. Where we process the little data that does reach us — support correspondence — we take reasonable steps to protect it in line with applicable law.

Changes to this policy

This page changes when the products do: a new product, a new permission, or anything that begins to send or store what is not described here is written in first, and the effective date at the top moves with it. Cosmetic edits do not move the date.

Contact

The Spintax product line is published by 301.st, and spintax.net is its website. Questions about this policy, about what a product does with your data, or a request under the rights above: use the 301.st contact page. For the open-source products you can also open an issue in the project's GitHub repository.

Trademarks

Google Chrome and the Chrome Web Store are trademarks of Google LLC. Microsoft, Microsoft Edge, Visual Studio Code and the Microsoft Store are trademarks of Microsoft Corporation. Firefox is a trademark of the Mozilla Foundation. WordPress is a trademark of the WordPress Foundation. Telegram is a trademark of Telegram FZ-LLC. Cloudflare is a trademark of Cloudflare, Inc. ChatGPT is a trademark of OpenAI, and Claude of Anthropic. Our products are not created, endorsed or sponsored by any of them.