Cost Advisor — Privacy Policy

The Cost Advisor is designed with a privacy-first architecture. The Application:

• Runs entirely within your Snowflake account
• Performs only read-only queries against Snowflake system views
• Does not transmit your data outside of your Snowflake account
• Does not make any outbound network calls
• Does not collect personally identifiable information (PII)

2.1 Snowflake System Views

When granted the IMPORTED PRIVILEGES ON DATABASE SNOWFLAKE privilege, the Application reads from the following Snowflake system views:

• ACCOUNT_USAGE.ACCESS_HISTORY — Which objects queries touched, used to find unused tables
• ACCOUNT_USAGE.AUTOMATIC_CLUSTERING_HISTORY — Clustering activity
• ACCOUNT_USAGE.CORTEX_AGENT_USAGE_HISTORY — Cortex Agent tokens and credits
• ACCOUNT_USAGE.CORTEX_AI_FUNCTIONS_USAGE_HISTORY — Cortex AI function calls: model, function, tokens, credits
• ACCOUNT_USAGE.CORTEX_ANALYST_USAGE_HISTORY — Cortex Analyst request counts and credits
• ACCOUNT_USAGE.CORTEX_FINE_TUNING_USAGE_HISTORY — Fine-tuning tokens and credits
• ACCOUNT_USAGE.CORTEX_PROVISIONED_THROUGHPUT_USAGE_HISTORY — Provisioned throughput commitments and credits
• ACCOUNT_USAGE.CORTEX_REST_API_USAGE_HISTORY — REST-invoked Cortex tokens and the region inference ran in
• ACCOUNT_USAGE.CORTEX_SEARCH_DAILY_USAGE_HISTORY — Cortex Search serving credits and tokens
• ACCOUNT_USAGE.METERING_DAILY_HISTORY — Daily aggregated metering
• ACCOUNT_USAGE.METERING_HISTORY — Serverless and cloud-services metering
• ACCOUNT_USAGE.PIPE_USAGE_HISTORY — Snowpipe credits, bytes and file counts per pipe
• ACCOUNT_USAGE.QUERY_HISTORY — Query execution details
• ACCOUNT_USAGE.STAGE_STORAGE_USAGE_HISTORY — Stage storage volume
• ACCOUNT_USAGE.STORAGE_USAGE — Table and database storage
• ACCOUNT_USAGE.TABLES — Table metadata
• ACCOUNT_USAGE.TABLE_STORAGE_METRICS — Per-table storage and retention bytes
• ACCOUNT_USAGE.TAG_REFERENCES — Tag assignments
• ACCOUNT_USAGE.USERS — User metadata (usernames only)
• ACCOUNT_USAGE.WAREHOUSE_LOAD_HISTORY — Query queue and load metrics
• ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY — Warehouse credit consumption
• ORGANIZATION_USAGE.RATE_SHEET_DAILY — Account pricing rates (optional)

The seven CORTEX_* views report what each AI call cost: model name, function name, token counts, credits, and the query and warehouse it ran on. They do not expose prompt or completion text, and the Application reads no column that would.

These views contain operational metadata about your Snowflake account. The Application does not access any of your business data, application tables, or user-created databases.

2.2 Session Information

The Application reads the current user's username via CURRENT_USER() to display a personalized greeting. No additional privilege is requested for this.

3.1 Internal Application Tables

The Application creates the following tables within its own application database to support its functionality:

• core.config — Pricing configuration (credit price, storage price, egress price)
• core.analysis_cache — Query result caching (cached aggregated metrics, no raw data)
• core.cost_tracking — Historical cost data (aggregated cost totals by service and entity)
• core.recommendations — Optimization results (generated recommendations with savings estimates)
• core.analysis_log — Audit log (timestamps and status of analysis runs)

These tables are stored within the Application's own database in your Snowflake account. They are automatically deleted when you uninstall the Application.

3.2 No External Storage

The Application does not store any data outside of your Snowflake account. There is no external database, cloud storage, or third-party service that receives your data.

4.1 No Outbound Network Access

The Application makes no outbound network calls. It does not connect to any external APIs, webhooks, or services. All processing occurs within your Snowflake environment.

This remains true when you enable the optional daily email digest (see 4.3). The Application renders the digest inside your account and hands it to Snowflake; it never opens a connection itself.

4.2 No Data Exfiltration

The Application does not:

• Export data to external stages
• Execute COPY INTO commands to external locations
• Share data with other Snowflake accounts
• Send data to the Provider or any third party

4.3 Email Alerts, If You Enable Them

The daily digest is off unless you turn it on, and turning it on requires you to create a Snowflake notification integration and grant the Application permission to use it. Until you do, no email is ever sent.

When enabled, a digest naming your warehouses and describing detected anomalies is delivered to the recipients you configure. That content does leave your Snowflake account, and we would rather state it plainly than let 4.1 imply otherwise. Two constraints bound it, and Snowflake enforces both:

• Snowflake performs the delivery, not the Application. The Application never transmits the message.
• Recipients must be verified email addresses of users in your own account. Snowflake rejects anything else, including shared aliases that are not Snowflake users. A digest cannot reach anyone without a login on the account whose data it describes, and it cannot reach us.

You can stop it at any time from the Application's console, which suspends the scheduled task.

4.4 Telemetry

As required by the Snowflake Native App framework, the Application shares the following telemetry with Snowflake:

• ERRORS_AND_WARNINGS (Mandatory) — Application-level error messages and warning logs generated during execution

This telemetry is managed by Snowflake's built-in event sharing infrastructure. It does not contain your account data, query results, cost figures, or personally identifiable information. The Provider receives this telemetry only in aggregated, anonymized form through Snowflake's provider analytics.

5.1 Application Data

Cached query results and configuration data persist in the Application's internal tables for as long as the Application is installed. You can clear cached data at any time using the "Refresh All Data" function in the Settings page.

5.2 Upon Uninstallation

When you uninstall the Application (DROP APPLICATION TABBY_COST_OPTIMIZER), all internal tables and stored data are permanently deleted. No data is retained by the Provider.

5.3 Provider Data Retention

The Provider does not retain any consumer data. We have no access to your Snowflake account data, query results, or configuration beyond what Snowflake provides through anonymized provider analytics.

6.1 Read-Only Design

The Application is architecturally restricted to read-only operations. It requests only SELECT privileges on Snowflake system views and cannot modify, delete, or create objects in your account.

6.2 No Authentication Credentials

The Application does not request, collect, or store any authentication credentials (passwords, API keys, tokens, or key pairs).

6.3 Application Isolation

The Application runs within Snowflake's Native App sandbox, which enforces isolation between the Application and your account objects. The Application can only access objects for which explicit privileges have been granted.

6.4 Compliance

Tabby Stack maintains information security policies aligned with SOC 2 controls, including data classification, access control, and incident response procedures.

The Application is a business-to-business tool intended for use by Snowflake account administrators. It is not directed at individuals under the age of 16, and we do not knowingly collect information from children.

You have the following rights regarding data processed by the Application:

• Access: The Application displays all data it processes directly in the dashboard UI
• Deletion: Uninstall the Application to permanently delete all stored data
• Control: You control which privileges the Application has at all times and can revoke them via Snowflake's standard privilege management

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Updated versions will be made available through the Application listing on the Snowflake Marketplace. The "Last updated" date at the top of this policy indicates the most recent revision.

If you have any questions about this Privacy Policy or our data practices, please contact us at: