Skip to content

Privacy Policy

Last updated: September 23, 2026

TOMOSHIBI LLC (“we,” “us,” or “our”) describes how DirectCue (the “App”) handles information below.

1. Core principles

  • The App captures a Mac screen in response to a user-initiated action and locally creates an annotated image, AI-ready Prompt, human-readable Markdown, and structured manifest.
  • The App does not automatically send captures, annotations, Prompts, Markdown, or output files to an AI service.
  • Usage Analytics and Crash Diagnostics are off by default. Each can be enabled separately with user consent and changed later in Settings.
  • Feedback is sent externally only after the user submits the feedback form.
  • No account registration is required to use the App.

2. Information handled on the device

The App handles the following information on the device to provide its features:

  • The Area, Window, or Screen capture selected by the user and a still image held with Freeze
  • General context, annotation type and geometry, instructions, and supporting text entered by the user
  • Generated `raw.png`, `annotated.png`, `prompt.md`, `instructions.md`, and `annotations.json`
  • Output location, creation date, and other metadata required to display and manage History
  • Settings such as language, shortcuts, output image style, History retention, Launch at Login, and consent state
  • Free Prompt-creation usage and DirectCue Pro entitlement state

A capture may contain personal or confidential information displayed on screen. The user chooses the capture target and what to hand off to another app or person.

3. Screen Recording permission

The App uses macOS Screen Recording permission and Apple's ScreenCaptureKit to take still images of the Area, visible Window, or Screen the user selects. After the user starts a capture and selects a target, `DONE` takes a still image, or reuses the image already held by Freeze. Area `Freeze` takes a still image after a three-second countdown and reuses it for preview and output. Window selection uses window and display information locally and does not require Accessibility permission. The App does not record video, system audio, or microphone audio, and does not continuously record in the background.

Screen data is used only to create, display, annotate, save, and reopen the user's visual change request from History. The App does not analyze screen content for advertising or profiling or upload it to our servers, AI services, Usage Analytics, or Crash Diagnostics. Section 4 explains sharing explicitly initiated by the user.

Permission can be changed in macOS System Settings. Disabling Screen Recording prevents use of the capture feature.

4. Local storage, clipboard, and handoff

Images are processed on the Mac. During onboarding, the user chooses an output folder with the standard macOS folder chooser. `DONE` creates an output package in a timestamped, uniquely identified subfolder at that location, accessible in Finder. The location can be changed in `Settings > Output > Choose Output Folder`. The App retains a macOS security-scoped bookmark to access the selected folder after restarting. If the location has not been selected or cannot be accessed, the App does not automatically fall back to storing output inside its app container.

`Save & Close` commits the package to History. Returning to edit and discarding without saving deletes that working package. Section 9 describes retention and deletion of saved output.

When the user chooses to copy or drag an Image, Prompt, Markdown, or Bundle, the App writes the selected data or local file references to the macOS pasteboard. Clipboard contents are not sent through Usage Analytics or Crash Diagnostics.

Information the user sends to another app, AI service, cloud service, or third party through copy, drag, or file operations is handled under the recipient's terms and privacy policy. If the user chooses a cloud-synced output folder or uses an OS clipboard-sharing feature, that synchronization or sharing follows the user's service and OS settings.

5. Usage Analytics and Crash Diagnostics

The App uses the following services only when the user separately consents:

  • Firebase Analytics (Google LLC): app-screen and high-level usage events, app version, OS, device, language, and service-generated identifiers or session information for understanding usage and improving features and navigation.
  • Sentry (Functional Software, Inc.): crashes, errors, stack traces, app version, OS, device, event identifiers, and timestamps for investigating defects and improving quality.

The App does not send the following user content to Usage Analytics or Crash Diagnostics:

  • Captures and Freeze images
  • General context, annotations, instructions, and supporting text
  • Prompts, Markdown, and manifests
  • Clipboard contents and output files

Before sending a Sentry event, DirectCue rechecks consent and removes free-text messages, exception values, breadcrumbs, and stack source or variable contents. It removes device-specific local file paths from retained technical information and does not preserve arbitrary information attached to the original error. Captures, Prompts, and output file contents are not attached to error reports.

Usage Analytics and Crash Diagnostics can each be enabled or disabled in Settings. Disabling an option stops future transmission from the App for that service. Retention and deletion of data already sent follow the service provider's systems and policies.

6. Feedback and contact

When the user submits the in-app feedback form, the App sends:

  • Feedback type and message
  • Name and email address, only if the user enters them to request a reply
  • App version, build number, language, Free / Pro state, and submission time

Captures, annotations, Prompts, clipboard contents, and output files are not attached automatically. Information submitted through the contact form is used to respond to and manage the inquiry.

7. Purchase information

DirectCue Pro purchase and restore operations are handled through Apple's App Store and StoreKit. We do not receive complete payment-card details. The App may keep entitlement state on the device as required to provide the purchased feature.

8. External services and third parties

The following external services may be involved in providing the App:

  • Apple: macOS, Screen Recording permission, App Store, in-app purchase, and purchase restore
  • Google LLC / Firebase Analytics: optional usage analysis after user consent
  • Functional Software, Inc. / Sentry: optional crash diagnostics after user consent
  • Feedback infrastructure provider: receipt and forwarding of feedback the user submits

Except where required by law, we do not sell or provide user information to third parties for purposes outside this Policy. Information sent to an external service is handled under that provider's terms and privacy policy. Network metadata such as an IP address may be processed by the relevant service provider when communication occurs.

9. Retention and deletion

  • Saved output packages remain in the folder the user selected. The user can delete them individually in the App, by clearing History, or in Finder.
  • Files remain by default when entries fall outside the `Keep History` limit. Enabling `Auto-delete old output folders` also deletes older output folders beyond that limit. `Unlimited` retention does not trigger deletion based on an entry limit.
  • Uninstalling the App does not automatically delete output files in the user-selected folder. Copies in cloud storage or other sharing destinations must be managed through those services.
  • App settings, History metadata, Free usage state, and purchase entitlement are kept on the device for as long as needed to provide the features.
  • Usage Analytics and Crash Diagnostics data is retained under each service provider's policies.
  • Feedback and contact information may be retained for the period needed to respond, improve quality, and maintain appropriate records.

Contact us using the form below to request access, correction, or deletion of feedback or inquiry information we hold.

10. Security

The App Store version uses App Sandbox and accesses the folder the user selects to save output files. Section 3 explains the scope and purpose of screen capture, and section 4 explains storage and sharing.

Optional Usage Analytics and Crash Diagnostics do not initialize their SDKs before the corresponding consent. Sentry has memory introspection, default PII transmission, automatic breadcrumbs, network/file-I/O tracking, performance tracing, and session tracking disabled. The App applies the protections described in section 5 before sending an event.

We take reasonable administrative and technical measures to protect information handled by the App. Users should review capture targets, output packages, clipboard content, and handoff destinations for personal or confidential information and appropriately secure their Mac account and device. Report a security or privacy concern using the contact form below.

11. Children's privacy

The App is not designed primarily for children.

12. Changes to this Policy

We may update this Policy in response to changes in law, external services, or App features. Material changes will be announced on this page or in the App, and the last-updated date will be revised.

13. Contact