AdHocKit: Temporary Operations Privacy Policy

# AdHocKit: Temporary Operations Privacy Policy Last updated: August 23, 2026 ## Overview AdHocKit is a planned local-first Android toolkit for temporary real-world operations such as check-ins, equipment assignments, coat or bag claims, badge or key checkout, and simple counters. AdHocKit is currently in pre-implementation planning. This policy describes the approved V1 privacy and security design and must be reconciled against the actual release-candidate code before Google Play publication. It does not claim that planned features are already shipping. ## Planned V1 Data Handling AdHocKit is designed around data minimization. A workspace should collect only what a temporary operation needs. Depending on the tools an organizer chooses to use, planned V1 local data may include: - Names or other organizer-entered identifiers. - Check-in or attendance state. - Item names, numbers, or descriptions. - Temporary assignments such as a person holding a radio, badge, key, or other item. - Coat or bag claim numbers and descriptions. - Counter values. - Custom fields or notes deliberately entered for the operation. - Workspace configuration, retention choice, status, and operational history needed to reconcile actions safely. Some of this information can be personal or sensitive in context. AdHocKit is designed not to require email addresses, phone numbers, birthdays, permanent profiles, or other identity fields unless a future user-configured workflow genuinely needs them. ## Local-First Storage The approved V1 design stores core operational workspace data in the app-private local database on the Android device. Workspace database files are not intended to be written to shared public storage. V1 operational workspace data is designed to be excluded from Android backup and device-transfer restore paths so expired or deleted temporary records are not silently restored later. The V1 baseline does not add database-level encryption beyond Android app-private storage and normal device/OS storage encryption. AdHocKit must not be marketed as a regulated-data vault or as providing protections the implementation has not verified. ## Accounts, Network, Analytics, And Advertising Local V1 is designed to require no AdHocKit account and no developer-operated cloud backend for core workflows. The approved V1 foundation does not require third-party analytics or advertising. Operational content such as names, contact details, item labels, claim descriptions, notes, custom-field text, and raw workspace records must not be sent to analytics. If future telemetry is added, it should be content-minimized and limited to non-content operational categories or aggregate counts where appropriate. Any future cloud collaboration, account system, backend, analytics, crash-reporting SDK, advertising, billing, or other network-dependent feature must be documented here and in the applicable Google Play declarations before release. ## Retention And Deletion At workspace creation, the approved V1 design lets the user choose how long AdHocKit should retain that workspace after it is closed: - 24 hours. - 7 days. - 30 days. - Until manually deleted. An active workspace is not intended to disappear merely because a wall-clock duration has elapsed. For timed retention, the deletion deadline begins when the workspace is closed. Android background scheduling is best effort, so AdHocKit must not promise deletion at an exact minute. The V1 design uses persisted expiry state plus deterministic in-app reconciliation, with a local recovery grace period before final cascade deletion. A user may also explicitly permanently delete a workspace after a clear confirmation where implemented. Clearing AdHocKit app storage or uninstalling the app removes local application data according to Android platform behavior. Because local V1 has no AdHocKit server account, there is no V1 server-side workspace copy to request deletion from. ## Import And Export Planned import/export features use Android system document and share mechanisms rather than broad shared-storage access. Exports are user initiated. Exported files may contain personal or operational data depending on what the user entered, and once a user saves or shares an export outside AdHocKit, that copy is controlled by the destination selected by the user. ## QR And Barcode Features QR/barcode support is planned for a later phase rather than the local manual V1 foundation. The design calls for generated codes to prefer opaque application identifiers instead of embedding raw personal information. Scanned external codes must be treated as untrusted input and must not automatically execute arbitrary URLs, scripts, privileged imports, or destructive operations merely because a payload was decoded. If scanning ships, this policy must be updated to reflect the actual camera permission and data flow. ## Logs And Diagnostics The AdHocKit design requires content-minimized logs. Operational values such as attendee names, email addresses, item labels, coat descriptions, notes, claim data, and export contents should not be written to normal logs or diagnostic breadcrumbs. Google Play may process standard app distribution, installation, update, purchase, and platform reliability information under Google's own policies when those platform services are used. ## Children AdHocKit is a general-purpose operations utility and is not currently designed as a child-directed service. Any release or use case specifically targeting children requires a separate review of the product, data practices, store declarations, and applicable legal requirements. ## Future Changes This policy must be updated before shipping any implementation that materially changes AdHocKit data handling, including cloud synchronization, multi-device staff access, accounts, analytics, crash reporting, advertising, QR/barcode scanning, billing, or broader collection of personal information. The release-candidate code and Google Play declarations remain the source of truth for what the published app actually does. ## Contact Developer: Quinn Favo / Quazmoz For privacy questions or support, contact: Quazmoz@vivaldi.net Public policy URL: https://consultant.quinnfavo.com/privacy/adhockit