Permissions, Safety & Security
Last updated: October 4, 2026
SynaBot is an AI workforce for small business. Your AI workers prepare work, but you stay in control of anything that leaves your business. This page explains what SynaBot can and cannot do with your accounts, how your data is kept separate, and how to report a security issue.
Does SynaBot act without my approval?
SynaBot prepares work for review. Owners and admins control external work through explicit actions and configured permissions or automation. Members can prepare work but cannot execute priced jobs; viewers have read-only access. Once authorized and scheduled, a social post can publish later without another confirmation.
What can each connected integration do?
Access depends on the account you connect and the permissions you grant. The following describes SynaBot's current operations, not a guarantee that every OAuth permission is limited to those operations. Owners and admins review and authorize external work; configured automation can carry out authorized actions.
- Gmail: reads recent inbox metadata and message previews; prepares replies and saves drafts when you authorize the action; the current integration does not send email, although its gmail.compose permission also permits sending.
- Google Calendar: its permission allows event access, but the current scheduling workflow does not read existing events; prepares and creates an authorized event on your primary calendar without attendees or invitation notifications; does not manage calendar sharing.
- Google Drive: its permission allows access to app-authorized files, not your whole Drive; the current workflow does not browse existing documents, and creates an authorized private Google Doc; does not change sharing permissions.
- Google Sheets: drive.file permits access to app-authorized files; the current workflow does not read your existing spreadsheet contents, and can create a lead tracker, set its headers and append approved lead records; it does not browse all spreadsheets or change sharing permissions.
- Google Analytics: reads accessible account/property information and reports for the property mapped to your selected business; prepares analysis from those reports; it cannot change Analytics settings through its read-only permission.
- Google Search Console: reads accessible site information and search performance for the property mapped to your selected business; prepares recommendations; it cannot modify Search Console properties or submit sitemaps through its read-only permission.
- Social posts: reads configured public feeds and supported connected-account information; prepares posts and can publish or schedule them when an authorized user chooses to do so, with scheduled posts publishing later; it cannot publish without a supported, enabled publishing connection, and canceling a scheduled post does not remove a post already published. Permissions vary by platform and connection.
How connected Google access is protected
Google connection credentials are used on the server rather than exposed to the browser. Business Analytics and Search Console OAuth credentials are stored encrypted. The other Google integrations use the connection gateway and server-held connection keys. See the Privacy Notice for the Google OAuth disclosure.
SynaBot's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How is one business kept separate from another?
Each business has its own AI workforce, Business DNA, connections, work history and Credits. Connections are scoped to the signed-in user and the selected business, and database access rules prevent one business's records being read from another. Credits cannot be transferred between businesses.
How do I revoke a connection?
Owners and admins can disconnect any connected account from the business settings. Disconnecting requests revocation from Google and removes the stored connection credentials and related mappings. You can also remove SynaBot's access at any time from your Google Account permissions page.
Which AI providers process your data
SynaBot uses the following AI model providers. Depending on the feature you use, relevant business context, conversations, documents or generation inputs may be sent for processing.
- Anthropic (Claude): provides answers to submitted questions in SynaBot's multi-model answer feature.
- OpenAI (GPT models): powers selected text features, image creation and editing, and text-to-speech.
- Perplexity: provides web-grounded answers to submitted questions in the multi-model answer feature.
- Google (Gemini): powers workforce conversations, business analysis, drafting, document and audio processing, and image features.
- xAI (Grok): used only in a review feature run internally to analyze SynaBot's own public homepage; the resulting reviews may be published. This feature does not send your private business records or account data to xAI.
The model used depends on the feature and its configuration; not every provider receives every business record.
Who handles payments?
Checkout is handled by Stripe. SynaBot never sees or stores your full card number.
Reporting a security issue
Email security@synabot.ai with:
- A clear description of the issue and its potential impact;
- Steps to reproduce (URLs, request payloads, screenshots);
- Your name or handle if you would like credit.
We aim to acknowledge security reports within 1 business day and to provide an initial assessment within 7 days.
Safe harbor
If you make a good-faith effort to comply with this policy, we will not pursue or support legal action against you for your research. Please:
- Only test against your own accounts or accounts you have explicit permission to test;
- Do not access, modify or destroy other users' data;
- Do not run automated scans that degrade the Service for other users;
- Give us a reasonable time to remediate before any public disclosure.
Out of scope
- Reports produced solely by automated scanners without a demonstrable impact;
- Missing security headers or best-practice recommendations with no exploit path;
- Social engineering of SynaBot staff, customers or vendors;
- Denial-of-service attacks and physical attacks on infrastructure;
- Issues in third-party services (for example Stripe or Google) — please report those to the vendor directly.
What happens if personal data is affected?
If we determine that personal data has been affected by a security incident, we will notify affected users and, where required, the relevant regulator, in line with applicable law and our Privacy Notice.
Contact
SynaBot Inc., 16192 Coastal Highway, Lewes, Delaware 19958, USA — security@synabot.ai.
