Privacy Policy
Version 2026-10-25 · Effective October 25, 2026
How Maggie Home collects, uses, shares, stores, and protects household account data.
First-party product analytics and email delivery evidence
Privacy disclosure updated October 26, 2026. MAGGIE may record limited first-party product usage from eligible signed-in adult sessions: account and household references, allowed feature/page identifiers, coarse browser/mobile platform, time, session activity, reported widget opens and verified adult routine actions. These measurements help us understand product use and beta engagement; a reported open is not proof of a completed household action. We do not put calendar contents, financial amounts, private notes, child identifiers or chat text in these analytics events, and do not add advertising trackers to authenticated household screens for this purpose. Optional collection respects browser Do Not Track and Global Privacy Control and excludes sample, child/Kid Mode, guest-locked/shared-display and AppMaster activity. Registration and invitation history may also support aggregate account and beta reports.
Usage reports are restricted to authorized AppMaster operators and contain aggregate results rather than public account-level activity. Reporting covers up to 90 UTC days. This separate analytics namespace is removed during subsequent successful collection once outside its retention window; if collection stops, physical cleanup can be delayed until it resumes. Existing security, support and financial audit records have their own retention purposes and are not deleted by analytics cleanup. Average session duration is unavailable because it is not reliably measured; we do not claim unavailable historical or native-TV engagement was measured. Contact [email protected] for privacy questions or applicable access/deletion requests.
For supported transactional emails we keep limited delivery evidence such as the Resend message reference, message category, creation time and last checked provider status, without copying security tokens, message bodies or recipient addresses into that evidence log. The new operational log uses a 90-day reporting window and namespace-specific cleanup on subsequent recorded sends; the provider and underlying invitation/support/security records may have different retention. API acceptance, provider sending, receiving-server delivery and actual inbox receipt are distinct. An accepted send request is not represented as proof that the message reached your inbox. General customer inquiries use [email protected]; individual security, verification and invitation messages remain addressed to their intended recipient.
Information we collect
We may collect account information such as name, email address, password hash, profile photo, household name, plan, billing identifiers, and login provider identifiers. We may collect household information such as calendar items, chores, grocery items, meals, recipes, notes, reminders, child profile display names, profile photos, incentives, device labels, and dashboard settings.
When integrations are enabled, we may process OAuth tokens, calendar metadata and selected events, email configuration, recipe URLs, voice recordings and transcripts, generated audio responses, support diagnostics, and audit logs. Payment card details provided at checkout are handled by the payment provider, such as Stripe, rather than stored directly by Maggie Home.
If you use Budget & Finances, we process the income, expense and bill names, amounts, categories, dates, recurring schedules, manually recorded payments and receipts, budgets, savings goals and contributions, notes, optional member associations, access grants, calendar and reminder preferences, and related operation and audit records you provide. These are household-entered planning records, not information retrieved from a bank. The feature does not request bank login credentials, routing or account numbers, or payment-card details; do not put those details in notes or other free-text fields.
How we use information
We use information to create and secure accounts, provide household dashboards, sync integrations, personalize layouts and themes, send account and subscription emails, support users, process billing, detect abuse, troubleshoot errors, and improve reliability.
If AI voice features are enabled, voice input, transcripts, and related context may be processed to understand requests, generate responses, and perform requested dashboard actions.
Google API Data & Limited Use Compliance
The use of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. This applies to calendar content and information derived from it, not just the original API response. It is a commitment about our data use, not a statement that Google has approved or certified MAGGIE.
Connecting Google Calendar is optional and separate from Google sign-in. The upgraded Calendar Connections flow requests openid and email to identify the connected Google account, calendar.calendarlist.readonly to list calendars you can select, and calendar.events.readonly to synchronize their events. Event data may include titles, dates, times, descriptions, locations, recurrence and provider privacy labels. The upgraded flow does not request event-editing permission. An older connector, if available to your account, requests broader Calendar access for its existing event create, update and delete functions. Review the actual Google consent screen; do not grant unexpected permissions. Google sign-in separately requests basic identity information to authenticate your MAGGIE account and does not itself connect Calendar.
MAGGIE uses selected calendar information to synchronize and display your schedule in its calendar and supported household views. Periodic checks and provider change notifications update the cached display; temporary failures can leave an older cached view. In upgraded connections, household sharing is off by default, and authorized household managers control sharing. Shared TV views omit Google events marked private or confidential and Google cache entries whose privacy label is not available. Your authorized account calendar is not changed by that TV omission. Review household-sharing and display choices before using a shared screen.
Connected Google Calendar API events are excluded from automatic household AI context, event counts, model-generated answers and generated spoken summaries. Subscribed ICS/iCal feeds are also excluded because their upstream provenance cannot be reliably established. This does not disable calendar synchronization or the full on-screen calendar. MAGGIE does not operate a generalized AI or machine-learning model training or fine-tuning pipeline. The verified exclusion concerns connected Calendar records, not every Google-derived account value or information you enter yourself. If you independently type, paste, upload or speak calendar information into a chat, voice request, feedback form or support ticket, that submission is processed by that feature; please do not include private Google calendar content or other sensitive information in those inputs.
Google sign-in identity is different from Google Calendar content. Sign-in supplies a Google account identifier, verified email and available basic profile information to create or link your MAGGIE account. A supplied name, or an email-derived label when a name is unavailable, may initialize your MAGGIE display name, household name and owner profile. When an authorized adult uses the configured household assistant, those saved household/profile labels may be included in the request to OpenAI and may appear in its answer or generated speech. Google sign-in does not authorize Google Calendar access. Informational MAGGIE Help does not automatically receive your account name or email. Avoid putting sensitive information in household/profile labels; the AI section below explains provider processing and controls. The Calendar exclusion is not a promise that all Google-derived identity information is excluded from AI.
Google calendar information is processed by the application and the hosting/database services needed to provide your selected calendar features. It is not sold, used for targeted advertising, used for credit decisions, or intentionally supplied to an advertising platform or data broker. Advertising eligibility does not use Google calendar events, and MAGGIE suppresses new advertising for households with connected or retained Google Calendar records or subscribed calendar feeds. A page that already loaded advertising withholds Google/feed calendar widgets and requests a fresh, advertising-free document; this is not a browser-level sandbox for an already-loaded third-party script. The advertising notice explains cleanup and retry limits. Other transfers are restricted to necessary, consented visible features, security or abuse prevention, legal obligations, or a qualifying business transfer with required prior consent. Human reading requires your documented affirmative agreement for specific data, a necessary security or legal reason, or aggregated and anonymized internal operations; feature delivery alone is not staff permission to read calendar content. The general sharing paragraph below does not override these Google-specific restrictions.
For upgraded Calendar Connections, open My Account → Connected services → Manage Calendars to change selections. Disconnect removes that connection's cached events, synchronization work and saved access/refresh tokens, while keeping limited disconnected connection/source metadata. It does not delete events from your Google account or sign you out of MAGGIE. Disconnect does not by itself guarantee revocation of the Google grant; you can remove MAGGIE through your Google Account third-party connections. Older connections use their own available disconnect controls. Contact the privacy address on this page to request deletion of remaining connected-data records; identity checks and necessary security/legal retention apply. We do not offer a self-service whole-account deletion button at present.
Calendar access and refresh tokens are protected with application-level encryption and handled by the backend rather than placed in frontend code. Requests to Google's services use HTTPS, and connection actions enforce the current account and household authorization. Event cache fields are not all separately encrypted by the application; this is not end-to-end encryption. No system can guarantee absolute security. Disconnecting or deleting application data cannot erase copies another authorized household member already exported or screenshots they saved.
Google Maps Event Previews
Where the site has configured Google Maps Embed, an authorized adult can choose Load Google Map in an event window. Opening the event or typing a location does not automatically send that location to Google. Choosing the preview sends the displayed location directly from your browser to Google Maps, together with network/browser information such as your IP address and the MAGGIE site origin. MAGGIE does not put the event title, notes, household/profile names, attendees or Calendar access tokens into the map request. Google may use cookies and may show advertising inside its own embedded map under its terms; this is not MAGGIE using calendar records for targeted advertising.
Map previews are optional and do not verify that a saved address or place name is correct. Check the intended destination. You can hide the map, continue using plain-text locations, or explicitly open the location on Google Maps instead. Hiding the map stops displaying that frame but cannot erase information already received by Google. No Google request is made just by displaying the external link; following it opens Google's service under its own terms. This feature does not add location autocomplete, geocoding results, device-location tracking or a new AI data feed.
The map option is limited to authorized adult web views, not managed child, guest-wall, kiosk/shared-display or read-only SAMPLE experiences. Advertising-capable Basic dashboards and documents that have already loaded MAGGIE advertising use the external Maps link rather than an embedded map; an authorized adult can use Calendar management on a clean page. MAGGIE does not save map screenshots or Google Maps content as household records. Existing Calendar authorization, sharing choices and Google/ICS AI exclusions remain unchanged.
Artificial Intelligence & Your Data
MAGGIE uses optional AI for different purposes with different access boundaries. MAGGIE Help provides informational product support to signed-in adult accounts on every plan. The household assistant supports typed or spoken household requests on Family, Family Pro and Complete when configured. Recipe suggestions and meal-saving actions additionally require the applicable meal-planning entitlement and household management permission. Optional MAGGIE Insights analysis helps authorized operators understand submitted product feedback. These are not unrestricted access to all household records, and not every feature is available merely because an AI model exists.
Help processes your question, a limited recent support conversation, relevant approved Help content, and general page, plan and role context, not an automatic household-data dump. The household assistant may process an adult's request and limited authorized context such as household/profile display names, native MAGGIE and connected Outlook/iCloud schedule information, chores, to-dos, groceries, meals, household notes and announcements, and configured weather. This can include information about a managed child that an adult put in household records. Private finance books, billing credentials, connected Google Calendar API events and subscribed calendar feeds are not automatically included. Do not put bank details, health records, private calendar information, unnecessary children's details or credentials into shared notes, AI requests or feedback.
The implemented server-side model, transcription and speech requests go directly to OpenAI's API, not through an additional model gateway. Text may be processed to answer questions, draft supported actions or suggest recipes. Recordings may be sent for transcription, and eligible response text may be sent to generate speech. Models can change with the service's configured settings; a model name does not determine its privacy terms. Browser speech-recognition fallback and optional voice activation can instead use services supplied by your browser or device vendor. We cannot promise that browser recognition runs entirely on your device or has the same retention rules as OpenAI. Microphone use requires the applicable browser permission; avoid voice activation or revoke microphone permission if you do not want this processing.
Processing to answer a request is different from training a generalized model. OpenAI's API terms state that API inputs and outputs are not used to train its models by default unless the customer explicitly opts into sharing. MAGGIE does not operate a general-model training or fine-tuning pipeline using household information. Connected Google Calendar records are excluded from automatic AI requests, while Google-derived household/profile labels can be part of the permitted household context described above. A provider's optional sharing settings are separate from MAGGIE's application storage controls; the API default is not a guarantee about every provider-account setting or past request. Text Responses requests ask OpenAI not to store response application state, but this does not mean zero retention: operational, abuse/security monitoring, legal retention and endpoint-specific processing may still apply. We do not promise a special zero-retention arrangement or that clearing a MAGGIE conversation deletes a provider's security records. See the linked API data-controls and service terms, not only a consumer chatbot privacy notice.
You may use non-AI tools without sending a chat or voice request. There is no single household switch that deletes all AI-related records or disables every AI service. Help's New conversation and Delete conversation controls clear its browser-memory conversation, not provider records or a separately submitted support ticket. The household assistant's current exchange is browser-session state; a confirmed calendar, chore, grocery, announcement or meal action remains a saved household record until changed through its normal editor. Insights responses, images and analysis reports have separate retention/deletion controls described below. Use My Account notification preferences to stop optional survey invitations, or contact the privacy address for account-wide access/deletion requests. Avoid the Speak to Maggie button and enabled voice activation, or revoke microphone permission, to stop new voice input.
Managed child profiles, Kid Mode, guests, locked guest walls and display sessions do not have direct access to the household AI or AI Help endpoints. Adults remain responsible for minimizing child information used in their own requests and shared household context. An adult's use of a family feature is not a guarantee that no child-related information is processed. We do not enable unrestricted child-facing AI through this policy. AI answers can be inaccurate; review suggestions and any real save confirmation, and do not rely on AI for emergencies, supervision or professional medical, legal or financial advice.
AI credentials remain server-side, request endpoints are fixed to the implemented provider services, and the service checks account, role and applicable household permissions. We use bounded requests, rate limits or timeouts where implemented and avoid storing Help transcripts in application usage logs. The sections below explain the different storage, support and survey practices; none of these safeguards is a promise that all data is anonymous, encrypted end-to-end or retained for no time at all.
Sharing and service providers
We may share information with service providers that help operate Maggie Home, such as hosting, database, email, payment, AI, calendar, advertising, and support providers. The information involved depends on the feature you use and the provider's role in delivering it. Google API data remains subject to the stricter Google API Data & Limited Use Compliance section above.
We may also disclose information when required by law, to protect rights and safety, to investigate abuse or security issues, or as part of a merger, acquisition, financing, or sale of assets.
Beta invitations and registration access
MAGGIE may offer public registration, invitation-only registration, or temporarily closed registration. These settings affect new accounts, not an existing account's ability to sign in. For beta invitations, we keep the intended recipient's name when supplied, email address, invitation reference, expiration, permitted uses, delivery records and successful redemptions. A verification email or a supported sign-in provider's verified email confirms the invited identity before account creation. Opening an invitation link does not redeem it.
A pending email signup temporarily stores encrypted signup details, including a password hash rather than a plain-text password, and a hashed verification code for up to 20 minutes of eligibility. Expired pending records are removed during subsequent signup activity. Invitation secrets are stored hashed for validation and encrypted for authorized operator copying or resending. Do not share your invitation or verification code with other people.
Accounts created through a beta invitation retain their registration origin, beta cohort and invitation history for administration and product feedback comparisons. Authorized operators may remove an active Beta Tester designation without erasing the account's original enrollment or feedback history. Beta Tester status does not grant administrator permissions, a paid subscription or unlimited access. Public registration does not erase previous beta history. Existing accounts without reliable registration-origin records are treated as unknown rather than assumed to be public registrants.
A Beta Tester designation makes an adult account eligible for configured optional testing feedback; it does not guarantee a survey will be sent or override survey preferences. Authorized operators can compare beta and public feedback using recorded registration origins and submission-time snapshots. AI analysis receives limited, de-identified feedback references and permitted segment labels, with the redaction limitations described below; not recipient invitation secrets or account contact details. You can request account-data access, correction or deletion through support, subject to necessary security and audit retention.
Manual household finances and private displays
Financial planning records are stored separately from the general household dashboard data, with application-level encryption for the finance book. The service processes those records to calculate your authorized views, reports, calendar projections and configured reminders. This is not end-to-end encryption: the authorized application service must process the records to provide these features. Limited audit and operation records identify actions, actors and record references without copying finance titles, amounts or private notes into the audit history.
The household owner controls access for other current adult household members, including separate permissions to view finances, edit income and expenses, manage bills, manage budgets and goals, or export records. Household administrator and platform AppMaster status do not automatically grant access to a household's private finances. Children, guests, Kid Mode and shared wall/TV displays do not receive these finance views. Access is checked by the service, not granted by adding a dashboard widget. Removing access cannot erase an already-downloaded report or a screen image another person saved.
Finance calendar display and bill reminders are optional and start off. Authorized calendar views can hide amounts and use generic reminder titles. Finance calendar entries derive from the private records and are not automatically added to Google, Outlook, public/shared calendar feeds or other external calendars. Enabled bill reminders use the existing in-app inbox, with generic messages and no amounts; they do not send email, SMS or device push notifications or initiate a payment. An authorized dashboard may show a next-bill summary. Private finance records are not added to the general household snapshot used by the household-management assistant or automatically sent to MAGGIE Help.
Authorized exports create a file you control outside Maggie Home. Review who can access your device and downloaded files. Financial history is retained with the household records under the retention and deletion practices below; stopping a recurring schedule, hiding a widget or losing a plan entitlement does not itself delete historical records.
Dashboard preferences, local weather, and imagery
Dashboard layouts and visibility settings use your existing household profiles, role permissions and saved preferences. The greeting, date and time use the configured household timezone. Weather uses the household location you configure and the weather service handling that request; the redesigned dashboard header does not itself request your device location. No weather conditions are invented when a location or usable response is unavailable.
The scenic header and matching grocery-item illustrations are static application assets. Displaying these assets does not itself add a new data collection, bank connection or location permission. An unmatched grocery item may have no illustration. Removing the photo gallery from the main dashboard does not delete photos stored elsewhere in the household.
MAGGIE Help and AI support
MAGGIE Help is an optional, informational support chat powered by OpenAI, separate from the household-management assistant. When you send a question, OpenAI processes that question, a limited recent conversation, selected approved public Help articles, and general application context such as your current page, subscription tier and household role. MAGGIE Help does not automatically send household calendar contents, child profiles, private notes, messages, passwords, payment information or account email to the AI. Private finance records, bill amounts and budget details are not automatically included. Do not type sensitive family or financial information or credentials into the chat.
Support-chat history is kept only in memory for the current browser support session, with a configurable inactivity expiry. New conversation or Delete conversation clears that local history; leaving or reloading the app, signing out or switching accounts also clears it. We do not store support-chat transcripts in our application database or ask OpenAI to store Responses application state. OpenAI may retain abuse-monitoring data under its own account policies; clearing the local conversation is not a request to erase provider security records. API data is not used to train OpenAI models by default.
We keep limited account-linked operational metadata, such as request time, model, token counts, estimated usage cost, result status and optional helpful/not-helpful feedback, for service reliability, usage limits and abuse prevention, not the message text. AI support is disabled for child, Kid Mode, guest-locked and display sessions. Chat answers may be inaccurate; use the linked Help articles or contact support when uncertain. The chat cannot change household records, subscriptions or permissions.
Contacting human support is a separate action. You review the ticket before sending and can choose whether to include a conversation excerpt, an optional screenshot and a preferred reply email. Screenshots are sent only to human support, not to the AI. Only the information you deliberately include in that form and your account identity is included in the support request. Support requests and voluntarily included attachments may be kept with the support record and delivered by our email provider.
MAGGIE Insights surveys and product feedback
MAGGIE Insights surveys are optional and are not anonymous. When an invited adult submits feedback, we associate it with the signed-in account, account display name, household, subscription plan at submission, survey and question version, date, general browser platform and available application release identity. We record invitation delivery, display, opening, postponement, dismissal and completion to avoid repeated interruptions and duplicate submissions. Account identity comes from authentication, not a contact-information form. Direct invitations are disabled for child, Kid Mode, guest-locked and display sessions. We do not automatically enroll all customers in live testing.
Authorized platform operators can review identifiable responses, ratings and deliberately uploaded screenshots to improve the service, and export results for that purpose. Other households cannot view your feedback. Please do not include children's personal information, passwords, payment details or sensitive household records. Optional images are validated, privately stored and excluded from AI analysis; removing a pending image deletes it, and unused temporary images expire after 24 hours.
If AI feedback analysis is enabled, authorized operators may ask OpenAI to process selected feedback text and limited plan/platform context. We use opaque response references rather than sending account identifiers and apply best-effort text redaction, but free text can contain identifying information that automated redaction does not recognize. Do not treat this process as guaranteed anonymization. We do not ask OpenAI to store Responses application state; provider abuse-monitoring retention may still apply under its policies. AI themes and sentiment are estimates, and reported bugs are not independently verified simply because a respondent mentioned them.
You can suppress optional survey invitations in My Account → Notifications. Email invitations additionally respect applicable email consent and unsubscribe preferences. Turning off surveys does not remove prior submissions or disable security notices. Reopen your original invitation while signed into the same account to download or delete its saved response; deletion also removes related screenshots and derived analysis reports containing that response. Account-wide access or deletion requests can be sent to support. Stored feedback normally expires after 365 days, subject to an operator-configured period between 30 and 1,095 days; invitation and analysis records are also subject to retention cleanup. Deleting application feedback does not erase provider security records or copies already lawfully exported by authorized operators.
Children and kid profiles
Kid profiles are intended to be parent-managed. We aim to collect only the information needed to operate household features, such as display name, profile photo, role, color, chores, rewards, and schedule context selected by the household admin.
Parents and legal guardians may manage child profiles through household settings and request access, correction, export, or deletion of child profile information. Requests are subject to identity and parental authority verification and applicable retention requirements.
Advertising and cookies
Free accounts may display ads. Advertising providers such as Google AdSense may use cookies, device identifiers, or similar technologies to provide, measure, and limit ads. See the Cookie and Advertising Notice for more information.
You can manage cookies through your browser settings and advertising preferences through the provider's controls. Ad-free plans are described on the pricing page and in your subscription settings.
Data retention and deletion
We keep account and household information while needed to provide the service, comply with legal obligations, resolve disputes, prevent abuse, maintain security, and support billing or audit requirements. Some records, such as invoices, fraud-prevention logs, and legal acceptance records, may need to be retained after account deletion.
Security
Maggie Home uses safeguards such as secure cookies, password hashing, role-based access, audit logs, and limited token handling. No system can be guaranteed perfectly secure, so users should use strong passwords and remove access for household members who no longer need it.
Your choices and rights
Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing of personal information. You may direct privacy questions and requests to Maggie Home. Requests are subject to identity verification and applicable legal requirements.
Google advertising privacy and choices
When advertising is enabled, Google and its advertising partners may use cookies to serve ads based on visits to this or other websites, including personalized ads where permitted and according to your choices.
How Google uses information from sites and apps explains its data practices. You can control or opt out of personalized advertising through Google Ad Settings. Turning off personalization does not necessarily disable all advertising cookies or remove ads.
Support and privacy requests
For account support, questions about these agreements, or requests to access, correct, export, or delete personal information, email [email protected].
Do not include passwords, payment card details, or other sensitive information in your email.