Privacy
Curfew stores everything locally and requests only the permissions it uses.
What Curfew stores
| Data | Where | Retention |
|---|---|---|
| Schedule, budgets, preferences, license key | ~/Library/Preferences/studio.hypertext.curfew.plist and ~/Library/Group Containers/group.studio.hypertext.curfew/Curfew/widget-settings.json |
Until uninstall |
| Activity log (lockouts, extensions, overrides) | ~/Library/Group Containers/group.studio.hypertext.curfew/Curfew/activity.sqlite3 |
52 weeks rolling |
| Reflections (your morning & evening journal answers) | ~/Library/Application Support/Curfew/reflections.sqlite3 |
52 weeks rolling |
| Pending MCP write requests | ~/Library/Application Support/Curfew/mcp-requests.json |
Until resolved |
What Curfew does not do
- No analytics, telemetry, or crash reporting.
- No network requests except iCloud sync (Pro, opt-in).
- No access to your files, browser history, or app content.
Permissions
| Permission | Why |
|---|---|
| Calendars (Pro) | Read today's events for display. Never written to. |
| Notifications | Warning countdowns and lockout alerts. |
| Accessibility (optional) | Keyboard shortcut interception during lockout. |
iCloud sync (Pro)
When enabled, your schedule is stored in your private iCloud database (CloudKit). Hypertext Studio has no access — it lives in your personal iCloud account, encrypted by Apple.
MCP server
When curfew-mcp is running, AI assistants can read
your enforcement state and your daily reflections, and request
changes. Reflections are exposed read-only; write operations
require your explicit approval in the app. No data leaves your
machine through this path.
Questions: hello@hypertext.studio