Thank you for choosing Hiveon! Hiveon 'us', 'we', or 'our') operates the https://hiveon.com/, https://hiveon.com/forum/, https://hiveon.net/ websites (the 'Services').

This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our Services and the choices you have associated with that data.

We use your data to provide and improve the Services. By using the Services, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, accessible from Terms of Use

Information Collection And Use

We collect several different types of information for various purposes to provide and improve our Services to you.

Types of Data Collected

Personal Data

While using our Services, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ('Personal Data'). Personally identifiable information may include, but is not limited to:

Email address
Username
Farm IDs
Cookies and Usage Data

Usage Data

We may also collect information how the Services are accessed and used ('Usage Data'). This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Services that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

Tracking and Cookies Data

We use cookies and similar tracking technologies to track the activity on our Services and hold certain information.

Cookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Services.

You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Services.

Examples of Cookies we use:

Session Cookies. We use Session Cookies to operate our Services.
Analytics Cookies. We use analytics cookies to improve the quality of our Services.

List of cookies we use:

Cookies in the account (the.hiveos.farm):
- necessary authentication cookies (jwtt)
- necessary Cloudflare cookies (__cfduid)
- analytics cookies (_gat, _gat_conversionTracker, _ga, _gid)
Cookies on the website (hiveon.com):
- necessary Intercom cookies (intercom-id-[app_id], intercom-session-[app_id])
- necessary Cloudflare cookies (__cfduid)
- Analytics, Facebook and Google cookies (_ga, _gid, _fbp, _gat)
- Settings cookies (settings-gdpr-GA-accept, settings-gdpr-GTM-accept, settings-gdpr-FB-accept)

The functions of the cookies we use:

jwtt — the session ID
__cfduid — cookie associated with websites using CloudFlare (required to speed up page loading)
_gat — limits the frequency of requests
_gat_conversionTracker — limits the frequency of requests
_gali — this cookie is associated with Google Analytics. This cookie is used to collect information about how visitors use our site
_ga — allows to to distinguish users
_gid — allows to to distinguish users
intercom-id-[app_id] — an anonymous visitor identification cookie. Default expiration is 9 months
intercom-session-[app_id] — is used to keep track of sessions and remember logins and conversations. Default expiration is 7 days
_fbp — allows to to distinguish users
_hjSessionUser[site_id] — Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. Default expiration is 365 days
_hjSession[site_id] — A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. Default expiration is 30 minutes
_hjClosedSurveyInvites — Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. Default expiration is 365 days
_hjDonePolls — Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. Default expiration is 365 days
_hjMinimizedPolls — Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. Default expiration is 365 days
_hjShownFeedbackMessage — Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. Default expiration is 365 days
_hjSessionTooLarge — Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. Expires on session end
_hjSessionRejected — If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues. Expires on session end
_hjSessionResumed — A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. Expires on session end
_hjid — Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. Default expiration is 365 days
_hjRecordingLastActivity — This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records). Expires on session end
_hjTLDTest — When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. Expires on session end
_hjUserAttributesHash — User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. Expires on session end
_hjCachedUserAttributes — This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present. Expires on session end
_hjLocalStorageTest — This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. Expires in less than 100ms
_hjIncludedInPageviewSample — This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit. Default expiration is 30 minutes
_hjIncludedInSessionSample — This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit. Default expiration is 30 minutes
_hjAbsoluteSessionInProgress — This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. Default expiration is 30 minutes
_hjFirstSeen — This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. Expires on session end
_hjViewportId — This stores information about the user viewport such as size and dimensions. Expires on session end
_hjRecordingEnabled — This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. Expires on session end
settings-gdpr-GA-accept — used to save cookie settings
settings-gdpr-GTM-accept — used to save cookie settings
settings-gdpr-FB-accept — used to save cookie settings
settings-gdpr-hotjar-accept — used to save cookie settings

How to manage cookies

You can manage and delete cookies:

Removing cookies from your device. You can remove all cookies that are already on your device by clearing the browsing history of your browser. This will remove all cookies from all websites that you have visited. Please note that you may also lose some saved information (e.g. saved login details, website preferences).
Managing website-specific cookies. For more detailed control over website-specific cookies, check the privacy and cookie settings in your preferred browser.
Blocking cookies. You can set most modern browsers to prevent any cookies being placed on your device, but in this case may then have to manually adjust some preferences every time you visit a website or a page. Due to this, some functions may not work properly.

Hiveon uses the collected data for various purposes:

To provide and maintain the Services
To notify you about changes to our Services
To allow you to participate in interactive features of our Services when you choose to do so
To provide customer care and support
To provide analysis or valuable information so that we can improve the Services
To monitor the usage of the Services
To detect, prevent and address technical issues

Transfer Of Data

Your information, including Personal Data, may be transferred to - and maintained on - computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.

Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.

Hiveon will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.

Disclosure Of Data

Legal Requirements

Hiveon may disclose your Personal Data in the good faith belief that such action is necessary to:

To comply with a legal obligation
To protect and defend the rights or property of Hiveon
To prevent or investigate possible wrongdoing in connection with the Services
To protect the personal safety of users of the Services or the public
To protect against legal liability

Security Of Data

The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

Links To Other Sites

Our Services may contain links to other sites that are not operated by us. If you click on a third party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.

We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.

Children's Privacy

Our Services does not address anyone under the age of 18 ('Children').

We do not knowingly collect personally identifiable information from anyone under the age of 18. If you are a parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from children without verification of parental consent, we take steps to remove that information from our servers.

Changes To This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

We will let you know via email and/or a prominent notice on our Services, prior to the change becoming effective and update the 'effective date' at the top of this Privacy Policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

Contact Information

If you have any questions about this Privacy Policy, please contact us: [email protected]

Ready to Get started?

Free for home mining! Pay as you grow.

Start mining