Use it. Don't abuse it.
Effective: 2026-05-21 · Last updated: 2026-05-21
The 30-second version
- Use the extension for your own calendars. Personal scheduling, contractor gig management, juggling multiple employers. That is exactly what it is built for.
- Don't resell or redistribute it. Building a service on top of our extension or bundling it into another product is not allowed.
- Don't use bots or scrapers against our infrastructure. The license server handles lightweight key checks, not bulk automated requests.
- We warn before we restrict. If something looks off, we will reach out first. Nobody gets cut off without notice unless the abuse is severe.
- Questions? Just ask. Email [email protected] if you are unsure whether your use case qualifies.
1. What "fair use" means here
This is not the copyright doctrine. This is our plain-English policy about how manyCalendars is intended to be used, and the boundaries we set to keep the product fast, affordable, and sustainable for everyone.
We built this tool for individual contractors, freelancers, and professionals who need to see all their calendars in one place. The pricing, infrastructure, and feature set all assume that kind of use. This policy exists to make sure that assumption holds.
2. Permitted uses
You are welcome to use manyCalendars for:
- Personal calendar management across any number of calendar providers (Google, Outlook, Apple, corporate OWA, ICS feeds, etc.)
- Multiple employers or clients. If you are a contractor working three gigs simultaneously, that is a perfect use case. Add all three calendars.
- Complex, multi-role schedules. We do not judge. Your scheduling complexity is your business, not ours.
- Freelance and agency work. Designers, developers, consultants managing project calendars across multiple client accounts.
- Personal and professional overlap. Combining your personal Google Calendar with your corporate Outlook is fine and expected.
- Team visibility (coming soon). When shared overlay features launch, sharing your availability with a small team is an intended use.
3. Prohibited uses
The following uses are not permitted under any plan:
- Reselling or sublicensing. You cannot sell access to manyCalendars, bundle it as part of a paid product, or offer it as a managed service to third parties.
- Automated syncing services. Using the extension (or its underlying code) to build a calendar-syncing pipeline, data-extraction service, or monitoring tool for someone else's calendars.
- Using it as infrastructure for another product. If your product depends on manyCalendars running in the background to function, that is not fair use. Contact us about an OEM license instead.
- Circumventing paid tiers. Sharing a single Pro license across multiple people, using automation to reset trial periods, or patching the extension to bypass license checks.
- Bulk account creation. Creating multiple free accounts to avoid upgrading to a paid tier.
- Attacking our infrastructure. Load testing, DDoS, or any deliberate attempt to degrade the license server or marketing site.
4. Rate limits
The extension makes one license-check request per day. That is the only request it makes to our servers. There is no practical rate limit for normal use because normal use generates almost no server traffic.
If we detect abnormal request patterns from a license key (hundreds of checks per hour, requests from dozens of different IPs simultaneously, or automated probing), we reserve the right to throttle or temporarily suspend that key while we investigate.
ICS feed fetches go directly from your browser to your calendar provider. We are not in that loop and do not impose limits on those requests.
5. Enforcement approach
We believe in proportional responses. Here is how we handle violations:
- Step 1: Notice. We email you explaining what we observed and ask you to stop or clarify within 14 days.
- Step 2: Restriction. If the behavior continues after notice, we may downgrade your account to the Free tier or temporarily suspend your license key.
- Step 3: Termination. Repeated or severe violations (attacking infrastructure, large-scale redistribution) may result in permanent account termination without refund.
We skip directly to Step 3 only for deliberate, malicious activity. A contractor who accidentally bumps into an edge case will always get a conversation first.
6. Edge cases and good faith
If you are doing something you think might be close to the line, email us before you do it. We are happy to clarify, and we have yet to say no to a reasonable request from an individual user.
Examples of things that are fine but might feel ambiguous:
- Using the extension on both your personal laptop and your work laptop (same person, same license = fine)
- Adding 15+ ICS feeds (you paid for Pro, use it)
- Running the extension in a Citrix or VDI environment for your own use
- Recommending the extension to coworkers (thank you, but each person needs their own account)
7. Changes to this policy
If we change this policy in a way that restricts currently permitted uses, we will give at least 30 days notice by email. We will not retroactively punish behavior that was allowed when you did it.
8. Contact
Fair use questions: [email protected]
OEM / enterprise licensing: [email protected]