Skip to content
DatagistDatagistDatagistDatagist
  • Services
  • Practices
  • Industries
  • Insights
Datagist

Recent

    Your chats show here. They stay in this browser only.

    Ask Dex, Datagist's AI assistant

    Hi, I'm Dex.

    Ask me about Datagist's services, practices, accelerators or how we work. I answer from datagist.ai and link to the pages I used.

    Pages on datagist.ai

      See all results

      Want a copy of this chat, or to talk it through with someone on our team?

      About Dex and your privacy

      • Dex is an AI assistant. It answers only from datagist.ai pages and can make mistakes, so check the linked sources.
      • Please do not enter personal or confidential information.
      • We do not store your questions. Your recent chats are kept in this browser only, and you can clear them from the chat list.
      • If you ask us to email you a chat or set up a call, we keep that chat with your details. See our Privacy Policy.

      Answers are generated by AI from datagist.ai pages.

      Email me this chat.

      We will send you everything you asked and Dex's answers, with links to the pages it used.

      We use your details and this chat to send you the copy and to reply to you. No mailing list. See our Privacy Policy.

      Sent.

      Your chat is on its way to . If it isn't there in a few minutes, check your spam folder.

      We will also email you within two business days to find a time for the call.

      Datagist

      Start with the problem. Each page shows how we would begin.

      Plan

      • StrategyPick the data and AI work worth paying for.

      Build

      • Modern DataGet your core data in one place, and agree what it means.
      • AnalyticsOne number for each metric, in every report.
      • AI & MLModels that keep working after launch.
      • GenAI & AgentsAssistants and agents that answer from your data and stay in bounds.

      Run

      • Governance & OperationsShow anyone who asks how your data and AI are controlled.
      Accelerators →All services →Which problems we solve →Check your AI readiness →

      Hands-on help with the platform you already use.

      • Anaplan logoAnaplan
      • Databricks logoDatabricks
      • Informatica logoInformatica
      • Reltio logoReltio
      • Salesforce logoSalesforce
      • Snowflake logoSnowflake
      All practices →

      Every industry has its own records and its own rules.

      • Banking & Financial Services
      • Energy & Utilities
      • Healthcare
      • Hi-Tech
      • Insurance
      • Life Sciences
      • Retail
      • Travel & Hospitality
      All industries →
      • AboutWho we are and how we work with clients.
      • Our approachThe GIST framework, from first workshop to run.
      • Careers ↗Open roles at Datagist. (opens in a new tab)
      Insights
      Contact

      Follow us

      • Datagist on LinkedIn (opens in a new tab)
      • Datagist on X (opens in a new tab)
      • Datagist on Facebook (opens in a new tab)
      • Datagist on Instagram (opens in a new tab)
      • Datagist on YouTube (opens in a new tab)
      • Datagist on GitHub (opens in a new tab)
      Start a conversation →
      Trust

      Security: How We Protect Client Data

      Last updated October 1, 2026

      On this page

      1. Overview
      2. How we handle client data
      3. Salesforce and platform delivery
      4. Access control
      5. Use of AI tools
      6. Our people
      7. Infrastructure and vendors
      8. Subcontractors
      9. Incident response
      10. Security reviews and documentation
      11. Reporting a security issue

      Our clients give us access to their customer records, their Salesforce orgs, and their data platforms. This page describes the standards we follow to protect that access and that data.

      Overview

      Security is part of how we deliver every engagement. We work inside our clients' environments whenever we can, give each person and system only the access the work needs, and remove that access when the work ends. The contract for each engagement sets out the specific security, confidentiality, and data protection terms that apply, and those terms take precedence over this page.

      How we handle client data

      • We process client data only on the client's instructions and only for the purposes of the engagement.
      • We work in client-provided environments, accounts, and tools wherever possible, so client data stays under the client's own controls.
      • We do not copy client data to personal devices, personal accounts, or tools the client has not approved.
      • We use the minimum data needed for each task, and use masked, sampled, or synthetic data for development and testing where possible.
      • At the end of an engagement, we return or delete client data as the contract requires.

      Salesforce and platform delivery

      • We build and test in sandboxes and promote changes to production through a controlled release process agreed with the client.
      • We do not load unmasked production data into lower environments without the client's approval.
      • Each team member uses a named account. We do not share logins.
      • Integration users and connected apps get the narrowest permissions that work, and their credentials are stored in the client's approved secret store.
      • Before go-live, we review profiles, permission sets, sharing rules, and field-level security with the client.
      • The same practices apply to data platforms, warehouses, and integration tools we work on.

      Access control

      • Datagist staff sign in to company systems through Microsoft 365 single sign-on with multi-factor authentication.
      • Our internal applications are protected by Cloudflare Access and are available only to authorized staff.
      • Access to client systems is requested per engagement, limited to the people working on it, and removed when they roll off.
      • We remove all access promptly when someone leaves Datagist.

      Use of AI tools

      • We do not enter client data into public AI tools. AI tools are used with client data only when the client has approved the tool and its data terms.
      • AI assistants and agents we build for clients use the client's existing access rules, so users see only what they are already permitted to see.
      • Each agent is limited to the data and actions it needs, and its activity is logged.
      • We test AI systems for quality and safety before launch and after changes.

      Our people

      • Everyone who works on client engagements signs a confidentiality agreement before they start.
      • Staff receive security and data protection training when they join and periodically after that.

      Infrastructure and vendors

      We run our business on established providers that maintain their own independent security certifications, including Microsoft 365 for email, documents, and identity, and Cloudflare for our website, internal applications, and storage. Data is encrypted in transit, and storage that holds documents or personal information is private and not exposed to the internet. We review the security and data terms of the tools we adopt.

      Our Privacy Policy lists the service providers that handle personal information from this website.

      Subcontractors

      When we use subcontractors on an engagement, they are bound by written agreements with confidentiality and security obligations at least as protective as ours, and they follow the client data practices on this page. We tell clients when subcontractors will have access to their systems or data.

      Incident response

      If we become aware of a security incident affecting client data or systems, we act to contain it, investigate it, and notify the affected client without undue delay and within the time set by our contract. We work with the client on remediation and share what we learn.

      Security reviews and documentation

      We complete client security questionnaires and vendor due diligence reviews as part of onboarding, and can share further detail on these practices under a non-disclosure agreement. Contact us to request it.

      Reporting a security issue

      If you believe you have found a security vulnerability in our website or applications, or have a concern about how we handle data, email hellodatagist.ai with the subject line "Security." Please give us a reasonable time to investigate and fix the issue before disclosing it publicly.

      Datagist LLC, Attn: Security
      11720 Amber Park Drive, Suite 160
      Alpharetta, GA 30009, United States
      hellodatagist.ai · (888)-2680

      Services

      StrategyModern DataAnalyticsAI & MLGenAI & AgentsGovernance & Operations

      Practices

      AnaplanDatabricksInformaticaReltioSalesforceSnowflake

      Industries

      Banking & Financial ServicesEnergy & UtilitiesHealthcareHi-TechInsuranceLife SciencesRetailTravel & Hospitality

      Company

      AcceleratorsApproachInsightsAboutCareers (opens in a new tab)Check your AI readiness →

      Get in touch

      11720 Amber Park Drive
      Suite 160
      Alpharetta, GA 30009
      United States
      (888)-2680hellodatagist.ai
      Datagist on LinkedIn (opens in a new tab)Datagist on X (opens in a new tab)Datagist on Facebook (opens in a new tab)Datagist on Instagram (opens in a new tab)Datagist on YouTube (opens in a new tab)Datagist on GitHub (opens in a new tab)
      Contact us →

      Your data, in context.

      Alpharetta Noida


      © 2026 Datagist LLC. All rights reserved. Various trademarks held by their respective owners.
      • Privacy Policy
      • Terms of Use
      • Cookie Policy
      • Accessibility
      • Security
      • Anti-Bribery Policy

      By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. We also count page views with Cloudflare Web Analytics, which uses no cookies and stores nothing on your device. Cookie PolicyYour browser sent a Global Privacy Control signal. Marketing cookies stay off whichever option you choose.

      DatagistDatagist

      Privacy Preference Center

      Privacy Preference Center

      Your Privacy

      Your browser sent a Global Privacy Control signal. We honor it, so marketing cookies stay off.

      When you visit a website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences, or your device and is mostly used to make the site work as you expect it to. It does not usually directly identify you, but it can give you a more personalized experience.

      Because we respect your right to privacy, you can choose not to allow some types of cookies. Select the category headings to learn more and change the defaults. Analytics and marketing cookies stay off until you allow them. Blocking some types of cookies may affect your experience of the site.

      We also use Cloudflare Web Analytics to count page views and measure how fast pages load. It sets no cookies, stores nothing on your device, and does not identify or follow you, so it runs whatever you choose here.

      Your choice is saved for six months. You can change it at any time from the Cookie settings link in the footer of every page.

      Privacy PolicyCookie Policy

      Analytics Cookies

      These cookies let us count visits and see how visitors move around the site so we can measure and improve it. Microsoft Clarity also records how pages are used (clicks, scrolling, and mouse movement), with text you type into forms hidden. If you do not allow them, Google Analytics and Clarity will not record your visit.

      Cookies in this category

      • _ga, _ga_*Up to 2 years

        Google Analytics · Distinguishes visitors and sessions.

      • _clck, _clskUp to 1 year

        Microsoft Clarity · Distinguishes visitors and links page views into one session.

      • CLID, MUIDUp to 1 year

        Microsoft · Recognizes the browser across sites that use Clarity.

      Marketing Cookies

      Leadfeeder uses these to show us which companies visit the site. If you do not allow them, Leadfeeder is not loaded and your visits are not linked to your company.

      Your browser sent a Global Privacy Control signal, so this category is kept off.

      Cookies in this category

      • _lfa2 years

        Leadfeeder · Recognizes a returning browser so visits can be linked to the visiting company.

      Strictly Necessary Cookies

      Always Active

      These cookies are necessary for the website to function and cannot be switched off. They are set in response to actions you take, such as choosing your cookie preferences or passing a security check. You can set your browser to block them, but parts of the site will not work.

      Cookies in this category

      • dg_consent6 months

        Datagist · Stores your cookie preferences.

      • __cf_bm, cf_clearanceUp to 1 year

        Cloudflare · Bot detection and security challenges.