Skip to content

Private Beta

Spillway is currently available through a private TestFlight beta.

The Mac app is the most mature daily-work surface. The iPhone app is independently useful for ordinary mail, triage/action workflows, attachments, and selected cross-device use.

Privacy during the beta

Spillway does not automatically collect email, App data, usage history, diagnostics, crash reports, or other information from a tester's device.

The Operator cannot remotely inspect the tester's mailbox, local App database, Keychain, diagnostics, backups, or files through the App.

Bug reports and feedback reach the Operator only when a tester deliberately sends them.

Any future in-App diagnostic or feedback feature should explain what information would leave the device, where it would go, and who could receive it. Transmission should require explicit opt-in.

Who the beta is for

The beta is best suited to people who:

  • do substantial Gmail work on a Mac, iPhone, or both;
  • manage a complicated inbox or several accounts;
  • are comfortable using unfinished software;
  • can keep Gmail or another established mail client available as a fallback; and
  • are willing to report bugs or describe where the workflow does not fit their needs.

What testers should expect

Spillway is changing quickly. Features may be incomplete, interfaces may move, and some actions may fail.

Testers should not rely on Spillway as the only copy of important information.

Installation may occur through TestFlight or another explicitly provided Apple-signed test build. During private testing, some Gmail accounts may need to be enrolled before they can connect.

Testers should use the ordinary Connect Gmail flow and should never need to receive an OAuth JSON file or manually enter the application's client secret.

Review the Privacy Policy and Terms of Service before participating.

What feedback is most useful

Useful feedback includes:

  • mail navigation or interaction that feels unexpectedly slow or inconsistent;
  • messages or categories handled incorrectly;
  • recipient, account, thread, draft, or attachment behavior that differs from what you intended;
  • background AI that uses unexpected CPU, GPU, memory, or battery;
  • cross-device state that does not behave as expected;
  • confusing controls or wording; and
  • privacy or trust concerns.

Feedback is voluntary. Before sending a report, remove email bodies, credentials, student, patient, client, or other sensitive information unless including a specific excerpt is necessary and you deliberately choose to share it.

Local and cloud AI during testing

Local AI runs through the configured local service. Supported cloud AI providers can be configured explicitly.

Selected content sent to those services goes directly to the chosen provider under its terms, not to a Spillway-operated collection server.

Testers can pause new local AI work when they do not want background inference to start.

See Why Spillway uses local AI.

Giving feedback

Questions, beta inquiries, bug reports, and feedback may be sent to software@joshpasek.com.

Documentation provenance: Iterative human–AI construction. See Documentation Provenance.