The purpose of using this data for personalization is to help the incoming visitor find what they are looking for and understand more specifically why a product would be right for them. Our system is built such that when a user visits a Mutiny enabled website, their information is never shared nor sold. Only the company whose website the user has chosen to engage with has access to this data, similar to how company's use analytics platforms today.
We do not use 3rd party cookies, so user data is always protected across companies and domains. If users prefer to forgo personalization we respect these privacy settings and allow users to opt-out.
> If users prefer to forgo personalization we respect these privacy settings and allow users to opt-out.
Could you point out where this is in your privacy policy? My admittedly-basic reading seems to show the opposite. https://www.mutinyhq.com/privacy says this:
"“Do Not Track”. Do Not Track (“DNT”) is a privacy preference that users can set in certain web browsers. Please note that we do respond to or honor DNT signals or similar mechanisms transmitted by web browsers."
If, as you note, you respect users' privacy settings, why don't you honor Do Not Track? Forgoing personalization is the whole reason that DNT exists.
If this was an oversight, how about updating your service's behavior and the privacy policy?
You pulled out the correct line in the privacy policy: "Please note that we DO respond to or honor DNT signals or similar mechanisms transmitted by web browsers".
We do indeed honor Do Not Track in our service. Additionally, users can opt-out by emailing privacy@mutinyhq.com as detailed in the privacy policy.
Hey there, I'm Nikhil - CTO and cofounder here at Mutiny.
Within the Mutiny product, you can use our website editor to select and update any element of your page without requiring any code changes. The changes you make are compiled into a unique JavaScript file that is distributed globally through our CDN, this ensures Mutiny loads from the location closest to the visitor, making it performant and reliable. Once the incoming visitor loads the website in the browser, the Mutiny JavaScript classifies them based on their information and updates the relevant HTML elements to reflect the personalization (for example, you may change your hero CTA to "Get a Demo" for enterprise companies).
We have worked with customers running client-side, single page applications (using React, Vue.js, Angular, and more) from day 1 and have built our software to handle these environments. We hook into the browser's paint lifecycle using APIs like `requestAnimationFrame` (https://developer.mozilla.org/en-US/docs/Web/API/window/requ...) to avoid seeing a flash of the original content when personalization is rendered. We subscribe to DOM manipulations using `MutationObserver`s (https://developer.mozilla.org/en-US/docs/Web/API/MutationObs...), allowing us to render correctly in a dynamic JavaScript environment.
I took a look at your website and tried it out in our editor - all the personalized changes render well!
Is it able to do something "dumber", like just adding a class to the <body> element to then modify what shows up with just CSS? (Tried finding documentation on your site, but seems like it's not a thing).
Yes! Using the editor, you can apply class changes to whatever elements you like (including the <body>). We also expose a JavaScript SDK, so you can further integrate personalization into your application, enabling Mutiny to handle segmentation while you orchestrate any functionality/display changes.
