CCullapse
Support

Support, updates, and what to expect.

Cullapse is built and maintained by one person. There is no company, no support staff, no on-call rotation. The app is provided as is. This page sets honest expectations for what that means in practice.

Updated 2026-05-14·Version 1.0

Contact

One inbox covers everything: dev@snxt.ai. Bug reports, feedback, questions about the app, licensing, privacy — they all arrive in the same place.

What to expect when you write

I read every message. I do not commit to a response time and I do not promise a reply on any particular schedule. If I can help quickly, I will. If your message needs investigation, it may take longer or it may not get a reply at all.

The most useful messages are the ones I can act on without a back-and-forth. Bug reports especially benefit from including the Cullapse version, your OS version, and the mail provider involved.

What I can help with

  • Bug reports — please include the version, OS version, and provider where relevant.
  • Feedback on the app's behavior, design, or copy.
  • Questions about how a feature is supposed to work.
  • Licensing and purchase questions (mostly handled by Apple's App Store, but I can answer Cullapse-specific things).

What I cannot help with

  • Configuring your mail provider. Gmail app passwords, server hostnames, account suspensions, OAuth grants — those are between you and your provider.
  • Recovering deleted mail. Cullapse cannot restore messages your mail provider has already removed. See EULA §5.
  • Custom development, private builds, or integrations with internal tools.
  • Anything outside the app itself. I cannot debug your network, your mail rules, or your inbox at large.

Compatibility

Cullapse 1.0 targets macOS 14 (Sonoma) and later, and iOS 17 and later. There is no formal support window — when a new major OS ships, the current Cullapse continues to work on the previous versions for as long as it does, and the next release may require something newer.

The app has been used against Fastmail, iCloud Mail, Google Workspace (with app-specific passwords), and generic IMAP providers that implement RFC 3501 and TLS. Providers can change behavior at any time. When that breaks something visible, I'll fix it when I can.

Update philosophy

  • The privacy contract is permanent. No future release will read message bodies, send mail, fetch attachments, or ship inbox content to a server I operate. If that ever changes, the app has changed identity and you'll know.
  • Small releases when they're ready. Cullapse ships updates when they exist. There is no roadmap, no release cadence, no schedule. New versions land when they are done.
  • No beta program. What ships is what ships. I do not maintain a public TestFlight ring or pre-release channel.
  • No timeline promises. A bug being reported does not commit me to fixing it on any particular schedule, or at all. I will if I can.

What “lifetime” means

Definition

“Lifetime” refers to the period during which I continue to release updates for the then-current major version. It is not a promise of perpetual access to every future major release.

When you buy Cullapse, you get the current version and any updates I release for that major version. If a future major version is significantly larger work, I may release it as a separate paid app. I will say so clearly when that happens. What I will not do is silently flip the app to a subscription.

Refunds

App Store refunds are handled by Apple. Use reportaproblem.apple.com within Apple's published refund window. I cannot issue refunds for App Store purchases.

No service-level commitment

Cullapse is a desktop and mobile application, not a hosted service. There is no uptime SLA because there is no service to keep up. If this website or the build pipeline goes down, the app on your machine keeps working.