Privacy and Terms
When you use our services and solutions, you trust us with your information. This Privacy Policy is meant to help you understand what data we collect, why we collect it, and what we do with it. This is important; we hope you will take time to read it carefully.
- Information you give us.
- Information we get from the use of our services.
- Use Cases
- Implementation Methods
- Feedback
For example, many of our services require you to sign a contract. When you do, we’ll ask for personal and/or professional information, like your name, email address, telephone number or payment information.
We collect information about the services that you use and how you use them, like the business problem you're trying to solve or how these tools are useful in the organization. This information includes:
Understanding how our products are used in the industry is important to us. How users envision using our products, how you are using our products, and what you are using them for.
There are times when our products are integrated into larger systems. We collect and use the details about how our products and services are used in relation to the total project scope.
During meetings, whiteboarding sessions, demos or other client interactions we collect the comments, opinions, and ideas. We also use the feedback generated from emails and surveys to better our offerings and services.
We use the information we collect from all of our services to provide, maintain, protect and improve them, to develop new ones, and to protect TechBuilders, LLC and our users. We also use this information to offer you tailored products and services.
When you contact TechBuilders, LLC, we keep a record of your communication to help solve any issues you might be facing. We may use your email address to inform you about our services, such as letting you know about upcoming changes or improvements.
We will ask for your consent before using information for a purpose other than those that are set out in this Privacy Policy.
- With your consent.
- With domain administrators.
- change your product passwords.
- suspend or terminate your product access.
- restrict your ability to delete or edit information or privacy settings.
- receive your information in order to satisfy applicable law, regulation, legal process or enforceable governmental request.
- For external processing.
- For legal reasons.
- meet any applicable law, regulation, legal process or enforceable governmental request.
- enforce applicable Terms of Service, including investigation of potential violations.
- detect, prevent, or otherwise address fraud, security or technical issues.
- protect against harm to the rights, property or safety of TechBuilders, LLC, our users or the public as required or permitted by law.
We will share personal information with companies, organizations or individuals outside of TechBuilders, LLC when we have your consent to do so.
If your project is managed for you by a third party, then your domain administrator and resellers who provide user support to your organization will have access to your information (including your email and other data). Your domain administrator may be able to:
We provide information to our affiliates or other trusted businesses or persons to process it for us, based on our instructions and in compliance with our Privacy Policy and any other appropriate confidentiality and security measures.
We will share personal information with companies, organizations or individuals outside of Google if we have a good-faith belief that access, use, preservation or disclosure of the information is reasonably necessary to:
We work hard to protect TechBuilders, LLC and our users from unauthorized access to or unauthorized alteration, disclosure or destruction of information we hold. In particular:
- We encrypt many of our services using SSL.
- We review our information collection, storage and processing practices, including physical security measures, to guard against unauthorized access to systems.
- detect, prevent, or otherwise address fraud, security or technical issues.
- We restrict access to personal information to TechBuilders, LLC employees, contractors and agents who need to know that information in order to process it for us, and who are subject to strict contractual confidentiality obligations and may be disciplined or terminated if they fail to meet these obligations.
Our Privacy Policy applies to all of the services offered by TechBuilders, LLC and its affiliates, products and services offered on other sites (such as our consulting services), but excludes services that have separate privacy policies that do not incorporate this Privacy Policy.
Our Privacy Policy does not apply to services offered by other companies or individuals.Our Privacy Policy does not cover the information practices of other companies and organizations who advertise our services, and who may use cookies, pixel tags and other technologies to serve and offer relevant services.
We regularly review our compliance with our Privacy Policy. When we receive formal written complaints, we will contact the person who made the complaint to follow up. We work with the appropriate regulatory authorities, including local data protection authorities, to resolve any complaints regarding the transfer of personal data that we cannot resolve with our users directly.
Our Privacy Policy may change from time to time. We will not reduce your rights under this Privacy Policy without your explicit consent. We will post any privacy policy changes on this page and, if the changes are significant, we will provide a more prominent notice (including, for certain services, email notification of privacy policy changes). We will also keep prior versions of this Privacy Policy in an archive for your review.
We may use verbiage or terms throughout our website, documentation, or meetings that may not be intuitive outside of a niche technology community. These terms are generally referenced the most and should be thought of in the context involving data or technology. This set of terms is nowhere near a comprehensive list but should help provide clarity in most cases.
Ad-hoc reporting is a model of business intelligence (BI) in which reports are built and distributed by nontechnical business intelligence users. In other words, with ad-hoc reporting, all the technical user does is set up the BI solution, connect it to the data-sources, establish security parameters and determine which objects end-users can see. From that point on, the actual reports are created by business end-users.
Ad-hoc is Latin for “as the occasion requires.” This means that with this BI model, users can use their reporting and analysis solution to answer their business questions “as the occasion requires,” without having to request queries from IT. This generally infers the end-user has access to the database to run queries, being the main difference between self-service analytics.
Ad-hoc reporting’s goal is to empower end-users to ask their own questions of company data, without the time and expense of involving IT with the task of creating a myriad of reports to serve different functions and purposes. Ad-hoc reporting therefore makes the most sense when a large number of end-users need to see, understand, and act on data more or less independently, while still being on the same page as far as which set of numbers they look at.
Data volume mainly refers to the number of rows and columns in a "data set". A data set can be refered to as the data model, containing all of the database tables used to create the report. The usage of "data volume" is subjective at best. When people refer to large or huge data volumes, it can mean different things to different people. Sometimes this can mean a very "long" or "wide" data set, one with many fields and rows, regardless of persisted size. Other times people refer to the data set's persisted size of the data on a harddrive.
What gives? Different tools compress data in different ways. The same data set can be highly compressed and to some not be considerend large.
Data captured in a transactional database or other that summarizes a business process in the past. The visualizations built on top of this data are usually aggregated and tell the end users what happened in the past, or "describes" what occured. The majority of self service and adhoc reporting is built using descriptive statistics, which is easy for others to interpret and convey.
Examples include Bar Charts, Pie Charts, Line Charts, Box Plots and Heat Maps
Methods used to predict a future business process. Gone are the days of eye-balling a time series graph and adding a static growth percentage for the next N number of periods. Today, advanced statistical methods are used to more accurately project business processes or add value to a users experience. Methods of implementing predictive models often have a trade off between complexity and interpretability. Predictive models are not just a "set and forget", they usually carry some form of training and maintenance to stay accurate. Predictive Statistics is a subset of Machine Learning and often thought of more as an Art than a Science.
The definition of a node depends on the network and protocol layer referred to. A physical network node is an active electronic device that is attached to a network, and is capable of creating, receiving, or transmitting information over a communications channel.
Nodes can have many software servers or web services running on one physical server, either as a virtual machine or container. When referencing "edge node" or "central node" etc. people are referencing the physical server (as it resolves to a single IP address).
The seamless assembly of many software applications, scripting languages, and frameworks integrated together to satisfy a business problem. A product can be, but doesn't have to be, ambigous to an industry. For example, some products can be used in the Finance and Logistics industry, some products only service Health Care.
Behind the scenes (in most cases nowadays), the provider of the product relies on the respective individual companies of the software applications for patching bugs, security, and new features.
The capability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged to accommodate that growth.For example, a system is considered scalable if it is capable of increasing its total output under an increased load when resources (typically hardware) are added.
Performance and Scalability are often misinterpreted or used synonymously. A product is said to be scalable if when we increase the resources in a system, it results in increased performance in a manner proportional to resources added. Increasing performance in general means serving more units of work, but it can also be to handle larger units of work, such as when datasets grow.
Need it in real world terms? Performance is how fast a calculation completes with 1 user and 1 server, Scalability is the change in calculation time proportional to each additional user and/or server. If calculation times increase materially per user with 2 users, it's obviously not going to scale.
Self-service business intelligence is an approach to data analytics that enables business users to access and work with corporate data even though they do not have a background in statistical analysis, business intelligence (BI) or data mining.
This type of analytics infers that the curation of the data set (SQL, conforming dimensions & metrics, data modeling etc.) is completed by IT and handed off to the user. The end-user has access to the this curated data and can build visualizations from it, but that's it. The user doesn't have access to the transactional database or query capability, and doesn't have the freedom to dictate the business rules around the field "Loan Funded Date" for example.
Self-service analytics has really taken off the past few years with tools like Qlik Sense and Tableau, giving the power to both IT & the end-user to control the data yet enable reporting as the user sees fit.
In technology, the term "service" can be used in relation to a variety of things. On our website, given we are consultants, we reference "service" in the context of augmenting, providing guidance, or implementing a product.
An answer to a specific business problem usually containing a industry specific or functional aspect. For example, if we have a health care client looking to speed up the drug discovery process, we can implement a product and tailor the product and technical architecture specifically for the client and/or optimize it for health care research purposes. The software stack, built-in intellectual property, and hardware details comprise the overall solution.
TechBuilders services encompass the implementation of products as solutions to answer specific business needs.