What it is for
Teachers plan around the school calendar: holidays, breaks, professional development days, early releases, field trips, and testing windows. Most schools already publish those days on a Google Calendar. Lumerell’s Import from Google Calendar button lets you bring those days into your curriculum map in one step, so a planned week automatically skips a holiday and a substitute plan knows an early-release day is short.
The import is optional. Lumerell works fully without it; you can add every one of those days by hand instead.
The permissions Lumerell asks for
When you click Connect Google Calendar, Google shows its own permission screen for the Lumerell app. It asks for two read-only permissions and nothing else:
| Permission | Why |
|---|---|
| See the list of Google calendars you’re subscribed to | So you can pick which calendar to import from — for example your school’s shared “District Calendar” rather than your personal one. Lumerell reads each calendar’s name, identifier, and whether it is your primary calendar, shows you that list, and does not store it. |
| View events on all your calendars (read-only) | So Lumerell can read the events on the one calendar you picked, for the date range you choose. This is the only permission that reaches event data, and it is read-only: Lumerell cannot create, change, or delete anything on your calendar. |
Lumerell does not ask for write access to your calendar, for Gmail, for Google Classroom, or for general access to your Google Drive.
Step by step
- Open a month of a course’s curriculum map, click Actions ▾ beside the course name, and choose Import from Google Calendar. A dialog explains, before anything is connected, what will be read and what will be saved.
- Click Connect Google Calendar. Google’s permission screen opens in a pop-up. You can close it to stop here.
- Choose a calendar from your list, choose a From and To date, and choose whether the days apply to all your courses or just this one.
- Click Find events. Lumerell reads the events on that calendar between those dates and shows them to you as a list. Days that look like school-calendar days (for example “No School” or “Early Release”) are ticked already; anything Lumerell did not recognize is left unticked.
- Untick anything you do not want, then click Add N days (the button counts what you ticked). Only the ticked days are saved. Nothing is saved before this click. If a ticked title looks like it is about a particular student (for example “Jordan’s IEP meeting”), Lumerell asks you to check first, and you can untick that day before anything is added.
Exactly what is read from each event
Lumerell asks Google for only these fields, and Google sends nothing else: the event’s title, its start and end dates (and whether it is an all-day event), its status (so canceled events can be skipped), and its Google event identifier.
Lumerell does not read event descriptions, locations, attendees, organizers, attachments, conferencing links, reminders, or colors. Recurring events are expanded into their individual dates so a weekly PD day lands on every week it happens.
What is saved, and where
For each day you tick, Lumerell saves a school-calendar day in your own curriculum map: the title, a day type such as “No School” or “Field Trip”, the dates, and the Google event identifier. The identifier is kept so that a later import can recognize the same event and update it rather than create a duplicate.
The list of your calendars and the events you did not tick are shown to you and then discarded. The reading happens in your browser; only the ticked days are sent to Lumerell’s servers. Saved days are private to you, the same as everything else in your map, and you can edit or delete them at any time. Days you have already edited by hand are never overwritten by a later import.
Because the saved days are part of your map, Lumerell’s drafting features can see their titles and types — for example, when you ask for a planned week, the AI provider is told which days are “No School” so it can skip them. Our Privacy Policy lists the providers involved and what each one receives.
How access works, and how to remove it
Connecting gives your browser a short-lived access token from Google that expires after about an hour and is then discarded. It is never sent to or stored on Lumerell’s servers, and Lumerell holds no long-term credential, so it cannot reach your calendar in the background or when you are not using the import.
You can remove Lumerell’s access at any time at myaccount.google.com/connections. Because nothing is stored on our side, that removal is complete. The days you already imported stay in your map until you delete them; deleting your Lumerell account removes them too.
What Lumerell never does with your calendar
- Never creates, edits, or deletes a Google Calendar event.
- Never reads a calendar you did not select, or dates outside the range you chose.
- Never reads descriptions, locations, attendees, or attachments.
- Never stores your calendar list, or events you did not tick.
- Never stores a Google credential, and never syncs in the background.
- Never shares your calendar data with another Lumerell user, school, or district.
- Never uses your calendar data for advertising, or sells it.
See also our Privacy Policy and Terms of Service.