Privacy Policy

Queue Manage Console

Effective date: 2026-10-12

This policy explains how this application handles information and how to contact us about privacy.

Information we process

Queue Manage Console stores your administrator display name, environment URL, polling interval, language, appearance, alert thresholds and cached queue, worker and event records on your device. A random installation secret is stored in iOS Keychain separately for each HTTPS server origin. The service stores a hash of this secret, installation settings, queue names, task payloads awaiting processing, queue depth history, worker status and metrics, and operational events. Tasks perform repeated SHA256 hashing; completion events contain the queue name and digest, not the original payload. Railway receives network requests and may process IP addresses, request timing, paths, response codes and infrastructure logs. The app has no accounts, advertising, analytics SDKs or geographic maps.

How we use information

Data is used to operate installation-scoped task queues and real worker processes, display resource measurements and events, synchronize settings, provide offline reading, export logs when you choose the system share sheet, and deliver local threshold alerts when iOS permits a refresh. The installation secret authorizes access only to your installation. No email delivery or support ticket service is implemented.

Service providers and sharing

The backend is hosted on Railway, which processes service data and infrastructure request logs to provide hosting. No advertising or analytics recipients are integrated. Log exports are shared only with the app or recipient you select through the iOS share sheet; those recipients apply their own practices. Network infrastructure and your selected custom server, if changed in Settings, receive the requests you send. The public privacy contact is ursula.templeton@icloud.com.

Data retention

Device settings and cached snapshots remain until you delete them or remove the app. Keychain items may survive uninstall; use the in-app deletion action before uninstalling when you want them removed. Pending task payloads remain until processed, explicitly cleared or the installation is deleted. Successful processing removes the pending payload. The service retains at most the latest 10,000 events per installation. Queue history older than one hour is pruned when depth is sampled. Installation settings and queue records remain until installation deletion. No separate application backup or scheduled backup process is configured. Railway may maintain infrastructure logs or recovery copies under its own hosting practices; a specific retention period or immediate erasure from provider recovery media is not asserted.

Deleting your information

The Settings deletion action calls DELETE /install to stop your worker and delete your installation settings, queues, pending tasks, history and events from the live service database. After successful server deletion the app clears all its local snapshots, saved profiles and server addresses, notification requests and installation secrets, and returns to the bundled initial environment. Only the active server installation is deleted remotely; data on previously selected servers is not erased by this action. Save or delete those installations separately before changing servers if needed. If the server cannot be reached, deletion reports an error and retains the secret so you can retry; it does not claim server deletion. Exported files shared with other apps are outside this deletion action. Provider recovery copies, if any, are subject to the provider lifecycle and are not explicitly erased by this API. Losing the installation secret prevents automatic recovery of the previous installation.

Permissions and your choices

Notifications are optional and requested only when you enable local alerts. You can disable alerts in Settings or withdraw notification permission in iOS Settings; queue management continues to work. Background refresh is subject to iOS scheduling and may be disabled in system Settings; periodic background delivery is not guaranteed. No location, contacts, camera, microphone or photo-library access is requested.

Your privacy rights

You may inspect your records in the app, change local and server settings, export selected logs, and delete your installation data from Settings. For privacy questions or rights requests contact ursula.templeton@icloud.com. Applicable rights depend on your jurisdiction. There is no account-based recovery or cross-device login. Do not email an installation secret; it is a credential and is not needed for a general privacy inquiry.

Security

The native app requires HTTPS for remote API endpoints and relies on the operating system certificate validation. Random installation secrets are stored in Keychain; the server stores only SHA256 hashes and verifies authorization and installation ownership on every private operation. Public home, health and privacy pages do not require this secret. SQLite foreign-key constraints and transactions protect record consistency. Payload limits, request limits and destructive-action confirmation headers are enforced server-side. Secrets are not deliberately logged. No security certification or absolute protection is claimed.

Children’s privacy

The product is intended for adult system administrators and technical operators, not directed to children. It does not request age or create user accounts. Users should not submit sensitive personal information in task payloads or queue names. Privacy concerns about data submitted by a child can be sent to the stated privacy contact.

Changes to this policy

This policy reflects the current app and backend processing and takes effect on 2026-10-12. Changes to processing will be reflected on this public page with an updated effective date. Review the Privacy Policy link in Settings for the current version.