feat: WhatsApp + LinkedIn integrations, SquareMCP rebrand, opencode docs

WhatsApp Business API (Meta Cloud API)
- New client: src/clients/whatsapp.ts
- Tools: whatsapp_send_message, whatsapp_send_template, whatsapp_list_templates
- REST endpoints: POST /api/whatsapp/send, POST /api/whatsapp/template, GET /api/whatsapp/templates
- Multi-account env var pattern: WHATSAPP_{ACCOUNT}_*

LinkedIn API (OpenID Connect)
- New client: src/clients/linkedin.ts
- Tools: linkedin_get_profile, linkedin_create_post, linkedin_search_connections, linkedin_send_message
- REST endpoints: GET /api/linkedin/profile, POST /api/linkedin/post, POST /api/linkedin/search-connections, POST /api/linkedin/message
- Multi-account env var pattern: LINKEDIN_{ACCOUNT}_*
- Uses /v2/userinfo (OpenID Connect) for profile reads

Domain migration
- hermes.fetcherpay.com -> hermes.squaremcp.com
- Updated K8s ingress, TLS cert, SERVER_URL env var
- Updated OPENCODE.md and opencode.json references

SquareMCP site
- Added logo assets (SVG, LinkedIn variants)
- Added terms.html
- Updated Dockerfile, nginx config, styles, index, privacy pages

Docs
- Added OPENCODE.md for opencode AI integration setup
- Updated .env.example with WhatsApp and LinkedIn credentials
- Added opencode.json to .gitignore (contains live API key)

Total tools: 19 (email 6, obsidian 5, whatsapp 4, linkedin 4)
This commit is contained in:
Garfield
2026-05-05 01:25:26 -04:00
parent e3a272c332
commit 73f83c0d86
18 changed files with 1207 additions and 45 deletions

View File

@@ -1,41 +1,136 @@
<!DOCTYPE html>
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Privacy Policy — SquareMCP</title>
<style>
body { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; max-width: 680px; margin: 60px auto; padding: 0 24px; color: #111; line-height: 1.7; }
h1 { font-size: 1.6rem; margin-bottom: 0.25rem; }
.sub { color: #666; font-size: 0.9rem; margin-bottom: 2rem; }
h2 { font-size: 1.05rem; margin-top: 2rem; }
a { color: #111; }
nav { margin-bottom: 2rem; font-size: 0.9rem; }
nav a { text-decoration: none; color: #666; }
nav a:hover { color: #111; }
</style>
</head>
<body>
<nav><a href="/">← squaremcp.com</a></nav>
<h1>Privacy Policy</h1>
<p class="sub">SquareMCP &mdash; Last updated April 28, 2026</p>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Privacy Policy — SquareMCP</title>
<meta
name="description"
content="SquareMCP privacy policy covering pilot requests, service data, and how customer environments are handled."
/>
<link rel="stylesheet" href="./styles.css?v=20260505b" />
</head>
<body class="legal-shell">
<nav class="topbar">
<div class="wrap topbar-row">
<a class="brand" href="/">
<img class="brand-logo" src="./squaremcp-logo.svg" alt="" />
<span class="brand-text">SquareMCP</span>
</a>
<div class="topbar-actions">
<a class="topbar-link" href="/terms">Terms</a>
<a class="button secondary" href="mailto:info@squaremcp.com">Contact</a>
</div>
</div>
</nav>
<h2>What SquareMCP is</h2>
<p>SquareMCP is a personal MCP server platform that connects AI assistants to your own tools — email, notes, and internal systems. It is operated by Garfield Heron and is currently in private pilot.</p>
<main class="legal-main">
<article class="legal-card">
<div class="legal-eyebrow">Legal</div>
<h1 class="legal-title">Privacy Policy</h1>
<p class="legal-subhead">Last updated May 5, 2026</p>
<h2>Data we collect</h2>
<p>We collect only what is necessary to operate the service: your name, email address, company, and use case when you submit a pilot request. This information is stored securely and used only to evaluate and onboard pilot participants.</p>
<section class="legal-section">
<h2>Scope</h2>
<p>
This Privacy Policy describes how SquareMCP collects, uses, and protects information
when you visit squaremcp.com, contact us, or participate in a SquareMCP pilot or
managed deployment.
</p>
</section>
<h2>Data we do not collect</h2>
<p>SquareMCP does not use analytics, advertising trackers, or third-party data sharing of any kind. We do not sell or rent your information.</p>
<section class="legal-section">
<h2>Information we collect</h2>
<p>We may collect:</p>
<ul>
<li>contact details such as your name, work email, company, and role</li>
<li>pilot intake details such as your use case, target systems, and security requirements</li>
<li>service and operational data needed to provision, secure, and support a deployment</li>
<li>communications you send to us by email or through the pilot intake form</li>
</ul>
</section>
<h2>Your data and your tools</h2>
<p>When you use SquareMCP to connect your own accounts (email, notes, calendars), those connections are authenticated via OAuth and run entirely within your own environment. Your data does not pass through SquareMCP infrastructure — the MCP server runs on your own host or a host you control.</p>
<section class="legal-section">
<h2>How we use information</h2>
<p>We use information to:</p>
<ul>
<li>review and respond to pilot requests</li>
<li>configure and operate SquareMCP deployments</li>
<li>authenticate access, troubleshoot issues, and maintain security controls</li>
<li>communicate about pilots, support, billing, and service changes</li>
</ul>
</section>
<h2>OAuth tokens</h2>
<p>OAuth access tokens used to authenticate AI sessions are stored in a private database on your server. They expire after 24 hours and are never shared with third parties.</p>
<section class="legal-section">
<h2>Customer data and connected systems</h2>
<p>
SquareMCP is designed to act as a managed MCP gateway for internal tools. Depending on
the deployment, customer data may remain in a customer-controlled environment or may be
processed in SquareMCP-managed infrastructure as part of the service. The exact data
path depends on the deployment architecture and connector configuration.
</p>
<p>
Pilot and production customers are responsible for evaluating which systems they choose
to connect and which tool permissions they enable for their users and agents.
</p>
</section>
<h2>Contact</h2>
<p>Questions or requests: <a href="mailto:garfield@fetcherpay.com">garfield@fetcherpay.com</a></p>
</body>
<section class="legal-section">
<h2>Authentication credentials and tokens</h2>
<p>
SquareMCP may process API keys, OAuth credentials, session metadata, audit records, and
related access-control data needed to operate the service. We use these credentials only
to authenticate approved integrations and support the configured deployment.
</p>
</section>
<section class="legal-section">
<h2>Sharing</h2>
<p>
We do not sell personal information. We may share information with infrastructure,
hosting, email, or support providers only to the extent reasonably necessary to run the
service, support customers, comply with law, or protect SquareMCP and its users.
</p>
</section>
<section class="legal-section">
<h2>Retention</h2>
<p>
We retain information for as long as reasonably necessary to evaluate pilots, deliver
services, maintain records, and meet legal, operational, or security obligations.
</p>
</section>
<section class="legal-section">
<h2>Security</h2>
<p>
We use reasonable administrative, technical, and operational measures to protect
information. No system can guarantee absolute security, and you should not submit
information through the service unless you are comfortable with that risk profile.
</p>
</section>
<section class="legal-section">
<h2>Your choices</h2>
<p>
You may contact us to request access, correction, or deletion of personal information we
hold about you, subject to legal and operational limits.
</p>
</section>
<section class="legal-section">
<h2>Contact</h2>
<p>
Questions about this Privacy Policy can be sent to
<a class="footer-link" href="mailto:info@squaremcp.com">info@squaremcp.com</a>.
</p>
</section>
<div class="legal-note">
This page is a general website and pilot-stage privacy policy. It should be reviewed and
adapted if SquareMCP moves into broader commercial availability or regulated deployments.
</div>
</article>
</main>
</body>
</html>