Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

For further information, contact Typesnse team or refer to Data Processing Agreement.

Access

...

control for Typesense

...

cloud data

Access to the data stored in your Typesense Cloud cluster is managed securely through API keys. These keys can be generated via the Typesense Cloud dashboard or the API, providing you with full control over data access.

...

  • Safeguard API keys: Store API keys securely and restrict access to authorized personnel only.

  • API key management: We use a single API key, securely stored as a variable in Google Cloud Build, exclusively accessible within our backend environment. This approach ensures the key is safeguarded and not exposed in the frontend. For development purposes, we use a local Typesense setup without customer data, eliminating the need for the API key except in production environments.

  • Set permissions: Assign appropriate permissions to each API key. For example, keys used in frontend applications should have search-only permissions.

Other data we store

Our apps are hosted by Google and utilize Firebase.

Info

Firebase is a development platform from Google that provides tools for tracking analytics, reporting and fixing app crashes, creating marketing and product experimentations, and more. It supports the development of both mobile and web applications, offering services like real-time databases, cloud storage, authentication, and hosting. This integrated platform is designed to streamline the process of app development, making it easier for developers to build high-quality applications efficiently.

This is what we store in Firebase:

  • Navigation

    • Navigation settings and design (Colors)

    • Entries structure

    • User permissions are not identifiable, we are storing only account Ids

  • Dashboard

    • Widget settings and order

  • Newsroom, Space Station and People Network

    • Layout settings (colours, border radius, gaps etc.)

  • Employee Database

    • Background image settings

    • No personal data, only IDs for users

    • Each field in Cosmos has its own ID, which is used to store details about the field, such as its name, type, and its position in the database and user profile.

    • Field values (non identifiable, only if Entra ID is not used), this serves as backup to TypeSense

  • Collections

    • Collection filters

    • Background colour

  • General

    • Header settings used in Space station, People network, Newsroom (image data, title and description)

    • Widget settings -> Database field id used for fetching data in widgets

    • Colors for corporate identity

Tip

We do not store any personally identifiable information (PII). All data stored in Firebase is non-identifiable and necessary for the normal operation of the app and to provide additional features.