Privacy

Cloak

Cloak watches which app is frontmost using NSWorkspace. That's the entire auto-trigger mechanism. No screen content is read, no keystrokes are captured, and nothing related to what's on your screen is processed or stored.

Notification silence works through a bundled macOS Shortcut you install once during setup. Cloak invokes it by name. The Shortcut itself is Apple's infrastructure, running locally on your Mac.

For the Pro Tab Guard feature, Cloak uses Safari Apple Events to move Safari windows. It does not read, modify, or transmit tab URLs, titles, or any tab content. It only moves windows.

• No screen-recording permission. Icons and wallpaper hide through system APIs, not a screen capture.
• No Accessibility permission. Window cover only touches Cloak's own windows — no cross-app access.
• NSWorkspace is used to observe which app is frontmost. Screen content is never read.
• Notification silence via a bundled macOS Shortcut (user-installed, one time). No private API.
• Safari Apple Events (Pro, Tab Guard): window movement only. No tab content accessed.
• Settings stored in UserDefaults on your Mac. Never transmitted.
• License state stored in Keychain, Apple's encrypted credential store. Local only.
• Activation snapshot (what Cloak hid) stored in Application Support during active sessions. Cleared on restore or relaunch.
• No analytics, no telemetry, no external server. StoreKit purchases handled entirely by Apple.

ShowPoint

ShowPoint watches your mouse position and clicks using macOS's standard event monitoring API — that's how it knows where to draw the halo and when to fire a pulse. That data is used only to position the overlay — it never leaves your Mac.

Your license state (whether you've bought Lifetime Unlock or used the 10-minute trial) is stored in your Mac's Keychain, Apple's built-in encrypted credential store. That's local only. We have no servers to sync it to.

• No screen-recording permission — ShowPoint is a transparent overlay, not a recorder
• Mouse position and clicks are processed locally only — used to position the overlay, then discarded
• Modifier-key HUD watches ⌘ ⇧ ⌥ ⌃ state only — not which keys you press or what you type
• License state in Keychain — on your Mac, stays on your Mac
• Purchases go through Apple — we never see your payment details

LumaSip

Your intake log lives in the app on your phone. If you turn on HealthKit sync, that goes to Apple Health on-device — we don't read from Apple Health ourselves, and nothing syncs to our servers. There aren't any.

• Intake data stored locally on device
• HealthKit read/write is on-device only — we never access your Health data
• No account required

Cyvelle

Cycle data stays in the app's local database. It doesn't leave your device. If you back up your phone to iCloud, that backup is between you and Apple — we're not involved.

• Cycle and symptom data stored locally — never transmitted
• No account, no sync to our end
• iCloud device backup is Apple's infrastructure, not ours