Reading a calendar tab: how does that work?
The extension reads what is already on a calendar page you opened in your own browser, the same content your screen reader sees. There is no remote server, no automated login, and no stored credentials. It only ever reads calendars you add yourself.
Because nothing connects through a third-party cloud, there are no OAuth grants and no connected-app entries in any admin console.
How is this different from CalendarBridge, Reclaim, or Motion?
Those tools need API access to your calendars. When IT blocks third-party API access, which most enterprise IT departments do, they stop working. manyCalendars works without API access by reading the calendar tabs you already use, and it stores everything on your device instead of in a cloud.
Is my data private?
Your calendars are read and merged on your device, not in our cloud. No tracking, no telemetry, no ads, no data sold. The only network call a paid plan makes is a license check to confirm your subscription. We do not see your calendar data.
Do I need to know how to code?
No. Install the extension, click "Add calendar," paste an ICS URL or pick a tab. That's the whole flow. No webhooks, no JSON, no API keys.
Mac, Windows, Linux, Chromebook?
All of them. If Chrome or Firefox runs on it, our extension runs on it. macOS, Windows, Ubuntu, Fedora, ChromeOS - doesn't matter.
Can I cancel anytime?
Yes. Cancel from inside the extension or email us. You keep Pro until the end of your billing period, then drop to Free. Your local data stays put - we don't touch it.
Is manyCalendars safe? What can it actually read?
At install, nothing: the extension ships with no blanket host access, so it cannot read any website until you act. When you add a calendar, your browser asks permission for that specific site, in context, and you can revoke it any time. It reads the events drawn on the calendar pages you added, keeps them in local storage on your device, and transmits none of it to us. Full breakdown on the security page.
Can I use it without violating an NDA or client confidentiality?
An NDA problem starts when client information reaches a third party. Cloud calendar tools transmit meeting titles and attendees to the vendor's servers, and that is the disclosure your contract restricts. manyCalendars discloses nothing to anyone, including us: the merge happens in your browser, on data your client's IT already shows you. We are not your counsel, so read your engagement letter, but the security page has the full analysis, including the lawyer-specific one.
Do you sell my data or train AI on it?
No. We make money one way: subscriptions. No ads, no analytics, no telemetry, no data sales, and no AI training, because there is no server holding your events, so nothing is available to train on. The free tier makes zero network requests to us; paid plans make a license check carrying only your account email and license status. Verify it yourself.
manyCalendars