Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
Visual Website Optimizer (VWO account 1176295) is deployed on twilio.com for A/B testing and behavioral optimization, with a conditional consent handler that reads TrustArc consent category '2' from localStorage to determine whether to initialize VWO with full tracking, limited tracking, or opt-out status.
This analysis describes what Twilio's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes VWO as an active behavioral tracking and experimentation tool on twilio.com. The consent handler reads a specific TrustArc consent key from localStorage and maps it to VWO initialization states (1=allowed, 2=no consent data found, 3=denied), indicating a consent-conditional loading mechanism for this specific tool.
Interpretive note: The operational behavior of VWO.init(2) when no consent data is found cannot be fully determined from the page source; whether this state permits any data collection requires vendor documentation review.
The updated Privacy Notice now explicitly discloses that Twilio is subject to FTC investigatory and enforcement powers, clarifying the regulatory oversight applying to the company. The policy also establishes an opt-out right allowing users to prevent disclosure of their data to third parties (other than service providers) or use of data for purposes materially different from the original collection purpose. You can exercise this opt-out by contacting Twilio through the mechanisms described in the privacy notice.
View change record →The updated notice establishes more explicit disclosures of Twilio's Data Privacy Framework certifications and specifies the legal hierarchy governing data processing. Under the revised policy, the DPF Principles now take precedence if they conflict with other terms in the privacy notice. The updated language also clarifies your right to opt out of third-party disclosures (except to service providers acting on Twilio's behalf) and to opt out of uses that materially differ from original collection purposes. You can exercise these choices by contacting privacy@twilio.com.
View change record →The updated Privacy Notice now provides more detailed explanations of how Twilio collects and processes personal data, including explicit definitions of what constitutes personal data and descriptions of direct relationships (when you create an account or opt into communications) versus indirect relationships (when you are a customer of one of Twilio's customers). The revised language establishes that Twilio acts as a data controller and determines how and why personal data is processed, subject to applicable law. The notice states it aims to be transparent about data use and to explain how you can exercise your rights, but the change itself does not modify what data is collected, how it is used, or what rights or controls are available to you.
View change record →Introduces previously undisclosed VWO tracking technology that modifies page visibility during optimization testing, which could impact user experience and requires explicit disclosure.
View full change record →This provision establishes that visitor behavior on twilio.com may be subject to A/B testing and behavioral tracking through VWO, with initialization conditioned on TrustArc consent category '2'. Visitors who have not accepted functional cookies may have VWO initialized in a limited or opt-out state.
How other platforms handle this
If you choose to reveal any personal information about yourself to other users, you do so at your own risk. We strongly encourage you to use caution in disclosing any personal information online.
When you are asked to provide information, you may decline to do so; but if you choose not to provide information that is necessary to provide some of our Services, you may not be able to use those Services.
Monitoring
Twilio has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"var account_id=1176295, version=2.2, settings_tolerance=2000, hide_element='body', hide_element_style = 'opacity:0 !important;filter:alpha(opacity=0) !important;background:none !important';Excerpt from Twilio's Privacy Notice
1) REGULATORY LANDSCAPE: VWO's deployment as an A/B testing and behavioral analytics tool engages ePrivacy Directive and GDPR requirements for functional and analytics cookies. The consent handler reads localStorage key 'truste.eu.cookie.cmapi_cookie_privacy' to determine consent state, which links VWO's activation to the TrustArc consent record. Relevant enforcement authorities include EU national DPAs. 2) GOVERNANCE EXPOSURE: Low to Medium. The consent handler implementation appears designed to respect visitor cookie preferences for VWO. However, the default state when no consent data is found (VWO.init(2)) should be verified to confirm it does not activate full tracking in the absence of explicit consent, which would be inconsistent with GDPR opt-in requirements. 3) JURISDICTION FLAGS: EU and EEA visitors are the primary affected population given GDPR and ePrivacy requirements. The localStorage-based consent check is a non-cookie storage mechanism, which may itself require consideration under ePrivacy Directive interpretations in certain EU jurisdictions. 4) CONTRACT AND VENDOR IMPLICATIONS: A data processing agreement with VWO (Wingify) should be confirmed. The VWO account identifier (1176295) and version (2.2) should be documented in the vendor inventory. Procurement teams should verify that VWO's data processing occurs within the scope of the disclosed privacy notice categories. 5) COMPLIANCE CONSIDERATIONS: Legal teams should verify the behavior of VWO.init(2) in the no-consent-data scenario and confirm it does not result in behavioral data collection. The use of localStorage for consent state reading (rather than cookies alone) should be reviewed for consistency with ePrivacy Directive interpretations applicable in target EU markets.
Regulatory citations, enforcement risk, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
This provision establishes VWO as an active behavioral tracking and experimentation tool on twilio.com. The consent handler reads a specific TrustArc consent key from localStorage and maps it to VWO initialization states (1=allowed, 2=no consent data found, 3=denied), indicating a consent-conditional loading mechanism for this specific tool.
This provision establishes that visitor behavior on twilio.com may be subject to A/B testing and behavioral tracking through VWO, with initialization conditioned on TrustArc consent category '2'. Visitors who have not accepted functional cookies may have VWO initialized in a limited or opt-out state.
ConductAtlas has identified this type of provision across 294 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Twilio.