Compliance
Messaging compliance, designed deliberately.
When BindIQ sends on behalf of agencies, compliance will be a shared obligation. The platform is being designed to make the agency side consistent, visible, and auditable.
Draft guidance pending counsel and provider review. It describes planned platform controls, not completed Twilio or SendGrid registration.
The planned consent model
- Consent is intended to be recorded per contact and per channel, with marketing and transactional choices held separately.
- The planned record includes what was shown, when, how, and from where.
- The quote flow is designed not to require messaging consent to receive a quote or do business with the agency.
- Supported messaging channels are intended to recognize STOP and HELP automatically.
- A revocation is intended to suppress further messaging until the contact opts in again.
The planned quote consent flow
- Request. A consumer requests a quote. The proposed flow delivers the quote regardless of messaging consent.
- Opt-in. Separately and optionally, the consumer may choose text updates about that quote.
- Confirm. The planned flow asks an opted-in consumer to reply or tap a confirmation, creating a double opt-in record.
- Record. The design keeps the confirmation, timestamp, and exact language shown on the contact record.
- Opt-out. The planned control recognizes STOP and suppresses future messages for that channel.
The proposed flow does not withhold a quote pending consent.
What the agency is responsible for
Agencies remain responsible for accurate brand and campaign registration, truthful use-case descriptions, matching content to the registered campaign, never importing purchased lists, and honoring opt-outs.
Planned email safeguards
- The proposed baseline calls for SPF, DKIM, and DMARC on sending domains, with an aligned From domain and a published DMARC policy moving toward enforcement.
- The infrastructure plan includes forward-confirmed reverse DNS on sending IPs and TLS in transit.
- Promotional email is intended to support RFC 8058 one-click unsubscribe and process requests within the applicable timeframe.
- Complaint rates will be monitored against provider and mailbox-service thresholds before production sending scales.
- Commercial email templates are intended to require a physical postal address and accurate From, Reply-To, and subject lines.
- The policy will prohibit purchased, rented, or scraped lists; planned controls include automatic bounce and complaint suppression.
Google, Yahoo, and Microsoft bulk-sender requirements apply at 5,000 messages per day to their respective recipients.