Mudd Labs Notebook (“the app”) is a personal notebook made by Mudd Labs, run by David Mudd. This policy explains what the app stores, what it does with it, and how to get it removed. It is written in plain language on purpose; if anything here is unclear, write to david@muddlabs.com.
What the app is
A place to keep notes, checklists, dye-development sheets, film-development logs and photos, with a built-in assistant (“Woofbot”) that files what you tell it, answers questions about your own notes, and, when you connect Google Calendar, puts appointments on your calendar. Its Post Planner turns a spreadsheet of lines into pictures and, when you connect a Facebook Page, schedules them on that Page. Today the app is used by its maker; if it opens to other people, this policy applies to them the same way.
Information the app stores
- What you write, dictate or upload: notes, checklist items, sheets, logs, tags, and photos, with the dates and times they were made or changed.
- The Post Planner's log: the lines, captions, dates and states of the posts you queue, the layout you chose, the background images you add, and the pictures it generates.
- The calendar day and time zone your device reports, so that a note made at 9 pm is dated correctly and reminders land on the right day.
- Your preferences (for example which notebook catches unsorted notes, your home time zone).
- Sign-in: you sign in with Google or with the app's password, and a signed session cookie keeps you signed in for 30 days. Your account holds your email address; signing in with Google also stores the Google account's identifier, so the same account is recognised next time.
- If you connect Google Calendar: your Google account email and the credentials described below.
- If you connect a Facebook Page: the Page's id and name, the credentials described below, and the id of each post the app scheduled.
The app does not collect location, contacts, advertising identifiers or analytics about your behaviour.
Voice
Dictation happens on your device: the iPhone Shortcut and your browser's speech recognition turn your voice into text before it reaches the app. The app receives text, never a recording. Your device's speech service has its own privacy terms.
Camera (Timelapse)
The Timelapse page uses your device's camera only while it is open, after your browser asks you. The pictures it takes are stored in your browser on that device and are never uploaded: the app's servers do not receive, see or keep them, and the assistant is not sent them. A timelapse may be linked to one of your entries or projects; that link is kept on the device too. To tell which way up the phone is held, the page reads its tilt sensor, on the device, while the camera runs; that reading is not stored or sent. The pictures leave the device only when you download them. Clearing the site's data in your browser deletes them.
In the Mudd Labs iPhone app the timelapse camera is part of the app itself. Its photos are saved as files in the app's own folder on the iPhone (visible in the Files app), are never uploaded, and are copied to your photo library only when you press Save to Photos. Send to Mac sends them straight to the Mudd Labs app on your own Mac over your Wi-Fi, protected by a pairing code; they do not pass through the app's servers.
The assistant
To file, tag, summarise and answer, the assistant sends the relevant text to Anthropic's Claude API together with what it needs for context (for example the names of your notebooks, the open items on a checklist, the events on your calendar when you ask about them, and today's events when it writes your daily check-in). A photo you ask it to describe is sent the same way. Anthropic processes this to produce the response under its commercial terms and privacy policy. The app does not use your information to train any model, and does not allow its providers to. If you flag one of the assistant's answers for the developer, that note, what the assistant did and your words are kept in the app as a test case, used only to check and improve the assistant's instructions. The app keeps a record of what the assistant changed in your notes and projects (what it added, where, and when), so that you, or the assistant, can take any of it back. The app can also be pointed at a model running on your own machine, in which case that step never leaves it.
Sign in with Google
Signing in with Google asks Google only for your email address and a stable account identifier. The app uses them for one thing: to check that the account is one it already knows, and to sign you in. It stores the identifier on your account and nothing else; it receives no access to your Google data. A Google account the app does not already know is turned away and nothing about it is kept.
Google Calendar
Connecting Google Calendar is optional and separate from signing in. You grant it in Settings and can withdraw it there at any time. When connected, the app uses your Google data only as follows:
- What it accesses: events on your calendars (to answer “what is on Friday” and to fit the day's plan in your daily check-in around today's events), and the ability to create, change and delete events. It only ever changes or deletes events the app itself created, which it marks with a private tag: the ones you ask the assistant to make, and, unless you turn it off in Settings, your planner's tasks that have a time and today's plan, which it keeps in step with the tasks. Events you made anywhere else are never changed or deleted by the app. It also receives the email address of the Google account, to show which account is connected.
- What it stores: the connection credentials Google issues (encrypted at rest), your Google account email, which calendar to write to, identifiers of events the app created, and the identifier, title and start time of each event a check-in's plan is arranged around.
- What it does with it: provides the calendar features above. Nothing else. Your calendar data is not used for advertising, is not sold, is not shared with anyone except the service providers listed below acting on the app's behalf, and is not used to train models.
- Withdrawing access: press Disconnect in Settings, which revokes the credential with Google and deletes it from the app, or remove the app at myaccount.google.com/permissions. Events already on your calendar stay yours.
Mudd Labs' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Facebook Page
Connecting a Facebook Page is optional and separate from signing in. You grant it in Settings and can withdraw it there at any time. When connected, the app uses your Facebook data only as follows:
- What it accesses: the list of Pages your Facebook account manages (to let you choose one), and the ability to create, schedule and delete posts on the Page you chose. It does not read your profile, friends, messages or the Page's other content.
- What it stores: the connection credentials Facebook issues (encrypted at rest), the chosen Page's id and name, and the id of each post the app created, so it can show you where a post stands and take a scheduled one back.
- What it sends to Facebook: only what you asked to post: the picture the Post Planner generated, its caption and hashtags, and the time it should go up. Nothing goes to Facebook unless a post is dated, generated and either you press Send or you switched on the daily feed.
- Withdrawing access: press Disconnect in Settings, which revokes the app's permissions with Facebook and deletes the credentials from the app, or remove the app under your Facebook settings (Apps and websites). Posts already on the Page stay yours.
Service providers
The app runs on services that process data only to run the app:
- Vercel: hosts the app.
- Supabase: the database (Postgres, hosted in the United States).
- Cloudflare R2: stores uploaded photos, Post Planner backgrounds and the pictures it generates.
- Anthropic: the assistant's model, as described above.
- Cloudflare Workers AI, Google (Gemini) or OpenAI, whichever is set up: paints a background image for a post only when you press the button for it; it receives a one-paragraph description of the picture written from that post's words, nothing else.
- Google: your calendar, only when you connect it.
- Meta (Facebook): your Page, only when you connect it.
Cookies and local storage
One signed session cookie keeps you signed in for 30 days. Signing in with Google also sets a short-lived cookie for the ten minutes it takes, so the sign-in can only finish where it started. Your browser's local storage holds per-device preferences such as the handwriting font and which pages show the assistant. There are no advertising or analytics cookies.
Keeping and deleting
Your notes and photos are kept until you delete them. A deleted note sits in Recently deleted for 30 days, then is removed for good. Disconnecting Google Calendar or Facebook deletes the stored credentials immediately. To have everything removed, write to the contact address below.
Security
Traffic is encrypted in transit (HTTPS). Connection credentials are encrypted at rest. Access to the database is limited to the app and its maker. No system is perfectly secure; if something goes wrong you will be told.
Children
The app is not directed to children under 13 and does not knowingly collect their information.
Changes
When this policy changes, the date at the top changes with it. A change that matters to how your data is handled will be pointed out inside the app.