All Collections
Why are the Terms & Conditions (T&C) and privacy policy needed?
Why are the Terms & Conditions (T&C) and privacy policy needed?
Katy avatar
Written by Katy
Updated over a week ago

When you are bringing a new client to Tatango for a short code we request a number of assets from you. These assets are used to fill out your application for the mobile carriers (T Mobile, Verizon, AT&T). When we have all of the assets together and the application complete, we send your applications in for approval. Each carrier takes it own time, but typically we see a short code approved in 4-6 weeks after the application is submitted.

One of the things we create is a Terms & Conditions page.

This is NOT something you need to create or host. Our compliance team will create and host this page. They will provide this link to you so you can use it in your disclaimer (See below.)

Here is a sample of what the Terms & Conditions page looks like.

This T&C page will be hyperlinked in your disclaimer. The disclaimer must be included on your donation and lead pages next to the mobile field on your form.

Here is what the disclaimer looks like on a donation or lead page form.

The carriers require your T&C page is linked in your disclaimer. You must also hyperlink the privacy policy. Normally our clients have their privacy policy linked at the bottom of their organization or campaign website. Our compliance team will work with you to ensure the privacy policy has verbiage the carriers approve of. Why is this? When the carriers are reviewing your application they will visit the privacy policy link. If they do not see the appropriate wording, they may reject the short code request or ask us to have you update the page.

Our goal is to get your code live as quickly as possible which is why we ask up front for a specific list of assets. Work with your customer success manager and compliance manager as quickly as possible to ensure a quick application process. If you have any questions, please reach out to your customer success manager.

Did this answer your question?