Drumstick ID — Privacy Policy — lizefield
Drumstick ID
Images and recognition results
Drumstick ID uses the camera to capture drumstick markings and recognize text on the device. The working history stores OCR input images, recognized text, recognition source and confidence/quality information, image/text associations, timestamps and technical metadata so you can review results and product candidates. Android uses bundled ML Kit text recognition and an ONNX Runtime model; iOS uses Apple Vision.
Diagnostics and third-party processing
Explicit diagnostic recording can additionally save wider camera images, OCR inputs/results, processing events, errors and device/app information locally. Diagnostic archives can be retrieved through separate development/USB tools. Google documents that ML Kit Android SDKs can collect device/app information, installation identifiers and diagnostics/usage metrics. On-device OCR does not by itself exclude processing by the recognition SDK or platform services; see the linked provider data-disclosure information.
Retention and deletion
The working history persists between sessions and provides a reset operation. Resetting working history is separate from deleting diagnostic sessions or archives already copied elsewhere. Storage size/count limits are not a time-based retention period; diagnostic recording can stop at capacity while retaining existing sessions. History and diagnostic copies can remain until removed through the corresponding controls or operating-system app-data controls.
Common provisions
Developer and scope
lizefield is the developer and provider of the apps named on this site. The shared policy applies to lizefield apps that link to it, including existing apps not yet individually listed. Each named app page includes these common provisions and its own disclosures; a statement about one app is not a statement about every app.
Information handling and sharing
The information used depends on the app and feature, as described in the app-specific sections. Local processing or storage does not by itself exclude processing by SDKs, operating-system services or stores. If you export/share content, the destination you choose receives the exported content and handles it under its own terms. Revoking a permission stops access subject to the platform controls; it does not by itself delete previously saved data.
Retention, deletion and privacy inquiries
Saved local data can remain between sessions. The app-specific sections explain available deletion controls and their limits. Android app-storage clearing or uninstalling removes local app data; this does not erase copies already exported or data held by stores, service providers or support systems. Backup/restore behavior depends on the platform and app configuration; deleting an app record does not by itself erase separately held backups. For a privacy or deletion inquiry, use the contact form below; do not include unrelated sensitive information. The inquiry-content target below is separate from local app data and technical access logs. Deletion of records controlled independently by another provider is subject to that provider's controls.
Contact and external services
The PrivacyPolicy inquiry form sends your message, selected app, optional reply email, receipt reference and source-site information through Octerv's HTTPS inquiry endpoint to external communications and message-storage service providers used for receiving and handling inquiries. Providers receive and store that information; processing is not limited to this website or your device. Later email correspondence can create additional copies. This form sends no automatic reply email. Earlier contact forms could create separate form, spreadsheet, email and communications-service records; any copies still under lizefield's control are covered by the inquiry-retention rule below. Changing the contact route does not itself erase earlier copies. This site is hosted with GitHub Pages, whose hosting services and privacy statement apply to visits.
Protection and revisions
The inquiry form submits to an HTTPS endpoint. App-local storage and operating-system permission controls are described for each app. Exported copies, backups and records held by external services are subject to their own access and protection controls. The date above indicates this policy's latest content update.
Inquiry retention target and deletion requests
lizefield aims to delete inquiry content, reply contact details and related correspondence under its control around 90 days after receipt. If an inquiry is still in progress at that point, it is retained until handling is complete and then deleted. This is a manual retention policy, not a claim that automatic deletion or historical cleanup has occurred. It covers PrivacyPolicy inquiries, Octerv Setlist feedback and remaining developer-managed copies from previous contact routes where present. For a deletion inquiry, use the PrivacyPolicy form and provide the receipt reference or approximate submission date and app. Sending a request does not itself delete data, establish authority over another person's records or guarantee erasure from independently controlled provider backups. The inquiry rule does not set retention for app-local data or technical access logs.
Technical logs and separate retention
Website and inquiry hosting can involve technical connection records such as IP addresses, request information and user-agent information, separately from inquiry content. Octerv application logs use a seven-day retention setting. Log events are deleted through the service's retention processing after expiry, so this is not a guarantee of physical erasure at exactly seven days. lizefield does not retain additional load-balancer access logs for the inquiry endpoint under its current operation. Hosting and external-service providers may separately handle their own technical records and backups under their respective policies; those records are not assigned a seven-day expiry by this policy.