Services

Six tools. Each one its own answer.

What we build

01

Data Vault

Encrypted local storage with layered access controls and biometric lock options. File organisation, tagging, and retrieval without anything leaving the device. Keys are generated and stored locally; there is no server component.

Swift CryptoKit LocalAuthentication FileProvider CoreData SwiftUI

02

Cache Sweep

Deep scan across app containers, system caches, download folders, and residual install data. Results are grouped and totalled by category. Nothing is removed until the user reviews the breakdown and confirms. Supports scheduled scan reminders.

Swift SwiftUI FileManager BackgroundTasks UserNotifications StoreKit 2

03

Privacy Guard

Permission audit across installed apps. Surfaces camera, microphone, location, contacts, and health access in a single readable view. Flags any access that has changed since the last scan and links directly to system settings for remediation.

Swift SwiftUI CoreMotion Contacts HealthKit Amplitude

04

File Bridge

On-device conversion between document, image, audio, and data formats. Supports batch queues. No upload, no third-party API call, no waiting on a remote server. Output stays in the format and location the user specifies.

Swift PDFKit AVFoundation CoreImage UniformTypeIdentifiers SwiftUI

05

Scan & Extract

Camera-based document scanning with automatic edge detection, perspective correction, and clean PDF output. Optional field extraction for structured documents — receipts, IDs, forms — using on-device OCR. No paywall on the core scan function.

Swift VisionKit Vision PDFKit CoreML Adapty

06

System Watch

Continuous monitoring of battery health, thermal state, memory pressure, and CPU load. Presents diagnostics in plain language with trend history. Designed to measure without contributing to the resource pressure it reports. Lightweight background footprint.

Swift SwiftUI IOKit os.log MetricKit Instruments

Common questions

What platforms do you build for?

iOS and Android, using the native SDK for each. We don't use cross-platform runtimes where they compromise access to platform-level APIs — particularly around file access, permissions, and cryptography, which are central to most of what we build.

Do you handle app store submission and compliance?

Yes. Submission, review query responses, and ongoing policy compliance are standard. We keep up with store policy changes as part of the engagement, not as an add-on.

What does a typical project look like end to end?

Most start with a short discovery exchange to establish the scope. From there: architecture, incremental build, review cycles, submission, and a post-launch window. We don't attach unnecessary process to clearly defined work.

Can you take over maintenance of an existing app?

Occasionally. We'd want to review the codebase before committing. If the foundation is sound and the scope is clear, we're open to it — and we handle ongoing SDK updates, OS compatibility, and store compliance as part of that.

Do you work with early-stage ideas, or only production-ready specs?

Both. Some briefs arrive fully formed. Others start as a problem statement and a rough idea of the function. We're comfortable working upstream from the spec if the problem is well understood.