Compliance Practices

Overview

HyveWyre™ builds compliance controls into the platform rather than leaving them to the sender. This page describes what the platform actually enforces today, and what remains the responsibility of the business using it.

Where a control is not implemented, it is not listed here. Nothing on this page is a certification, and none of it is legal advice.

TCPA Compliance

The Telephone Consumer Protection Act (TCPA) regulates telemarketing calls and text messages. HyveWyre™ helps you stay compliant through:

• Prior Express Written Consent: Obtain explicit written consent before sending marketing messages
• Clear Opt-In Language: Use clear, conspicuous consent language that discloses the nature of messages
• Opt-Out Mechanisms: Include "Reply STOP to unsubscribe" in all marketing messages
• Time Restrictions: The platform blocks sending outside the permitted window, calculated in the recipient's local time rather than the sender's. The default window is 8:00 AM – 8:00 PM, an hour tighter than the TCPA limit, and is configurable per account. Where a recipient's state spans multiple time zones, a message is held if it is quiet hours in any of them
• Record Keeping: HyveWyre records how and when consent was established for each contact, and retains that record for the life of the account. Deciding how long your own records must be kept, and preserving them if you leave, is your responsibility

CTIA Messaging Principles

We adhere to CTIA (Cellular Telecommunications Industry Association) best practices:

• Transparent communication about message frequency and costs
• Immediate processing of STOP requests — applied on receipt, permanently, before any queued message can be delivered
• Support for HELP keyword to provide customer service information
• No age-restricted content — HyveWyre is not used for age-gated programs
• No sharing of mobile numbers without explicit consent

Do-Not-Contact Suppression

HyveWyre maintains its own suppression list, which is separate from the National Do Not Call Registry and is enforced by the platform on every message:

• Anyone who replies STOP — or any of a broad set of equivalent phrases — is suppressed immediately and permanently
• The list is checked before every outbound message, on every sending path, and the check fails closed: if it cannot be read, the message is not sent
• Suppression cannot be removed, overridden or worked around by a business using the platform. Only the recipient can reverse it, by replying START
• HyveWyre does not scrub against the National Do Not Call Registry. Checking that registry, and relying on any exemption to it, remains the responsibility of the business sending the messages

Carrier Guidelines

We follow guidelines from major U.S. carriers (AT&T, Verizon, T-Mobile) to ensure deliverability:

• Brand and campaign registration with The Campaign Registry (TCR) is required before an account can obtain its own local number, because an unregistered long code cannot legitimately carry business traffic. A business can start immediately on a shared toll-free number that is already verified with the carriers, under a strict daily sending limit that lifts once its own registration is filed
• Every outbound message is scored for spam characteristics before it is sent, and the score is shown to the sender in the composer
• Per-number volume limits, with a daily ceiling and shorter-interval caps, so a single number cannot be driven into a pattern carriers filter on
• Numbers with a poor opt-out or delivery record are automatically throttled, and can be rested from sending entirely

Data Protection

What is actually in place today:

• Encryption in transit: TLS 1.3, enforced by our hosting provider (Vercel) on every connection
• Encryption at rest: AES-256, provided by our database platform (Supabase, on AWS). Sensitive stored credentials are separately encrypted by HyveWyre before they reach the database
• Tenant isolation: Every table carries row-level security tied to the account that owns the row, so one customer's data is not reachable from another customer's session
• Data minimization: We collect only what the product needs to operate
• Incident response: Automated alerting on failures and abuse signals, and breach notification as required by law

User Responsibilities

As a HyveWyre™ user, you are responsible for:

Compliance Tools

HyveWyre™ provides built-in compliance features:

• Consent Tracking: Every contact records how consent was established — opt-in form, agent attestation, or an inbound message from the contact — and when. A contact with no consent record is marked as such rather than assumed to be consenting
• Auto Opt-Out: STOP, UNSUBSCRIBE, CANCEL and a broad set of equivalent phrases are handled automatically, without the sender needing to act
• HELP Handling: HELP and INFO always receive a reply identifying the sender, as carriers require
• Time Zone Detection: The recipient's local time is derived from their location and applied to the sending window automatically
• Opt-Out Footer: The first message to any new contact automatically carries opt-out instructions, on every sending path — individual, bulk, scheduled, campaigns and automated follow-ups alike. Later messages in the same conversation do not repeat them
• Message Templates: Starting templates written to follow the rules on this page. They are a starting point, not a legal review — you remain responsible for what you send
• Audit Logs: Complete message and consent history, exportable
• Spam Scoring: Messages are scored before sending and the score is shown in the composer, so problems are visible before a message goes out

Prohibited Content

The following content types are strictly prohibited:

Enforcement and Violations

Violations of compliance policies may result in:

• Warning notifications and compliance guidance
• Temporary account suspension
• Permanent account termination for severe violations
• Reporting to relevant authorities if required by law

Best Practices Checklist

Resources and Training

Stay informed about compliance through:

• FCC TCPA guidelines: fcc.gov/TCPA
• CTIA Messaging Principles: ctia.org
• National Do Not Call Registry: donotcall.gov
• The Campaign Registry (10DLC): campaignregistry.com

Compliance Support

Need help with compliance questions? Our team is here to assist:

Last reviewed against the running platform: 3 August 2026.