Privacy policy and terms URLs need to be ready before A2P submission.

What changed

Twilio announced that new Messaging REST API A2P 10DLC campaign registrations after June 30, 2026 require privacy policy and terms and conditions URL fields.

• The change applies to new campaign submissions after June 30, 2026, not existing registered campaigns.
• Both URLs need to be valid and publicly accessible.
• A missing URL field is different from a policy or terms page that exists but fails review.

What reviewers need to see

• A public website that clearly identifies the business and service context.
• A privacy policy that covers SMS or text-message data handling.
• Terms or SMS terms that describe message frequency, HELP/STOP, and message/data rates where applicable.
• Opt-in evidence that matches the campaign use case and sample messages.

HighLevel agency workflow

HighLevel agencies usually manage this across many client subaccounts, so the cost is in repeated collection, review, and resubmission work.

• Collect website, opt-in, privacy, terms, sample messages, and rejection context before review.
• Keep client-specific evidence organized instead of rebuilding the checklist from scratch.
• Use submission packs to review copy blocks and URL fields before pasting into provider workflows.

How A2P Desk helps

• Keeps privacy policy and terms URLs visible in client intake, scans, submission packs, PDFs, and reports.
• Flags missing URL fields, weak policy language, opt-in evidence gaps, and sample-message issues.
• Maps source-backed findings to current TCR rejection-code guides where the issue fits.
• Keeps claims limited to preparation, evidence quality, and workflow speed. No legal advice or approval guarantee.