All Question Categories
Why Deploy R;pple?
The Technical Components
What Similar Tools Have Existed Previously?
The Security
The Future Development
The Impact of R;pple
The Data Privacy
How to Install R;pple
The Financials
The Communications
How Does R;pple Work?
How to Support R;pple
Our Biggest Challenges
R;pple’s Visual Appearance
The Data Privacy

Why are Read/Write Permissions needed rather than just Read?

Menu icon

We have to adapt the Search Engine results page (e.g. Google, Bing) to show the R;pple popup and record a random ID to local storage for analytics.

There are two reasons for this:

  1. Our roadmap includes detecting self harm content within websites and on social media sites. There is no way to know the URL in advance to narrow this permission requirement
  2. Right now, Ripple uses a mask to trigger only on supported search engine URL’s. Ripple is also deployed around the world     and needs to support searches across a large number of search engine TLD properties, hence the use of a mask, vs explicitly trying to keep track of     all TLDS and URL structures in use.

The same extension is used globally, by corporates, in education and in local government. The extension does not collect personal data or screen scrape. A limited amount of data is collected to help improve the tool. When the extension is triggered, our webservice is contacted which results in the collection of an IP address, temporarily, in order to serve the content. This data is purged, usually within 4 days and is not reported on at all.