Privacy Policy

At Hariome.com, the privacy of our visitors is of extreme importance to us. This privacy policy document outlines the types of personal information is received and collected by hariome.com and how it is used.

Log Files

Like many other Web sites, hariome.com makes use of log files. The information inside the log files includes internet protocol (IP) addresses, type of browser, Internet Service Provider (ISP), date/time stamp, referring/exit pages, and number of clicks to analyze trends, administer the site, track user’s movement around the site, and gather demographic information. IP addresses, and other such information are not linked to any information that is personally identifiable.

Cookies and Web Beacons

hariome.com does use cookies to store information about visitors preferences, record user-specific information on which pages the user access or visit, customize Web page content based on visitors browser type or other information that the visitor sends via their browser.

DoubleClick DART Cookie

  • Google, as a third party vendor, uses cookies to serve ads on Hariome.com
  • Google’s use of the DART cookie enables it to serve ads to users based on their visit to Hariome.com and other sites on the Internet.
  • Users may opt out of the use of the DART cookie by visiting the Google ad and content network privacy policy at the following URL – http://www.google.com/privacy_ads.html.

These third-party ad servers or ad networks use technology to the advertisements and links that appear on Hariome.com send directly to your browsers. They automatically receive your IP address when this occurs. Other technologies ( such as cookies, JavaScript, or Web Beacons ) may also be used by the third-party ad networks to measure the effectiveness of their advertisements and / or to personalize the advertising content that you see.

Hariome.com has no access to or control over these cookies that are used by third-party advertisers.

You should consult the respective privacy policies of these third-party ad servers for more detailed information on their practices as well as for instructions about how to opt-out of certain practices. Hariome.com ‘s privacy policy does not apply to, and we cannot control the activities of, such other advertisers or web sites.

If you wish to disable cookies, you may do so through your individual browser options. More detailed information about cookie management with specific web browsers can be found at the browser’s respective websites.

Privacy Policy Changes

Although most changes are likely to be minor, Hariome Network may change its Privacy Policy from time to time, and in Hariome World sole discretion. Hariome Network encourages visitors to frequently check this page for any changes to its Privacy Policy.Your continued use of this site after any change in this Privacy Policy will constitute your acceptance of such change. 

SMS Usage

We are authenticating user by using facebook SDK it requires SMS to validate the user.

Phone Number Verification Flow

  1. We are using facebook Account Kit API with a phone number to initiate a login or registration.
    • Phone call — People can choose to receive a phone call with the SMS code. For a list of the languages into which the call can be localized, see the Supported Langages for Phone Calls section of Supported Languages.
    • Facebook notification — If the phone number is linked to a Facebook account, people can choose to have a notification containing the SMS sent to that account.Account Kit servers send an SMS with a confirmation code to continue the login. If people fail to receive the SMS code, Account Kit offers two backups that people can choose from:
    • Account Kit may also verify the number directly without sending an SMS code. See Instant Verification
  3. The SDK verifies the SMS confirmation code.
  4. If your app has enabled Client Access Token Flow, your app will receive an access token containing an account ID in response to a successful login. If your app has not enabled Client Access Token Flow, your client app will receive an authentication code that the application’s server may use to securely request an access token.