NiroCoder

Privacy & data

Exactly what NiroCoder sends, and when

NiroCoder needs its AI service to plan, build and answer. Here is every piece of data that leaves your site, when it leaves, and what never does.

Never sent

  • ✕ Posts and pages
  • ✕ Orders
  • ✕ Customers and users
  • ✕ URLs of your content
  • ✕ Passwords, keys or other credentials

When data is sent

Before anything
Nothing goes to the AI service until an administrator connects the site under Settings → AI Connectivity and ticks the data-sharing notice. The one exception is the plugin’s update check, which asks my.nirosuite.com for the latest NiroCoder version a couple of times a day and, like every WordPress update check, identifies your site’s URL.
When you connect
Site URL, site title, and the name and email entered on the connect screen. The email receives the verification key.
With every chat message
Your message, the last 10 messages of the conversation, the site summary and four diagnostics. If the chat belongs to an extension, that extension’s manifest and files.
With every build
The approved plan and the site summary. For a change or a fix, the extension’s files and its last error. After a blocked build, the blocked findings.
When showing your plan
The site key, to fetch your plan and remaining credits.
When you disconnect
The site key, so the service can deregister the site.

The site summary

Environment metadata only, what the AI needs to write code that fits. The Build screen shows it as “What NiroCoder sees”, with Rescan.

WordPress and PHP versions, locale, whether it is multisite
Active theme: name, version and parent theme
Active plugins: name, slug and version
WooCommerce: whether it is active, its version, and whether HPOS is on
Your NiroCoder extensions: name, slug, type, status and what each adds or leaves alone
The NiroCoder version

Diagnostics (chat messages only)

Number of active plugins
Total size of autoloaded options, in bytes
Whether an external object cache is in use
Whether WP-Cron is disabled

What stays on your site

Conversations, kept in two tables in your own database
An activity log of every extension event
Generated code, with every version, in wp-content/nirocoder/
The site key, masked in the interface and never in the public settings payload

Deactivate, disconnect, remove, uninstall

Deactivate NiroCoder
Extensions stop loading. Nothing is deleted, reactivate and they run again.
Disconnect the AI
The site key is removed and AI requests stop. Extensions keep running; settings are kept.
Remove an extension
Its code moves to NiroCoder’s trash and its private settings store is deleted. Content it created stays.
Delete (uninstall) NiroCoder
Removes its tables, settings, chat history and the whole wp-content/nirocoder/ folder, every generated extension and its history. Export (a paid-plan feature) any extension you want to keep first.

A note for Nginx

NiroCoder protects wp-content/nirocoder/ with an .htaccess file that only lets static assets through. That works on Apache and LiteSpeed. On Nginx, add a rule that denies web access to that folder; extension PHP files already exit on direct requests.

The service

NiroCoder Cloud is operated by NiroSuite at my.nirosuite.com. Developers can point the plugin at another instance with NIROCODER_CLOUD_SITE, or run fully offline with the NIROCODER_AI_MOCK client.

Questions

Your messages and recent conversation, a summary of your setup (versions, theme, plugins, WooCommerce status, your NiroCoder extensions), four diagnostics with chat messages, and, when changing or fixing an extension, that extension’s files and last error. Posts, pages, orders, customers and users are never sent.