Weldbook AI · powered by Appalachian Integrity
Field PRD Privacy Policy
Version 2.0 · October 29, 2026 · effective prospectively after affirmative acceptance
Field PRD prepares drafts, planner results, nameplate OCR and publication lookups on your device. Optional online functions use Google Play for purchases and Appalachian Integrity's account/hosting services for account access and selected report preparation. Preparing a server preview sends the selected report, attached processed photos and source-history entries to Appalachian Integrity before an issue charge. It does not send your full local workspace. Review the notice and send only information you are authorized to share. Keep independent copies.
1. Device, account, agreement and purchase information
The app stores report fields, including any technician, facility, equipment, and service details you enter; inspection-planning answers; processed copies of photos you attach; preferences; extracted page text used to search a standard you choose to load; and local manufacturer-database source metadata, extracted text, and reviewed model/size rows. Bundled lookup rows identify cited manufacturer publications; user-added sources and rows are marked user-added and unauthenticated. Nameplate OCR keeps recognized text and the processed scan in session memory until cleared, replaced, applied, or the page or app reloads. If you apply suggestions, that temporary scan session is cleared and the report stores the selected values, confidence/source trail, source kind, title or file name, revision/date when entered, authentication warning, and processed nameplate image; it does not store the complete raw OCR text as a separate report record. Reports, photos, and extracted text use local application databases. Planner answers, preferences, and acceptance settings use browser or app storage. These records belong to the current browser profile or app installation. The optional report account does not synchronize your full local workspace.
The app stores a local acceptance receipt containing the Terms and Privacy hashes, acceptance time from the device clock, app version, and confirmation that the Terms were scrolled and the electronic-consent box was checked. It does not contain a verified name, company identity, IP address, or server timestamp, and Appalachian Integrity does not receive or independently verify it. You can export a copy from About for your own records.
If you request or use an online account, Appalachian Integrity receives your email, name and company when provided, authentication/account status information and account requests. It uses the shared Appalachian Integrity identity also used by supported apps. Unverified registration name/company suggestions are stored separately from the shared profile until the email owner confirms them through setup. The authenticated owner separately accepts the current Field PRD account documents.
The server account receipt records account identity, typed name, stated self/organization authority and organization where applicable, separate electronic consent, document-view/end-scroll flags, document versions and hashes, server acceptance time, IP address, user-agent and app version. You may export the account receipt. A typed name or view flag records the account action; it does not independently verify identity, authority, professional credentials or actual reading. The separate device receipt described above remains local unless you choose to send or export it.
App access uses a signed original Google purchase receipt stored on the device, including its purchase token. Report credits separately use server records of product/order references, purchase-token hashes and encrypted tokens, purchase/consumption and verification/refund status, balances, reservations and credit entries. An opaque app-account identifier links a credit purchase to the signed-in account. These records support verification, duplicate-grant prevention, refund reconciliation and operation of the credit service; they are separate from report content.
2. Local processing and information not requested
Ordinary drafting, planner calculations, Your Standard searches, manufacturer publication extraction and nameplate OCR remain on your device. The built-in report-credit payload does not upload complete selected standards or manufacturer publications, their extracted pages, planner answers, other drafts or the complete manufacturer database. Selected titles, revisions, page references, source URLs and user-confirmed values can form the report provenance you choose to upload. Attached processed nameplate photos and any material you enter inside the selected report travel with it. Local OCR does not send images or recognized text to the Tesseract project or a cloud OCR or AI service. This feature adds no AI-processing service or general app-usage analytics; Google Billing diagnostics are described below.
Field PRD is designed for equipment records, not identity, payment-card or bank credentials, health, personnel, or credential records. Do not enter passwords, payment credentials, Social Security numbers, government identifiers, or unnecessary information or images about people. Free-text fields and photographs can contain personal or facility-sensitive information even though the app does not request it.
3. Uses, recipients and destinations you choose
Local information supports drafting, planning, OCR, lookup, export and settings. Connecting the report account sends account and connection requests to Appalachian Integrity. Separately confirming server preview preparation sends the selected report fields, notes, attached processed photos and lookup provenance to Appalachian Integrity's private service hosted by Bluehost. It stores the snapshot and generates preview and clean PDF artifacts before you decide whether to issue. The clean file becomes available after the recorded credit issue. These are private account records, not public posts; authorized company administration and hosting providers can access them as needed to operate, secure, troubleshoot and support the service. Receiving or rendering them is not technical review.
Google Play processes purchases under its own terms and privacy practices. Billing connections can occur when you request prices, purchase, redeem or restore access, or reconcile an existing or unfinished app purchase. Google's Billing library may send technical diagnostics about billing API success/failure and connection problems for performance and error support. For report credits we also exchange product/purchase references and the opaque account link with Google to verify and complete purchases and check later reversals. These paths do not send report contents or report photos to Google. We do not receive your payment-card number through this flow.
Requesting a launch pass sends the passphrase, a random installation claim and connection information to the reservation service. It stores keyed claim and IP-derived rate-limit references, a reserved voucher and time to enforce the limited pool and reopen the same reservation on retry. Google separately handles redemption and the resulting app purchase. Reservation can consume a slot without redemption. The in-app reservation-data removal control unlinks that installation reservation; an unlinked spent-slot record remains so the pool cannot be reset. It does not remove host logs or Google's records.
JSON exports contain the selected records and can include attached images in readable form; the app does not encrypt those files. Android export opens the system destination picker, and printing uses your browser or operating-system print service. A destination or print service you select may store or send the content, including to a cloud account. Review the contents, recipient, and destination before continuing. Deleting an app record does not recall copies you saved, printed, or shared.
Visiting the hosted app, connecting an online function, setting up or recovering an account, or requesting support can create hosting, connection and security records such as IP address, request time/resource, browser/app information and rate-limit references. Setup and recovery use email delivery providers. A public app-file request does not carry report, planner or loaded-document content; selected uploads and account requests are separate flows. External source links, PDF viewers, print services and destinations you select have their own practices.
If you send us a support message, we receive the message and anything you choose to include. Copy feedback details places app/source versions and browser/device information on your clipboard; it does not send the details or include report content.
4. Retention, export, restore and deletion
Local and optional server storage are working conveniences, not archival, backup or inspection-records-management services or your sole system of record. Keep readable issued copies, original photographs, original publications and verification records sufficient for your employer, client, program and applicable duties. Local records have no automatic time-based retention schedule and can be lost through updates, storage failure, corruption, browser eviction, clearing data, uninstall or device loss. We cannot recover device-only information we never received. These local limits do not remove the paid-download commitment below.
Unissued server-report content is scheduled for cleanup 24 hours after its initial preparation. Issued content is available for download for 90 days after first successful issue and is scheduled for cleanup after that window. Downloading, reopening or renewing a quote does not restart these clocks. Content cleanup covers the report snapshot, attached processed images and generated preview/clean PDF content. A quote's shorter confirmation expiry controls acceptance of its displayed charge; it is not the deletion deadline. Unchanged paid downloads carry no additional credit charge throughout the 90-day window and whenever the same paid artifact remains available or can be recovered afterward. Save your own copy promptly; ongoing preservation or reconstruction after cleanup is not promised.
Contact john@appalachianintegrity.com about failed delivery, loss of access during the promised window or recovery of the unchanged issue. We will address the service problem and any applicable remedy without requiring another same-content purchase merely to correct delivery or restore that issue. Changed content requires a new issue. An authenticated deletion request may end file availability earlier at your request. A specific legal requirement or urgent security restriction may limit access or require earlier removal; where permitted, we explain the effect and available remedy. A planned service ending or material shortening does not retroactively reduce an existing paid-download commitment. Removing content does not expire unspent credits.
Account, agreement, purchase, balance, credit-ledger, issue-audit, deletion-request, security and support records have purposes distinct from report content. We retain records reasonably needed to administer accounts and balances, reconcile purchases and reversals, prevent duplicate or fraudulent claims, meet applicable obligations, and establish or defend disputes. Encrypted purchase tokens remain usable by our server to check purchases, including consumed purchases, with Google. A transaction/audit reference does not require retaining report text or photos. Retention is limited to the justified purpose; calling a record an audit record does not require keeping it permanently. On a deletion request we identify necessary retained categories and reasons. No unverified fixed statutory retention period is asserted here.
Export record contains that report's fields and attached processed images. Export reports + planner contains report records, images, and current planner answers. Import backup keeps existing reports, imports supported reports as new copies, and, when included, replaces the current planner answers after confirmation. Lookup provenance stored in a report travels with that report backup. The separate manufacturer-database export contains user-added source metadata and reviewed lookup rows but intentionally omits extracted publication pages. It is a readable audit copy only and cannot restore the manufacturer database in this version; keep the original publications separately. A separate Export plan file is a readable record, not an importable report backup. Report backups omit a loaded standard, preferences, and acceptance settings; the local legal receipt has a separate export control. Export and import use a 50 MiB file limit, and import filters data to fields supported by the installed version, so a backup is not an exact historical installation image. Keep original standard files and original photographs separately where required.
Delete record removes the selected report, its lookup provenance, and embedded processed photos from the app's report store. Clear document removes the extracted text used by Your Standard, not the source file. Update Database lets you remove one user-added manufacturer source and its rows or clear all user-added manufacturer data. Deleting reports does not clear manufacturer data, planner answers, preferences, or acceptance settings. Clearing user-added lookup data does not remove source facts already preserved in a report's lookup provenance. Clearing the applicable browser site data or native app data removes those local stores. Uninstalling the native Android app removes its private app data; removing a browser shortcut or installed web-app icon may leave browser site data. Local deletion does not erase original photos/documents, downloaded files, print-service records, or recipients' copies.
Deleting a local report does not delete its server quote or paid issue. For server-record questions or deletion use section 8. The app's account-deletion control submits a request for the shared account and associated app data, which can affect other apps; it does not itself complete erasure or request a Google refund. It does not clear device drafts, originals, exported files, print records, recipients' copies or Google's records. Save needed copies before requesting it. Necessary retained transaction/dispute records are distinguished from report content as described above. We explain the handling of retained backup copies, including any temporary isolation pending overwrite or specific legal preservation, when responding to the request; no immediate erasure of every backup copy is promised.
5. Permissions and safeguarding your records
When you choose a camera, photo or file, your browser, operating system or file provider may request access needed for the action. OCR and initial photo processing occur locally; processed photos attached to a selected report upload only when you confirm server preparation. Photos may be resized or compressed; preserve originals where required. Authenticated account access protects server functions but does not separate or encrypt local drafts or readable JSON exports on a shared device/browser profile. Online requests use HTTPS. Stored purchase-token encryption does not mean report content is end-to-end encrypted or inaccessible to Appalachian Integrity and its host.
The native report-credit connection keeps passwords and session credentials in memory rather than app storage. The app separately retains signed app-unlock purchase evidence, including its purchase token; therefore not all purchase information is memory-only. Opening or downloading a PDF can create temporary app-cache and viewer copies; saving creates a copy at your chosen destination. Cache removal, logout and provider controls do not recall external saved or recipient copies. Protect your device, account and exports.
The Android package is configured to exclude its private app data from Android cloud backup and device-transfer backup. This does not control independently exported files or a destination provider's backup practices. Do not rely on automatic operating-system restoration.
6. Children
Field PRD is intended for adult professional field users and is not directed to children. We cannot remotely access or erase files stored only on a user's device.
7. Changes
We identify this policy's revision date and explain material changes. Recorded-document changes are presented through the applicable app/account gate. Online account email addresses may be used for material service/privacy notices; device-only users have not necessarily supplied an address. An offline installation may not receive notice until it updates or reconnects. A new policy does not retroactively authorize an earlier impermissible use.
When a new agreement is required, new covered transactions require affirmative acceptance; mere posting or offline use is not acceptance. We provide any required notice and a reasonable opportunity to save available work before a planned material shortening of server retention or service ending. Existing paid-download commitments are not retroactively shortened. A specific legal requirement or urgent security restriction may require other action, without removing applicable rights.
Declining a new agreement does not forfeit existing balances or require acceptance to request deletion/support, export existing agreement receipts, recover purchase status, access prior paid history or download an existing paid issue during its applicable availability window and while otherwise available afterward. Keep your account notice address current and save needed outputs promptly. Prior accepted versions remain available through the applicable legal-document access. Earlier document references are: Terms proposed September 24, 2026 and Privacy Policy proposed September 24, 2026; Terms dated September 20, 2026 and Privacy Policy dated September 20, 2026. A saved copy of this policy does not itself contain those separately linked archives.
8. Contact and privacy requests
Contact Appalachian Integrity LLC, Virginia, USA, at john@appalachianintegrity.com about privacy, security, access, correction, a copy of information we hold, or deletion. Identify Field PRD and the account/records involved; do not email your password, purchase token or unnecessary report content. We may request information reasonably needed to verify the request. You need not create a new account to make a privacy request.
The report-account section includes Request account deletion. It asks you to verify the existing password and confirm the shared-account scope, then returns a request reference/status for processing. If you cannot sign in, use the contact route above. A request is not a Google refund and does not prove erasure is complete. We explain necessary retained categories and reasons and communicate the outcome. Local controls govern content held only on your device, which we cannot retrieve or erase remotely. These technical limits do not waive an applicable right or remove our responsibility for information we hold.
If applicable law gives you a right to appeal a privacy-request decision, reply to the contact above identifying the decision and requesting review. We respond within the period required by applicable law and provide available regulator-complaint information when required. Nothing in these Terms or this policy waives a right that applicable law does not permit us to limit.
Previous offline version dated October 29, 2026: Terms of Use and Privacy Policy. Prior rights and claims are not changed retroactively.