Maddy Privacy Policy

Effective date: May 28, 2026

Maddy helps you plan, schedule, and organize your calendar from chat messages, screenshots, tasks, routines, and reminders. This policy explains what information Maddy collects, how it is used, and what choices you have.

This policy is written to be clear and accurate, not overly legalistic.

Account Identity

Maddy requires account identity to keep calendar actions, screenshot limits, future collaboration features if offered, subscriptions, support, abuse prevention, and data deletion requests connected to the right user. Maddy may use Sign in with Apple or another supported account method for authentication.

Website Privacy

When you visit maddylabs.com, MaddyLabs and its infrastructure providers may receive basic technical information such as your IP address, browser type, device type, pages visited, timestamps, and security logs. This information is used to keep the website reliable, secure, and working correctly.

If you submit the support form, MaddyLabs collects the email address, topic, device or app details, and message you provide so we can respond. Support form messages are processed through Cloudflare and Resend, and an automatic confirmation email may be sent to you.

Service providers are expected to process information only for MaddyLabs and protect it under appropriate confidentiality and security obligations.

MaddyLabs does not sell website visitor information and does not use website data for advertising targeting. The website is intended to stay lightweight and respectful of visitor privacy.

Information Maddy Collects

Maddy may collect or process the following information when you use the app:

• Messages you send to Maddy, such as scheduling requests, edits, cancellations, tasks, and follow-up replies.
• Screenshots or images you choose to send to Maddy.
• Text extracted from screenshots using OCR.
• Calendar context needed to understand conflicts, duplicates, availability, and schedule changes.
• Event, task, and routine details created or edited through Maddy, such as titles, dates, times, recurrence, notes, and locations.
• App settings and preferences, such as notification preferences, sleep window, scheduling preferences, and learned planning preferences that can be reviewed or reset in the app where available.
• Usage information needed for reliability, limits, abuse prevention, and debugging, such as request type, quota usage, success/failure status, latency, and approximate token usage.

Maddy only processes screenshots, messages, and calendar information that you provide or allow the app to access.

Information Maddy Does Not Intentionally Collect

Maddy does not intentionally collect:

• Payment card details.
• Precise location history.
• Contacts, unless a name appears in a message, screenshot, calendar item, or text you provide.
• Photos or files you do not select or share with Maddy.
• Hidden content from other apps.
• Advertising identifiers for ad targeting.

Maddy does not sell your personal information.

How Maddy Uses Information

Maddy uses information to:

• Understand scheduling requests.
• Read screenshots you send.
• Create, move, update, delete, or clarify calendar events.
• Create and manage tasks and routines.
• Detect conflicts, duplicates, unavailable times, and protected sleep windows.
• Send notifications about booking results, confirmations, or follow-up questions.
• Enforce free and premium usage limits.
• Improve reliability, safety, and abuse prevention.

Maddy uses AI to interpret natural language and screenshots, but deterministic app logic is responsible for validation, conflict checks, and calendar writes.

Backend and AI Processing

Some Maddy features require sending information to Maddy's backend and to AI providers for interpretation.

For example, when you send a screenshot, Maddy may send:

• The screenshot image.
• OCR text extracted from the screenshot.
• Relevant calendar context.
• Your scheduling preferences.
• The current date, time zone, and app context needed to interpret the request.

Maddy currently uses OpenAI to interpret scheduling messages and screenshots. Information sent to OpenAI is used to return structured scheduling results to Maddy.

Maddy tries to send only the information needed to complete the scheduling task.

Calendar Access

Maddy uses calendar access only after you grant permission. Calendar access is used to:

• Show your agenda.
• Check availability.
• Detect conflicts and duplicates.
• Add, update, move, or remove events when requested or confirmed.

Clear low-risk typed requests may be handled directly. Deletes, conflicts, uncertain changes, and destructive actions ask first. Clear low-risk screenshots may be added automatically when permissions and settings allow it. If Maddy is missing details or finds a conflict, it asks first.

Events created by Maddy remain your calendar events. Deleting the app does not automatically delete calendar events that were already written to your calendar.

Screenshots and Images

Screenshots are used to find schedule-related information, such as event details, deadlines, class schedules, work shifts, tickets, reservations, and plans.

Maddy may temporarily store screenshot processing jobs and results so the app, share extension, and notifications can stay in sync.

Maddy should not be used to upload highly sensitive screenshots unless you are comfortable with that content being processed for scheduling.

Notifications

Maddy may send notifications for:

• Booking results.
• Confirmation requests.
• Follow-up questions.
• Reminder or scheduling updates.

Private notification previews are enabled by default, so notification text avoids exposing plan details until the device is unlocked.

Retention

Maddy keeps information only as long as reasonably needed for the app to function, provide history, enforce limits, debug reliability, and prevent abuse.

Retention practices:

• Temporary screenshot jobs are designed to expire.
• Usage metadata may be retained for quota, reliability, and abuse prevention.
• Support emails may be retained for support and abuse prevention.
• Local chat history is designed to be short lived, with recent chat context generally expiring after about 24 hours.
• Pending notification context is designed to expire quickly, generally after about 24 hours.
• Timeline history may remain locally for a limited window, generally about 7 days, so results do not replay or duplicate.
• Apple Calendar events remain in your calendar until deleted by you.
• Backend account, usage, pending screenshot, notification, entitlement, and idempotency records can be deleted through Delete Maddy Data where available.

Maddy's backend is designed to clean up expired temporary records.

Security

Maddy uses reasonable technical safeguards, including:

• HTTPS for backend communication.
• Cloudflare-hosted backend infrastructure.
• Backend session tokens.
• Rate limits and quota checks.
• Server-side validation.
• Privacy-safe logging that avoids raw messages, screenshots, calendar details, and OCR text in production logs.
• Local file protection for shared app data where supported by the operating system.

No system can be guaranteed perfectly secure, but Maddy is designed to reduce unnecessary exposure of personal scheduling data.

Free and Premium Usage

Maddy may enforce message, screenshot, or AI usage limits depending on whether you are using the free tier or Premium tier.

Usage limits are enforced to keep the service reliable and prevent abuse.

Your Choices

You can:

• Stop using Maddy at any time.
• Revoke Calendar, Photos, or Notification permissions in device Settings.
• Delete or edit calendar events created by Maddy.
• Reset Maddy's local preferences and learned data in the app where available.
• Use Delete Maddy Data in Settings to ask Maddy's backend to delete server-side account, usage, pending screenshot, notification, entitlement, and idempotency records connected to your Maddy identity, then clear local Maddy data on the device.
• Delete the app to remove local app data from your device.

If you delete Maddy, events already added to your calendar may remain unless you delete them from the calendar.

Children

Maddy is not intended for children under 13. If you believe a child has provided personal information to Maddy, contact us so we can help remove it.

Changes to This Policy

This policy may be updated as Maddy changes. If the changes are important, Maddy may notify users in the app or on the website.

Contact

For privacy questions, contact:

hello@maddylabs.com