Security whitepaper

Purpose and scope

This whitepaper describes how Reefo, Inc. ("Pacific Machines", "we") protects the Pacific Machines desktop application, related cloud services, and pacificmachines.ai. It is written for security, legal, and procurement readers who need a public, no-login summary of our program.

It covers:

• The product security model (what stays on the device vs. what uses the cloud)
• Access control, encryption, and release integrity
• Vendors, people, incident response, and vulnerability reporting
• Current compliance status

Contractual terms live in the Terms of Service. Data collection, retention, and user controls live in the Privacy Policy. Operator how-to lives in product documentation. This document is not a SOC 2 report, not a HIPAA certification, and not a substitute for a signed agreement.

Version 2026.10.18 · Classification: public

Security program

Pacific Machines is operated by Reefo, Inc., based in San Francisco. We maintain a documented information security program. Approved internal policies cover access control, operations, cryptography, secure development, risk management, vendors, human resources, asset management, business continuity, and incident response. Those policies are reviewed at least annually.

Roles for designing, operating, and monitoring security controls are assigned in job descriptions and in our information-security roles policy. Production access is limited to authorized personnel with a business need.

Current examination

We are currently in process with Vanta toward SOC 2 Type II and expect to obtain SOC 2 in the coming weeks. Until an independent report is issued, we are not SOC 2 certified. Do not treat this whitepaper, our Trust Center, or marketing materials as a completed attestation.

Product architecture

Pacific Machines helps a company decide what to automate with AI by learning from approved real work. Capture begins on the user's computer. A person reviews evidence and decides what should move forward. The product does not deploy automations on its own.

What we observe

Learning uses approved accessibility and interaction signals while it is turned on. It does not capture screenshots, pixels, OCR frames, video, or images. It does not capture audio, store accessibility trees, retain raw keystrokes, or save pointer coordinates. Meeting transcription is not part of the product.

Operating-system permissions gate capture. On macOS that includes Accessibility and Input Monitoring. Pacific Machines cannot override those OS controls. Learning does not request Screen Recording because it does not read pixels.

What stays on the device

The raw record stays on the computer. Learning writes it under ~/.jarbas (UI brand: Pacific Machines; on-disk root unchanged), in ~/.jarbas/db.sqlite. That database holds bounded accessibility text, the focused app and window, available document or repository context, focus transitions, clicks, shortcuts, and semantic typed or pasted text after local redaction. It does not hold screenshots, pixels, video, images, accessibility trees, raw keystrokes, or pointer coordinates. The raw library is not uploaded.

A Daily Recap is a separate file the app writes from that local record, one per day, in time order. It is an activity log: app, window, what was opened, clicked, shortcut, pasted, or typed. It is not a story, screenshot, image, or copy of raw accessibility text. While recording is on, that log is sent to the organization a few times during the day. The raw database stays on the computer.

What uses the cloud, on purpose

Controls available to the user

• Pause or stop Learning
• Ignore lists for apps and URLs (saving the list applies going forward and does not delete past captures)
• Text cleanup that replaces common secrets and personal data in stored text with labeled placeholders
• Date-range delete or a full local reset from Settings → Storage

Text is redacted before it reaches local storage; text is dropped if redaction fails. The separate cleanup tool is pattern-based and runs on the computer. It can miss sensitive data that does not match a rule, and it edits stored text in the local database. It does not upload that database. Legacy image files left by an older capture mode are not modified; current Learning never reads or writes screen pixels. Full file paths, detection categories, and limitations are in the Privacy Policy.

Identity and access

Customer and employee access to Pacific Machines accounts uses unique identities through our identity provider (Clerk). Organizations manage seats and membership. Privileged access to production systems is restricted to authorized personnel and revoked when employment or contractor access ends.

Personnel acknowledge information security, confidentiality, and acceptable-use policies. User access to in-scope systems is based on role, or requires a documented request and approval, in line with our Access Control Policy.

Customers are responsible for protecting their own account credentials, for choosing who joins their organization, and for configuring capture permissions, ignore lists, and cleanup on each device.

Encryption

In transit

The public website and cloud APIs are served over HTTPS (TLS). Chat, Agent, authentication, Brain sync, and shared-report traffic to our providers also uses encrypted connections.

At rest (cloud)

Cloud services we use for authentication, Brain sync, shared reports, and related backends encrypt data at rest under their own controls.

At rest (device)

Local capture files are not encrypted at rest by Pacific Machines. Protection relies on the operating-system user account and disk encryption (FileVault on macOS, BitLocker on Windows). Organizations that process regulated data should require disk encryption, MDM, and other endpoint controls in their own environment. That is a customer control, not something this app can enforce on the laptop.

Secure development and releases

We follow a documented secure-development and change-management approach: production changes are reviewed before they ship, and access to promote builds is limited to authorized people.

Desktop installers are not offered as a self-serve download on pacificmachines.ai. To receive the current signed build, book a call. We share the installer after that conversation.

Book a call

Before a Mac build is promoted it is signed, notarized, stapled, and integrity-checked. Windows builds receive equivalent signature and integrity checks. Only authorized people can promote a build for customer distribution.

Once installed, the app receives newer builds through the signed in-app updater. When an install is below the minimum required version, Pacific Machines blocks with a clear Update action that installs through that updater on macOS and Windows.

Shipped product changes are listed on the public changelog.

Vendors and subprocessors

We use subprocessors for work we do not run ourselves. Written agreements with vendors that handle company or customer data include confidentiality and privacy commitments applicable to that relationship. Critical vendors are inventoried and reviewed as part of our third-party management policy.

Connected plugins never replace locally observed work. They run only for tasks you approve. The production hosts the desktop app may reach are listed in the Privacy Policy.

People and endpoints

Human-resource security policy requires personnel to be suitable for their roles and to understand their security responsibilities. Employees acknowledge a code of conduct and confidentiality terms. Security awareness training is required as part of onboarding and on a recurring schedule.

Company endpoints used for production work are subject to our workstation and operations policies. We do not treat a customer's laptop as our managed estate: the customer controls disk encryption, MDM, and who may run Pacific Machines on that machine.

Incidents and vulnerability disclosure

We maintain a documented incident response plan, including a HIPAA addendum for potential ePHI incidents when that program applies. Security and privacy incidents are logged, tracked, resolved, and communicated to affected or relevant parties according to that plan, the applicable contract, and law. Customer-facing availability for Pacific Machines application and services is published on the public status page.

How to report a vulnerability

Email hans@pacificmachines.ai with:

1. A short description of the issue
2. Steps to reproduce, or a proof of concept that does not include customer data
3. Impact as you understand it

Do not include secrets, PHI, passwords, or customer data in the first message. We will follow up on a tested channel.

Please do not probe, scan, or attack our systems or other users except with prior written authorization, as described in the Terms of Service.

Shared responsibility

Pacific Machines is used inside the customer's environment. We protect the service we operate. Customers protect the devices, accounts, and data they choose to put in front of the app.

If you process PHI/ePHI, you must do so only under an appropriate agreement (such as a Business Associate Agreement) and with controls you implement in your environment.

Compliance status

Reefo, Inc. uses Vanta to operate and evidence its security program.

Customer-facing product description is on pacificmachines.ai. For diligence beyond this whitepaper, book a call or email hans@pacificmachines.ai.

Related public documents

• Trust Center — compliance evidence and security questionnaires
• Product documentation — user guide and FAQ
• Changelog — public release notes
• Status — public application status and incident communications
• Privacy Policy — collection, storage, sharing, and user controls
• Terms of Service — contractual terms, including security commitments

Security contact: hans@pacificmachines.ai

Reefo, Inc. · San Francisco, California · Whitepaper version 2026.10.18