Privacy Policy

1. Who we are

Lumerell is a teaching and curriculum-planning application operated by Open Meadow LLC, a Massachusetts limited liability company (“Open Meadow”, “we”, “us”, “our”). This policy explains how we handle information when you visit Lumerell, use an account, connect Google services, or contact us.

For privacy questions or requests, email hello@openmeadow.io.

2. Information we collect

We process the information you give us and what is needed to run the features you use:

• Account information. Your email address and, when you sign in with Google, the name, Google account identifier, and profile picture Google supplies. You can also sign in with an emailed link instead of Google. In Settings you may add your name, your school’s name, and teaching preferences; all of that is optional.
• Access list. Lumerell is only open to schools and districts working with Open Meadow. To decide who may create an account, we keep a list of email addresses and school email domains (such as “district.org”). School and district leaders can add addresses on their own district’s email domains by inviting someone in Lumerell; we add any others when a school or district asks. We use it only for that. If an address is not on the list, no account is created; the attempt appears only in the standard technical records described below.
• Your work. Courses, units, curriculum calendars, lessons, worksheets, substitute packets, files you attach to a packet, reflections, professional goals, review results, and the instructions you type or say to drafting features.
• Support messages. What you send us when you ask for help.
• Technical records. Standard connection records kept by our hosting and database providers (such as IP address, browser and device details, timestamps, and error logs), and a record of each drafting request (which feature ran, which provider, how long it took, how much text it used, whether it succeeded). That record never contains the text of your request or the result.
• Voice. Audio you record when you press a microphone button, handled as described in section 5.
• Usage. Not collected today. If we turn on usage analytics, it will record which pages you visit and which buttons you use, so we can see what helps and what confuses. See sections 6 and 10.

3. Information from Google

When you use a Google feature, Google asks you to authorize it. Each permission does one job:

The three integration permissions above are Google scopes under https://www.googleapis.com/auth/. Google’s events permission can technically permit access to events on any calendar you can access. Lumerell’s interface and API requests use that permission only for the calendar you select and the date range you choose (or, for a leader’s Meetings, your primary calendar for the next 30 days), and ask Google for only the event fields listed above.

How access works. Each Google feature asks for a short-lived access token that lives only in your browser for about an hour and is then discarded. It is never sent to or stored on our servers, and we hold no long-term credential, so Lumerell cannot reach your Google account in the background. Your Google password is handled by Google and is never seen by Lumerell. Lumerell does not request Gmail, Google Classroom, or general Drive access.

4. How we use information

We use information to run your account; save and organize your teaching work; provide the planning, drafting, review, and export features you ask for; support the Google connections described above; answer support requests; keep the service secure; and tell you about relevant changes to the service or this policy.

We do not sell or rent your information, or use it for advertising.

Google information is used only for the features described here. We do not use it for marketing, advertising profiles, or resale.

5. Drafting and voice features

Some features draft or check material for you: a worksheet, a week of lessons, a re-planned day, a review of a unit. To do that, Lumerell sends the instruction you gave and the relevant parts of your work to a provider that generates the response. You stay in charge of your plans. Suggestions wait for you to apply them. When you ask Lumerell to make a change for you, like planning your week by voice, it tells you what it changed, and Undo last action puts it back.

• Anthropic generates written drafts and reviews. It receives your instruction and the relevant teaching content — which can include plans you imported from Google Drive files and the titles and types of school-calendar days you imported from Google Calendar (for example, so a drafted week skips a holiday). When a teacher runs a review against their district’s checklist, Anthropic also receives that checklist: its name and each item’s title and description. When you ask for an article for a lesson, a short topic description (never your name, school or anything about students) goes to Anthropic, which searches a fixed list of educational sites; our server then opens the page it picked to check that it can be read. When you or your students open the link, you go to that site directly, and its own privacy policy applies.
• OpenAI draws worksheet illustrations from a short description of the picture, and turns voice recordings into text. It never receives a Google file or calendar. A picture description can be written by you, or drafted by Lumerell from the worksheet’s teaching content — and that content may have started as a plan you imported from Google Drive. Only the short description is sent — never the rest of the worksheet, and never anything about you or your students. When Lumerell makes a new worksheet, it may draw up to two of its pictures straight away (up to four for a new presentation); you can read each picture’s description beside it, and redraw or remove it. Pictures are only ever drawn when you create a worksheet or presentation, or press Draw.
• OpenRouter helps give some of Lumerell’s spoken replies a natural-sounding voice using the open Kokoro voice model. It receives only sentences Lumerell writes itself, such as a summary of the days it just planned. It never receives your voice recording, anything you said or typed, or your Google files, calendar, name, or account information. Requests are routed only through providers configured not to retain them or use them for model training. OpenRouter deletes the text and audio promptly after the voice is made, except where the law or preventing misuse of its service requires otherwise. Lumerell does not store the generated audio, and if the service is unavailable, your browser’s built-in voice may be used instead.
• DeepInfra converts Lumi’s written replies into speech, using the open Kokoro voice model. It receives the text of each sentence Lumi is about to say. That text can include details from your plans, such as a lesson title or a date, or your name if Lumi says it. Lumerell does not send DeepInfra your account profile or your Google sign-in information, and Lumerell does not keep the audio. DeepInfra’s terms say it does not use this text to train models and deletes it after processing, with limited exceptions such as records kept for security, abuse prevention, or legal reasons (see DeepInfra’s privacy policy). If the voice service is unavailable, your browser’s speech feature may read Lumi’s reply instead.

Our agreements with these providers are their business API terms, under which they do not use what we send them to train their models. We do not use information obtained through Google APIs — nor anonymized or derived versions of it — to develop, train, or improve general-purpose or other non-personalized machine-learning models, and we do not allow our providers to.

Voice. The microphone opens only after you press a microphone button (on “Plan by voice” it opens right after Lumerell has asked you its question aloud, using Lumerell’s recorded voice or your browser’s own voice). Your recording is sent to OpenAI to be turned into text, then discarded; Lumerell does not keep the audio. The text becomes your instruction, and stays only if you keep what it produced. Please avoid recording students or reading out confidential student information.

Lumi. Lumi is a helper you can talk to from any page. It listens only after you press its microphone. Your recording is sent to OpenAI to be turned into text, then discarded; Lumerell does not keep the audio. Anthropic receives that text, together with the parts of your plans Lumi needs to answer: for example, upcoming lessons, the lessons on the page you are viewing, and, when you ask Lumi to replace a lesson, relevant details from recent lessons in the same class. Lumi’s access is limited by your existing Lumerell permissions. When you ask for a change, Lumi makes it and tells you what it did, and you can undo Lumi’s most recent change. When you tell Lumi how a lesson went, it can add that to the day’s “How it went” note or record what the class didn’t get, and Undo takes it back. To do that, and to read a note back to you, Lumi sends Anthropic the words of the note with student names, your name, and your school’s and district’s names taken out, and never your email address. Anthropic keeps that text for 30 days and doesn’t use it to train models.

Meetings. A leader can build meeting slides from documents they upload. Uploads are sent to our AI provider to draft the slides, read once, and not stored; only the finished slides are kept, until the leader deletes them or their account. Please don’t upload student records or personnel files. Lumerell never shows meetings about individual students when you pick from Google Calendar.

6. Who receives information

Our service providers each handle the part of Lumerell they deliver:

• Vercel hosts the application in the United States (Washington, D.C. region) and keeps its standard request and error logs for 30 days.
• Supabase stores your account, your work, imported school-calendar days, Google Doc links, packet attachments and worksheet illustrations, runs sign-in, and sends the sign-in link and invitation emails. Our database is in the United States (AWS us-east-1).
• Google provides sign-in and the Drive and Calendar connections you authorize, and, when you ask Lumerell to find a video, YouTube search. Only a few search words are sent, from our server — never your name, your account, or your plans.
• Anthropic, OpenAI, OpenRouter, and DeepInfra, as described in section 5.
• PostHog (usage analytics) is not currently turned on in Lumerell, so it receives nothing. If we turn it on, it will receive usage events (page views, button use, and whether a drafting request succeeded) tied to your account, in its United States region, and we will update this policy first. It will never receive your teaching content or the text of a request: the text on anything you click is masked, web addresses are sent without their search terms, page titles are not sent, and Lumerell does not record your screen or your session.

Lumerell learns with you. To offer timely help, such as setting up a review game before a test the way you did before your last one, Lumerell looks at your own work when you open Today or a month of your map, and, if drafting help is on, when you press Generate:

• your units and lessons
• the kinds of materials you made and when
• your calendar
• your “Next time” notes, reflections, and goals (unless you turn them off)

To show how your classes did on different kinds of quizzes and tests, it also reads what you’ve recorded a class didn’t get and the text of your own Lumerell quizzes, tests and other assessment materials. This happens on our servers with no AI; nothing is sent anywhere, and the sorting isn’t saved — it’s worked out fresh each time.

This happens on our servers each time. It does not use an AI provider, and it does not keep a separate copy of your notes. What it stores is limited to:

• your choices in Settings
• suggestions you’ve asked it not to show
• which material you made for which assessment, when you set one up from a suggestion

None of these contain the text of your notes.

By default this is on, and drafting help is off. You can turn any part of it off, see why a suggestion appeared, or reset what Lumerell has learned in Settings → Lumerell learns with you. Resetting means earlier activity is never used again. It does not delete your materials, notes, or goals.

This is private to you. School and district leaders, colleagues, and anyone you share with cannot see it, and it never feeds district reports, Insights, or shared curricula. Like all your data, it is stored in our database, and people who operate our infrastructure have the technical access described in section 8.

If you turn on Use what Lumerell learns when drafting, up to three short sentences Lumerell writes from fixed templates, such as “The teacher wants to use more vocabulary activities.”, are added to what is sent to Anthropic when you press Generate. Your notes and goals themselves are not sent, though a sentence may name the topic of a goal or a teaching approach you’ve written about.

Who else can see your work. Your work is private unless you share it, or unless your district uses the leader view described below. Nothing is shared automatically.

When you choose to share. You can share a course’s curriculum map, or something you created, with a colleague by their email address, or with everyone in your district. The people you share with can see what you shared, your name, and your email address. They can copy it into their own curriculum. If you allow it, they can also edit the days on a shared map. You can stop sharing at any time.

What never travels. Sharing never includes your reflections, “How it went” notes, professional goals, goal evidence, or what Lumerell has learned about how you work. From your calendar, only school closures travel with a shared map (for example “No School” or “Early Release”), shown by their standard name, never your own titles or notes. Your absences and personal entries never travel.

School and district records in our database hold your school’s name and, where your district works with Open Meadow, which district you belong to.

School and district accounts. If your school or district uses Lumerell, its leaders can see a list of the teachers they lead: name, email address, school, role, and the date you joined. They cannot see anything you have made unless the section below applies. Leaders can invite teachers (district leaders can also invite school leaders), cancel an invitation that hasn’t been used yet, change a teacher’s school or role, and ask for or approve wider access; we keep a record of those changes (who, what, and when, never your content) for as long as your district uses Lumerell.

When leaders can read your curriculum. Only if your district chose this when it signed up, a district leader has turned it on, and you have seen our notice and not kept yours private, your school’s leaders can read — never change — your courses, units, lessons, calendar, and the materials you have created. They never see your professional goals, goal evidence, reflections, “How it went” notes, sub plans, or review results. Days you were out show only as “Sub / Absent”, never why. You can turn this off at any time in Settings. A department head can be given the same read-only access to their own school, approved by a school leader, until June 30.

Goal progress totals. If your district chose it and a leader turned it on, and you choose to be counted, your goal progress is included in anonymous totals: how many teachers have a goal underway, and how many have completed one. The totals use only each goal’s status: never what your goals say, never your evidence, never your name, and never a group of fewer than 5 teachers. You can keep yours out at any time in Settings.

Priority standard counts. If your district has priority standards in Lumerell, chose coverage counts with Open Meadow, and a district leader turned them on, you can choose in Settings to be counted. You are not counted unless you choose to be. If you are counted, district leaders see, for each priority standard, how many counted teachers have a confirmed alignment to it in their own curriculum maps. An alignment marked “Not yet evident” does not count. A number is shown only when at least 5 counted teachers have an alignment and at least 5 don’t; otherwise leaders see “Fewer than 5” or “Nearly all”. Leaders see how many teachers are counted only as a range (5–9, 10–19, or 20 or more). Only classroom teachers are counted, never school or district leaders. Leaders see numbers only: never your name next to any number, which of your courses or lessons is aligned, or anything from your goals or reflections. If fewer than 5 teachers in the district are counted, leaders see nothing. A confirmed alignment is a record in your map, not proof that a standard was taught. Choosing to be counted does not change who can read your map. You can stop being counted at any time in Settings, and if you move to another district your choice is cleared. Each leader’s on/off change is recorded in the district’s change record; your own choice is recorded without your district, so leaders can’t see who chose.

District usage totals (paid add-on). If your district has bought the usage add-on from Open Meadow, your school and district leaders can see totals of how Lumerell is used across the schools they oversee: how many teachers have signed up, how many made a material or used an AI feature in the last 30 days, how many materials have been created of each kind, how many reviews have been run, and how many materials were created in each of the last six months. These are counts only. Leaders never see your name next to any number, never see what you made or how often you used Lumerell, and never see the titles or contents of your materials or reviews. Any number that would describe fewer than 5 teachers is hidden, and school-by-school numbers are hidden whenever a small school could be worked out from the district total. A leader can print these totals or download them as a spreadsheet (CSV) for their school board; the file holds the same totals shown on screen and nothing else.

Material your district gives us. A district may give us a default standards framework or its own review checklist, which a district leader can edit in Lumerell. We store it for that district’s teachers. When a teacher chooses to run that review, the checklist is sent with their lesson or unit to our AI provider, as described in section 5. Leaders don’t see teachers’ review results.

District guidance. If your district leader writes guidance for teachers (for example priority standards, a Portrait of a Graduate, a teaching framework, or local terms), we store that text with your district, and teachers in the district can read it in Settings. A leader can tag guidance with subjects and grades; Lumerell uses the tags only to show matching guidance first, and everyone in the district can still read all of it. It is for reference only: Lumerell never sends it or its tags to an AI provider, and it doesn’t change anything Lumerell makes. Every change a leader makes to it is recorded in the district’s change record. We also remember whether you’ve dismissed the notice about it, and nobody else can see that. Guidance is deleted when the district is.

District tools. A district leader can turn off some Lumerell tools for new materials in their district. Teachers still see those tools, marked “Turned off by your district”. Turning a tool off never hides, deletes, or changes anything a teacher has already made, and it gives the leader no access to teachers’ materials. Each change is recorded in the district’s change record with the tool and the leader who changed it.

District library. If your district’s leaders publish resources in Lumerell (links, or PDF files they upload), every teacher in that district can see and open them under “From your district” in their Library. Uploaded files are stored privately and opened only through short-lived links that only people in that district can request. Lumerell never fetches or previews a link; your own browser opens it. We do not record who opens a resource or how often. Each resource a leader adds, edits, or removes is recorded in the district’s change record. A district resource is published only when a district leader adds it; nothing a teacher or leader makes in Lumerell is ever added to the library automatically. Leaders are asked not to upload student records or personnel files. Resources are kept while the district works with us, and when a district leaves we delete its resources and uploaded files. When you choose Save to my Library, we make your own copy in your Library: its title, description, and link, or a copy of the PDF kept in your own private storage. That copy is yours: it stays if the district later removes the original, it is included in Download my data, and it is deleted when you delete it or your account. Leaders can group resources into named collections; a collection’s name and description are stored with the district, and deleting a collection never deletes its resources.

District priority standards. A district leader can mark official standards as district priorities and add a short note. We store these with your district, and teachers in the district see “District priority” beside those standards in their planning, with the note in their course summary. Lumerell never sends priorities or notes to an AI provider. Each priority a leader adds, edits, or removes is recorded in the district’s change record, with the standard’s code but not the note. Priorities are deleted when the district is.

Common assessments. A district leader can publish common assessment windows (a title, an optional description, subject and grade tags, dates, and optionally a district library resource). Teachers in the district see them in their Library, and a reminder may appear on a matching course’s month view. Lumerell never sends them to an AI provider. If you choose Add to My Calendar, we save an ordinary entry in your own calendar, linked to the district’s assessment so we can tell you if the district later changes it. That entry is yours: it stays if the district removes the original, it is included in Download my data, and your existing calendar-sharing settings apply to it, so anyone who can already see that calendar can see the entry’s title. Lumerell creates no report of who added an assessment. Leader changes are recorded in the district’s change record without the assessment’s text.

Feature settings from Open Meadow. Districts can have different Lumerell features. Open Meadow sets which features each district has, and keeps a record of each change (when, which features, and an optional short reason), with no teacher content in it. Turning a feature off never deletes or hides anything a teacher already made. Features your district doesn’t have may appear greyed out; how often you click a greyed-out button is counted only in your own browser and never sent to us. Open Meadow’s feature settings give Open Meadow no access to your curriculum or any other content.

For Google user data, we disclose to a provider or anyone else only what Google’s policies permit: delivering the feature you asked for, necessary security work, a legal obligation, or a business transfer for which you have given explicit prior consent. People at Open Meadow look at Google-derived content only with your express agreement for a support request, for a necessary security investigation, to comply with the law, or in aggregated, anonymized form.

7. Our Google-data commitments

We follow the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API user data policy.

We do not sell Google user data, give it to data brokers, use it for advertising or credit decisions, or transfer it for anyone’s general model training. Removing names or combining records does not lift these restrictions. Our providers and anyone acting for us must respect them too.

8. Storage and security

Information travels between your browser, our servers, and our providers over encrypted connections, and our database provider encrypts stored data. Every database read and write is restricted to the signed-in teacher who owns the record, enforced by the database itself. Files you attach to a substitute packet are kept in private storage reachable only through short-lived links; worksheet illustrations are stored where anyone with their link can view them, because they must print and export. Provider credentials are kept in server-side configuration and never reach your browser. No service can promise that every security incident will be prevented.

If your district adds its logo, we store that image and show it beside Lumerell to everyone in your district. The logo is stored at a public web address, as logos usually are; it contains nothing about teachers or students. District leaders can replace or remove it at any time, and adding, changing, or removing it is recorded in the district’s change record.

9. Retention, deletion, and disconnecting Google

We keep your account and your work for as long as your account exists, so that what you planned last year is there next year. Imported school-calendar days and Google Doc links are part of your work and are kept the same way. So that Undo still works after you close a worksheet or other material, each save also keeps the version it replaced: at most the 50 most recent per material. They are deleted automatically 72 hours after they are made (sooner once there are more than 50), and all of them are deleted with the material or your account. Voice recordings are not kept at all. Anthropic keeps the text it is sent and the text it returns for 30 days; OpenAI keeps picture descriptions for up to 30 days for abuse monitoring, and does not keep the audio it turns into text; neither uses what it is sent to train models. Records of drafting requests and hosting logs are kept by the providers named in section 6 under their standard retention.

Lumerell doesn’t save a history of your conversations with Lumi; a conversation is cleared from the page when you close or reload it. Changes Lumi makes to your plans are saved like any other edit. Our AI providers may keep what they receive for a limited time under their own terms (see section 5). To help prevent duplicate changes, Lumerell keeps a short record of each change: codes and a one-line result such as “Planned 3 days,” not your lesson content. Once a record is over a day old, it is deleted the next time you use Lumi.

Your Teacher Memory settings and the suggestions you’ve stopped are kept until you change them in Settings or delete your account. Links between materials and assessments are kept until you reset what Lumerell has learned or delete your account.

Entries on the access list are kept while the school or district works with us. To have your address removed, email hello@openmeadow.io; removing it does not delete an existing account — use “Delete my account” for that.

To download your data, open Settings and choose “Download my data”. You get one ZIP file of everything you have made in Lumerell: your courses, plans, worksheets and other materials, packets (also as Word documents), reviews, goals, reflections, meetings, imported calendar days, Google Doc links, the shares you made, your Teacher Memory settings, the suggestions you’ve stopped, links between materials and assessments, and your attached files and illustrations. It is made on request from your own account only and is not kept by us. A school or district leader cannot download your data. If your download is too large for one file, email hello@openmeadow.io and we will send you a copy.

To delete your account, open Settings and choose “Delete my account”. It takes effect straight away. If you can no longer sign in, or want particular information removed rather than the whole account, email hello@openmeadow.io and tell us which account and what you want removed; we may need to confirm you are authorized to ask. Please do not email passwords or confidential student records. Deleting an account first removes your attached files and illustrations from storage, then your account record and, with it, your courses, plans, worksheets (and their earlier versions), packets, reviews, goals, imported calendar days, and Google Doc links from our database. Our database provider takes one backup a day and keeps seven; a deleted account’s database records can therefore remain in a backup for up to seven days, while attached files and illustrations are not part of backups and are gone at once. The same applies to anything else deleted from our database, including the earlier versions kept for Undo: it can remain in a backup for up to seven days. We will tell you if anything must be kept for a specific legal or security reason.

To disconnect Google, remove Lumerell in your Google Account connections. Because Lumerell holds no long-term Google credential, that simply stops any future authorization; it does not remove information already in your Lumerell account. Use the deletion request above for that.

Documents saved to your Google Drive are yours and separate from Lumerell’s copy. Manage or delete them in Google Drive; Lumerell never deletes them.

10. Cookies and similar technologies

Lumerell uses a sign-in cookie to keep you signed in, small preference cookies (which course you last viewed, how you like to edit a day, your time zone so “today” is your today, and — for school and district leaders — whether you were last in Leader view), and your browser’s storage to remember light or dark mode. Lumerell does not currently use an analytics cookie. If we turn on our usage-analytics provider, PostHog, it will set its own cookie and browser storage to recognize your visits, and we will update this policy first. There are no advertising or marketing cookies. When a lesson includes a YouTube video, its preview picture loads from YouTube, and the video plays from YouTube’s privacy-enhanced player only when you press play; YouTube may then use its own cookies or storage. Google’s sign-in and file picker load from Google when you use them. Your browser lets you control or remove all of these; blocking the sign-in cookie will keep Lumerell from working.

11. Teachers, schools, and student information

Lumerell is for teachers and adult school staff. It is not a student-account service. Please avoid entering identifiable student records: student names tied to grades, health information, individualized education plans, or other confidential records.

When you talk to Lumi, Lumerell applies automated checks designed to remove student-identifying information from what you say or type before sending it to its AI providers. Lumi also applies these checks to lesson content it reads or sends for re-planning (titles, goals, steps, exit tickets, homework, and notes) and to calendar entry titles. In lesson content, the checks use surrounding words to help distinguish student names from historical figures and fictional characters—for example, references to an IEP, an accommodation, an absence, or a parent contact. When Lumi re-plans a day, a lesson block in which these checks detect a student name is preserved unchanged in your saved plan. These checks may miss identifying information, especially names without that context, or occasionally remove names that do not identify students. Please keep student names and other identifying details out of your plans and out of what you say to Lumi.

We do not knowingly collect personal information directly from children. If you believe a child’s information has been entered, contact hello@openmeadow.io so we can look into it and remove it.

This policy does not itself authorize the upload of student records or establish compliance with every school privacy requirement.

12. Your choices and changes to this policy

Contact hello@openmeadow.io to ask about, see, correct, or delete information associated with your account. Depending on where you live you may have further rights under law. We may verify your identity first.

We will update the effective date when this policy changes and give appropriate notice of material changes. Before using Google information for a new purpose, we will explain it here first and ask for any renewed consent that is required.

Privacy contact: Open Meadow LLC — hello@openmeadow.io. See also our Terms of Service.