Skip to content

Data Security

Data security is a primary concern of our clients and Daeda Technologies.

HubSpot data is stored in a secured portal mirror. Portal mirror services are hosted in Germany, and the database provider is the German instance of Supabase.

During portal construction, large HubSpot objects are gathered through HubSpot Exports. Smaller artifacts can be fetched through the HubSpot API and stored in Supabase before being downloaded into the portal mirror.

Yes. The client connection process controls what data Daeda AI is allowed to retrieve for the mirror.

Mirror configs can also apply filters, so the mirror does not need to include every property, workflow, or record from the portal.

The Bridge adds extra HubSpot data that is not available through the standard HubSpot API or export flow. Bridge-backed plugin data is only refreshed when the Bridge is enabled for the portal and the HubSpot extension is connected.

If the Bridge is not connected, those Bridge-backed plugins are skipped rather than fetched another way.

Daeda AI exposes the portal mirror to your connected AI client through tools. Anything in the mirror can be used in an AI answer and could be sent to your AI provider’s servers by that AI client.

The important control is that Daeda AI lets you choose what enters the mirror in the first place.

Yes. The Daeda AI settings include a Delete Database button. Deletion pauses the portal, removes HubSpot export records, cleans up stored Supabase artifacts, and deletes the local portal mirror files.

Where are Daeda AI services provided from?

Section titled “Where are Daeda AI services provided from?”

Daeda AI services are provided from Germany. We use Supabase’s German instance as our database provider, and our servers are hosted in Germany through Hetzner.

What is Daeda AI’s data security strategy?

Section titled “What is Daeda AI’s data security strategy?”

Daeda AI focuses on three areas of data security:

  1. Reducing the amount of data stored on our servers.
  2. Securing portal mirror data technically.
  3. Making it easy to purge data when it is no longer needed.

We only want to store the data required for Daeda AI to work effectively.

The bulk of portal data is gathered through HubSpot Exports, which stream directly from HubSpot into the secured portal mirror. During the client connection process, you can choose which data Daeda AI is allowed to store in that mirror.

We take technical security seriously.

  • Portal mirror data is encrypted at rest using an HKDF-SHA256 derived key.
  • Communications are protected through TLS.
  • Data is only handled by the services required to run Daeda AI: HubSpot, Supabase, and Hetzner.

Daeda AI includes a Delete Database button in settings. This deletes the portal mirror and associated artifacts from our servers.

If you need to use the portal again, it can be rebuilt. Depending on portal size, that can take from a few minutes to a couple of hours.

We also automatically purge old artifacts and data, and we are planning additional purging for portal mirrors that appear to be unused.