About this plugin
Tamicon Connector lets a site administrator approve a dedicated publishing connection to the Tamicon content service. A Tamicon account is required for the service. The connector does not create accounts, send data to Tamicon, or publish content merely by being activated.
The connection keeps the site’s administrator password private. On explicit approval, WordPress creates a restricted publishing account and an application password for that connection. The site administrator can choose an existing content author without granting that author’s credentials or general editing privileges to Tamicon.
Existing unrelated posts, users, themes and plugins are not changed.
Tamicon can create, read and publish authorized content through the WordPress REST API. Supported content features include draft verification, excerpts, tags, author attribution and links to confirmed Instagram/YouTube posts. Links to other platforms are shown as ordinary links; this plugin does not embed external tracking scripts.
External services and privacy
com. The service provides content preparation and publishing orchestration and requires an account; service plans may be paid. The WordPress plugin itself is fully available under the GPL.
Data is sent only when a site administrator approves a connection initiated from Tamicon. app/oauth/wordpress/callback. The callback receives the site URL, dedicated publishing username, application password and single-use authorization state.
The administrator password is never sent. Tamicon stores the publishing credential to authenticate subsequent authorized REST requests.
After connection, Tamicon can send content, media, selected author/category references and signed post attribution metadata, and read connection verification and publication results. Creating/verifying a private draft may be part of connection checks. Activation or viewing the settings page does not by itself contact the service.
There is no background analytics or custom update endpoint in this directory build. org.
com/policies/terms
com/policies/privacy
Requirements and supported sites
Use an HTTPS, single-site WordPress installation at its site root, with Application Passwords enabled and MySQL/MariaDB GET_LOCK support. Multisite, WordPress installed in a subdirectory, and differing WordPress/site home origins are not currently supported. Security plugins or hosting rules must permit the relevant WordPress REST and authorization endpoints.