Securely sharing credentials for Data Integration
Connecting your external data sources to Birdie.ai is the first step toward unlocking deep, AI-driven insights. We understand that sharing credentials involves a high level of trust, which is why we’ve built a secure, encrypted process to ensure your data remains protected.
Follow this guide to safely set up your integrations.
How to Add Your Credentials
To initiate a new data connection, ensure you are logged into your Birdie account and follow these steps:
Navigate to Organization Settings
Go to the Settings Page via the sidebar or by clicking your profile icon.
Access the Integrations Tab
Select the My Data / Integrations tab from the top navigation menu. You can also jump directly there via this link.
Note: For platform-specific instructions on where to find these keys, please refer to our dedicated "How to integrate with [Platform Name]" articles within the Help Center.
Data Retention and Deletion
We believe you should have full control over your credentials. Because these keys are the "bridge" that allows Birdie to securely fetch data from sources like BigQuery, we must maintain them to ensure your insights remain up to date.
How long are credentials stored?
Your keys are stored only for as long as they are active and necessary for your data operations. We will permanently delete this information in the following scenarios:
Contract Termination: Upon the end of your service agreement with Birdie, all stored credentials and connection data are purged from our systems.
Formal Request: We will remove credentials upon receiving a Data Subject Access Request (DSAR) or a formal written removal request from your organization’s administrator.
Managing Your Connection
Since these credentials are required for Birdie to communicate with your data warehouse (e.g., BigQuery), they must remain stored as long as you wish to continue importing data.
Important: You have the right to revoke or block these credentials within your own provider’s console (like Google Cloud Platform) at any time. However, please be aware that revoking access will immediately stop Birdie from being able to import or refresh your data.
Our Security Commitment
We prioritize the confidentiality and integrity of your administrative data. Here is how we handle your sensitive information:
Isolated & Encrypted Storage: All credentials (API keys, tokens, and secrets) are stored in a private, dedicated database hosted within Birdie’s secure cloud environment. Data is encrypted at rest.
Perimeter Protection: We enforce rigorous access controls on our infrastructure. This database is not exposed to the public internet; it is isolated within a private network and can only be accessed via our internal VPN by authorized system processes.
Restricted Access: Access is strictly limited to automated connection setups and background synchronization. Internal Birdie users and developers do not have direct access to view or retrieve your raw credential information.
Encryption in Transit: All data moving between your source platforms and Birdie.ai is protected by TLS 1.2+ protocols, ensuring your information remains secure as it travels across the web.
⚠️ Important Security Disclaimers
While Birdie.ai maintains rigorous security standards, we recommend the following best practices:
Principle of Least Privilege: When generating API keys or service accounts for Birdie, whenever possible, provide only the read-only permissions necessary for the integration to function.
Avoid Public Channels: Never share your API keys or credentials via email, Slack, or support chat. Always use the secure input fields within the Birdie dashboard.
Credential Rotation: We recommend rotating your API keys periodically as part of your organization's standard security hygiene.
Last updated