Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Contact support

Email support@stackyapper.dev for product, account, billing, portal, app, and AI client connection help. Report a suspected vulnerability or security incident to security@stackyapper.dev, and send privacy or legal questions to legal@stackyapper.dev.
Support is handled on business days, Monday through Friday, excluding United States federal holidays. Stackyapper targets an initial response within two business days. This is a response target, not a guaranteed response or resolution time and not a service-level agreement. See the complete Support Policy.

What support covers

Email support includes reasonable help with account access and billing, clarification of documented Stackyapper features, investigation of suspected Stackyapper defects, and investigation of connector failures that may originate within Stackyapper.
Self-service support does not include onboarding, implementation, migration, training, meetings, telephone calls, screen sharing, custom development, consulting, managed operations, or configuration of third-party systems.
For managed customer workspaces, the managing Stackyapper account contacts Stackyapper support. The managing business remains responsible for supporting its own customers.

What to include

  • Your workspace name and, for an MSP, the affected customer workspace
  • The app, tool, portal page, or AI client involved
  • The approximate time of the attempt and your time zone
  • The exact error shown to you
  • Relevant Audit request or result identifiers, shown on the audit entry detail (see Audit and investigation)
  • A screenshot if it does not contain confidential provider data
  • The safe troubleshooting steps you already tried
These details help support correlate your report with operational metadata without needing the content of a provider request or response.

What not to send

Do not send:
  • Passwords
  • MCP API keys
  • Provider API keys or client secrets
  • OAuth access or refresh tokens
  • Session cookies
  • Raw provider request or response bodies containing customer data
If a credential may have been exposed, revoke or rotate it before contacting support.

Trust center

For security, privacy, data-handling, and access-control questions that do not need a support ticket, start at the Stackyapper Trust Center.
Stackyapper keeps provider credentials behind its remote MCP endpoint. Before a tool runs, it checks the caller, workspace, connected app, exact tool permission, action risk, and any required confirmation. Routine activity records contain operational metadata, not tool arguments or the data returned by the connected app.
Resources for administrators:
Public review documents:
Stackyapper does not currently hold a third-party security certification. The Trust Center describes implemented product controls and their limits without claiming an outside audit or warranty.