Terms of service

These draft terms describe the proposed conditions for using Agency Memory, provided under the name agencymemory.ai. Questions can be sent to [email protected]. They are prepared for review and are not a completed agreement or a substitute for a processing agreement where one is required.

1. The service

Agency Memory stores client and brand information, including Brand Knowledge, Playbooks, platform details, and related records, and makes that context available through the app and MCP. It does not itself execute advertising campaigns, grant external platform permissions, or authorize spending.

Your connected AI agents and tools are separate services. Their availability, compatibility, charges, and terms are their providers’ responsibility.

2. Workspace administration and access

You are responsible for ensuring that the people administering your workspace have authority to do so, and for keeping account credentials and MCP keys secure. Issue keys only to people and agents trusted with all the information in that workspace.

Every active MCP key can read the workspace. Solo mode controls writes with one workspace switch; Agency mode controls writes per key. Allowed changes apply directly. You are responsible for reviewing permissions and revoking connections that should no longer have access.

3. Your content

As between you and agencymemory.ai, you retain the rights you hold in content you provide. You must have the rights and permissions needed to store it in the service and make it available to your chosen agents and teammates.

The proposed service permission is limited to hosting, storing, copying, transmitting, and otherwise processing that content as needed to provide, maintain, secure, and support the service under the applicable agreement. It does not transfer ownership of your client or brand content to agencymemory.ai.

4. AI outputs and external actions

You remain responsible for reviewing retrieved information and AI-generated work before relying on it. Stored context may be incomplete, stale, or incorrect. Source information, verification labels, and version history assist review but do not guarantee correctness.

A Playbook is an instruction document. It does not provide an approval queue, enforce a publishing review in another tool, or grant authority to spend. Confirm external account access, approvals, and destinations through the tools that perform those actions.

5. Acceptable use

Do not use the service unlawfully, infringe others’ rights, attempt to bypass access controls, use another workspace without authorization, distribute malicious material, or interfere with service availability. Do not put third-party passwords or API secrets into brand knowledge as a substitute for a credential manager.

Notify support if you suspect that an account or MCP key has been compromised. Do not include the secret itself in the report.

6. Personal data and confidentiality

Use the service consistently with your obligations to clients and individuals. The privacy policy draft describes the information involved in the service. Where personal data is processed on your instructions, the applicable processing agreement must be in place before that use begins.

The final agreement must define the parties’ confidentiality obligations and any permitted disclosures, including obligations that continue after the service relationship ends.

7. Plans and commercial terms

Any paid service must be governed by the plan and commercial terms accepted when it is purchased. This draft does not establish a paid subscription, renew an account, or authorize a charge.

Final commercial terms must address prices and taxes, billing periods, renewal, cancellation, refunds, plan changes, and the applicable payment provider’s role before paid checkout becomes available. No unverified refund entitlement, minimum commitment, or billing policy is implied here.

8. Availability, changes, and support

The service and its connection options may change as the product develops. External agent or tool changes can affect compatibility. No specific uptime, support response time, or recovery commitment is established by this draft. Any such commitment must be expressly included in the applicable agreement.

9. Suspension, account closure, and records

The final agreement must set out when access may be suspended or ended, how an account holder can close a workspace, and what opportunity exists to retrieve content. A revoked key stops future access through that key; it does not erase content already retrieved by an agent.

Archiving preserves records and history. Retention, permanent deletion, and backup handling after closure must match the final privacy policy and applicable processing agreement.

10. Final legal provisions

The effective agreement must address appropriate warranties, liability allocation, mandatory rights, dispute handling, governing law, and notices. Those provisions have not been selected in this draft. No liability cap, dispute forum, or waiver is invented here.

Contact [email protected] with questions about these terms.