MeetZone — Privacy & Acceptable Use

Product: MeetZone — Timezone Meeting Overlap API · Version 0.1.0 · Updated 2026-09-23

What MeetZone does

MeetZone computes overlapping meeting windows across public IANA timezones using deterministic scheduling math. Inputs are timezone identifiers, civil dates, and local clock times (work hours / duration). Outputs are UTC intervals, per-zone local times, and an optional ICS snippet.

What MeetZone does not do

• Does not connect to Google Calendar, Microsoft Outlook, Apple Calendar, or any private calendar
• Does not scrape calendars, free/busy feeds, email, or contacts
• Does not require OAuth or end-user identity
• Does not infer personal availability beyond the zones and windows you supply
• Does not sell personal data (none is required to use the API)

Data you should send

• IANA timezone IDs (e.g. America/Denver)
• Dates (YYYY-MM-DD) and local HH:mm work windows
• Meeting duration in minutes

Data you should not send

• Names, emails, phone numbers, or other PII (not needed)
• Calendar event contents, attendee lists, or private notes
• Access tokens or credentials for third-party calendar systems

Data sources

Timezone conversions use the public IANA Time Zone Database as exposed by the JavaScript runtime’s ICU / Intl implementation on Cloudflare Workers. MeetZone ships a curated city→IANA search index for discovery; unknown-but-valid IANA ids are still accepted when Intl validates them.

Logging & retention (Day-1 posture)

• Provider infrastructure (Cloudflare / RapidAPI) may retain standard request metadata (timestamps, status codes, IP via proxy, rate-limit counters) for abuse prevention and billing.
• Do not put secrets or PII in query strings or JSON bodies.
• Daily unique visitors (homepage and the free MCP endpoint at /mcp only): a salted, daily-rotating hash of your network (IP, IPv6 grouped by /64) is kept for up to 9 days to count unique visitors per day. No IP address, user agent or request content is stored. Fleet, monitoring and health-check traffic is not counted.
• MeetZone application logic does not persist request bodies to a product database in Day-1 MVP.

Acceptable use

Allowed: scheduling automations, SaaS demo/interview slot suggestions, internal bots, education, research, and legitimate product features built on public timezone math.

Prohibited:

• Attempting to reconstruct private calendars or surveil individuals
• Abuse, credential stuffing, or bypassing RapidAPI rate limits
• High-volume scraping of the API beyond plan quotas
• Using the service for unlawful activity

Contact

Privacy and support questions: digitalpromohub.support@gmail.com. You can also reach us through RapidAPI Hub messaging.