Effective date: [EFFECTIVE_DATE] · Last updated: [EFFECTIVE_DATE]
1. Purpose and Scope
This Acceptable Use Policy (the “Policy”) describes what you may and may not do with the Synapse AI platform, including its applications, APIs, AI features, agents, automations and integrations (the “Service”), and our website at [SITE_DOMAIN] (the “Site”), provided by [LEGAL_ENTITY_NAME] (“Synapse AI,” “we” or “us”). It applies to every customer, Authorized User, Guest and visitor, and forms part of our Terms of Service. Capitalized terms not defined here have the meanings given in the Terms.
Customers are responsible for their Authorized Users’ and Guests’ compliance with this Policy. This Policy works together with our AI & Responsible Use Policy, which explains how to use AI features responsibly, and our Privacy Policy.
2. Lawful and Respectful Use
You must use the Service and the Site in compliance with all applicable laws and regulations, including privacy, data protection, consumer protection, anti-discrimination, employment, export control, sanctions, anti-spam and intellectual property laws. You may not use the Service or the Site to:
- engage in, promote or facilitate illegal activity, fraud or deceptive practices;
- infringe, misappropriate or violate the intellectual property, privacy or publicity rights of others;
- harass, threaten, bully, stalk or intimidate any person, or promote violence or hatred against people based on protected characteristics;
- impersonate any person or organization, or misrepresent your affiliation with them;
- collect or process personal information without a lawful basis and any required notice or consent.
3. Prohibited Content
You may not upload, store, generate, share or transmit through the Service content that:
- sexually exploits or endangers minors, including child sexual abuse material, which we report to the National Center for Missing & Exploited Children as required by law;
- depicts intimate images of a person without their consent;
- contains malware, ransomware, spyware, exploit code intended for unauthorized use, or other harmful code;
- is defamatory, fraudulent or knowingly false and intended to deceive;
- provides instructions for creating chemical, biological, radiological, nuclear or explosive weapons;
- you do not have the right to use, including confidential information you are obligated to protect.
4. AI Features: Prohibited Uses
4.1 Harmful or deceptive generation
You may not use AI features, including Synapse Copilot, AI automation steps, agents and meeting summaries, to:
- generate content prohibited by Sections 2 and 3;
- create phishing messages, fraudulent documents, fake reviews or other deceptive content;
- impersonate real people, including by generating statements, messages or meeting notes falsely attributed to them;
- generate or distribute election disinformation or conduct coordinated inauthentic campaigns;
- develop malware, attack tooling or techniques to compromise systems you are not authorized to test;
- present AI-generated content as human-created where the law requires disclosure of AI involvement;
- provide legal, medical, financial or other regulated professional advice to others without review by a qualified professional.
4.2 Prompt injection attacks
A prompt injection attack is content crafted to manipulate an AI system into ignoring its instructions or acting against the interests of its users. You may not create, plant or distribute content, whether in tasks, documents, comments, tickets, emails, chat messages, calendar invitations, file names or metadata, spoken meeting content, code repositories, or web pages or other sources ingested through connectors, that is designed to cause Synapse AI features or agents to:
- ignore or override instructions set by users or workspace administrators;
- reveal content that the requesting user is not permitted to access, or disclose system instructions or configuration;
- exfiltrate data, including through links, images, webhooks, automations or integrations;
- take actions without required approval, or take actions the triggering user did not intend;
- target other users, other customers’ workspaces or our systems.
This prohibition applies to indirect attacks, such as posting instructions in a shared channel, repository or document that another organization’s workspace ingests. You may test how AI features handle adversarial content inside a workspace you control, using test data and without affecting other users, provided you follow the security testing rules in Section 8 and report any bypass you find to [SECURITY_EMAIL].
4.3 Circumventing safeguards
You may not attempt to bypass, disable or defeat safeguards in the Service, including prompt-injection detection, output schema validation, PII redaction, AI exclusions set by administrators, permission-aware retrieval, approval gates, rate limits or AI credit metering, and you may not attempt to jailbreak the models used by the Service.
4.4 Model extraction and competitive use
You may not systematically query AI features or collect Outputs to extract model behavior, reconstruct system instructions or retrieval indexes, create training datasets, or develop or improve models or products that compete with the Service.
4.5 Model provider restrictions
Some AI features are powered by third-party model providers ([LLM_PROVIDERS]). You must comply with any usage restrictions of those providers that we make available to you, in addition to this Policy.
5. Automated Employment Decisions
Synapse AI is built to plan and deliver work, not to evaluate people. The Resource & Capacity Planner, Portfolio Analytics & Risk Radar, Meeting Intelligence, task data, flow metrics and AI Outputs are not designed, tested or offered as automated employment decision tools or as high-risk AI systems for employment decisions.
5.1 Prohibited employment uses
You may not:
- use data or Outputs from the Service, including workload, capacity, throughput, cycle time, meeting participation, risk scores or Copilot answers, to make, or as a substantial factor in, decisions to hire, reject, terminate, discipline, demote, promote, compensate or evaluate the performance of any individual;
- configure agents or automations to initiate adverse employment actions, such as disciplinary steps, performance ratings or termination workflows, without meaningful review by a person with authority to change the outcome;
- use AI features or analytics to rank, score or profile individual workers, for example by productivity, responsiveness or meeting participation;
- use meeting recordings or transcripts to infer emotions, health conditions or protected characteristics of participants;
- monitor or discourage legally protected activity, such as employees discussing wages or working conditions.
5.2 Your compliance obligations
If information from the Service is considered in any employment-related process, a qualified person must make the decision based on a complete review, and you are responsible for compliance with applicable law, including federal, state and local anti-discrimination laws; New York City Local Law 144 on automated employment decision tools; the Illinois Human Rights Act, as amended to address the use of artificial intelligence in employment decisions, and the Illinois Artificial Intelligence Video Interview Act; the Colorado Artificial Intelligence Act and California regulations on automated-decision systems in employment and on automated decision-making technology, to the extent in effect; the EU AI Act, for customers in the European Union; and workplace monitoring notice laws, such as New York’s electronic monitoring notice law. See also our AI & Responsible Use Policy.
6. Meeting Features and Recording Consent
Meeting Intelligence can join Zoom, Google Meet and Microsoft Teams calls, record and transcribe them, separate speakers and extract action items. Recording and transcribing conversations is regulated by wiretapping, eavesdropping and privacy laws. As the customer, you are responsible for complying with those laws.
6.1 Notice and consent
- Before a meeting is recorded or transcribed, you must give every participant clear notice and obtain consent where the law requires it.
- Several US states require the consent of all parties to a conversation, including California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington, and other states apply similar rules to certain types of communications. When participants are located in different jurisdictions, follow the strictest applicable rule. Laws outside the United States may impose additional requirements.
- Keep the meeting consent notice and per-participant opt-out enabled whenever Meeting Intelligence joins or records a meeting.
- Before importing an existing recording, confirm that the required notice was given and consent was obtained when it was made.
- If a participant objects or opts out, do not record or transcribe that participant, or stop the recording.
6.2 Prohibited recording practices
- Recording or transcribing meetings covertly, including by renaming or disguising the meeting assistant.
- Recording meetings you are not hosting or authorized to record.
- Recording privileged legal discussions, medical conversations or other highly sensitive meetings without first confirming that recording is appropriate and lawful.
6.3 Voice and biometric information
If you use features that associate voices with identified individuals, you are responsible for providing any notice and obtaining any written consent required by biometric privacy laws, such as the Illinois Biometric Information Privacy Act, the Texas Capture or Use of Biometric Identifier Act and Washington’s biometric identifier law.
6.4 Retention
Workspace administrators control how long audio and transcripts are kept. Set retention periods consistent with your legal obligations and internal policies, and delete recordings that are no longer needed.
7. Security and System Integrity
You may not:
- access or attempt to access accounts, workspaces, data or systems without authorization, including by exploiting misconfigurations or using another user’s credentials;
- probe, scan or test the vulnerability of the Service except as permitted in Section 8;
- interfere with or disrupt the Service, including through denial-of-service attacks, flooding, or sending malformed or excessive requests;
- circumvent authentication, permissions, tenant isolation or security controls;
- use API keys or tokens issued to someone else, or share your API credentials outside your organization;
- introduce malware or use the Service to host or distribute it;
- forge webhook signatures, request headers or other identifying information.
8. Security Testing and Vulnerability Reporting
We welcome reports from people who find security issues. Security testing is permitted only under these rules:
- Scope: test only workspaces and accounts you own or are authorized to test. Do not test other customers’ workspaces or our corporate systems.
- Data: do not access, modify, download or delete data that is not yours. If you encounter someone else’s data, stop, do not retain it, and report it immediately.
- No disruption: no denial-of-service, load or stress testing, and keep automated scanning within the API rate limits of your plan.
- No social engineering: do not use phishing, pretexting, physical intrusion or other attacks against our employees, contractors, customers or facilities.
- No third-party targets: do not test the systems of our hosting, AI model, payment or other service providers, or of integration partners.
- No persistence: do not install backdoors, maintain access after confirming a vulnerability, or pivot to other systems.
- Reporting: send findings promptly to [SECURITY_EMAIL] with enough detail to reproduce the issue, and keep them confidential until we have confirmed a fix or agreed with you on a disclosure date.
Enterprise customers who want to conduct penetration testing beyond these rules must obtain our written authorization and agree on a schedule in advance. If you follow these rules in good faith, we will treat your research as authorized and will not initiate legal action against you for it. Our safe harbor and the findings we consider out of scope are described in Section 16 of our Security Overview.
9. Scraping, Crawling and Automated Access
Automated access to the Service is permitted only through our documented APIs, SDKs and webhooks, within the limits of your plan. You may not:
- scrape, crawl, spider or harvest content or data from the Service or the Site using bots, scripts or other automated means;
- circumvent robots.txt directives, CAPTCHAs, rate limits or other access controls;
- use automated means to create accounts, submit forms, add items to the cart or place orders;
- harvest names, email addresses or other personal information of users;
- bulk-extract content through Copilot, search or exports to build datasets, other than exporting your own Customer Data;
- use content from the Site or Service to train AI models.
Search engines may index public pages of the Site in accordance with our robots.txt file.
10. Messaging, Automations and Integrations
You may not use automations, AI steps, email or chat integrations, or webhooks to:
- send unsolicited bulk messages or marketing in violation of the CAN-SPAM Act, the Telephone Consumer Protection Act or other anti-spam laws;
- send data to systems or endpoints you are not authorized to use;
- overload or abuse third-party APIs, or violate the terms of connected Third-Party Services;
- post content into channels or repositories without authorization from their owners.
11. Sensitive and Regulated Data
Unless we have agreed otherwise in writing, you may not submit Restricted Data, as defined in Section 7.4 of our Terms of Service: special categories of personal data, protected health information regulated under HIPAA, payment card or financial account numbers, government-issued identification numbers, personal data of children under 16, and export-controlled technical data. Where sensitive information appears incidentally, for example in a meeting transcript or a support ticket, use administrative controls such as AI exclusions and field redaction to limit its processing, and make sure you have a lawful basis to process it.
12. Fair Use of Resources and Accounts
- API rate limits: Starter 120 requests per minute, Team 300, Business 1,000 and Enterprise 3,000, with bursts up to 2×. Requests above the limit receive HTTP
429 responses with a Retry-After header; your clients must respect it.
- Plan allowances: AI credits, automation runs and storage are limited by plan. Do not create additional accounts or workspaces, or split usage across organizations, to evade these limits.
- Member accounts: each member account is for one named person. Do not share credentials or rotate a member account among multiple people. Each plan includes a maximum number of members (up to 5 on Starter, 15 on Team, 50 on Business and 150 on Enterprise); do not create additional workspaces or accounts to exceed your plan’s member limit.
- Workloads: do not use the Service for purposes unrelated to managing work, such as general-purpose file hosting or content delivery.
13. Reporting Violations
- Abuse or suspected violations of this Policy: [LEGAL_EMAIL]
- Security vulnerabilities: [SECURITY_EMAIL]
- Copyright infringement: follow our DMCA & Copyright Policy
- Privacy concerns: [PRIVACY_EMAIL]
Include a description of the activity, relevant links or identifiers, and your contact information. We may share reports with the affected customer to resolve them, and we will not disclose your identity unless you agree or we are required to do so by law.
14. Enforcement
We may investigate suspected violations of this Policy. Depending on the severity and circumstances, we may remove or disable content; disable integrations, automations, API keys or AI features; notify the customer about a user’s violation; suspend or terminate access under Sections 10 and 11 of our Terms of Service; and report activity to law enforcement or cooperate with lawful investigations. Where practicable and appropriate, we will notify you and give you an opportunity to correct the issue before taking action. Fees are not refunded when access is suspended or terminated for a violation, as described in our Refund & Cancellation Policy. Our failure to act on a violation does not waive our right to act on it or on later violations.
15. Changes to This Policy
We may update this Policy to address new features, risks or legal requirements. We will notify customers of material changes as described in our Terms of Service. The “Last updated” date above shows when this Policy was last revised.
Questions about this Policy can be sent to [LEGAL_EMAIL] or to [LEGAL_ENTITY_NAME], [MAILING_ADDRESS]. Our other policies are available in our Legal Center.