Privacy, in plain sight.

01. Scope and who is responsible

Stackintosh is developed by Brandon Donnelly. This notice covers the Stackintosh Mac app, the bundled macbridge and macbridged command line tools and background service (internally called MacBridge), and the static website at stackintosh.ai. Contact: b@smn.vg.

The developer handles information received through this website and support correspondence. When you or an organisation operate the software and configure workers, you or that organisation control those machines, projects, check profiles and their data. If you use Stackintosh at work, ask your administrator about the organisation’s policies. The final notice must confirm the responsible legal entity, business address, jurisdiction, and any required representative or data protection officer.

02. The short version

The reviewed development source does not require a Stackintosh account and does not include developer-operated advertising, tracking or analytics. Project files, check output and worker hardware readings are not sent to the developer by a built-in reporting service. They are still processed and stored on your machines and configured workers, and may contain personal or confidential information.

This website has no contact form, advertising scripts or analytics added by the site author. Its assets are served locally from the hosting origin. Animation preferences last only for the current page; the site’s own code does not set cookies, local storage or a cross-site identifier. The hosting provider can still process ordinary request and security information. External links and email have their own data flows.

03. Project files and snapshots

When you submit a check, the service reads the saved files of the registered Git worktree. This includes tracked files as saved on disk, staged or unstaged edits, and untracked files that Git does not ignore. Ignored files or folders are included only when a reviewed task profile lists them as required excluded inputs. Unsaved editor buffers are not captured. Unsupported layouts, including nested repositories, submodules, sparse checkouts and Git LFS inputs, are refused.

File contents, relative paths, permitted link targets, executable information, content digests and the snapshot manifest are processed to prepare and identify the exact source checked. Project locations, profile definitions, command arguments, configured environment values and executable identities may be recorded with a run. Source files can contain personal data or secrets: review the project and required inputs before submission. Ignoring a file is not a substitute for controlling a secret already present in a tracked file.

Checks run in a separate materialised copy. Snapshot capture does not write your Git index, HEAD or branches. This protects the capture workflow; it does not promise that every reviewed tool is harmless or unable to access other resources available to its operating-system account.

04. Workers, SSH and network discovery

For a configured remote worker, the coordinator sends the snapshot objects needed for a check over SSH, sends the reviewed task and execution information needed to run it, and receives status, output and capacity readings. The worker stores snapshot objects, an attempt directory, execution records and output. Configure only machines and accounts you trust, verify SSH host keys, and protect the SSH identities you select. Stackintosh uses the system SSH tooling; your SSH configuration and any jump hosts or administrators also affect the route and who can access the machines.

Bonjour discovery on the local network can expose a sharing machine’s service name, host name, account, addresses, SSH port and protocol version. Other devices on that discovery network may see the advertisement. Nearby candidates are not verified or automatically trusted, and discovery alone does not send them project files or pair them. Sharing and browsing depend on configuration, active interfaces and macOS local-network permission.

A worker may be in another location or country. You or your administrator choose it. File transfers, remote access, backups and the worker account’s permissions must be appropriate for the data in the project, including any employer, customer or regulatory restrictions.

05. Hardware readings and scheduling

The service reads operational information such as available memory, memory pressure, slots, power and battery conditions, thermal readings where available, operating system and architecture, detected GPUs and drivers, and Tiny CPU kernel support. It uses these readings to display capacity and decide whether a check can start under the reviewed configuration. These are machine scheduling readings, not developer-operated usage analytics.

The coordinator and clients can receive readings from configured workers. Host names, accounts and machine details may identify a person or device. If required readings are unavailable or stale, work can be deferred. Scheduling does not evaluate people or make decisions about employment, credit or other legal rights.

06. Results, output and diagnostics

The service records runs, attempts, caller subscriptions, snapshot and action identities, states, timestamps, exit outcomes and check output. Standard output and error can contain file paths, personal data, test fixtures, credentials or other secrets printed by tools. Stored output is bounded by configuration, but a size limit does not redact sensitive content. Access to the state directory, the machine account and backups should be restricted accordingly.

Runtime diagnostics can be written to standard error and macOS Unified Logging. They may include operational errors, paths and worker connection information. Apple may separately receive App Store or operating-system diagnostics according to Apple’s practices and your settings. This is distinct from an automatic developer-operated upload. If you share a log with support, inspect and redact it first.

07. Permissions and local storage

In sandboxed app distribution, selected project folders and explicitly allowed tool folders, files and SSH identities are represented by app-scoped security bookmarks. The app also keeps preferences such as appearance. The background service and bundled tools can use an app-group state directory; standalone tools use a platform state directory unless you choose an override. These records are kept to reconnect to permitted resources and operate checks.

You can manage project choices, folder and file allowances, worker configuration and local-network permission. Removing an allowance affects the service when it next starts; it does not recall files already transferred to a worker or remove existing snapshots. Turning off a feature, revoking future access or closing a client is not the same as deleting stored data or cancelling accepted work.

08. Optional Apple Intelligence and Siri

If you explicitly request a summary of finished output, the app supplies a bounded excerpt to Apple’s on-device SystemLanguageModel on the current Mac. Stackintosh does not send that excerpt to a remote AI provider, use it in a developer-operated model training service, or save the generated summary. A summary can be wrong; the original log and result remain authoritative. Model availability depends on the Mac and Apple Intelligence settings.

App Intents let you create Mac shortcuts to request a reviewed check, read status or open Workers, and Siri can invoke a shortcut by name. Apple handles Siri audio, voice requests, Shortcuts and Apple Intelligence system services under its own privacy notices and your settings. The app’s on-device output summary claim does not mean all Siri interactions are processed only on-device. Use the app or command line if you prefer not to invoke Siri.

09. Your reviewed tools have their own behaviour

A task profile selects the executable, arguments, working directory and configured environment. Commands, dependencies, test suites and development tools may contact package registries, cloud APIs, telemetry endpoints or other services; read files accessible to their account; and write output containing sensitive information. Their data practices are governed by the tools and services you choose. Stackintosh does not provide a universal network-isolation or secret-redaction guarantee for arbitrary commands.

The software does not automatically install dependencies on workers. Review and maintain the required tools and inputs yourself. If you deliberately use a third-party AI, cloud service or telemetry client through a check, that is a separate data flow from the optional on-device summary described above.

10. Website hosting and support email

The website is statically hosted using the Porkbun hosting account selected by the site owner. To deliver and secure a page, the host and its infrastructure providers may process IP addresses, request times, requested URLs, browser or device headers, referring information when provided, and security or error logs. The site author has not added analytics or advertising. The provider’s exact subprocessors, server locations, access-log configuration and retention have not yet been confirmed and must be documented during professional review.

If you email b@smn.vg, your email provider, the recipient’s email providers and the developer process your address, message, attachments and related correspondence to answer and resolve the request. Email is optional; the app’s core local workflow does not require sending support mail. Do not include passwords, private keys, access tokens or private source code. An external source or documentation link connects you to GitHub, which handles that visit under its own privacy notice.

11. Purposes, legal bases and disclosures

Local project, configuration and machine information is processed to provide the check workflow you request. Website request information is processed to deliver and protect the website, and support correspondence is processed to respond to you, investigate issues and maintain a record of the resolution. The appropriate controller and lawful basis depend on who operates the software, the purpose and the laws that apply.

For developer-controlled website and support processing, a professional must confirm whether legitimate interests (operating a secure site and answering requests), steps requested before a contract, contractual necessity, consent or a legal obligation applies to each purpose. This draft does not assert a blanket lawful basis. If consent is used, it must be specific and withdrawable; withdrawal does not undo earlier lawful processing.

The current app has no built-in sale of project or usage data and the authored site has no behavioural advertising integration. Developer-controlled information may be accessible to hosting and email providers as needed to deliver their services, or disclosed where legally required or necessary to handle a valid legal claim. Any future business transfer or additional service provider would require an accurate updated notice and any legally required safeguards or choices. The draft does not promise arrangements that have not been put in place.

12. Retention and deletion

On your machines, retention is controlled by the service configuration and the records still needed for active or retained work. The current example configuration keeps 200 finished runs; that is a configurable run count, not a guaranteed number of days. Referenced snapshots, attempt copies and output can remain while their records are retained. Coordinators and remote workers may retain separate records. Backups, exported output, system logs and copies made by your tools follow their own lifecycles.

Uninstalling the app does not by itself delete service state. To remove local data, stop the service after dealing with accepted work, identify the actual state directory and remove the state you no longer need on each participating Mac. The app bundle normally uses ~/Library/Group Containers/9TAF9G7C93.macbridge/state; standalone macOS tools normally use ~/Library/Application Support/MacBridge. --state-dir and MACBRIDGE_HOME can change the location. Confirm it before deleting anything and account for backups and worker copies.

Support correspondence should be retained only as long as needed to resolve the request, handle follow-up, meet legal duties or establish and defend legal claims. A fixed schedule has not been confirmed. Hosting-log retention is controlled by the provider and has not been verified. Contact the developer to request deletion of developer-held correspondence; the final notice must replace these unknowns with verified periods or concrete criteria.

13. Security and international transfers

The implementation uses private local service communication, restricted state directories, content digests and SSH transport to configured remote workers. The website is intended to be served over HTTPS. These measures have limits: digests are not encryption, private directories do not encrypt data at rest, and a separate task directory is not a complete operating-system security boundary. Protect your devices, accounts, SSH keys, backups and reviewed commands; no system can promise absolute security.

Developer-controlled hosting or email may involve international processing. The relevant countries, provider agreements and any required transfer mechanism must be verified before the final policy is adopted. This draft does not claim that standard contractual clauses, an adequacy decision or another transfer safeguard is already in place. Your independently configured remote-worker transfers are controlled by you or your organisation.

14. Your privacy rights and choices

Depending on the laws that apply and the data involved, you may have rights to access, correct, delete or obtain a portable copy of personal data; restrict processing; withdraw consent; or complain to a relevant data protection authority. Exceptions and identity checks may apply. Email b@smn.vg with a description of the request and the information concerned. Provide only what is necessary to identify the request; do not send identity documents or secrets unsolicited.

Right to object: where processing relies on legitimate interests, you may have a right to object based on your particular circumstances. State that you are objecting and describe the relevant processing. A final notice must confirm which rights and response periods apply in the operator’s actual jurisdictions. It should also assess California and other US state privacy requirements if their applicability thresholds are met, including any legally required sale, sharing or opt-out disclosures.

The developer cannot remotely delete information stored only on Macs you or your administrator control. Direct those requests to the machine owner or organisation. Revoking permissions, removing workers from configuration and deleting stored records are separate choices. You can pause this website’s animations, and it respects your system’s reduced-motion preference without saving a visitor profile.

15. Children and automated decisions

Stackintosh is a developer tool and is not directed to children. The authored website does not ask for age or provide an account or form. If you believe a child has provided personal information to the developer through support, contact b@smn.vg so the situation can be assessed and appropriate action taken. Professional review must confirm age-related obligations for the markets where the product is offered.

The app makes technical scheduling decisions about checks and worker capacity. The reviewed source has no feature for developer-operated profiling of visitors or solely automated decisions producing legal or similarly significant effects on people. Optional generated explanations do not alter the recorded outcome of a check.

16. Changes, contact and review status

Material changes to software data flows or developer-controlled processing should be reflected here with an updated date and any additional notice or consent required by law. This draft was prepared on 27 October 2026 from the current repository and authored website. It must be checked against the actual release build, distribution method, hosting configuration and business practices before being treated as final.

Before release, professional review must confirm the legal operator and contact address; applicable jurisdictions and rights; controller or processor roles and any required data processing agreement; actual providers and subprocessors; logging and retention; international transfers and safeguards; Apple distribution disclosures; and an operational process for responding to requests and security incidents. For questions, corrections or privacy requests, email b@smn.vg.

The review checklist was informed by the UK Information Commissioner’s guidance on privacy information. That guidance is itself under review following legal changes; it is a reference for professional review, not a claim that UK law necessarily applies or that this draft satisfies it.