Privacy Policy

Effective Date: April 4, 2026

Michael Neill Hartman built the gref app as a macOS application. This service is provided by Michael Neill Hartman and is intended for use as is.

1. Data Collection and Telemetry

gref collects absolutely zero personal data, behavioral analytics, network telemetry, or usage tracking information.

The application is explicitly designed to operate completely offline. There are no tracking scripts, analytics pipelines, or external authentication servers. Your workflow is strictly your own.

2. Local File and Security Access

gref heavily utilizes Apple's native App Sandbox security architecture.

• It will natively prompt you through macOS for explicit, user-granted authorization to evaluate and write to your designated target workspace directories.
• All data generated, ingested, hashed, or archived by gref remains cryptographically localized directly inside the exact directories you point it at. Or inside the app's local private container.
• The application securely stores directory access "Bookmarks" inside its local private container so you do not constantly have to re-authorize the precise paths on reboot. These bookmark tokens securely persist via the OS and never leave your machine.

3. StoreKit Validation

For gref instances downloaded automatically through the Mac App Store, standard Apple StoreKit AppTransaction validation sweeps execute strictly locally connecting through Apple's native OS daemons to guarantee software integrity. We do not maintain off-site validation licensing hubs.

4. Changes to This Privacy Policy

If our baseline data constraints ever expand in the future, we will update this document directly ahead of time.

5. Contact

If you have any questions, integration bugs, or suggestions regarding our secure workflow engines, please reach out via our primary developer support channels!