Guides

Privacy and security

What is sent to Tomba

Only the values you pass to a procedure: the columns you name (domains, names, emails, URLs, phone numbers) or the filters of a company search. The rest of your table never leaves Snowflake.
Only to api.tomba.io, over HTTPS. The app's network rule allows no other destination, and it works only after you approve the Tomba API connection.
Install details, when the app activates: your Snowflake organization and account names, account locator, region, and the app's name and version.
Usage counts for billing: run id, tool, number of rows and hits, credits and amount charged. Never your data.
Request logs: as for any Tomba API key, each lookup that returns a result is recorded in Tomba's request log, with the values sent.

Result tables, in the app's results schema, readable by the roles you grant app_public.
Run history, settings, the cache and schedules, inside the app.
The app's Tomba credentials, in a private schema that no role can read. They can only call Tomba's lookup endpoints.

Tomba doesn't keep a copy of your tables.

The app reads only the tables you GRANT it, and you can revoke a grant at any time.
People use the app through its roles, app_public and app_admin (see Installation).
Background runs and schedules run as the app, on serverless tasks, using the same grants.

Last modified on September 29, 2026

Guides

Only the values you pass to a procedure: the columns you name (domains, names, emails, URLs, phone numbers) or the filters of a company search. The rest of your table never leaves Snowflake.
Only to api.tomba.io, over HTTPS. The app's network rule allows no other destination, and it works only after you approve the Tomba API connection.
Install details, when the app activates: your Snowflake organization and account names, account locator, region, and the app's name and version.
Usage counts for billing: run id, tool, number of rows and hits, credits and amount charged. Never your data.
Request logs: as for any Tomba API key, each lookup that returns a result is recorded in Tomba's request log, with the values sent.

Result tables, in the app's results schema, readable by the roles you grant app_public.
Run history, settings, the cache and schedules, inside the app.
The app's Tomba credentials, in a private schema that no role can read. They can only call Tomba's lookup endpoints.

Tomba doesn't keep a copy of your tables.

The app reads only the tables you GRANT it, and you can revoke a grant at any time.
People use the app through its roles, app_public and app_admin (see Installation).
Background runs and schedules run as the app, on serverless tasks, using the same grants.

Last modified on September 29, 2026