> For the complete documentation index, see [llms.txt](https://tinkerhub.gitbook.io/th-shelf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tinkerhub.gitbook.io/th-shelf/privacy-policy.md).

# PRIVACY POLICY

The following document outlines the Privacy Policy of TinkerHub Foundation \[TTIF]. Also review our Terms of Service (terms*of*use), which govern your use of our services. There is a short explanation at the end of each section that is not legally binding.

### 1. Acceptance of policy <a href="#id-1-acceptance-of-policy" id="id-1-acceptance-of-policy"></a>

This privacy policy ("Policy") describes how TinkerHub Foundation \[TTIF] collects, uses and shares personal information of its Users. This Policy also applies to any of our other websites that post this Policy. This Policy does not apply to websites that post different statements. To use our website / portals of you must agree to this Policy and our Terms of Service.

Basically: This policy describes how we collect, use and share personal information.

### 2. What we collect <a href="#id-2-what-we-collect" id="id-2-what-we-collect"></a>

We get information about you in a range of ways.

Information You Give Us. We collect your name, postal address, email address, phone number, fax number, username, password, demographic information (such as your gender and occupation), and other information you provide to us.

Information We Get from Others. We may get information about you from other sources. We may add this to information you provide to us.

Information Automatically Collected. We automatically log information about you and your computer. For example, when visiting our Site, we log your computer operating system type, browser type, browser language, the website you visited before browsing to our Site, pages you viewed, how long you spent on a page, access times, Internet protocol (IP) address and information about your use of and actions on our Site.

Cookies. We may log information using "cookies." Cookies are small data files stored on your hard drive by a website. Cookies help us make our Site and your visit better. We use cookies to see which parts of our Site people use and like and to count visits to our Site.

Web Beacons. We may log information using digital images called Web beacons on our Site or in our emails. We use Web beacons to manage cookies, count visits, and to learn what marketing works and what does not. We also use Web Beacons to tell if you open or act on our emails.

Basically: In order for you to use the services, we need to collect certain information.

### 3. How we use personal information <a href="#id-3-how-we-use-personal-information" id="id-3-how-we-use-personal-information"></a>

hWe use your personal information as follows: We use your personal information to operate, maintain, and improve our sites. We use your personal information to respond to comments and questions and provide customer service. We use your personal information to send information including confirmations, invoices, technical notices, updates, security alerts, and support and administrative messages. We use your personal information to communicate about, upcoming events, and other news offered by us \[and our selected partners]. We use your personal information to protect, investigate, and deter against fraudulent, unauthorized, or illegal activity.

BBasically: We use the information we collect to provide you with the services.

### 4. How we share personal information <a href="#id-4-how-we-share-personal-information" id="id-4-how-we-share-personal-information"></a>

We may share personal information as follows: We may share personal information with your consent. For example, you may let us share personal information with others for their own marketing uses. Those uses will be subject to their privacy policies. We may share personal information when we do a partnership deal, or negotiate a partnership deal, involving sale or transfer of all or a part of our organization or assets. These deals can include any merger, financing, acquisition, or bankruptcy transaction or proceeding. We may share personal information for legal, protection, and safety purposes. We may share information to comply with laws. We may share information to respond to lawful requests and legal processes. We may share information to protect the rights and property of \[our organization], our agents, customers, and others. This includes enforcing our agreements, policies, and terms of use. We may share information in an emergency. This includes protecting the safety of our employees and agents, our customers, or any person. We may share information with those who need it to do work for us. We may also share aggregated and/or anonymized data with others for their own uses.

Basically: Under certain circumstances, we can share this information with others.

### 5. Control over your information <a href="#id-5-control-over-your-information" id="id-5-control-over-your-information"></a>

You may send requests about personal information to our Contact Information below. You can request information about and updates to your personal information. Our marketing emails tell you how to "opt-out." If you opt out, we may still send you non-marketing emails. Non-marketing emails include emails about your accounts and our business dealings with you. You can typically remove and reject cookies from our Site with your browser settings. Many browsers are set to accept cookies until you change your settings. If you remove or reject our cookies, it could affect how our Site works for you.

Basically: You have to opt out to avoid us using your data, but we do give you some control over your data.

### 6. Security of your personal information <a href="#id-6-security-of-your-personal-information" id="id-6-security-of-your-personal-information"></a>

We take steps to help protect personal information. No company can fully prevent security risks, however. Mistakes may happen. Bad actors 2 may of 4 defeat even the best safeguards.

Basically: We have security measures in place to protect your information but internet accessible information is vulnerable

### 7. Contact information <a href="#id-7-contact-information" id="id-7-contact-information"></a>

We welcome your comments or questions about this Policy. You may also contact us at <kurian@tinkerhub.org>

Basically: Email <kurian@tinkerhub.org> if you need assistance.

### 8. Changes to this privacy policy <a href="#id-8-changes-to-this-privacy-policy" id="id-8-changes-to-this-privacy-policy"></a>

TinkerHub Foundation \[TTIF] reserves the right, at its sole discretion, to modify or replace the Policy at any time. If the alterations constitute a material change to the Policy, TinkerHub Foundation \[TTIF] will notify you by posting an announcement on the Site. What constitutes a material change will be determined at TinkerHub Foundation \[TTIF] sole discretion. You shall be responsible for reviewing and becoming familiar with any such modifications. Using any service or viewing any content following notification of a material change to the Policy shall constitute your acceptance of the Policy as modified.

Basically: We may change this policy from time to time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tinkerhub.gitbook.io/th-shelf/privacy-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
