This page is the technical boundary for a buyer who needs to judge deployment risk. It states what is already published. It does not add a new data right.
What stays in your account
Table contents stay where they are. Anavsan does not read, copy, or transmit the rows in your Snowflake tables or BigQuery datasets. Customer records, proprietary datasets, and financial records are not the input.
Snowflake stays in Snowflake. BigQuery stays in BigQuery.
What operational metadata includes
Hosted APEX reads operational metadata through a read-only service user you configure. For Snowflake, the privacy policy lists that metadata as:
- Query history, including SQL query text, execution time, warehouse, user, and credits consumed
- Warehouse usage and configuration
- Storage metadata: table sizes, Time Travel settings, clone metadata
- Account usage and cost signals from
SNOWFLAKE.ACCOUNT_USAGE - AI Services and Cortex usage metadata
SQL text is included. It is query text from history, not the contents of the tables that query touched.
Access is read-only on SNOWFLAKE.ACCOUNT_USAGE and INFORMATION_SCHEMA. There is no write access to Snowflake objects, and no access to business-data tables, views, or procedures.
On BigQuery, APEX reads the same class of operational metadata: jobs, slots, reservations, and scans, including INFORMATION_SCHEMA-class signals. It does not read your datasets. The privacy policy's itemized metadata list is written for Snowflake. This page does not invent a second list.
Where hosted metadata goes
On hosted APEX, Snowflake metadata processed for the service is stored in Anavsan infrastructure. The privacy policy states that. It is encrypted in transit (TLS 1.2+) and at rest (AES-256).
That metadata is not sold, and it is not used for advertising. The Native App is a different deployment: processing stays inside the Snowflake account, and that metadata is not sent out. See the comparison below.
Retention
The privacy policy states:
- Snowflake metadata: retained for up to 13 months, for trend analysis and historical comparison
- Account data: kept for the life of the account, plus 30 days after closure
- Usage logs: 90 days, for security and debugging
You can request deletion at contactus@anavsan.com. The policy says deletion is within 30 days, except where the law requires longer.
The 13-month clause names Snowflake metadata. It does not, in that section, state a separate BigQuery retention number. Do not read this page as creating one.
Hosted APEX and the Native App
| Hosted APEX | Snowflake Native App | |
|---|---|---|
| Where it runs | Anavsan's service, connected to your account | Inside the Snowflake account |
| What leaves the account | Operational metadata, including SQL text, stored for the service | Nothing. Processing stays in Snowflake. |
| Table contents | Not read | Not read |
| What it does | Recommends an action. Your team approves and deploys production changes. | Monitors credits and usage. Advisory. It does not rewrite queries or change warehouses. |
They are two products. You do not have to install the Native App to use hosted APEX, and you do not have to send metadata to Anavsan to use the Native App. The longer choice is on Native App vs full platform.
Permissions
- You create the Snowflake service user. Anavsan does not take a password to your tables.
- That user is read-only on metadata schemas.
- APEX does not grant itself rights to apply a warehouse, reservation, or query change.
- A production change leaves as a recommendation — and, on the full platform, can leave as a pull request in your repository. Your approvals and your deployment still apply. Anavsan does not reach into production and change a setting because it preferred that path.
Nothing sits in the production query path
APEX reads a workload after it has run. Before you deploy a recommended change, a simulation can estimate runtime and cost. That simulation is change-safety. It is not a gate in front of Snowflake or BigQuery.
There is no agent in the query path. Redirect recommends a different warehouse or reservation. It does not route the workload. Run means no change. Review means a person decides.
Readable without an account
You do not need an Anavsan login to read this page, the privacy policy, or the product documentation at docs.anavsan.com. The docs homepage is public.
Questions about a specific connection or a contract term: contactus@anavsan.com.