Mindset AI Documentation
  • General
    • Welcome
    • AI and Security
      • AI Guidelines
      • Security Q&A
      • AI Buyers Guide
  • Platform
    • Overview
    • Features
      • Welcome workflow
        • How to configure the Welcome workflow
        • Welcome workflow best practices
      • Onboarding workflow
        • How to configure the Onboarding workflow
        • Onboarding best practices
        • How to configure Single Sign-On (SSO)
        • How to Configure Multi Factor Authentication (MFA)
      • Knowledge workflow
        • Content Discovery
          • How to configure Content Discovery
          • Setting up the Content Discovery carousels
          • ‘Trending’ carousel calculations
        • Knowledge Banks
          • How to configure a Content Knowledge Bank
          • Learn about Synced Knowledge Banks
          • How to create Speakers
          • How to exclude Content from being visible
          • How to process PDF files
          • How to process SCORM files
          • Knowledge Bank best practices
          • Prompts
            • How to configure Prompts
            • Prompts best practices
        • Events
          • How to configure External Events
          • How to Configure Live Streaming Events
        • Knowledge workflow FAQs
      • Agents
        • How to configure the Agent workflow
          • How to add an Agent Disclaimer message
        • How to create Agents
          • Settings
          • Personality
          • Policy
          • Capabilities
            • Capabilities best practices
          • Tools
          • LLM (Beta)
          • Design
          • Knowledge
          • Bias
          • Testing
          • Preview
          • Access
        • Language Translation within Agents
    • Design
      • Navigation
      • Branding
      • Thumbnail Design
      • Images
        • SVG Images
        • Selecting the Right Image for your Application
    • Accounts
      • How to configure Accounts
      • How to configure Account branding
      • How to invite end-users to an Account
    • Humans
  • Developers
    • Embed SDK
      • Embed an AI agent: step by step guide
      • How to embed an agent in your site
      • Testing your Embedded Agent
      • Authentication
    • Mindset API
      • Mindset Public APIs
      • HTTP API
        • API Key authentication
        • API Servers
        • api-authenticate-embedded-user
      • REST API
        • Contexts API
        • Context Files API
        • Labels API
  • Analytics
    • Overview
    • ThoughtSpot
      • ThoughtSpot FAQs
        • Adding a logo or image to a liveboard
        • There is data missing from liveboard
        • Exporting raw data
        • Exporting data to a csv file
        • How to add a note to a liveboard
        • How to pin in a liveboard
        • Editing individual data visualizations in a liveboard
        • Thoughtspot Alerts
    • Connecting a BI tool
  • Integrations
    • Overview
      • Choosing Data for your Agent
      • Supported Files
    • Content management
      • Google Drive
        • Google Drive Integration Set-Up
      • SharePoint
        • SharePoint Integration Set-Up
      • Hubspot
      • Podbean
      • Wistia
      • WordPress
      • Dropbox
    • Communication
      • Microsoft Teams
      • Slack
    • Customer Management and Payment
      • Hubspot
      • Stripe
  • Support
    • Contacting support
    • Taking a screenshot on any laptop
    • Resizing & compressing images
    • Performing a hard refresh
    • Application loading time
    • Raise a support ticket
    • Service Level Agreement (SLA)
  • Mindset AI Website
  • Book a Demo
Powered by GitBook
On this page
  • Mindset Data Security Overview
  • Certifications
  • FAQs
  • Authentication
  • Which data center is the data stored in?
  • How is authentication managed?
  • How is the Firebase database secured?
  • Is penetration testing necessary in a serverless architecture?
  • What personally identifiable data is stored in the Firebase database?
  • Is data encrypted in transfer and at rest?
  • How long is the data held, and what is the retention strategy?
  • What would the impact be to individuals or the company if an unintended audience accessed the data?
  • Is static code analysis used?
  • How is the source code deployed and compiled?
  • To what extent are development and testing environments separated from operational environments?
  • To what extent are IT systems protected against malware?
  • To what extent is information security ensured among contractors and cooperation partners?
  • Do Mindset staff have the ability to access my account data?
  • Do you have a formal incident management procedure? What happens if there is a client data breach?

Was this helpful?

  1. General
  2. AI and Security

Security Q&A

The purpose of this page is to provide answers to frequently asked security questions.

PreviousAI GuidelinesNextAI Buyers Guide

Last updated 10 months ago

Was this helpful?

Mindset Data Security Overview

The Mindset platform is a modern, serverless architecture hosted by the Firebase PaaS on the Google Cloud Platform (GCP). All client-server communication is via Firebase, and Firebase Authentication handles authentication on GCP. Furthermore, Firebase authentication tokens are used for database segmentation and database security.

All client instances running in a browser (as compiled, minimized JavaScript) or as native IOS and Android applications are written in Dart on the Flutter framework.

The advantage of this approach is that all security responsibility is held by Google, which is recognized as the industry leader in cloud platform security and compliance. All data is secured in transit and at rest by Google.

Certifications

Additionally, Mindset AI is in the process of obtaining its own ISO 27001 certification.

The Mindset AI founders come from a regulated industry background, with over 100 years of combined experience in the legal, government, and financial sectors. We rely on the certifications provided by the platform on which we run the application (GCP), and our commitment to a serverless architecture provides the highest level of security available, managed by Google.

FAQs

Authentication

All authentication (and storage of authentication tokens and user’s personally identifiable information) is also handled by Google. Furthermore, the authentication tokens are used in the database security rules; thus, the databases are secured at the user level. This results in the highest data security achievable in modern cloud computing environments.

Which data center is the data stored in?

By default, data is stored in Google’s Europe-west2 data center in London, UK. Individual customers may request data centers in other countries. Google has comprehensive geographic coverage.

How is authentication managed?

Google handles all authentication through Firebase Authentication. The Mindset platform uses the unique user UID as the database token, which links a user’s data to an authentication session.

How is the Firebase database secured?

Firebase Security Rules secure the data in Firebase: These rules ensure that only the authenticated user can read from/write to data elements owned by the authenticated user. The implication is that you need to be authenticated as a specific user to see that user’s data, which means that if a user’s login credentials are leaked, only that user’s data is at risk.

Is penetration testing necessary in a serverless architecture?

No, all security is inherited from the GCP/Firebase platform, and the device's operating system handles the application (mobile instance). With authentication handled by Google, authentication governs database access and serverless architecture. Any penetration testing would be on the Firebase PaaS platform, which Google conducts regularly.

What personally identifiable data is stored in the Firebase database?

We store the users’ email addresses and the names they give themselves. All other data is metadata about their selections in the application. These are stored as GUIDs (large random numbers).

Is data encrypted in transfer and at rest?

All data is encrypted in transfer (HTTPS) and at rest using 2048-bit RSA encryption. Google handles all encryption. Messages sent through the app are end-to-end encrypted.

How long is the data held, and what is the retention strategy?

To provide a bespoke user experience, a user’s data is held on the platform for as long as the user is a user. When a user leaves the platform, all personally identifiable information of that user is deleted. Anonymized usage data is kept for all users for up to 24 months after they have left the platform.

What would the impact be to individuals or the company if an unintended audience accessed the data?

By design, the platform stores minimal personal information per user: Most of the stored data pertains to the user’s behavior while in the application. There is minimal risk to the individual or company if this data is accessed by a bad actor other than the leakage of email addresses.

Uploaded files and videos are stored in encrypted buckets, secured by authentication tokens and encrypted at rest. All pointers to these locations are stored in the Firebase database and secured by authentication tokens and Firebase security rules. Revoking a user’s access revokes all access to all data held.

Is static code analysis used?

Yes, all code is analyzed, and any deviations are marked as compiler warnings. We use Dart’s static code analysis and follow Flutter’s development guidelines.

How is the source code deployed and compiled?

All compilation and deployment to the app stores are handled through integration scripts running on Github as Github actions. We follow an infrastructure-as-code methodology.

To what extent are development and testing environments separated from operational environments?

Development, Testing and Production (operational) environments are separate instances with full systems, branches, code versions, users, and data separation.

To what extent are IT systems protected against malware?

We operate a fully remote infrastructure, with all IT systems hosted in Google or with system suppliers. We only operate using market-leading suppliers, offering full enterprise-level encryption and protection.

To what extent is information security ensured among contractors and cooperation partners?

All partner and contractor organizations operate under a full NDA, with contractual obligations specified and monitored. All proprietary and business information is stored on our IT systems, with access provided based on role requirements and full ability to revoke access at a user and organizational level.

Do Mindset staff have the ability to access my account data?

Limited staff within Mindset can access account information for support and maintenance on an as-required basis. Permissions are managed and monitored closely, requiring authorization from multiple sources.

Do you have a formal incident management procedure? What happens if there is a client data breach?

As part of obtaining an ISO 27001 certification, we follow and abide by the standards and guidelines outlined within this certification. We maintain Incident procedure documents and a risk register that are reviewed regularly. Upon becoming aware of an incident or breach, we notify our clients within 24 hours and keep live notifications running until the incident is resolved.

is a recognized industry leader in cloud security, holding ISO/IEC 27001, 27017, 27018, 27701, SOC 1/2/3, PCI DSS, FedRAMP certifications, alignment with HIPAA, GDPR, CCPA, and many other industry certifications.

GCP