Privacy Policy

By default, metadata only: the names of databases, schemas, tables, views and columns; their sizes, row counts and freshness; what depends on what; query history; warehouse credits and the rate you pay for them; roles, grants and who holds them. This is Snowflake's own ACCOUNT_USAGE catalogue — a description of your estate, not its contents.

It does not read the rows in your tables. There is one exception and it is explicit: an account owner can switch on data access in Settings, which the AI and ML modules need in order to look at values rather than shapes. It is off for every account until somebody turns it on, it is recorded when they do, and it can be turned off again.

The catalogue and lineage it builds, the findings it raises, the changes it proposes, the conversations you have with it, your support threads, and an audit log of who did what. Account and user records: your name, email address and a scrypt hash of your password — never the password.

Credentials you give Gecko for Snowflake, your git host and your model provider are encrypted at rest with AES-256-GCM under a key held outside the database. They are decrypted only to make the connection they are for.

The model provider you choose. Gecko sends the model the context a question needs — object names, schemas, SQL, findings. Which company that is, is your choice: your own Anthropic, OpenAI, Azure or Google key, a model we run for you, or an open-source model inside your own network, in which case nothing leaves it.

Our hosting. Gecko runs on Amazon Web Services in the United States. Backups sit there too.

The Gecko team. Support and engineering can open your account to help. It is read-only for most of the team, it expires after an hour, and it is written into your own audit log where you can see it — every time, without exception.

We do not sell anything to anybody, and there is no advertising network in the product or on this site.

For as long as your account is open. Close it and the estate we catalogued, the findings and the conversations go with it; the audit log and billing records are kept longer because they are what answers a later question about what happened.

Two things are trimmed before that, because keeping them longer helps nobody: the history of individual scans is kept for 90 days (the most recent one for each account is always kept, so the page can say when it last looked), and the record of column changes for a year, which is the longest period anything in the product can ask about.

Needs your lawyer. The exact retention periods for the other categories, and the lawful basis for each, are a decision rather than a fact about the code. They need setting before this page is published.

You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to go@gecko.com.

Needs your lawyer. Which regimes apply — UK GDPR, EU GDPR, CCPA — depends on where the company is established and where customers are, and each brings its own required wording, response deadlines and a named contact. Not something to infer.

Four, all first-party, none for advertising or analytics. They are listed individually in the Cookies Notice.