This policy describes how PitTech (iOS bundle identifier com.pittech and Android package com.pittech) handles information. PitTech is a barbecue cook logging app published by Sportfolio.
iOS app
On iOS, cook names, dishes, notes, dates, and temperature readings you enter are stored in the app's private local library. The library is excluded from device backup. Cook logging does not require an account, and PitTech does not upload your cook library to its servers. You can choose a PitTech ZIP backup in the Files picker to restore it, or export a ZIP archive to a location you choose. Files you export or share can be accessed by the destination you select.
The iOS app uses Google's User Messaging Platform to refresh consent information when the app starts and to present a consent form when required. PitTech requests Google Mobile Ads only after Google's consent state allows ads. Google may process information such as IP address, ad interactions, diagnostics, and device or advertising identifiers to provide ads, measure performance, and prevent fraud. PitTech does not include cook records, notes, or temperature readings in ad requests. PitTech does not request App Tracking Transparency authorization or use cook data for advertising.
The iOS app supports optional read-only Beta temperature connections described below, in addition to manual temperature logging. Selected readings stay in your local cook library. The iOS app does not submit feedback reports.
Android app
On Android, PitTech stores cook information, photos, crash diagnostics, and experimental controller-test observations in the app's private local storage as described below. The Android app includes additional cook logging, reminders, feedback, and experimental grill integrations.
Information stored on your device
PitTech stores the cook information you choose to enter. This may include cook and dish names, meat type and cut, weight, preparation and ingredients, notes, dates and times, temperature readings, grill and probe names, ratings, and results.
On Android and iOS, selected or imported photos are copied into the app's private storage. Android and iOS may also save a crash diagnostic locally. That report can include a reference code, time, error summary, exception details, thread name, stack trace, and, on Android, process-exit details.
Cook logging does not require sign-in or online sync. Cook records and photos stay on your device unless you export or share them. Crash reports are saved locally and are not sent automatically. The app does not use an automatic crash-reporting service. The app does use Google Analytics (Firebase Analytics) for product analytics, as described under Product analytics below. In experimental debug and Firebase Dev controller-test builds, BLE scan observations, GATT inventory, protocol responses, bounded passive-notification statistics, and bounded controller debug observations are held in memory for the current controller-test screen session and are not uploaded automatically. Raw controller interrogation data is not persisted as a controller history.
Optional Cook Pack code sharing
If you choose Share by code and confirm the selected pack, PitTech uploads only that pack to its Railway-hosted service over HTTPS. The preview identifies the selected recipes or recorded meal, enabled cook stories and photos. Photo derivatives exclude location metadata. Sharing does not upload your whole private library, device credentials or the owner management capability into a public pack.
The service stores the selected pack privately for 180 days. Anyone who has the code or link can download it; there is no public list of codes. Visiting a share page does not download the pack, renew it or import it. Opening a code in the app leads to a preview where you choose what to save. Independently saved copies and shared card images are not recalled by expiry or revocation.
A separate owner capability controls renewal and revocation. Its server copy is hashed; its phone copy uses device-only iOS Keychain or Android Keystore encryption in no-backup storage, separately from cook archives. An interrupted upload retains an immutable local retry file and its capability so retry can recover an already accepted code. Changing phones or removing the app can lose management access. Code sharing does not require an account or enable private library sync or public recipe publishing.
The service processes your IP address for abuse prevention using rotating, hashed rate-limit identities and quota windows. Application logs omit codes, owner capabilities and pack contents. Railway processes network requests and infrastructure logs under its service policies. Revocation stops new downloads; expiry and revocation queue stored-object deletion. Operational checks of host logging and storage deletion are required before this service is released.
Optional Beta temperature connections
Android and iOS store builds offer read-only Beta temperature connections to Combustion Bluetooth thermometers, your own Home Assistant server, FireBoard, Flame Boss, and MEATER. These are optional and do not require a PitTech account or a PitTech telemetry relay. Home Assistant is an additional option; you operate the server yourself. No equipment controls or manufacturer community plugins are included.
The phone connects directly to the provider you select. Cloud account passwords are sent only to that manufacturer's authentication service and are not saved. Android access credentials use Android Keystore encryption in no-backup storage; iOS uses device-only Keychain storage. Home Assistant OAuth uses the PitTech privacy-site origin as its client identifier; the phone intercepts the exact authorization callback, and the site does not receive the authorization code, credentials or temperature readings. Saved server/device configuration stays on the phone and is excluded from backup and cook exports.
Selected temperatures, sample times, local source identities and historical food assignments are stored as part of your local cook records and may be included if you export them. Credentials and dedicated original manufacturer device-ID fields are excluded from cook archives. Exported device and channel display names may still identify equipment or contain an entity identifier when no friendly name is available. Forgetting a connection deletes its local credentials and stops collection while preserving cook history. Home Assistant refresh-token revocation is attempted when online; advanced tokens and other vendor sessions may also need revocation through the provider. Telemetry is not sent automatically to PitTech, feedback or advertising services.
Android background monitoring is explicitly enabled by you and shows an ongoing notification with a pause action. It can increase battery use and Android may stop it. iOS cloud collection runs while PitTech is open and may stop while suspended or locked. History is recovered only where the provider supports it; missing measurements remain gaps. Development-only Android local Home Assistant HTTP exposes the token on that local network. Public connections use HTTPS or authenticated TLS; iOS Home Assistant requires HTTPS.
Internal Android controller-test builds
Legacy proprietary clients are excluded from the public connected-device binary. Historical recordings remain readable. In internal debug and Dev test builds, the experimental Wi-Fi monitor connects directly to the selected manufacturer's services. GrillirG uses the Prime Polaris HTTPS backend: an explicit code request sends the email you enter, and sign-in sends that email and code. Pit Boss/Louisiana uses an encrypted WebSocket to the Dansons relay for the exact controller ID you enter, with the optional controller-password compatibility value when required. Traeger WiFIRE sends your explicitly entered email/password to its HTTPS authentication service, then uses account tokens to discover your grills and subscribe to telemetry through its signed AWS IoT WebSocket. Supported token renewal uses Amazon Cognito. These requests are processed by those vendor services; PitTech does not send cook logs or photos to them. Nothing requests email codes or logs in automatically using an account password.
Entered emails, codes and passwords live in the current form. Password/code fields clear on submission or a provider switch. Traeger account passwords are not saved. Account/refresh tokens, optional Pit Boss controller credentials, expiry and the selected grill are stored locally with Android Keystore AES-GCM encryption in separate provider files in no-backup storage. Sign out removes that provider's saved session. There is no plaintext credential fallback. Up to 120 typed observations and 80 request events stay in memory. The selected provider and collection mode/interval are saved as local preferences. Timed monitoring runs while PitTech is visible or an explicitly started cook recording owns it; its active recording notification includes a pause action. Logging-only collection runs on user entry/refresh actions, without an idle recording service; the selected collection policy also stays with local cook history. Stored cook temperatures, probe assignments and copied log/photo context remain local and can be exported by you. Account credentials and remote controller identifiers/binding hashes are not included in archives.
You can preview and explicitly submit a connection report through the public GitHub feedback relay. It includes bounded numeric controller observations, recognized field names, request timings, HTTP/API result codes and alarm counts. It excludes email, login codes, passwords, account/refresh tokens, signed URLs, headers, raw responses, device IDs/names, Wi-Fi identities and alarm contents. Nothing is submitted automatically.
Android feedback
If you choose Report a problem or Request a feature in Settings, PitTech sends the title and description you enter plus the PitTech version, Android version, and device model to PitTech's feedback relay hosted on Railway. For a problem report, you can also choose to include the most recent crash report saved on your phone. In experimental debug and Firebase Dev controller-test builds, selecting a controller can automatically inventory its BLE/GATT surface, observe up to eight non-protocol notification channels for up to 10 seconds, and, when a recognized protocol is detected, issue explicitly allowlisted observational requests. Passive notification capture retains bounded counts and change statistics; raw notification payloads are not included in the public report. Some protocols require BLE characteristic or descriptor writes to carry an observational request or enable notifications; these transport-level writes are distinct from controller-setting operations. The automatic probe does not intentionally execute controller-setting, ignition, temperature-target, motor, credential, Wi-Fi provisioning, password, configuration-write, filesystem-write, reboot, firmware/OTA, MCU-command, or unknown RPC operations. It does not read the Mongoose configuration GATT value characteristic because that can disclose the currently selected setting. Nothing is submitted automatically. Before a controller report is submitted, PitTech removes the permanent Bluetooth address, withholds arbitrary advertised names, replaces raw advertisement/manufacturer/service-data/GATT payloads with byte counts and SHA-256 fingerprints, and sanitizes printable values, protocol responses, and debug text. Password/passwd/passphrase/psw/secret/token/authorization/SSID/BSSID/username/email/certificate/private-key/serial-like fields are redacted. The report is previewed before submission and includes only the controller you selected plus app-owned test events. Sanitized printable protocol and controller-state responses may still reveal implementation details, and the resulting GitHub issue is public.
The relay creates an issue in the public PitTech GitHub repository, so no GitHub account is required to submit feedback. The resulting issue can be viewed by anyone. Do not include personal or sensitive information in feedback. PitTech does not add cook records or photos to feedback submissions. Railway processes the network request used to reach the relay, and GitHub hosts the resulting public issue. Their handling of information is governed by their respective privacy terms and GitHub's Privacy Statement.
Advertising and Google Mobile Ads
PitTech may display one native Google ad in completed cook history after at least four cooks are complete and only when no cook is active. Ads may not always be available.
When PitTech checks privacy choices or requests an ad, Google Mobile Ads and Google's User Messaging Platform may process information such as the device's IP address, ad interactions (including app launches, taps, and video views), diagnostics and performance information, and device or account identifiers such as the Advertising ID and App Set ID. Google may use and share this information for advertising, analytics, and fraud prevention. Google encrypts this information in transit.
PitTech does not include cook records, notes, ingredients, temperature readings, or photos in ad requests. Those remain on your device unless you export or share them. Google's handling of information processed by its advertising and consent services is described in Google's Privacy Policy.
When a privacy choice is required, PitTech uses Google's consent form before requesting ads. Where required, the Settings screen provides a Privacy options control so you can revisit your choices.
Product analytics
PitTech uses Google Analytics (Firebase Analytics) to understand how the app is used — which screens are visited, and when cooks are started, finished and shared, recipes are created, and sign-ins happen — so we can improve the app. Analytics collects product-usage data such as screens viewed and those app interactions, together with app and device information and a pseudonymous app-instance identifier. We do not send Google Analytics your email address, account identifier, cook titles, notes, or photos. The analytics data is pseudonymous product-usage data processed by Google on our behalf; it is not sold, and it is not used to identify you personally. Google's handling of this information is described in Google's Privacy Policy.
Exporting and sharing
On Android, PitTech uses the system photo and document pickers when you choose images or files. You can export cook information as an Excel workbook, CSV, or ZIP archive and restore a ZIP archive. On iOS, you can export or restore a ZIP archive with the Files picker. Exported files are written to the destination you choose.
If you open or share a file with another app or service, that recipient may receive a copy and handle it under its own privacy policy. PitTech does not control separate copies or the recipient's practices.
Retention and deletion
Cook records and photos remain in PitTech's private app storage until you delete PitTech. On Android, you can also clear the app's data in Android settings; Android app-data backup is disabled. The iOS cook library is excluded from device backup. Exported files and copies shared with other apps remain at their chosen destinations until you delete them there.
A locally saved crash report stays on your phone until a newer report replaces it, you delete it in Settings, or you clear PitTech's app data or uninstall the app. If you submit feedback, the relay does not maintain a separate feedback database; the created public GitHub issue is retained under GitHub's retention and deletion policies. Railway may retain operational request logs under its service policies. Google handles information collected through its advertising and consent services under its own policies and controls.
Security
PitTech stores cook records, photos, and crash diagnostics in each platform's private app storage. Cook records and photos are not uploaded by the feedback flow. Android feedback is transmitted over HTTPS to PitTech's Railway-hosted relay and then to GitHub. A crash report is included only if you select it for a problem report. Controller diagnostic data is included only after you review and submit the report. The public-report representation removes the selected controller's permanent Bluetooth address, withholds arbitrary advertised names and raw advertisement/GATT payload bytes, redacts private LAN addresses and credential-like values, and can include service metadata, payload lengths and hashes, sanitized printable GATT previews, sanitized protocol/RPC responses, sanitized bounded debug observations, capability fingerprints, firmware/device metadata, and timestamped app-owned test events. The relay keeps its GitHub credential on the server and does not place that credential in the Android app. The app does not claim separate encryption of its local database or exported files. Protect access to your device with its screen lock and other security settings.
Children and intended audience
PitTech is intended for adults who want to record barbecue cooks. Its declared Google Play target age is 18 and older, and it is not designed for children. PitTech does not ask for a user's age.
Changes to this policy
If PitTech's data practices change, this policy will be updated. The updated date appears at the top of this page.
Contact
For privacy or support questions about PitTech, email sportfolioholdings@gmail.com.