Privacy Policy

Everything below is stored in Modulus's database, which is hosted by Supabase.

• Account: your email address, an optional name, your timezone, when the account was created and when you finished first-time setup. Sign-in is handled by Supabase Auth, which holds your email address and password credential; Modulus's own tables do not contain your password.
• Places: the locations you name and the travel minutes you enter between them.
• Fixed events: each event's name, dates or weekdays and times, location, whether it is mandatory and whether that was assumed rather than stated by you, how much attending matters, its stakes and pressure days, and a linked goal.
• Productivity windows: each window's label, kind, weekdays and times.
• Goals and checkpoints: goal names, horizon, weight, status and target date, and any weekly time you give a goal; checkpoint titles, structure, due dates, cadence, session length and when each was completed.
• Tasks: task names, size in minutes, deadlines, linked goal, checkpoint and location, status, and planning details such as whether a task can be offloaded, how much doing it yourself matters, whether its deadline is hard or soft, stakes, habit cadence, priority, tags and recurrence.
• Your anchor: the name of the person you plan around, their timezone, sleep window and typical busy windows. This is information about another person, entered by you.
• Settings: your modulus settings (type, target, margin and floor minutes, and whether the Jev decision model is on), flexible blocks (sleep, routine and meal durations) with your usual wake and sleep times, and preferences (sleep window, sleep durations, meals and daily modulus minutes).
• Plans: each plan's date, mode, status and delivery time, its items (move type, start and end times, linked task or event) and every item's reason text (which the language model may have written) with the engine facts behind it.
• Activity history: the completion log (planned and actual minutes and each entry's status, such as done or skipped); the event log (tasks completed, plans followed or deviated from, modulus kept or cut, and overrides with any reason you typed); move outcomes (whether each delivered move was followed, overridden, skipped or ignored, when it was delivered, when you acted and how many seconds that took); and app events (sign-up with its method and timezone, sign-in, sign-out, authentication errors, tasks created, updated, deleted or marked done, and preferences updated).
• Friction notes: the text of each friction note you save on the Today page, when you saved it, and the plan and move shown at that moment (its type, name, start and end).
• Setup questions: which questions Modulus has asked you to fill gaps in your context (for example, whether an event is mandatory), whether you answered or dismissed each one, when, and until when a dismissed question stays hidden.
• Planning jobs: each plan request you submit, its status, a link to the resulting plan, an error message if planning failed, and timestamps.
• Older records: schedules and schedule blocks from a retired scheduler. The current app does not write them, but rows created earlier remain until deleted.
• Waitlist: the email address you submit to join the waitlist and when you joined. It is not linked to an account.

Text you type into the context box is sent for extraction (see below); only the cards you confirm are saved.

Alongside each plan, Modulus keeps these records of how the plan was produced:

• The plan's input record: your planning request (mode, wake and sleep times, location, minutes available and whether your routine is done), which path produced the plan (Jev, the language model or a fallback), whether the validator repaired it, and a snapshot of the engine's plan.
• Decision metadata: when Jev was asked, its confidence values, response time, input token count, the cost the gateway reported, whether the reason text came from the language model, and a short error message if Jev did not answer.
• Cost record: for every model call made for the plan, which step made it, the model name, input, output and cache token counts, and the estimated cost in US dollars, with the plan's total. A daily total per account is calculated from these records.
• Event log entries: when planning fell back to the canonical plan, when a reason was rewritten, and the details of overrides.
• Planning job records: the request, status, resulting plan link and any error message, as listed above.

• Supabase provides the database and sign-in. It stores everything listed above. Supabase Privacy Policy
• Vercel hosts the app. Every page request and form submission passes through Vercel, which also holds the server logs the app writes. Vercel Privacy Notice
• Anthropic API runs the language model used for orchestration, extraction and suggestions. For planning it receives a summary of your context (task, event and location names, deadlines, times, your anchor's availability and your modulus type) and the engine's results. For context entry it receives the text you type and your existing context. For goal checkpoints it receives the goal name and your description. For task suggestions it receives the task name, size and deadline. Anthropic Privacy PolicyAnthropic Commercial Terms
• Vercel AI Gateway serves Jev, the decision model, when Jev is on. For planning it receives a summary of your context and the candidate plans to choose between. For task suggestions it receives the task name, size and deadline. Vercel AI Gateway documentationVercel Privacy Notice

Data held in Modulus storage is kept until you delete it or your account is deleted. You can delete tasks, goals, events, locations and windows yourself. Deleting your account deletes every record tied to it, including plans, logs, outcomes and planning jobs. A waitlist email is kept until it is removed.

You can delete your account yourself with Delete account on the Settings page.

Anthropic and Vercel AI Gateway may keep their own copies of the requests Modulus sends them. Modulus cannot delete those copies; each provider's own policy, linked above, governs how long they keep them. The same applies to Vercel's hosting logs.

Database access rules limit each signed-in account to its own rows. The people who run Modulus have administrative access to the database and hosting, and admins can view statistics combined across users: counts and rates of followed, overridden, skipped and ignored moves, response times, the number of active users per day, and the number of friction notes saved per day (not their text).

Modulus sets sign-in session cookies (through Supabase Auth) to keep you signed in, and a timezone cookie with your browser's timezone so days are calculated in your local time.

To get a copy of your data, use Download my data on the Settings page. To delete your account and its data, use Delete account on the same page.

Contact details pending