Meeting Fairness

What Meetzone is for

"Is 9am Eastern actually fair to our Singapore teammate, or are we just used to it?", "whose turn is it to take the bad slot?", "does our team have any hour that works for everyone?" — Meetzone is deliberately not a timezone-conversion or meeting-slot-finder tool. Pair it with a timezone/scheduling connector for "what time is it there" or "find an open slot" — Meetzone starts from a time you already have in mind (or a set of candidate times) and judges, distributes, and audits its fairness across a distributed team.

What it does

inconvenience_score scores one proposed UTC hour against each teammate's local time, classifying it as core hours, early-or-late, very-early-or-late, or overnight, and names who is most burdened. rotate_schedule takes two or more candidate times for a recurring meeting and spreads them across future occurrences so the inconvenient slot rotates between teammates instead of always landing on the same person, reporting the bounded fairness spread it achieved. burden_tracker tallies cumulative discomfort from a history of past meeting times and tells you who is owed the convenient slot next. core_hours_policy scans all 24 UTC hours against your team and reports which are universally reasonable, which need rotation, and which force someone overnight no matter what. meeting_load_report audits an existing set of recurring meetings for lopsided off-hours load per teammate.

async_vs_sync_guide recommends sync, async, or hybrid for a meeting's stated purpose (status update, decision needed, brainstorm, relationship-building, complex review, simple informational), adjusted for how spread out the team's hours are. equity_checklist, timezone_etiquette_glossary, and facilitation_tips_for_mixed_hours round out a hand-curated reference on running a fair, well-facilitated meeting across time zones.

What is computed vs. hand-curated

Local-hour math uses the Python standard library's zoneinfo (IANA time zone database) — real, standard timezone arithmetic, not a lookup table. The discomfort-tier thresholds (which local hours count as core/early-late/very- early-late/overnight) are a hand-curated, clearly labeled heuristic, not an external or universal standard. Scoring, rotation, burden tracking, policy scanning, and load reporting are all computed locally from the teammates and times you provide — nothing is invented about your team. The equity checklist, glossary, and facilitation tips are hand-curated reference content.

What it is not

Meetzone does not tell you what time it is somewhere, does not search for an open calendar slot, and is not a calendar integration — it has no access to any calendar and reads only what you send it in each call. It also does not decide policy for you: core_hours_policy and rotate_schedule surface the fairness tradeoffs; the team still has to agree on which tradeoff to accept.

Meetzone — Privacy Policy

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

What Meetzone is. Meetzone is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local meeting-fairness and etiquette tool for distributed teams — deliberately not a timezone-conversion or meeting-slot-finder tool — scoring how inconvenient a proposed UTC hour is per teammate, rotating a recurring meeting's slot fairly across occurrences, tracking cumulative burden, scanning for universally reasonable core hours, auditing an existing meeting set's off-hours load, and hand-curated async-vs-sync, equity, glossary and facilitation reference. You interact with your assistant; the assistant sends us only the text or values needed for that one response.

What we receive. the arguments of each tool call — teammate names and IANA time zone names, proposed or candidate meeting times, a meeting-purpose description, or a term/scenario name to look up, 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.

Everything is answered locally and nothing is stored. Local-hour classification uses the Python standard library's zoneinfo (IANA time zone database); scoring, rotation, burden tracking, policy scanning, and load reporting are computed locally from the teammates and times you send us; equity checklist, glossary and facilitation content is answered from a bundled hand-curated reference file — there is no upstream call at all; no request is forwarded to any third party, and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant, your name, contacts, or account credentials, and we do not build a profile from your queries — each request is answered independently and nothing carries over between requests. Teammate names and time zones you send us are used only to compute that one response and are not logged, retained, or used for anything else.

Rate-limit counters (a client identifier and timestamps) 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 — every tool is computed or answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived 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. Meetzone is a general-audience scheduling-fairness reference tool operated by the adult using the assistant.

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

Meetzone — Terms of Service

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

1. The Service. Meetzone returns meeting-time fairness scoring, fair rotation of a recurring meeting's slot across occurrences, cumulative burden tracking, core-hours policy scanning, and an off-hours load audit, all computed from your own input, plus hand-curated async-vs-sync, equity, glossary and facilitation reference. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Not professional advice. Meetzone provides general information, templates and reference material — it is not legal, financial, tax, HR, or other professional advice, and using it does not create any professional relationship. Verify anything consequential against authoritative sources or a qualified professional before relying on it.
3. Not a timezone-conversion, scheduling, or calendar tool. Meetzone does not tell you what time it is anywhere, does not search for an open slot, and has no access to any calendar — it only judges the fairness of times and teammates you supply yourself. Pair it with a dedicated timezone/scheduling tool for conversion or slot-finding.
4. Fairness heuristics, not team policy. The discomfort tiers and rotation logic are a labeled heuristic to inform a decision your team still has to make and agree to together.
5. Acceptable use. Automated use within the published rate limits is welcome.
6. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
7. Data. Our Privacy Policy describes what we process. In short: your input is answered on our server and nothing is stored.
8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
9. 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.
10. Governing law. California law; venue in San Mateo County, California.
11. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/meetzone

Meeting Fairness support

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

• MCP endpoint: https://meetzone.connectorbay.com/mcp
• REST API: https://meetzone.connectorbay.com/openapi.json
• Live status: https://meetzone.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. Meeting Fairness never asks for them.