In short
- The BenchHand app stores what you enter on your phone. It has no account, no cloud sync and no remote database.
- It does not use analytics, a crash-reporting service, advertising, an advertising ID, tracking, your location or your contacts.
- Information leaves your phone only when you export or share a file yourself.
- This website sets no cookies and runs no analytics or tracking.
Confirmed: app inventory “No implemented network request code, analytics SDK, advertising SDK, cloud service, account system, or remote database.” Website line confirmed in source.
1. Who we are
BenchHand is a woodworking app for Android, and this is its website, benchhand.app. In this policy, “we” and “us” mean the publisher of BenchHand.
Needs owner/legal approval Question 1: name the legal person or entity, country and contact address.
2. Information the app stores
BenchHand keeps the information you enter so it can do its job. All of it stays on your phone:
| Information | Where it is kept | Does it leave your phone? |
|---|---|---|
| Projects, design drafts, saved revisions, Build Sessions, Workshop tool list, favourites and settings | Stored in the app’s private storage on your phone. | Never sent automatically. |
| Business records: customer names and contact details, quotes, invoices, payments, receipts and business profile | Stored in the app’s private database on your phone. | Only inside a document you choose to export or share. |
| Optional profile picture and business logo | Chosen with Android’s photo picker and copied into the app’s private storage. | Only if included in a PDF or backup you export. |
| Project and business PDFs | Generated on your phone. | Only to the app or place you choose to save or share it to. |
| Encrypted backup files (preview builds) | Generated on your phone. | Only to the file location or share target you choose. |
Confirmed: app inventory Table reproduces “Verified current behavior”. Needs owner/legal approval Question 6: which rows apply depends on the beta flavor (Business, Workshop tools and backups are preview-only).
3. Photos, camera and microphone
If you add a profile picture or business logo, you choose it with Android’s photo picker. BenchHand copies that one image into its private storage. The app cannot use your camera or microphone: those permissions are blocked in the app.
Confirmed: app inventory Camera, microphone and overlay permissions are blocked (checked in the packaged APK).
4. Files you export or share
You can create PDFs of projects and business documents, and, in preview builds, encrypted backup files. BenchHand creates these on your phone and hands them to the place you choose: a folder, a printer, or another app. What happens after that depends on where you send it. If your PDFs include customer details, those details go wherever you send the file.
Confirmed: app inventory PDF and backup handling.
5. Network access
BenchHand works without a connection and does not upload anything you enter.
Needs owner/legal approval Question 5: the build still declares Android’s template INTERNET permission, although no code uses it. Decide whether to keep or block it; if kept, consider saying so here.
6. Information about your customers
If you use the Business features, you may enter information about other people, such as your customers’ names and contact details. It stays on your phone unless you share it. You are responsible for having a proper reason to hold it and for telling your customers how you use it.
Needs owner/legal approval Legal review: wording of the user’s responsibility for third-party data.
7. Deleting your information
Uninstalling BenchHand deletes everything it stores on your phone. Files you exported earlier stay wherever you saved or sent them.
Confirmed: app inventory Uninstall behaviour. Needs owner/legal approval Question 11: describe which records can be deleted inside the app.
8. This website
This website is a set of static pages. It does not:
- set cookies;
- use analytics, advertising or tracking scripts;
- load fonts, scripts or embeds from other companies;
- contain any forms or ask you for personal information.
Confirmed: website source True as built: the one font is self-hosted. Recheck if anything is added (question 12).
The website is hosted by Cloudflare. Like any web host, Cloudflare processes technical information needed to deliver and protect the site, such as your IP address, browser type and the pages requested.
Needs owner/legal approval Confirm Cloudflare Pages as the host, link Cloudflare’s policy, and confirm no Cloudflare Web Analytics.
9. Children
BenchHand is a tool for woodworkers and is not directed at children.
Needs owner/legal approval Question 9: a proposed policy statement, not an engineering fact.
10. Changes to this policy
If this policy changes, the updated version and its effective date will be posted on this page.
Needs owner/legal approval Questions 3 and 10: effective date and how changes are announced.
11. Contact
A contact address for privacy questions will be added here once it is set up. See the contact page.
Needs owner/legal approval Question 2: a monitored mailbox (Phase 6 suggests [email protected]). Not shown until configured and tested.
Open questions from the data-handling inventory
From docs/handoff/2026-11-01/privacy/phase6-privacy-data-handling.md. Each one needs an owner or legal answer before publication.
- What legal person or entity publishes BenchHand and must be named in the policy?
- What monitored support/privacy email address will be published?
- What effective date will the policy use?
- Who provides legal review and final approval of the website policy?
- Will the template INTERNET permission be kept or blocked before beta?
- Which beta flavor will testers receive, and therefore which local data categories and features are in scope?
- Will a website beta sign-up form exist? If so, where will its data be processed, retained, deleted and disclosed?
- What feedback channel will testers use, and what instructions will stop them sending customer data or backups?
- Is the proposed “not directed at children” statement approved by the owner/legal reviewer?
- How will policy changes be announced?
- Which in-app records can users delete individually in the beta, and how should the policy distinguish those controls from uninstalling?
- Are any future website analytics, crash reporting, hosted forms or third-party embeds planned?