Tools for Airtable Development
How Base Map protects your API keys and data
Base Map is designed with a client-side only architecture, which means:
When you enter your API keys:
Local storage is isolated to your browser and device, making it a secure way to store credentials for client-side applications.
Remember:
While Base Map is designed to keep your API keys secure, you should always follow your organization's security policies when handling API credentials.
Base Map does not collect, store, or transmit any personal data or API keys to our servers. All data processing occurs entirely within your browser.
Your browser communicates directly with:
These services have their own privacy policies and data handling practices.
All data (API keys, schemas, analysis results) is stored exclusively in your browser's local storage. Data persists until:
You have complete control over your data:
Important:
Since Base Map stores no data on servers, there is no account to delete or data to request. All data management happens in your browser.
Base Map uses Google OAuth solely for:
We request minimal Google account permissions:
openid - Authenticate your identityemail - Access your email addressprofile - Access your basic profile info (name, picture)Important:
Google OAuth is ONLY used for user authentication. Your Airtable and Gemini API credentials are NEVER sent to our servers and remain exclusively in your browser.
Base Map requires minimal Airtable permissions:
schema.bases:read - Read base schema onlyYour Gemini API key is used to:
Client-Side Security:
Your API credentials (Airtable PAT and Gemini API key) are:
We use Stripe for secure payment processing:
Your Google account is used only to:
By using Base Map, you agree to:
When you create an account:
Base Map is provided "as is" without warranties. We are not liable for:
Contact:
For questions about these terms or to request account deletion, please contact support.