---
title: "Security"
description: "How Solacia handles security today: how to report a problem, where data runs, and what we don't have yet."
canonical: https://www.solacia.ai/security
last_updated: 2026-10-30
---

# Security, stated plainly.

Solacia is a small company. This page says what we do today and what we don't have yet. Report a problem to hello@solacia.ai.

## Report a problem

Email [hello@solacia.ai](mailto:hello@solacia.ai?subject=Security) and we answer every report, in English or
Spanish. The same contact is in [security.txt](https://www.solacia.ai/.well-known/security.txt).

## Where data runs

- **Website and API:** our hosting provider. Every page and API call uses HTTPS.
- **Demo calls:** call infrastructure, speech recognition (no model training), voice and AI model providers.
- **Database:** a hosted Postgres provider.
- **Company lookup:** company data providers. We keep only the company they name, never the address.

Write to [hello@solacia.ai](mailto:hello@solacia.ai) for the list of providers.

What a demo keeps, and how to see or delete it, is in the [privacy notice](https://www.solacia.ai/privacy).

## Your tools

HubSpot and Slack connect through their own sign-in: you approve access on their screens, so there
are no keys to send us. API keys are made in your console, shown once and kept only as a
hash: see [keys](https://app.solacia.ai/docs#keys) in the API reference.

## What we don't have yet

- **No SOC 2 report.** Ask us where we are; we will tell you plainly.
- **No public penetration test.**
