Section | Content |
---|---|
Secure credentials storage |
Your credentials used to connect to external sources are never used directly by the add-on, are kept server side, and can only be accessed by the user they belong to. API Keys, OAuth tokens, Basic auth information are stored in Cloud Datastore in a secure and encrypted container (StoredCredentials) Stored credentials are also never shared or logged. |
Encrypted source data processing |
Communication All communications between add-on and back-end use HTTPS (TLS). You can learn more about the encryption we use in transit here. Source data We securely encrypt your data while it is in transit from a source to a spreadsheet. Source data are cached server-side for a short period of time (at most 30 minutes) to provide the best performance possible. Stored data are encrypted and at no point in time is your data accessible outside of Awesome Table. Connector services (used to retrieve source data) can only be accessed by Awesome Table. They cannot be called directly over the internet. |
Isolated user data access |
Query configuration Metadata required to run a query (user, query configuration) is encrypted before it is stored (Datastore encryption at rest). Access to the database is restricted to a limited number of Awesome Table employees and requires multi-factor authentication. |
Secure-by-design infrastructure |
Logging Awesome Table technical logs are stored on Google Cloud Logging for up to 30 days. We never log sensitive information like user credentials, API keys, OAuth tokens, and query private details (parameter values, filter values). Infrastructure Awesome Table infrastructure is hosted on Google Cloud Platform. It allows Awesome Table to benefit from the same secure-by-design infrastructure, built-in protection, and global network that Google uses. You can find more information about Google Cloud Platform security here. |