WoZoBridge Privacy Policy

This privacy policy explains how the WoZoBridge WordPress plugin and the related WoZoBridge OAuth bridge at wozobridge.com handle information when you connect a WooCommerce store to Zoho CRM and Zoho Books.

This policy specifically covers:

• The WoZoBridge plugin installed on your self-hosted WordPress site.
• The OAuth redirect bridge at https://wozobridge.com/auth/zoho.php, used strictly during initial Zoho authorization handshakes.

WoZoBridge enables WooCommerce store owners and administrators to:

• Securely authorize Zoho CRM & Books via OAuth 2.0
• Sync WooCommerce orders to Zoho Books automatically
• Inspect Zoho CRM contacts & Books records inside wp-admin
• Monitor detailed synchronization and API error logs

The vast majority of plugin data stays strictly within your own WordPress database. Depending on features enabled, WoZoBridge may store:

• Plugin configuration: Sync triggers, Zoho domain/region, and Organization ID.
• Credentials & Tokens: Encrypted Zoho OAuth client credentials, Access tokens, and Refresh tokens.
• Sync History & Logs: Timestamps, endpoints, HTTP status codes, order IDs, and response payloads.
• Order & Customer data: Name, billing/shipping address, email, phone, and purchased line items necessary to create corresponding Zoho Books invoices/sales orders.

When you authorize Zoho and perform CRM or Books operations, the plugin communicates with official Zoho API endpoints:

• accounts.zoho.* — OAuth authorization, token exchange, and refresh requests.
• zohoapis.* — CRM contacts and Books sync endpoints.
• books.zoho.com — Invoice generation and customer record mapping.

Data transmitted to Zoho is handled in accordance with Zoho Corporation's privacy commitments:

The bridge endpoint at https://wozobridge.com/auth/zoho.php is used exclusively during the initial OAuth handshake to redirect your browser back to your WordPress admin panel with the authorization grant.

The bridge is not a proxy for ongoing sync transactions. Your product catalogs, orders, and customer databases are never sent through or cached on our bridge servers.

To ensure total transparency, WoZoBridge does not:

• ✕Call remote license telemetry APIs without user consent.
• ✕Sync your full store customer base or product catalog to wozobridge.com servers.
• ✕Inject tracking scripts, third-party analytics pixels, or external CDNs on your storefront.
• ✕Reroute ongoing CRM or Books API calls through middleman proxy servers.

The WoZoBridge plugin does not place tracking or marketing cookies on your public storefront. All administrative screens run natively within the WordPress dashboard session.

The bridge endpoint at wozobridge.com uses only ephemeral session tokens strictly required to authenticate the redirect process.

• Credentials stored in WordPress options utilize OpenSSL / Sodium encryption where supported by your server environment.
• Access to plugin management screens is restricted to users with WordPress manage_options capability.
• All API communication between WordPress and Zoho is forced over TLS 1.2+ HTTPS.

• Data on your WordPress site persists until manually cleared, rotated via cleanup cron routines, or purged upon plugin uninstallation.
• OAuth redirect logs on wozobridge.com are purged automatically on rolling cycles and kept only for system debugging and rate-limiting purposes.

As a site administrator, you maintain absolute control:

• Disconnect Zoho OAuth credentials instantly with one click.
• Enable or pause automatic order syncing anytime.
• Purge sync log tables and temporary error logs from wp-admin.
• Override the OAuth bridge URL via the wozobridge_zoho_oauth_bridge_url filter for self-hosted or air-gapped enterprise setups.

WoZoBridge is a B2B business integration utility designed for merchants and administrators. We do not knowingly solicit or process information from children under 16.

We may periodically update this policy to reflect new plugin releases, Zoho API revisions, or regulatory changes. Material amendments will be highlighted in release change-logs and updated on this page.