Print this page
Customer and Partner Agreements
An icon of a down chevron
Terms of Service
Acceptable Use Policy
Service and Country Specific Requirements
Data Protection Addendum (DPA)
Security Overview
Service Level Agreements
Advisory Services Terms
Professional Services Terms
Twilio Marketplace Terms
Twilio Segment Customer Data Platform Destination Integration and Listing Terms
AI/ML Terms
Twilio Messaging Campaign Terms
Customer Name Changes and Assignments
Updates to Legal Terms and Conditions
Country Specific Disclosures
An icon of a down chevron
EU Data Act Disclosures and Twilio’s Commitment to Open Portability and Switching
European Electronic Communications Code Disclosures
Italy ALIAS Database Code of Conduct
Germany - Impressum
Privacy
An icon of a down chevron
Data Privacy at Twilio
Privacy Notice
Binding Corporate Rules
Customer Proprietary Network Information (CPNI)
Sub-processors
Customer Data Protection Addendum
Supplier Data Protection Addendum
Global Applicant Privacy Notice
Mobile Application Terms
An icon of a down chevron
Twilio Frontline End User App Terms
Twilio Authy App Terms
Supplier Agreements
An icon of a down chevron
Supplier Purchase Order Terms and Conditions
Country-Specific Terms
Supplier Data Protection Addendum
Supplier Code of Conduct
Intellectual Property
An icon of a down chevron
DMCA Policy
Trademark
Resources for Law Enforcement
An icon of a down chevron
Government Requests
Transparency Report
Civil Requests
An icon of a down chevron
Submit a request or subpoena
Code of Conduct & Ethics Hotline
An icon of a down chevron
Twilio Code of Conduct
Ethics and Whistleblower Hotline
Discord Community Code of Conduct
Twilio Discord FAQ
Digital Promotions General Rules
An icon of a down chevron
Sweepstakes Rules
Customer Research and User Experience
An icon of a down chevron
Acknowledgement and Waiver
Australian Phone Numbers
Last Updated:** July 6, 2023
Phone Number Reassignment to Third-Party Carriage Service Provider
If Customer reassigns an Australian phone number to a third party that is considered a carriage service provider under applicable law or regulation (“Third-Party CSP”), Customer will maintain true, complete, and accurate information associated with such Australian phone number. This includes, without limitation, the (a) actual Australian phone number that is assigned to a Third-Party CSP; (b) date the Australian phone number is assigned to a Third-Party CSP; and (c) name and contact information of the Third-Party CSP to which the Australian phone number is assigned.
Notification of Customer as Carriage Service Provider
Customer will immediately notify Twilio in writing if Customer is considered a carriage service provider under applicable law or regulation ("CSP").
**Customer as Carriage Service Provider. **If Customer is considered a CSP, the following requirements apply:
1. Appointment of Twilio Inc. as Data Provider. If Customer is considered a CSP, Customer (a) appoints Twilio Inc. to be its Data Provider (as defined in the Integrated Public Number Database Industry Code C555:2020, or its successor code, available at https://www.commsalliance.com.au/Documents/all/codes/c555 (collectively, “IPND Industry Code")); (b) grants Twilio Inc. the authority to provide Public Number Customer Data (as defined in the IPND Industry Code) to the Integrated Public Number Database (as defined in the IPND Industry Code) or its designated personnel (collectively, “IPND Manager”) on Customer’s behalf; (c) will provide Twilio with Customer’s Carriage Service Provider Code (as defined in the IPND Industry Code or the G619:2017 IPND Data Industry Guidelines, or its successor guidelines, referenced in the IPND Industry Code), which, as required by the IPND Industry Code, needs to be included in Public Number Customer Data records provided to the IPND Manager; and (d) will provide Twilio with any information required by the IPND Manager or applicable law or regulation to confirm Twilio’s role as Customer’s Data Provider. Customer further authorizes Twilio Inc. to use Customer’s Carriage Service Provider Code when providing any Public Number Customer Data to the IPND Manager on Customer’s behalf.
2. Public Phone Number Customer Data Requirements. Customer will provide Twilio with true, accurate, complete, and up-to-date Public Number Customer Data on a daily basis in a format that complies with the (a) Integrated Public Number Database (IPND) Technical Requirements (as defined in the IPND Industry Code), including any encryption requirements and (b) G619:2017 IPND Data Industry Guidelines, or its successor guidelines, referenced in the IPND Industry Code. If a technical failure of any kind prevents Customer from transmitting Public Number Customer Data to Twilio for more than one (1) business day, Customer will take all reasonable steps to provide Public Number Customer Data to Twilio as soon as practicable. Customer will take reasonable steps to resolve and correct any errors, which Twilio communicates to Customer, from the IPND Manager relating to Public Number Customer Data within one (1) business day.
Customer will promptly cooperate with Twilio’s requests regarding Public Number Customer Data that is transmitted to Twilio, and any operational issues or requirements raised by the IPND Manager, including, without limitation, requirements to connect with the IPND production environment directly to transmit Public Number Customer Data to the IPND Manager.
If Customer proposes technical changes to how it transmits Public Number Customer Data to Twilio, Customer and Twilio will work together, in good faith, to conduct an impact assessment on the proposed technical changes, and Customer will support Twilio, at Customer’s sole expense, if further testing is required in the IPND testing environment.