Connector and Integrations Policy
Last updated: November 17, 2026
Version date: November 17, 2026
For existing customers, changes take effect under Section 25 of the Terms and any applicable customer agreement.
This Connector and Integrations Policy describes how the Axamy Services connect to your third-party tools and data sources through Axamy's integration software, and how Axamy handles the data that flows through those connections. It is part of, and incorporated by reference into, the Axamy Terms of Service.
1. Purpose and Scope
This Connector and Integrations Policy (this "Policy") describes how the Axamy Services connect to your third-party tools and data sources (each, a "Connected Service") through Axamy's integration software (each, a "Connector"), and how Axamy handles the data that flows through those connections. It is part of, and incorporated by reference into, the Axamy Terms of Service at axamy.com/terms (the "Terms"). Capitalized terms used here have the meanings given in the Terms and the Axamy AI Acceptable Use Policy (the "AUP") unless otherwise defined.
This Policy is intended for both administrators evaluating Axamy and individual users connecting their own accounts. It addresses how Connectors work, what data Axamy accesses, where the data is stored and processed, who can see it, how long it is retained, and how it can be revoked.
2. How Connectors Work
2.1 Connection methods
Axamy supports three connection methods:
- OAuth 2.0 — the preferred method, in which the Connected Service issues Axamy a delegated token bound to a User account and to a defined set of scopes;
- API key — supported for services that do not implement OAuth, in which the User provides an API token the service has generated for them; and
- Model Context Protocol (MCP) — supported for both Axamy-managed and Customer-provided MCP servers, where the protocol governs the discovery and invocation of capabilities.
2.2 Identity binding
Every Connector is bound to a specific User identity and authenticates to the Connected Service as that User. The Services do not impersonate Users or use shared service accounts unless an administrator explicitly configures one. Permissions, audit visibility, and data access within the Connected Service follow that User's identity.
2.3 Token storage
Connector tokens and credentials are encrypted at rest and decrypted only at the point of use. Tokens are not exposed to Authorized Users, Agents, or LLM providers in plain form.
3. How Data Flows Through Axamy
3.1 Ingestion
When a Connector is active, the Services may read data from the Connected Service in response to (a) a User request, (b) an Agent action authorized by a User configuration, or (c) a scheduled sync the User has enabled. Axamy reads only the data within the scopes the User has granted and only as needed to perform the requested function.
3.2 Processing within the Workspace
Data read from a Connected Service is stored within the Customer's Workspace and processed by Agents to produce Outputs, build memory, and orchestrate work. Customer data is separated by workspace in the application. Internal service routes require a secret key that is restricted to named staff and rotated when any of them leaves.
3.3 Submission to large-language-model providers
Where the Services use an Axamy-selected third-party large language model, relevant excerpts of Customer Data may be transmitted for inference. Axamy engages those providers under arrangements consistent with Axamy's confidentiality, permitted-use, security, and applicable deletion obligations to Customer. A provider's public terms do not override Axamy's commitments or authorize use of Customer Workspace Data to train generalized AI models. This is distinct from a Connected Service independently selected and authorized by Customer, whose separate service terms continue to apply to that service.
3.4 Outbound actions
When you direct an Agent to take action in a Connected Service (sending an email, creating a task, posting a message, scheduling a meeting, updating a record), the Services call the Connected Service's API using the Connector's authenticated session and within the scope you granted. The Connected Service treats the action as having been performed by the User who authorized the Connector.
3.5 Hosting region
Axamy's primary Workspace hosting is in the United States. Subprocessors and Customer-authorized Connected Services may process data in other locations as described in the Privacy Policy and the applicable provider arrangements. United States hosting is not a promise that every processing activity or support access occurs exclusively in the United States. Additional location commitments require express written agreement.
4. Permission Model
4.1 Least privilege by default
Axamy requests the minimum OAuth scopes necessary to deliver the features you have enabled. Where a Connected Service offers a granular scope and a broader scope, Axamy requests the granular scope by default.
4.2 Administrative controls
Available administrative controls vary by plan and by Connected Service. Where supported, an administrator may approve, restrict, or block specific Connectors for the Workspace and manage which Authorized Users may connect them. Customers requiring controls not currently exposed in the product may contact support@axamy.com.
4.3 User responsibilities
Users are responsible for reviewing the scopes a Connector requests and for confirming they have authority to grant those scopes before authorizing the Connector. Section 4.2 of the Terms applies to every Connector that touches employer-controlled data.
5. Sub-processors
Axamy may use sub-processors to deliver the Services, including:
- infrastructure providers (cloud hosting, content delivery, networking, monitoring);
- model providers (large-language-model and other AI inference providers);
- developer tooling (logging, error tracking, observability);
- communications providers (transactional email, in-app messaging); and
- billing and identity providers.
Customers may request the current list of named sub-processors by contacting support@axamy.com.
6. Data Retention and Deletion
6.1 Workspace retention
Data ingested through Connectors, including Agent memory and profile records, is retained to provide the Workspace features Customer uses and as described in the Privacy Policy. Disconnecting a Connector or ending a subscription does not by itself erase previously ingested data. The provisions below govern subsequent retention, deletion requests, applicable DPA obligations, and any storage required by law; an inactive connection does not authorize retention beyond those provisions.
6.2 LLM submissions
Retention of prompts and completions by Axamy-selected model providers depends on the applicable service configuration and Axamy's agreement with the provider, subject to Section 3.3 and Axamy's obligations to Customer. Any permitted retention for security, abuse prevention, or legal requirements must remain consistent with those obligations and applicable law. Provider terms do not independently override required deletion, confidentiality, or restrictions on training.
6.3 On disconnection of a Connector
When a Connector is disconnected, the Services revoke the token and stop further ingestion. Disconnection does not itself delete previously ingested data or reverse completed actions. Previously ingested data, including inferences, memory, summaries, embeddings, and records derived from it, remains subject to the retention and deletion provisions of the Privacy Policy, the Terms, any applicable DPA, and applicable law. Transforming source data does not by itself make it anonymous or exempt it from deletion obligations. When Customer requests deletion, those obligations apply to derived data as well as source data, subject to applicable backup-retention practices, legal holds, and other retention required or permitted by applicable law and the customer agreement. Any retained personal information remains protected and is used only for the purpose that permits its retention. Information that has been anonymized so that it no longer constitutes personal information under applicable law may be retained only as permitted by the customer agreement and applicable law.
6.4 On termination of the Services
Section 19.4 of the Terms provides a thirty (30) day post-termination export-request window, subject to earlier deletion required by law, Customer's instructions, or an applicable DPA. It does not guarantee continued availability of data that must be deleted earlier. Customers whose DPA requires deletion or return when processing ends should arrange return before that time or agree a lawful handover schedule under the DPA. Otherwise, termination does not itself trigger deletion. Customer Workspace Data is deleted on written request, subject to the Privacy Policy, Section 14.7 of the Terms where applicable, and any expressly agreed DPA.
6.5 End Individual deletion requests
Section 13.4 of the Terms applies. Axamy will, at Customer's instruction and within a reasonable period, delete or anonymize End Individual data, subject to backup and legal-hold obligations.
7. Revocation and Disconnection
7.1 User-initiated
A User may disconnect any Connector they have authorized at any time through the Workspace integration settings. Disconnection takes effect immediately for new operations; in-flight operations may complete.
7.2 Administrator-initiated
Where supported by the plan and Connected Service, an administrator may revoke Connectors, restrict Connector categories, or revoke an Authorized User's access, as described in Section 4.2. Other control requests may be directed to support@axamy.com. Domain claims are subject to the authority, notice, disputed-access, and data-access limitations in Section 4.4 of the Terms. A domain claim does not itself expand Connector permissions.
7.3 Connected-Service-initiated
The Connected Service may, at any time, revoke a token, change the scopes it grants, or change its API. The Services will detect such changes and may stop or limit functionality accordingly. Axamy does not maintain off-channel access to Connected Services beyond the tokens you have authorized.
7.4 Axamy-initiated
Axamy may revoke or suspend a Connector if Axamy reasonably believes its use creates risk to the Services, the Customer, or any third party, or violates the Terms, this Policy, or the AUP.
8. Compliance with Connected Service Terms
8.1 Customer responsibility
Each Connected Service is governed by its provider's terms of service, acceptable-use policy, rate limits, and applicable law. Section 10.4 of the Terms applies: you are responsible for ensuring that your use of the Services, including actions Axamy takes on your behalf, does not violate any Connected Service's terms. Axamy makes no representation that any action taken in a Connected Service complies with that Connected Service's terms.
8.2 Rate-limiting and back-pressure
Axamy implements reasonable rate-limiting and back-pressure when calling Connected Service APIs to reduce the risk of inadvertent terms or rate-limit violations. Where a Connected Service enforces a quota you exceed, Axamy will pause the relevant operations and notify the User.
8.3 Prohibited automated use
Sections 3.11 and 4 of the AUP apply. You will not use the Services to scrape, mass-extract, spam, robocall, or otherwise automate use of a Connected Service in violation of its terms or applicable law.
9. Custom MCP Servers
The Services support customer-built or customer-deployed MCP servers ("Custom MCP"). When a Customer connects a Custom MCP, the Customer is responsible for:
- the security of the Custom MCP server, including authentication, authorization, rate-limiting, and patching;
- the data the Custom MCP exposes to the Services and the scopes it grants;
- compliance of the Custom MCP with the terms of any downstream services it accesses;
- appropriate logging and monitoring of the Custom MCP; and
- any privacy notices, consents, and other obligations triggered by the Custom MCP's data exposure.
Axamy provides documentation for the MCP capabilities the Services consume but does not assume responsibility for the operation, security, or compliance of a Custom MCP.
10. Security
10.1 Encryption
- Data in transit between Users, Axamy, and Connected Services is encrypted with TLS 1.2 or above.
- Customer Workspace Data stored in Axamy's AWS RDS databases is encrypted using AES-256 with AWS KMS. Other service providers use their own storage systems and encryption implementations. Their handling of personal information remains subject to the confidentiality, security, and data-protection requirements of the Agreement, the Privacy Policy, and any applicable DPA; this AWS RDS statement does not describe every provider's stored copies.
- Connector tokens and other secrets are encrypted at rest.
10.2 Access controls
- Production access is restricted to authorized Axamy personnel.
- Customer data is separated by workspace in the application. Internal service routes require a secret key that is restricted to named staff and rotated when any of them leaves.
10.3 Records of Agent and Connector activity
If a Customer requires a record of actions Agents have taken in their Workspace or in their Connected Services, they may request it by emailing support@axamy.com.
10.4 Vulnerability disclosure
Report suspected security vulnerabilities to security@axamy.com or through the security reporting page.
11. Compliance and Attestations
Axamy's compliance program is under development. Current status and any available reports may be requested under NDA by contacting support@axamy.com.
Government and regulated-industry Customers may require additional commitments (for example, FedRAMP, DFARS, CMMC, CJIS, NIST SP 800-171, NIST SP 800-53). Such commitments are addressed under an Order Form.
12. International Data Transfers
The Services are hosted in the United States. Before Customer uses a Connector for processing or transfers that require additional contractual safeguards, Customer and Axamy must put those safeguards in place under Section 14.2 of the Terms. Where expressly agreed and applicable, the DPA provides the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, and Swiss adaptations. Connecting a service does not by itself incorporate the DPA.
13. Changes to this Policy
Changes to this Policy are governed by Section 25 of the Terms, including its notice, renewal, cancellation, and refund rules. Material changes include materially expanding collected data, adversely changing retention, or materially reducing security commitments. Non-material changes take effect when posted. Urgent protective actions may be taken only as permitted by the Terms or law and do not bypass the amendment rules. An existing binding agreement continues until validly amended.
14. Contact
For questions about this Policy or for security and compliance inquiries:
Support: support@axamy.com. Security: security@axamy.com or the security reporting page.
Privacy: privacy@axamy.com
Legal: legal@axamy.com