How Data360 handles your data

Data360 reads your data where it lives, keeps only what your reports need, and writes only what you ask for.

Where your data goes

Where Data360 runs, and what it keeps.

What Data360 keeps: Your reports need their totals and up to 5,000 rows of each table they use. What you ask for: your model, the files and databases you bring in, and the tables you choose to save.
Where it runs: Data360 runs on Vercel. Its server functions run in Frankfurt, Germany.
Where it is stored: Your account, your settings and what Data360 keeps for your reports are stored in a PostgreSQL database run by Neon, in Frankfurt, Germany.
Your tables: If you connect Snowflake, your tables stay in your Snowflake account and are read there. Files you bring and tables you copy from PostgreSQL or MySQL go to the same place: your Snowflake account if you connected one, otherwise a separate space Data360 runs for your organisation, on Snowflake.
Emails: No email is sent yet: alerts and messages show in the app. When email is switched on, it will go through Resend.

What happens to the details you give Data360 to reach your data.

Snowflake: Encrypted before they are saved. Only Data360’s server can open them, at the moment it connects.
PostgreSQL and MySQL: Your password is used once, to copy the tables you pick, then forgotten. It is never saved.
Amazon S3: You grant access from your own Amazon account. No password or key is handed to Data360.
Your Data360 password: Stored only in a form that cannot be turned back into your password.

Which AI Data360 uses, and exactly what it sees.

Which AI: Kimi, from Moonshot AI. Data360’s server calls it; your browser never does.
What it receives: Never your tables. Depending on what you ask: the names of your columns with a short summary of each — its type, how full it is, how many different values it holds, its smallest and largest value or its dates; the figures and findings Data360 has already worked out, such as totals by store; and the question you typed.
What it never receives: Passwords and keys. Anything that looks like one is masked before a request leaves, and a request that still contains one is not sent.
What it costs: Signed in, each use is counted in credits, shown on the button before you run it.

A role for each person in your organisation, and another for each application.

Can view: Opens it and reads its reports.
Can run: Also runs, tests and re-checks things — without changing how they are set up.
Can edit: Also changes its data, model, reports and workflows.
Can approve: Also turns workflows on and accepts known problems.
Can manage: Also decides who gets in, and with what.

Every invitation, role change and removal is kept in a history the owner and admins can read.