This Policy sets out our privacy practices and explains how we handle the information we collect on our Requests app and service and more generally in our Content Glass Cloud services.
Scope of policy terms
This policy applies to Requests app and all of our services used this app. This includes:
- Requests website - requests.contentglass.com
- Requests apps
- Web app
- Mobile app
- Desktop app
- Browser plugin app
- Requests service
- Other services of Content Glass cloud used by Requests app include but not limited to:
- Accounts service
- Content Glass service
- Messages service
- Billing service
- CRM service
- and other.
For convenience we use the term apps, or Services to all these cases.
For service terms click here.
Services - general term refer to all services and apps in the scope of this policy
Rhizome Networks LTD - The company that develop and operate the Services. We use the term "We" or "Us" to refer to rhizome networks.
Requests - the name of the app and service we provide as referred by this website.
Content Glass Cloud - a collection of services, provided and operated by Rhizome Networks LTD. Requests app and service are part in Content Glass Cloud.
Entity - piece of information stored by the system, that is usually associate with some business-logic.
- Account - user account to allow authentication of user
- Request - system entity created in the service that represents a request for help made by user Request entity is of type Widget (see below)
- Profile - system entity that store user preferences and details.
Request status - the status of request
Requester - the term we use to call the user that create a Request.
Helper - the term we use to call user that handle a Request.
Operation Mode - each user can function as both Requester and Helper. These are two operation modes of Requests app.
Wallet - system entity dedicated for each user, that record the amount of money charged by user as well as information on transactions made by user. Wallet does not holt actual money, its only a record that hold user's credit.
Widget - system entity that represent piece of information and possibly logic that can be shared in association with various contexts and given various states.
Glass - system entity that represents a context for sharing information, a subject, a topic, event, scope of data etc.
State - system entity that represents a condition that determine visibility and/or operation, and or exposure of widget.
API - Application Programming Interface. Software libraries that can be used to develop code that extends or integrate with Requests app.
Database - a mean to store digital information on the cloud. This include relational database, service-index, directory service and other means we may found useful.
Social feeds - Social network and messaging platforms on which we may post request, in addition to requests view we present on our own apps. For example, Twitter wall, Facebook group and more.
Requests app and service is provided developed and operated by Rhizome Networks LTD, ID 514255132, Zichron Yakov 8 Petah Tikva Israel ISRAEL.
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 private information you provide with third parties, except for chosen permitted partners that operate the Services with us.
You always remain in control of your data. You may edit or erase your data from our Services at any time.
This Policy does not apply to information collected by third-party Web sites linked to or otherwise accessible from our Services.
This Policy does either apply to third party applications created by developers using the API we provide, except for the parts of information ("Widgets") that will be stored by our Services. The information collected or received by third-party services is subject to their own privacy policies.
We use browser database to store part of the information application use locally, on client-side. This is required for making the app more efficient when accessing data over and over again. We use software that make sure this data is synched with the related data stored on Database on our Services. If you are using your private PC there is no issue. However, if you are using public PC to view Requests app, you must clean browser data after you finish using the app. For convenience we provide in app menu a tool that help you to clear the data used by app.
Requests app let you share Request post with Helpers, ad explained below in more details. These requests are public and may expose to other user. Accordingly - NEVER EVER SHARE SECRET INFORMATION ON REQUESTS BODY OR COMMENTS. If you need to share private information with Helper, do it by phone, or by messaging but not in the body of Request post.
How do we use the information we collect?
The information we collect is used solely for operating and improving our Services. In the next sub-chapters we explain how do we use it.
Visiting the services
We may 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). You can opt-out using this tool. https://tools.google.com/dlpage/gaoptout/
We may also use log data to fight spam and other abuse of our services.
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.
When you create an account on one Content Glass Cloud you obviously provide us account information.
From time to time, we use your email exclusively to send you information about new features of available on our Services. You can decide to opt out newgroups at any time within your account setting page as provided by link on newsgroup mail.
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.
Profile entity information
We use Profile entity to store user details and preferences. The information of Profile entity is sent to our Services and there it is stored on a cloud database which is part of our Services.
The information of Profile entity is also stored on a local database located in your browser, to allow more efficient repeated access to data.
Request entity information
We use the information set for Request to implement the core Request / Help business-logic of the <a>Requests</a> application.
Requests app allow you to create Request entity that represent a request for Help. By posting request entity you act as a Requester.
The information of Request entity is sent to our Services and there it is stored on a cloud database which is part of our Services.
The information of Request entity is also stored on a local database located in your browser, to allow more efficient repeated access to data.
Helpers, other users that want to handle the request, can view requests posted by users and lock a request they want to handle.
You will get a notification to approve the Helper and then after approval you can both collaborate to solve the issue or fulfil the task.
Once done the Requester is required to pay the agreed amount and then Request can be closed.
As Requester you give us the permission to:
- Present Requests data to other users on out apps.
- Present Request data social-feeds. Since social-feeds require us to accept your permissions, we provide preferences in your profiel view, where you can allow or not, the post of Requests into social feeds.
- Use automated software or human review to generate aggregated insights from Requests data
- Use automated software or human review to monitor forbidden activity as defined by service terms. For example spams, affiliate-links posted outside of terms rules and more.
- Present your contact details to Helpers that was approved by you, to allow Helper to contact you and collaborate.
- Present a rating that represent your reliability as Requester on the system.
- Present to Helper various warnings if exists, for example if you were involved in disputes.
- Use content you posted on our ad campaigns for example, to attract helpers in specific niece to join the service and answer your request.
As Helper you give us the permission to:
- Present your contact details to Requester of a Request you handle to allow Requester to contact you and collaborate.
- Present a rating that represent your reliability as Helper on the system.
- Present to Requester various warnings if exists, for example if you were involved in disputes.
- If you are working as for a partner organization we may create aggregate reports that include your activity.
- Use content you posted on our ad campaigns for example, to attract requesters in specific niece to join the service and post new requests..
Any user, regardless of working mode gives as the permission to:
- Collect information on various activity events that allow us to improve our services. For example how long it took you to find Request you want to respond to, how long it took you implement task, offer and bid for specific requests category, which views were used and more.
- Generating anonymous aggregated data that allow us to improve the services. For example the average offer or bid given Request at some category.
Request posts are public and may expose to other user. Accordingly - NEVER EVER SHARE SECRET INFORMATION ON REQUESTS BODY OR COMMENTS. If you need to share private information with Helper, do it by phone, or by messaging but not in the body of Request post.
Messaging and Newsletter Information
When creating an account we create User entity if our system to represent the user for our services. We use this user entity as destination for sending messages, and those messages can be viewed and/or received with our apps or other ways.
There are few types of messages:
- System notifications - we notify you about some event or occurrence.
- Peer to Peers notifications - we notify you with activity made by related peer. For example when Helper lock a Request, we notify the Requester.
- Push message - we use push-message mechanism, to push messages into device also when app is not in focus. This improve real-time response of app to various events. We use internal technology for push messages as well as external service provided by Google - Firebase Cloud Messaging.
- Email messages - an ordinary Email message. For example when you register you receiver Email message.
In addition, you may subscribe to various newsgroup of various topics using your profile management page. Once subscribed, you can unsubscribe from newsletter.
some of the features provided by Requests app are paid features as specified and explained by pricing page. To collect money, we are using PayPal platform to collect the money.
We do not handle money transactions in our Services. Instead it is entirely handled by PayPal. Once payment accomplished and approved by PayPal we get a notification in the form of "webhook". This is an automated notification handled over HTTP. Our Billing service receive the webhook request and process the information.
First we verify that request includes some required info to affirm it is a valid PayPal webhook. Then we parse the information and extract the Paypal email address of the paying user.
We scan our system to detect Profile entity with the email address received from PayPal. When found, we load the Wallet entity if related user and calculate the new balance according to amount and currency reported by webhook notification. At the end of this procedure, the Wallet is set with new balance relative to the amount paid by user.
The actual Payment transaction is handled by PayPal and within PayPal. We only represent the paid amount in the Wallet entity.
We use a software provided by osticket.com as a platform to handle technical support 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.
Anti Spam Service
We use 3'rd party anti-spam service from https://cleantalk.org to protect against spammers.
When user sign-up to service we check user's IP address and Email against database of spamming and blacklisting address. If we find and error we avoid the sign-up and notify the user.
For monitoring and review purpose, we allow 3'rd party service to log the approved requests..
Types of information we Collect and Store?
In this chapter we describe the type of information we collect.
User Account Entity Data
Data provided by user upon registration that is used to authorizing the user to access the services. This includes Email, password and acceptance to terms.
Profile Entity Data
Profile data is used to store preferences, contact and billing information provided by user. Most of the fields are optional, some of the fields are optional but can help to provide better experience and few fields are required.
Here is partial list of core the data we may collect by profile: first-name, last-name, mobile-phone, home-phone, office-phone, fax number, country, state, city, po-box, zip-code, iban code, PayPal address and picture.
Any specific app or service or service of our Services and apps, such as Requests, Clicks, and more, can add its own custom fields data to profile.
Requests entity are created by user as explained above. Request entity represent a single request for help. The information may also be published on social-feeds, depending in your preferences as set on Profile. Other users may add comments to Request. The information is PUBLIC. Never expose secret or private information in the body of Request post.
The user that post a Request is the sole responsible for information exposed when creating a Request.
The user that post Comment in Request, is the sole responsible for information exposed in the comment
Wallet Entity Data
The Wallet store a number that represents the balance a user is having for using paid features such as locking a Request post by Helper for establishing a deal with the Requester.
Wallet data includes: balance, currency code, PayPal address and log of information received from PayPal platform upon performing a payment.
One should note that we DO NOT handle money transactions in our Services. Instead we use PayPal service or other 3'rd party services as we may found to be useful.
We DO NOT store any CREDIT CARD information.
We DO NOT ASK CREDIT CARD information.
You Should NEVER provide us with CREDIT CARD information unless expressly requested by Billing department.
You Should NEVER provide other app users with CREDIT CARD information.
On various events we create Message entity and store it on the database. We then distribute the message to relevant users. Message data usually include a title, text description and some times, an additional data that provide more details on the reported event. Client Apps use this information to show data to users.
Push Message Data
On various events we use push-message technology to push messages into device and alert the user also if user does not currently put the application in focus. For example, when Helper lock a Request, we notify the Requester with ordinary message (see above) but also with push message. We use Firebase Cloud Messaging for push technology. One should note that Firebase messaging technology may store the message in its servers if the device message is set to, is not available or that app is turn off. This is the way this technology works. The message is stored by Firebase in association with as account Rhizome Networks have on Firebase.
During processing on various events we store information that log the events. For example, when Helper make payment, once we get notification from PayPal that payment was approved we store a log of the event. Activity log is required for internal monitoring and management of our Services.
Information collected by third-party apps
Requests app and service provide an API for developers for creating apps. We are not responsible for policy set by third party partners when developing their apps. Yet as for Request entity, originated by 3'rd party apps, the same concepts apply as described above.
We may use Google Analytics or other similar technology to log end-user information, such as visited views, buttons that were clicked etc'. The information is used by us to understand how users actually use our services and apps and how can be improve.
Social Media Activity
To whom do we transfer this information?
We do not share your private information or data with third parties outside Rhizome Networks LTD except for when using 3'rd party platforms to collect usage-information as explained above, that help us to improve our Services.
We do not share private information with 3'rd party apps that uses our API. Those apps can only access the public information if Request data, as explained above, and private information associate with the account of user that manage the app.
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.
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.
Request information is stored until we need to clean it to free more space and given that Request is closed. Since we are using Request data to generate aggregated anonymous data that help us to improve the service, one should assume that we store Request data long enough for running the processes that calculate all stats we want to calculate.
Activity data is stored until we need to clean it to free more space. Many of the activity records relate with interaction between users, therefore one should NOT assume that once we delete an account, we also delete all related activity records. This is not the case. We keep activity records for as long as we need for management of the system.
Some of the data entities used by Request app are stored on the browser database. The data is stay until it is cleaned automatically by application or until user clean browser data. The recommended approach for deleting the locally stored data is as following:
1. First, enter Preferences from menu, select Tools and then Clear app data
2. Clean browser data as you usually do.
Account information is kept for as long as you keep your account. When you cancel your account, its data is removed. Note that the same user account can serve multiple apps and services on Content Glass Cloud. In addition, account is related with generic user resources such as Profile and Wallet. Deleting your account will also delete those entities.
Note that you can not delete your account while you have Request in work of dispute.
To delete your account act as following:
1. Open Requests app
2. Enter your Profile page
3. You will find below a button for closing the account. Click the button and fill the test to approve your action.
At this phase we will run a test to check is your current state allow deleting an account. If eligible for deletion we will send a code to your email. Once you get the code, write the code in the appropriate field on deletion view and click approve. This will block your account and notify support department for requested deletion. Support may double check that account is eligible for deletion and delete, of that account will be deleted automatically within a period of running automatic deletion of blocked account
If account is not eligible for deletion you will be notified. It means that before you can delete you need to work with Helper to close the open Request(s)
If you have problems with the procedure please contact support through Ticket system
Contact information used to newsletter mechanism and account mechanism is kept until the account is deleted.
Contact information used to submit support Ticket is stored until you ask support 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 purpose.
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.
Examples of cookies
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+:
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:
- First-party cookies used and require by our own services.
- Login user cookies
- Analytics cookies from these 3'rd party services:
- cookies generated by Rhizome Networks' accont
- Google Analytics
- Cookies of social-widgets: - Facebook Like button - Google+ button
- Social bookmarking such as 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.
Opt-Out from User's expressed constant
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 you the Requests service .
By accessing our Services, you and Rhizome Networks LTD agree that all matters relating to your access to, or use of our Services 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 Services, you agree to do so subject to the internal laws of Israel.
Contact person: Gilad Tiram CEO
Date of last revision: 09 February 2021