Quench Privacy Policy

Who is responsible

Quench is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). Questions and privacy requests:

Contact: captainlongevity@gmail.com

The records stored on your device

• Your shop equipment profile, custom steels, target hardness, blade thickness, selected quench medium, and heat-treatment schedules.
• Session stage times, batch results, measured hardness, calibration offsets, notes, and photos you select.

These records and preferences are used to provide the app features you choose. Local calculations do not send the input records to a developer-operated service. There is no in-app account or developer-operated cross-device sync.

Shop settings and batch notes update the local data model as you edit; they are not a separate recoverable backup. New custom-steel drafts and unfinished setup choices are held in the current screen until you choose Save or Start; unsaved screen state can be lost if the app closes. The app also stores local preferences outside the main database, including setup completion, the installed corpus version, and the time a system rating request was last made. The rating-request time is used only to avoid repeated prompts; it is not sent to the developer and does not record whether you rated the app.

How Quench handles its main features

Steel-reference data is bundled with the app. Schedule generation, temper interpolation, and calibration from your measured results run on your device. Opening a cited source in your browser is separate from the local calculation.

Optional permissions and system services

• Selected photos: The system photo picker gives the app the photos you choose for a record. Those copies stay in local app storage; the app does not browse or upload your entire photo library. Picking an item may cause the system Photos service to retrieve it from your own iCloud Photos account.
• Notifications: Optional reminders and timer alerts are scheduled locally after you grant notification permission. There is no developer-operated remote push service. iOS settings, focus modes, power state, or other conditions can delay or suppress an alert.

Permissions are requested in connection with the feature that needs them. You can refuse or revoke them in iOS Settings; features that need a refused permission may be unavailable. Selected photos and files are separate from granting unrestricted access to an entire library.

Widgets, shortcuts, and session displays

Widgets and shortcuts use locally stored or cached app data in this app’s shared container. Live Activities show current session information through Apple’s system interface. Information you choose to display can be visible on a Home Screen or Lock Screen; use the system’s display and notification settings for sensitive records. These displays do not create a developer-operated upload service.

Sharing, exports, and external links

Individual kiln programs can be shared as text or PDF, and individual batch cards as images, using the iOS Share Sheet. Programs are for manual entry into your controller; the app does not control a furnace. Generating a PDF creates a temporary file in the app container for sharing. That file can remain until replaced or cleaned up by the app or operating system; generated exports are not restorable database archives.

Generating a file locally does not send it to us. When you choose a sharing destination, that app or provider can receive the selected content and apply its own privacy and retention rules. Opening a web link sends an ordinary request to the linked site. Review a report, photo, or screenshot before sharing information about yourself or others.

Apple purchases, ratings, and diagnostics

Apple handles in-app payment and subscription billing. Optional rating requests use Apple’s system interface; iOS decides whether to display a prompt. The app processes StoreKit product and transaction information to purchase, restore, and verify paid access. We do not receive your payment-card details or billing address through the app. Apple may provide sales reports and, depending on your Apple settings, diagnostic information through its developer services.

The compliance update removes the earlier hidden sample-data mode and its local Pro unlock. In the updated app, paid access is re-established from verified Apple transactions at launch; an App Group cache mirrors that result for local feature checks and widgets. The previous demo-unlock cache is ignored and removed when the app writes the new cache. This change does not delete existing shop settings, sessions, batch records, or previously inserted sample data. Older installed app versions retain their earlier behavior until updated.

Apple’s handling of purchases, device services, backups, and diagnostics is described in Apple’s privacy information.

Analytics, advertising, and tracking

We have not added advertising, behavioral analytics, or third-party crash-reporting SDKs to Quench. We do not sell your app records or use them for cross-app advertising tracking. This does not mean that Apple, an external site you open, or an optional data provider receives no connection information. Their exchanges are described above.

Retention, deletion, and device security

In the updated app, deleting a batch removes its linked photo entries and the batch after a successful database save, then clears a matching last-batch summary in the shared widget cache and requests a widget refresh. Widget refresh timing is controlled by iOS. A summary left by a deletion in an earlier version can remain until a later batch overwrites it or the shared app storage is removed; installing this update does not by itself purge those older summaries. SwiftData manages the stored photo bytes; deleting database records is not a guarantee of immediate physical erasure from storage or backups. Deleting a steel profile retains previously saved batches and their frozen schedule and result data. There is no Recently Deleted or full-database archive restore; a generated result sheet is a reference copy.

If the local database cannot be opened, the updated app stops editing and offers a retry instead of silently creating a temporary replacement journal. Earlier versions could fall back to memory-only storage in that situation; records created in that fallback were not persistent across app termination. These changes apply after installing the update.

Removing the App normally removes its local container, not independently kept original media, exported files, recipient copies or older backups. Manage those copies separately. Device-backup recovery requires a usable completed backup; the developer has no record archive to retrieve.

Use a device passcode and appropriate operating-system protections. Quench does not provide an in-app biometric lock. Widgets and Live Activities may be visible outside the app. Because we hold no remote journal copy, we cannot recover a lost local record or delete a copy you sent to another provider.

If you contact support

Emailing captainlongevity@gmail.com voluntarily gives us your email address, message, and any attachments you send. We use that information to answer your request, investigate the issue, and meet applicable recordkeeping obligations. It is processed through email providers and kept as needed for those purposes; you may ask us to delete support correspondence, subject to any legal retention requirement. Please omit unnecessary private records.

This policy website

These static legal pages are hosted by Vercel. Loading a page makes a web request that can disclose your IP address, page URL, time, and browser or connection metadata to the host for delivery and security. We have added no advertising or analytics scripts to these pages.

Hosting information: Vercel’s Privacy Notice.

Children and privacy requests

Quench is not designed to solicit children’s personal information through accounts or a developer-operated journal service. If you believe a child has provided personal information to us through support, contact us. You can manage local records yourself and contact us about support correspondence or other data we actually hold. For information held by Apple or another provider, use that provider’s request process.

Policy changes and contact

We will update this page and its last-updated date if these practices change. Material changes to app data handling will be explained before or when the affected feature is introduced. Privacy questions: captainlongevity@gmail.com.

Checked equipment and library saving

The updated App checks equipment-profile creation and each equipment-setting change. Failed writes show an error and keep the prior setting; profile read failures do not create a replacement profile. Onboarding completes only after the equipment profile saves. Existing ambiguous profiles are retained for support rather than silently merged. The steel-library update commits its changes before recording the installed corpus version, preserves user-modified steel rows, and offers Retry library update after a failed read or save. Custom steel and batch/photo deletion failures retain their original records without rolling back unrelated pending drafts. Intentional temporary session editing remains available. This does not provide a backup, export/restore workflow or heat-treatment certification; verify current supplier data and maintain independently checked device backups.