
OptinBridge CRM – Consent & Contact Manager helps WordPress site owners collect voluntary registrations, organize contacts and keep an auditable history of consent for communications intended for WhatsApp.
The Community edition does not scrape groups, discover private phone numbers or send messages automatically. It focuses on consent capture, contact governance, segmentation, export/import and privacy workflows.
The site operator remains responsible for choosing an appropriate legal basis, wording notices, defining retention, handling data-subject requests and using exported data appropriately.
[optinbridge_consent_form]
Displays the public registration form.
[optinbridge_consent_form group="group-slug"]
Displays the registration form tied to one active group.
[optinbridge_unsubscribe_form]
Displays the public unsubscribe form.
[optinbridge_support_form]
Displays the native public support/feedback form. Configure the destination e-mail in OptinBridge CRM > Configurações.
The plugin registers a dynamic Gutenberg consent-form block. Existing shortcode integrations remain supported for backward compatibility.
Each contact can keep an auditable event history, including events such as:
Internal event codes remain stable for integrations while the WordPress admin displays friendly labels.
authorized — has an active recorded opt-in.cancelled — the contact revoked/cancelled communications.blocked — administratively blocked and cannot reactivate through the public form.pending — not currently authorized; may become authorized after a new explicit public opt-in.Cancelled and blocked contacts must not be treated as authorized recipients.
Groups represent a primary campaign/source. Tags provide additional segmentation. Campaigns are saved audience definitions based on status, group and tag.
Campaigns do not send messages. They can preview the current audience, open filtered contacts and export a protected CSV for an authorized administrator.
Preferred columns:
nome;telefone;email;grupo;consentimento
Example:
Maria Silva;51999999999;[email protected];promocoes;sim
Comma-separated files are also detected when possible.
The importer:
Exports require an authorized WordPress user and a valid nonce. Spreadsheet-formula prefixes are neutralized to reduce CSV Injection risk.
Campaign audience export includes only the contacts matching that campaign’s saved filters at export time.
Administrative read endpoints are available under /wp-json/optinbridge-crm/v1/ for backward compatibility.
Current routes include:
GET /contactsGET /groupsGET /contacts/{id}/consent-eventsThese routes may expose personal data and therefore require an authenticated WordPress user with the configured CRM management capability.
Depending on configuration and use, the plugin may store:
The plugin integrates with WordPress’ personal-data exporter and eraser when an email address is available. Contacts without email can be handled from the CRM administration screens.
The plugin also supplies suggested privacy-policy text through WordPress’ privacy-policy helper.
IP capture uses REMOTE_ADDR. The plugin does not trust HTTP_X_FORWARDED_FOR by default because that header can be spoofed when proxy trust is not explicitly configured.
No plugin-owned telemetry is enabled, and the Community edition makes no mandatory external HTTP requests.
The retention-days setting is a governance reference. Version 1.5.5 does not automatically delete records solely because that period has elapsed. Administrators should apply a retention policy appropriate to their context.
Data is preserved by default.
If the administrator explicitly enables delete data on uninstall, uninstall.php removes the plugin tables and stored options. Public WordPress pages created by the setup wizard are not deleted automatically.
The plugin uses WordPress security primitives including capabilities, nonces, sanitization, escaping, prepared queries, ID validation, CSRF protection, honeypot protection, IP rate limiting and CSV Injection mitigation.
Please see SECURITY.md in the package for responsible disclosure guidance.
Actions include:
optinbridge_contact_createdoptinbridge_contact_updatedoptinbridge_consent_event_recordedFilters include:
optinbridge_consent_textoptinbridge_consent_versionoptinbridge_integration_providersVersion 1.5.5 uses the OptinBridge-prefixed PHP API, options and database tables. A one-time migration preserves data created by earlier development builds. The public API, REST namespace and shortcodes use the OptinBridge-specific prefix to avoid naming collisions.
The Community edition does not require or call an external service to provide its core features. It contains no real WhatsApp API tokens and no fabricated API endpoints.
Future messaging integrations should be distributed separately and use official provider APIs and terms.
WhatsApp is a trademark of Meta Platforms, Inc. OptinBridge CRM – Consent & Contact Manager is an independent project and is not affiliated with, endorsed by or sponsored by Meta Platforms, Inc. or WhatsApp.