# Privacy Policy

_Last updated: 21 July 2026_

This Privacy Policy explains how **Lumus.gg LTDA** (CNPJ 40.325.568/0001-05)
("aliahlp", "we", "us"), operator of **alia.help**, collects, uses, and
protects personal data. It is written to be accurate to how the service
actually works, not to boilerplate.

We are the **data controller** for the personal data described here. For data
inside a database you connect, you are the controller and we act as your
**processor** (see "Data in your connected databases").

Contact for privacy matters: **privacy@alia.help**.

Registered office: Lumus.gg LTDA, Rua Francisco Rocha, 198, Batel, Curitiba –
PR, CEP 80420-130, Brazil.

## What aliahlp does

Founders connect a Postgres database (or upload a CSV) and plug their own AI
agent in over a remote MCP server to explore data, run **read-only** SQL, and
publish live hosted charts and dashboards. aliahlp never runs interactive AI on
your data itself — your agent does that. We call an external AI provider only
for one narrow background task described below.

## Data we collect

**Account data.** Your email address. Sign-in is passwordless (magic link), so
**we do not store any password**. We store API/MCP access tokens only as
irreversible **SHA-256 hashes**.

**Database connection data.** When you connect a Postgres database we store the
host, port, database name, and username, and the **password encrypted at rest**
using AES (via Cloak). We store **schema metadata** we introspect from your
database — table names, column names, data types, and constraints.

**Cached query results.** To render hosted charts without repeatedly hitting
your database, we cache the **most recent result** of each chart's query.

**CSV workspace data.** If you upload a CSV, its contents become a table stored
in a hosted per-user workspace database and are stored at rest by us.

**Billing data.** If you subscribe to Pro, payment is processed by Stripe. We
store billing metadata (plan, subscription status, customer/subscription
identifiers) but **not** your full card number.

**Operational logs.** Minimal request and error logs (e.g. IP address,
timestamp, endpoint) needed to run and secure the service.

## Data in your connected databases

When you connect your own database, aliahlp accesses it **read-only** and cannot
write to, alter, or delete anything in it (see our
[Security page](/security)). We access rows only to run the queries your agent
requests and to cache chart results as described above. You are responsible for
only connecting databases you are authorized to connect, and for what your agent
queries and publishes.

## What we send to third parties — and what we don't

To build the plain-language "semantic catalog" of your schema, we send
**schema metadata only** (table and column names, types, and constraints) to
our AI sub-processor, **Anthropic**. We do **not** send your table rows or cell
values to Anthropic for this. This processing runs only in background jobs.

A full list of sub-processors, their purpose, and their region is on our
[Sub-processors page](/sub-processors).

## How we use data

- Provide, operate, and secure the service.
- Introspect your schema and generate the AI catalog (schema metadata only).
- Run the read-only queries your agent requests and host the resulting charts.
- Process subscriptions and payments (via Stripe).
- Send transactional email such as magic-link sign-in (via Resend).
- Detect, prevent, and investigate abuse or security incidents.

**Legal bases (GDPR/UK-GDPR):** performance of our contract with you (providing
the service and billing); our legitimate interests (securing and improving the
service, preventing abuse); and your consent where required.

## Retention and deletion

- Deleting a database connection removes its stored credentials and schema
  snapshots and shuts down its connection pool
  (`Connections.delete_connection/1`).
- Deleting a chart or dashboard removes its cached query results.
- You can request deletion of your account and associated personal data by
  emailing **privacy@alia.help**; we will delete it except where we must retain
  limited records (e.g. billing) to meet legal obligations.
- Operational logs are retained for up to 30 days, after which they are
  deleted or anonymized, unless a longer period is required to investigate a
  security incident or meet a legal obligation.

## Your rights

**Under the LGPD (Brazil)**, you may request confirmation of processing, access,
correction, anonymization or deletion, portability, information about sharing,
and review of your data. **Under the GDPR/UK-GDPR (EU/UK)**, you have rights of
access, rectification, erasure, restriction, portability, and objection, and the
right to lodge a complaint with a supervisory authority. To exercise any right,
email **privacy@alia.help**.

## International transfers

We are based in Brazil and use sub-processors located in the EU and the USA (see
[Sub-processors](/sub-processors)). Where personal data is transferred
internationally, we rely on appropriate safeguards such as Standard Contractual
Clauses or the sub-processor's own transfer mechanisms.

## Security

Credentials are encrypted at rest, access tokens are stored hashed, customer SQL
is strictly read-only, and traffic is served over TLS. See our
[Security page](/security) for details. No method of transmission or storage is
perfectly secure, but we take reasonable measures to protect your data.

## Children

aliahlp is not directed to, and may not be used by, anyone under 18.

## Changes

We may update this policy. Material changes will be reflected by the "Last
updated" date above and, where appropriate, communicated to account holders.

## Contact

Lumus.gg LTDA — **privacy@alia.help**.