This Policy sets out our privacy practices and explains how we handle the information we collect on our Content Glass Services ("Services").
Scope of Content Glass term
This policy applies to all our Content Glass services
· Content Glass Website
· Content glass Cloud Website
· Content glass Store Website
· Content Glass SaaS applications which are part of our general Contentglass Cloud concept.
· Content Glass applications either web, desktop or mobile for example Content Glass Button Chrome plugin app.
For convenience we use the term Content glass to refer to all these as Content Glass ("Content Glass").
Across this policy we use a lot the term "Widget". A widget is piece of software (mini app), with or without visual presentation, that run on top Websites or mobile apps in a special container provided by Content Glass API, which is either installed on a website or injected by Browser extension. Widgets are the mean for sharing information on Content Glass ecosystem. One should note that although widgets may look as integral part of a website, and possibly interact with the DOM (data object model) constructed by a website within Browser container – widgets are actually not part of the website, and not included as part of website codebase. Instead, these are mini applications run in Content Glass container named "layer" (version-1) or "Glass" (version-2). Therefore one should make distinction, when considering privacy, between Content Glass widgets and the underline website context. These are two separate entities.
Since, during the period when this policy is written, the system is in a transition between Content Glass version-1 and version-2, and since these two versions are different in the way data is managed, we make some notes following this policy that refer to either version-1 or version-2. Currently version-1 is the active version. Once version-2 will be available we will adjust this policy accordingly.
We value your privacy a lot. When you share information with us using one of our Services, we make sure it is stored as securely as possible and kept only for the purpose intended.
As such, we never share the information you provide to third parties, except for chosen partners that are used for providing you the Content Glass service.
You always remain in control of your data. You may edit or erase your data from our Services at any time.
When we refer to "we" or "us" in this policy, we mean Rhizome Networks LTD , which controls the information collected when you use the Services. This Policy does not apply to information collected by third-party Web sites linked to or otherwise accessible from Content Glass. This Policy does either apply to third party applications what will be created using Content glass platform, except for the part of information ("Widgets") that will be stored by Content glass service. The information collected or received by third-party services is subject to their own privacy policies.
The information we collect is used solely for operating and improving our Services.
1.1.1 I visit one of your services
We use usage information and log data to compute non-identifying reports that are used to improve our services. For that purpose, non-identifying usage information and log data are also shared with our third-party analytics services (including, but not limited to, Google Analytics and Adobe Analytics). You can opt-out using this tool. https://tools.google.com/dlpage/gaoptout/
Log data may also be used to fight spam and other abuse of our services.
When you create an account on one of our Services you obviously provide us account information.
From time to time, we use your email exclusively to send you information about new features of Content Glass Services. You can decide to opt out of these Content Glass marketing and product update mailings at any time within your Account Settings page you can access upon login to Service.
We may also contact you to inform you about changes to our Services and important Service-related notices, such as new Terms or other security notices. These communications are considered part of the Service and you may not opt out of them.
We are currently do not use account-specific collection of log data and usage information. However, in the future we may use account-specific log data such as IP address to know which country you are connecting from. This information is used for statistical purposes.
1.1.3 I Create widget on Content Glass
As for version-1 you can create a widget without having any account. For sharing the widget, you associate it with one of your other social account identities. We therefor need to store the identity of yours that let as associate a in the database widget with you. As for version-2 (planned to end of 2018), any Widget of Glass entity created by user, are associate with Content Glass account.
Also note that part of the information stored when you create, view or update widgets, is stored locally on your browser cache. While this is not a problem when using personal computer or personal device, this may be a problem if you are using public computer for viewing widgets. It is therefore a good and recommended practice, when using public computer, to delete the entire cache when finishing to work with Content Glass. You can clean the entire Contentglass local cache from a menu option on Content Glass application.
The information stored by widget is not used for any other purpose other than sharing this information with other peers. As for version-1 Widgets are shared among closed peers-groups by default. Website admin that install Content Glass script using managed-app (for example CG Shopify App) can also share the widget on public layers, such as on a page, domain or TLD so that any visitor will see the widget also without need to login.
Shared widget is looked like part of Website content, but if fact it is rendered on a data layer that is not an integral part of the actual website, but of Content Glass. Since Widgets are shown over third party websites, and may show some interaction with website data, it is important to note that we are not responsible for third party policy, but only for data rendered and managed in the scope Content Glass layers.
1.1.4 I create managed-app account on Content Glass
Note: This section applies to web owners that install Content Glass script using managed-app account.
When you install Content Glass managed app (for example through Shopify or Directly) you obviously provide us with account information. Depending on the case, this information may include an information we receive form an API of third party platform, that is used as the container for Content Glass app. For example – when you install Content Glass app via Shopify App Store, we use Shopify API to read information about your site, that is required for the construction of the managed-app account. Any information you provide in such case is due to your prior consent for providing this information upon approving the App as part of following an "oAuth" procedure. For example, when you install Content glass Shopify app, you first grant access to resources presented to you by installation dialog.
Any information we collect and use for constructing managed-app account is an information required for creating the account and providing its functionality.
Currently we do not collect account-specific Log data and/or Usage data, but we do this in the future for improving our service and offering a more accurate selection of options to website owner.
When creating an account user is required to subscribe the main Content Glass newsletter. This acceptance is a required step for creating the account. We are using an internal Newsletter system, that uses your contact information (Name and Email) on your Account when sending messages. You may later subscribe or unsubscribe more specific newsletter topics. Across all this time your account information is used when message need to be sent.
When you unsubscribe from a newsletter the system turn-off a flag that relate your account with the specific newsletter. You can also unsubscribe from the main newsletter, however, doing so will prevent you from receiving important notifications from our service.
1.1.6 I submit a Content Glass helpdesk ticket
We use a software provided by osticket.com as a platform to handle assistance requests. The platform is hosted on our server and data is not shared with third-party. Whenever you submit a ticket (either through email or the helpdesk request online form), The helpdesk system collects contact information which is used to communicate with you. Your communication and help requests are safeguarded and stored on a database managed by us.
1.1.7 I submit a comment on the Content Glass Blog or Community Forums
Our services may include blogs and/or forum boards. If you leave a comment or ask a question in one of our blogs or forums you should be aware that any information you provide to these websites - including profile information associated with the account you use to post the information - may be read, collected, and used by any member of the public who accesses those sites. Your profile and the information you enter may remain, even after you delete your account. To request removal of your information from these publicly accessible sites, please contact us and set "Terms & Policy" option as the help topic.
1.1.8 I share public content on social media
When you share public content on social media (including but not limited to Twitter, Facebook, Google+, Youtube, Instagram), your public social media activity may end up in our platforms. To understand more about the type of activity you share publicly, we encourage you to check the Terms and Privacy Policies of the social media networks you use.
1.2 What information do we collect and store?
Widget information is created when you create Content Glass widgets by either our own content-Glass app or by third party CG App. The information is stored on our Service databases. Widget information include:
1. Reference to user account created on Content Glass (if exist)
2. Information from third party user-account that may be used to login and identify you as unique peer on Content Glass ecosystem. This may also include an information about contacts you have on the third-party account, that will be used for establishing peer-to-peer sharing relations with your friends and contacts. For example, Content Glass client (version 1) let you login with your Google account to identify yourself also without having Content Glass account. When you Login with Google account, we connect your Google Account on behalf of your request and use your account identity, to identify you as unique peer in the network. Using this approach your contacts on Google are able to connect with their own Google account too and establish beer-to-peer sharing relations with you – meaning sharing widgets with you. For this purpose, we do not store the connection credentials to third party service beyond what is required (Session), however, the identity of yours is stored as part of widget information.
3. Widget settings data such as position and width.
4. Widget data such as text, link to images, link to video, code and any other information a specific widget let you share.
Widgets information is stored on our Service databases with reference to the app-id and possibly add-on-id on which widget was created and when widget was created by managed-app, also with reference to the internal accent id. We do not share widgets information. We currently not use this information for any other purpose but providing the sharing experience.
Widgets are shared privately by default. However, in the case of managed-account it is possible for website owner to share widgets publicly.
You are the sole responsible for the information you expose when sharing widgets either privately or publicly. We recommend avoiding from sharing any sensitive information not privately neither publicly. We will not be responsible for any damage caused to you by sharing information on widgets. We cannot state that more clearly – Do not share what is not meant to be known to others and do not use widgets as information channel for sharing sensitive information.
Part of the information stored when you create, view or update widgets, is stored locally on your browser cache. While this is not a problem when using personal computer or personal device, this may be a problem if you are using public computer for viewing widgets. It is therefore a good and recommended practice to delete the entire cache when finishing to work with Content Glass on public computer. You can clean the entire Contentglass local cache from a menu option on Content Glass application.
1.2.2 Widget activity Log
Widget activity log is an internal log that collect information about the events of creating and deleting widgets. The information of this log is not shared with any other third part. In the future we may use this information for the providing various features and for improving and learn about usage in our service.
1.2.3 Information collected by third-party apps & widgets
Content Glass service provide platform for developers for create apps and widgets. We are not responsible for policy set by third party partners when developing their apps. Yet as for widgets, originated by their party app, and stored in our database the same concepts apply as described above.
Managed App is an entity in our Service logic that used to store information about integration of Content Glass script on third party website. This information include various settings of Content Glass client, running on third party website, such as name, style, application module, attached add-on apps and more. Any of this information is required for providing the managed-app functionality. Website admin has special permissions to share widgets publicly. Note that when doing so, you expose the widget to any visitor of your website.
1.2.5 Developer Account information
Developer Account is an entity in our Service logic created as part of launching an install procedure of managed account. The developer-account is used to store information required when developing Content Glass app or when running app associated unique UUID is assigned for apps. The UUID is used when app contact Content Glass Service. In addition, some app restrictions may be set.
Usage information includes the pages you visit, your language preference, your location, device and Internet browser details, and so on. Part of this information is maintained by your account, and other part of this information is collected by Google Analytics
Log data contain data about the nature of each access of our services, including originating Internet Protocol (IP) addresses, the requested files, operating system versions, device type and timestamps. Web servers usually keep log files that record data each time a device accesses those servers. The information is collected by Google Analytics.
You might provide us with your contact information, whether through a form on our website, a subscription to a paper newsletter or an interaction with our customer support team. Contact information includes your email address and name.
To become a Content Glass user you need to have an account with us. At registration, you share with us your name and email address and possible preferred password. Your request is sent to Content Glass CMS (Content Management System) when user account is created on your behalf. The information provided by registration form in addition to various default settings constitutes your account information. You can access your account and manage this information.
Note that currently we are in a transition from old model where accounts where created on www.contentglass.com to a new model where accounts will be created on www.contentglass.cloud. The new model is part of strategic shift to construct a cloud of Content Glass applications, all managed by single-sign-on. In addition, each account on www.contentglass.cloud may have a related account on www.contentglass.store where we plan to sell premium services in the future.
For as long as this transit exist, you should therefore be aware that you may have two accounts (assuming the store is not yet operational). Therefore if you decide to delete you may need to delete two accounts. To simplify here is a short guideline to explain where account is created:
Accounts related with version-1
Shopify App – when installing CG APP for Shopify, a user account, developer-account and managed-app entities are all created on www.contentglass.com. This is also where application preferences are set.
User registration view content Glass Button – Users that register to Content Glass account from the Cg-Button application, either running on a website or Chrome extension, is created on www.contentglass.com
Accounts Related with version-2
Any account related with one of Content Glass Cloud applications set below and other apps, is created on www.contentglass.cloud
Content-Glass-Direct, Reviews-Glass, Events-Glass, Online-Glass, Experts-Glass, Game-Glass, All-Apps directory, content glass store and more…
1.2.10 Payment Information
We are not collecting billing and payment information. For billing on Shopify app derivatives, we may use Shopify's billing system. In other cases, we may use PayPal billing system. As general rule, there is no need to provide and/or expose any billing information and therefore you should not expose such information either on your account, blog and forum comments, or help-desk tickets.
1.2.11 Billing Information
Future services on Content Glass may require purchase of service package from Content Glass Store. Content Glass Store keep purchase information such as record for orders made via third party payment gateway (e.g PayPal). However, it will not store and payment information. Any change to this term, if relevant will be provided in time.
1.2.12 Social Media Activity
1.3 To whom do we transfer this information?
In the case we will require to use a third-party service we will give a preference to third parties with a strong commitment to privacy and security standards.
We will also share your information when we are obliged to do so under applicable laws or by order of the competent authorities.
1.4 Data retention
All account data explicitly shared with us remains under your control. At any time, you can decide to cancel your account information of your account will be deleted from our Service. Non-identifying information is set to expire after a given period of time. In some limited cases, some information must be kept indefinitely due to legal obligations. The following sections describe our retention policy for each group of information.
1.4.1 Widgets Information
Widget information is stored until the owner user that created the widget delete it. In some cases, we may delete old widgets from our database for saving storage place and cleanup the widgets database from unused widget data.
Note that widgets ARE NOT automatically removed when you cancel your account, also since widget can be identified as assigned to peer, by other account than Content glass account (version 1). It is therefore your responsibility to delete the widgets when not used anymore. In special cases you may ask us to delete widgets by opening a ticket here, but you should be aware that we may not be able to handle it immediately.
As for Content Glass version-2 (planned to launch on the end of 2018) all widgets will be associate with specific user account, and this will make us easier to delete widgets upon canceling your account.
We may delete widgets by our own initiative – While we aim to keep widgets data for as long as possible it may happen from time to time that we delete old widgets that where not being update for long time and without prior notice, for freeing some database place and/or improve performance. You should therefore assume, when using Content Glass that shared information may not persist for as long as your account persist.
1.4.2 Widget activity Log
Widget activity log is an internal log that collect information about the events of creating and deleting widgets. Unlike widgets information that delete when widget is deleted, records of widgets activity log are persist across time, for until we decide to cleanup the log table in database. This log is our only source for knowing about deletion of widgets therefore we can't delete it when widget is deleted. As state, information is not shared with any other third party.
As for version-1 you may ask us to delete widgets by opening a ticket here, but you should be aware that we may not be able to handle it immediately. In such inquiry you must provide us with some identifying information set in the data of the widget, since the association with the creating owner peer is not kept.
As for Content Glass version-2 (planned to launch on the end of 2018) we are planning to improve this mechanism so that it will be easier to identify the origin of a record in the log, to previously exist account.
1.4.3 Widget Local Storage
Information stored locally on browser cache, when managing widgets is dynamically changed based on widgets loaded to client-side. In any case, all this information can be delete by user by clicking on the Clean Cache menu item in Content Glass application. Or alternatively, by deleting browser cache data.
1.4.4 Account Information
Account information is kept for as long as you keep your account. When you cancel your account, its data is removed.
Note that if you have managed-app associate with your account, it will be deleted when the parent account will be removed.
1.4.5 Managed-App Account entity
Managed accounts are designed to persist for as long as the parent user account persist. This design let user that uninstall third party app, to reinstall, and get back to last used settings (wh9ich is a requirement by some third-party app platform – for example Shopify).
Managed-accounts are deleted when parent user account is deleted. There is no manual control for deleting managed-account.
1.4.6 Developer Account entity.
Developer account entity is created as part of launching an install procedure for managed account. The developer account entity is persist as long as the parent user account is kept. Developer-accounts are deleted when parent user account is deleted. There is no manual control for deleting developer-account.
1.4.7 Contact Information
Contact information used to submit a Content Glass helpdesk ticket is stored until you ask us to delete it. Closed items may be deleted without notice for saving storage place and cleanup the help-desk system from holding unused information.
Usage information shared with Google Analytics is kept up to 26 months after your last visit.
Social media activity processed by our platform may be stored indefinitely for statistical purposes.
Like many websites, we use "cookie" technology to collect additional website usage data and to improve our Services. A cookie is a small data file that is transferred to your computer's hard disk. Content Glass may use both session cookies and persistent cookies to better understand how you interact with our Services, to monitor aggregate usage by our users and web traffic routing on our services, and to customize and improve our Services.
We are also using 3rd party cookies. Examples of services we may be using are
Cookies are small files of data, stored by websites scripts in the cache of your web-browser (Internet Explorer, Firefox, Chrome, Opera, Safari, etc') for the purpose of enhancing user experience, providing much faster surfing experience, and being able to provide many of the modern services of customizing user experience based on user behaviour in a website. In simple words: Cookies are a way for personalizing user experience on a website, and mainly for most of the cases where users are not subscribers of a website. So, saving a data about user uses the local cache of a browser.
1.5.1 Some examples
1. Google Analytics cookies: some of our websites uses Google analytics script. The purpose of this script is to collect information about website traffic. The collected data is then presented to website owner on a special account as Google Analytics website. Using this information website owner can have better understanding of the way, users use his of her website. This can include for example, graph of amount of visits, pages visited, the time user spend on a website, the location (country) from where user arrived, the type of browser user is using and more. Website owner may want to use this information in order to improve website, to evaluate the business model of a website, to evaluate the success of promotion activity and more. What important here is to understand that website owner does use statistical data for the macro perspective of a website. Note that I first used the term "traffic" and not "users". For us, website owners, understanding the trends of a "traffic" and the behaviour of the "traffic" on our website is extremely important in order to estimate the relevancy of our website, to the kind of "users" we expected to receive as a traffic. Your personal contact information is becoming important only when you subscribe, and only for websites, that allow subscription, like this website (www.rhizome-networs.com). Google analytics cookies are look like that in the browser's cache:
You can read about the exact purpose of any type of Cookie in this link: click here
3. Cookies from advertising widgets: Many websites uses advertising as a mean for funding website activity. In fact, advertising, and affiliate marketing (commission based advertising) is something that almost any website owner learn to use and apply to website at some point or another in a website life-cycle, unless a better approach for function website activity, and organization activities, is found. That way advertising widgets are so commonly used. The Cookie of advertising widget keep information that help the 3'rd party agency that provide the advertising to try and match ads to traffic. Have you noticed that many times, an advertisement, lets say from Google AdWords, is tracking you while you move from one website to another? How is that possible? You already know the answer - Cookie. Here is an example of cookies received from AdSense widgets that show Google Ads on some of our websites:
< 5. Cookies from social-widgets: Social widgets are features on a website that establish a connection between a website and social-networks. For example, by clicking the Like button of Facebook, a linkage is created from Facebook to the specific page on a website. By creating a Bookmark on Twitter a link is created from Twitter to the website. These links are essential part of SEO strategy of any modern website. wit the strict purpose to drive more traffic to the website. Some of the social-widgets may create cookies. Here is an example of Cookies created by Google+:
1.5.2 Type of Cookies we are using
You should be aware now, of what Cookie is - a file stored on the web browser's cache for the purpose of personalizing user experience when browsing a website. In the list below we summarize the Cookies we are using on our websites. Not all the cookies are used on each websites. Some websites provide only first-party Cookies (Cookies Rhizome Networks is generating) such as the "rhz-compare-list" shown in the example above. Other websites use also third-party cookies such as those generated by Google Analytics and Google ads. So formally we declare that A WEBSITE OWNED BY Rhizome Network LTD MAY NOW OR IN THE FUTURE, INCLUDES ONE OR ALL OF THE FOLLOWING COOKIES:
- 1. First-party cookies used and require by our own services such as: - Comparison widget - Cart - Listing of product - Social-Browsing proxy
- 2. Login user cookies
- 3. Analytics cookies from these 3'rd party services:
cookies generated by Rhizome Networks' accont - Google Analytics and other cookies generated when presenting IFrame with customer reviews from Amazon. 4. Cookies of social-widgets: - Facebook Like button - Google+ button - Social bookmarking: AddToAny.com and other
1.5.3 Avoiding Cookies
If you prefer to avoid cookies completely you can set your web-browser's settings not to accept cookies. We provide here a general pattern for setting. For the exact procedure please consult your browser's settings guide: Microsoft Internet Explorer Click the 'Tools' icon in the top right hand corner and select 'Internet options'. In the pop up window select the 'Privacy' tab. From here you can adjust your cookie settings. To delete: Tools->delete browsing history-> select the "Cookies" option and press the Delete button Google Chrome Click the spanner in the top right hand corner and select 'Settings'. From here select 'Under the hood' and change the settings under 'Privacy'. Mozilla Firefox From the drop down menu in the top left hand corner select 'Options'. In the pop up window select the 'Privacy' tab. From here you can adjust your cookie settings. To delete: Tools->Clear browsing data->check "Delete cookies and other site and plug-in data" option and press the deletion button. To delete: Tools->Clear recent history->Select the "Cookies" option and click the "Clean now" button. Safari From the settings drop down menu in the top right hand corner select 'Preferences'. Select the 'Security' tab and from here you can adjust your cookie settings. Opera Use Tools->Preference, then select the "Advanced" tab, the the "Cookies" item in the list. Make a settings. To delete: Delete discrete Cookies can be handled by Tools->Advanced->Cookies. To delete the entire cache of cookies use Tools->delete private data and in the "detailed options" select "delete all cookies". The press the deletion button. To
As explained above, Cookies are essential part of user experience on Rhizome Networks' websites. - Using cookies in our Services is essential for the operation of those services.
· Using Login-user cookies is essential for us in order to provide you subscription-based websites
· Using Advertising Cookies is essential for us in order to provide you with free websites.
· Using Analytics cookies is essential for us in order to improve and evaluate our websites.
· Using social-widgets cookies is essential part of website marketing and promotion efforts.
In addition, we act to make information about Cookies and other method we are using for collecting personal information, available and highlighted so that any visitor of our website, can access and read. In addition, we are acting to provide on our website, a special Widget to allow users like you to express their consent. However, many or our websites assume traffic of occasional users. Most of these uses will not stay more than few seconds on our website. The process of conditioning website usage prior to any invocation of Cookies is therefore - NOT PRACTICAL. In simple words asking occasional user to "Agree" on something is like telling this user "Go away..." and we don't want users to Go away. We want users to be what the terms "users" denote: "to use". We want users to use our websites.
1.5.5 Opt-Out from User's expressed constant
1.7 Can I object to my personal information being used and how to contact Content Glass?
You may object to the processing by Rhizome Networks LTD of your personal data. However, in this case, Rhizome Networks LTD may not be in a position to provide the Content Glass Service.
1.8 Governing Law
By accessing our Services, you and Rhizome Networks LTD agree that all matters relating to your access to, or use of, Content Glass shall be governed by and construed in accordance with the laws of Israel, without giving effect to any principles of conflicts of law. Our website, and services are managed and operated from Israel. As such, we are subject to the laws of Israel, and such laws will govern this policy, without giving effect to any choice of law rules. We make no representation that our website(s), platform or other services are appropriate, legal or available for use in other locations. Accordingly, if you choose to access our website(s) and Content Glass platform, you agree to do so subject to the internal laws of Israel.
Last update 2018-05-13