Remoteteam

What Remoteteam is for

"What hours actually overlap across our team's timezones", "should this be a meeting or can it wait for async", "how do we onboard someone remotely without it feeling like an afterthought" — a distributed-team management reference built around one piece of real computation (timezone overlap) plus hand-curated practices for the rest.

What it does

timezone_overlap_window takes two or more team members, each with a timezone (an IANA name like America/New_York is preferred — it's resolved against the real tz database so DST is correct for the date you give it — or a plain numeric UTC offset like +5:30) and a local work-hour window (default 09:00-17:00), and computes the actual overlapping window(s) in UTC by scanning the day at your chosen resolution and checking, at each slot, whether every member is inside their own working hours — correctly handling a window that wraps past midnight in UTC. It reports a genuinely narrow or nonexistent overlap honestly, with each member's own local-time view of any overlap found. async_communication_norms gives urgency-tiered response-time expectations (urgent/blocking, normal, FYI) and norms for documenting decisions in writing, writing for a time-shifted reader, and treating silence within the agreed window as normal rather than a reason to escalate. meeting_vs_async_decision is a decision framework — pass a keyword describing a situation (brainstorm, status update, sensitive feedback, ...) to get a matched recommendation with reasoning, or pull the full table. remote_onboarding_checklist covers the remote-specific logistics of onboarding (equipment and access before day 1, a synchronous welcome and access verification on day 1, 1:1 video intros and an early real task in the first two weeks, cross-team exposure in the first 90 days) — distinct from a full 30/60/90-day role-based plan. distributed_team_culture_guide covers practices for building culture on a distributed team: protecting shared overlap time, engineering low-stakes social space, documenting rituals, making recognition visible and async-friendly, rotating meeting-time pain across timezones, and periodic higher-bandwidth touchpoints.

What it is not

The timezone-overlap calculation is genuine timezone math (real tz-database offsets, real interval scanning with midnight-wraparound handling) — but it only knows what you tell it about each member's normal working hours; it can't account for someone's actual calendar, PTO, or a one-off schedule change. Everything else here is a hand-curated management reference, not a policy this connector enforces or a guarantee of team dynamics — treat it as a starting point to adapt to how your specific team actually works, and to talk through with your teammates rather than impose.

Remoteteam — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Remoteteam is. Remoteteam is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for distributed-team management reference and a timezone-overlap calculator. You interact with your assistant; the assistant sends us only the arguments needed for that one tool call.

What we receive. The arguments of each tool call — which may include team members' first names or labels, timezones, and work-hour windows, or a keyword for a reference lookup — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

We do not store, log, or retain the team/timezone details you submit. Every tool computes on the data you send in memory, for that one request, and returns a result — nothing about your team's makeup, member names, or timezones is written to a database, written to a request log, cached, or used to train anything. Request bodies are not logged.

What we do not receive or store. We do not receive your conversation with the assistant, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps, never the request content) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — there is no upstream call at all; every tool either computes locally or reads from a reference table bundled with the server. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived, content-free logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Remoteteam is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Remoteteam — Terms of Service

Effective 28 September 2026. These terms govern use of the Remoteteam connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Remoteteam provides distributed/remote-team management reference material and a real timezone-overlap calculator, computed or looked up entirely on our server. It is accessed through an AI assistant or directly over MCP or HTTP.
2. General information, not HR, legal, or employment-law advice. Remoteteam's output is a management drafting aid and reference tool based on generally known distributed-team practices. It is not HR, legal, or employment-law advice, and nothing it generates should be treated as a final policy without your own review and, where appropriate, qualified professional input.
3. Timezone calculations depend on your inputs. The overlap calculator only knows the working-hours windows and timezones you supply; it cannot account for an individual's actual calendar, time off, or one-off schedule changes.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your input is answered on our server and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/remoteteam

Remoteteam support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://remoteteam.connectorbay.com/mcp
• REST API: https://remoteteam.connectorbay.com/openapi.json
• Live status: https://remoteteam.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Remoteteam never asks for them.