Skip to content
Tidy
Virtual employeesThe workspaceMemorySee TidyPlans
Explore ⌄
Set up an employeeMemoryAutomationCollaborationFor businessFor yourselfTemplatesConsultingWhat’s newNewsletterQuestions
Request an invite ↗
← Terms & Privacy
Tidy Engineering / Legal

API and Integration Terms

Effective October 13, 2026

What this covers

These terms cover building on Tidy: the REST API, the MCP server, and the personal access tokens or OAuth clients your code uses. They are part of the Terms of Service. The member who owns the account is responsible for what their code does.

Getting access

API access and personal access tokens come with Max. Every plan includes the MCP server, so any plan can connect a compatible client to Tidy.

Credentials are for the account holder’s own use. Keep them secret. Don’t share them, sell them, or put them in software you give to other people. Use one credential per integration and revoke it in Settings when you’re done. If a token leaks, revoke it and tell us.

What you may build

Build tools and automations for yourself or your organization, on your own account. You may not:

  • Resell access to Tidy or charge others to reach your account.
  • Copy Tidy’s features into a competing product.
  • Pull data in bulk beyond your own account.
  • Use the API to get around plan limits. Plan limits apply to the API too.

Data you get through the API

Data you fetch belongs to the member who authorized it. You must:

  • Use it only for what that member asked for.
  • Keep it secure.
  • Delete what you hold when the member’s account is deleted.
  • Never sell it, and never use it to train AI models.

Content that came into Tidy from a provider such as Gmail, Google Calendar, Drive, or Microsoft carries the member’s permissions with it. Your code may not go beyond what the member authorized, and must follow that provider’s own policies.

Limits

The API is rate limited to protect the service for everyone. Limits apply per workspace, per token, and on expensive endpoints, and they can change as the service grows; we don’t publish fixed numbers. A request over the limit gets a 429 response; wait and retry.

Don’t probe, scan, or stress-test the service, and don’t interfere with other members. Name your integration honestly in user agents and client names. Endpoints can change; we give notice of breaking changes where we can.

Suspension

We may slow down, suspend, or revoke API access for breaking these terms, a security risk, or abuse, using the smallest step that fixes the problem. You can stop anytime by revoking your tokens.

Disclaimers

The API is provided as is. It can change, and it can be discontinued. The liability limit in the Terms of Service applies.

Our name

Describe your integration factually; “works with Tidy” is fine. Don’t imply a partnership or endorsement, and don’t use Tidy’s name or logo in a way that suggests Tidy made your product.

Tidy

People and virtual employees.
One workspace.

Never forget. Never miss.
The workspaceVirtual employeesMemoryAutomationCollaborationFor businessFor yourselfTemplatesDevelopersPlansWhat’s newNewsletterTalk to usJoin the waitlist
Terms & Privacy

© 2026 Tidy Engineering, LLC

Private beta · Web & Android