CrocoAI Data Bridge

Croco provides an authenticated REST API for reading a WooCommerce catalog and applying reviewed,
prepared product releases. It can be used by any compatible API client; a Croco subscription or
Croco service account is not required.

The WordPress admin contains Jobs and Health screens. Health creates or rotates one site-wide API
key and shows the full key only once. Bridge requests use the X-Croco-API-Key header. WordPress
Application Passwords are not bridge credentials. Authenticated clients can inspect supported
operations, limits, and quick-edit constraints through GET /wp-json/crocoai-data-bridge/v1/capabilities.

Croco can read products, variations, categories, attributes, prices, inventory, dimensions, media
URLs, and Croco-managed metadata. Authorized clients can publish product and media changes. Treat
the API key like an administrator credential and use the bridge only over HTTPS.

Croco is an optional compatible catalog-management service. The plugin is
fully usable without purchasing or registering for that service.

Privacy

Croco does not contain analytics, advertising, telemetry, or automatic communication with the Croco
service. Catalog data leaves WordPress only when an administrator gives the generated API key to a
client and that client requests it. The plugin may download product images from URLs explicitly
included in an authenticated publication request.

WordPress stores only a password hash, fingerprint, and timestamps for the active API key. The
plain-text key is shown once when it is created or rotated. Publication history, catalog identity
links, job records, and prepared-media records are stored in the WordPress database.

By default, this operational data remains after uninstall so an accidental removal can be reversed.
Administrators can enable permanent data removal from WooCommerce > CrocoAI > Health before
uninstalling. Product posts, terms, and media already published to WooCommerce are not removed.