Privacy Policy

General

This web app does not permanently store any user data, with the exception of information used to sign you into your account. Amalgam may at times make temporary use of user data in order to provide its services, as detailed below.

Integrated Services

This app may be connected to other services ("Integrated Services") such as Quickbooks and Stripe, and may be used to access and modify data within these integrated services. All data obtained from integrated services is subject to those services' respective privacy policies.

Data obtained from integrated services will pass through Amalgam and be transmitted, as requested by the user. An example would be taking Quickbooks data and transmitting it to a Google Sheet. This app does not retain the information transmitted.

Connecting a Financial Institution through Plaid

Some features let you connect a financial institution, such as a bank account, to Amalgam. This connection works differently from our other Integrated Services. With services like QuickBooks, Stripe, and Google, Amalgam connects to a system you already use, and data passes through Amalgam without being retained.

To connect a financial institution, Amalgam uses Plaid Inc. ("Plaid"), a third-party financial data provider. In this case you are choosing to link your financial institution to Plaid, and Amalgam then receives the permissioned data through Plaid. This means Plaid is a separate party in the connection, not simply a system you already use.

Plaid collects and processes your financial data, which may include account details (such as account and routing numbers and balances), transactions, and identity information, as an independent data controller under its own privacy policy and for its own purposes as described there. We encourage you to review the Plaid End User Privacy Policy. Many organizations already use Plaid through other applications, but we call it out here because this relationship is distinct from our other integrations.

This connection happens only if a user chooses to create it. It is not enabled by default and is not a built-in part of the Amalgam product. No financial institution is connected unless a user directs that connection themselves. As with our other integrations, Amalgam does not retain the data transmitted through this connection.

If you would prefer this option not be available to your team, we can disable Plaid-based connections for your organization on request. Contact us at support@amalgam.me.

Google User Data

Amalgam can connect to Google products you already use, including Google Ads, Google BigQuery, Google Drive, and Google Sheets. When you connect one, Google asks you to grant Amalgam specific permissions, and Amalgam requests only the permissions needed for that connection: reading your Google Ads data, running queries in BigQuery, creating and updating files you choose in Google Drive, working in the spreadsheet you open the Sheets add-in from, and seeing your email address.

How we use it. Your email address identifies the connection. Google data is read or written only when you run a report, query, or delivery, and only to return that result to you in Amalgam or in the destination you chose. Amalgam does not use Google user data for any other purpose.

What we store. Amalgam stores only the access and refresh tokens that keep each connection working. Report, query, and file data passes through Amalgam and is not stored. Amalgam does not keep copies of your Google data.

Who we share it with. Amalgam does not share, transfer, sell, or disclose Google user data to any third party. It is not used for advertising, not sold to data brokers, and not used to develop, improve, or train generalized AI or machine learning models.

How we protect it. Google user data is transmitted using TLS 1.2 or higher. Stored access and refresh tokens are encrypted at rest and further encrypted by the application. Access to production systems is limited to authorized Amalgam personnel by role, and Amalgam maintains SOC 2 Type 2 certification. More detail is on our Security page and in our Trust Center.

Retention and deletion. Tokens are kept for as long as the connection exists. When you disconnect a Google product in Amalgam, the stored tokens are deleted. You can also revoke Amalgam's access at any time from your Google Account permissions page. To request deletion of any Google user data associated with your account, email support@amalgam.me and we will complete the deletion within 30 days.

Amalgam's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google Sheets Add-In

The Amalgam add-in for Google Sheets allows users to access data from Integrated Services directly from Google Sheets. This add-in requires access to certain user information in order to provide a seamless user experience.

This add-in requires access to each user's email address, display window, and active spreadsheet in order to display the sidebar interface and make adjustments to spreadsheets as requested by the user. Amalgam login data is securely stored within the user's google profile to allow connections with the Hub to persist (rather than requiring a login for each action performed).

The add-in also requires permission to send and request data from an external app (the Hub), in order to access the financial information from integrated services. No information sent from the google sheets add-in is stored by this app, except in integrated services as directed by the user (e.g. by creating journal entries in an accounting platform).