
Turn an event on any page into a prefilled calendar entry.
The short version
Calendify reads one page, proposes one calendar event, and shows it to you before anything happens. It has no account, no server of ours and no database.
With neither, Calendify still works: the form is filled from the page’s own structured markup and you type in the rest.
Nothing leaves until you ask for an event, and then only if you have pasted in an API key and the page’s own markup did not already give a title and a date. Calendify then sends Google:
It does not send the page source, images, cookies, form contents, other tabs or anything from any other page. Selecting the event text first is the narrower option and the more accurate one.
On Google’s free Gemini API tier, Google may use what is sent to improve its models. If what is on screen is confidential, use the built-in model, select only the event text, or fill the form in by hand.
chrome.storage.local, in this Chrome profile.generativelanguage.googleapis.com, as the request header Google’s API requires.No analytics, tracking, telemetry or crash reporting. No browsing history is collected. No account or sign-in, and no server operated by us.
Calendify never writes to your calendar and never asks for access to it. It builds a Google Calendar link with the fields filled in and opens it, and you press Save. Nothing is created unless you do. Details a model inferred rather than read off the page are marked as inferred in the event description, so check them before you save.
contextMenus: the right-click Calendify option.activeTab and scripting: read event details from the page you are looking at, when you ask.storage: holds your API key if you set one, and passes the event details to the popup.notifications: confirms when the event is ready.We may update this privacy policy from time to time. We will notify you of any changes by posting the new policy on this page and updating the “Last Updated” date.
Questions about this policy? Reach us at spark-apps.co.