Privacy Policy
Build Perch is provided by Hollwick Technologies Inc. (“Hollwick”, “we”, “us”), a corporation incorporated in Canada and based in Ontario.
Effective date: July 12, 2026
Contact: contact@buildperch.com
The short version
Build Perch is a local-first desktop application. There is no Hollwick server in the data path. We do not hold a copy of your chats, files, documents, or credentials. Your content stays on your computer unless you direct the app to send it to a third-party service you chose (such as an AI model provider or an integration), authenticated with your own credentials. We do not run telemetry, analytics, or crash auto-upload to Hollwick.
Because of this, for your content Hollwick is a software vendor, not a cloud data controller. The limited personal data we do handle is described below.
1. Data stored only on your device (never sent to us)
The following stay on your machine and are never transmitted to Hollwick:
- App settings and interface state — toggles, workspace colors, model favorites, recent-activity log, directory paths, and tutorial flags (stored in the application’s local storage).
- A random device identifier and a display name (which defaults to your operating-system username), used only for the local “who else is in this shared workspace” presence indicator. Both are editable and regenerate on reinstall.
- Your workspace content — documents, chats, tasks, the local search index and embeddings, generated media, and downloaded attachments — in a folder you choose on your disk.
- Credentials — your OpenRouter API key and integration secrets (GitHub, Notion, and Discord tokens, and your email app password) are stored in your operating system’s secure keychain, not in a Hollwick account.
- Crash logs — written locally to your application data folder. They are not auto-uploaded. If you choose to send one to support, you do so manually.
If your workspace folder is inside a synced cloud folder (such as OneDrive, Google Drive, or Dropbox), your operating system’s sync client — not Build Perch — performs any cloud copy, under that provider’s terms.
2. Data sent to third parties you choose (we are a conduit)
When you use a feature that calls an external service, the app sends the relevant data directly from your device to the service you selected, using your own credentials. Hollwick does not receive or store a copy. These include:
| What is sent | To whom | When |
|---|---|---|
| Chat content, prompts, attached files and images, plus your OpenRouter key | OpenRouter, then the upstream model you chose | Each remote chat turn |
| Chat content | Ollama (on your machine) | When using a local model — stays local |
| Search and image-search queries | DuckDuckGo, Brave, Openverse (your keys where required) | Web and image search |
| Repository, page, or message content, plus your token | GitHub, Notion, Discord APIs | Integration tool calls |
| Email content, plus your app password | Your own email (IMAP/SMTP) server, over TLS | Email integration |
| Your IP address | ip-api.com (coarse location) | Only the location feature, and only after you grant per-use consent |
| Generation prompts and input images | Media-generation models via your provider | Image, speech, music, and video tools |
Each of these third parties has its own privacy policy that governs what it does with the data. AI model providers in particular may log or train on prompts depending on the model. The app surfaces a data-retention notice and offers a per-workspace privacy mode: when you turn it on for a workspace, the app asks OpenRouter to route that workspace’s requests only to providers that attest they do not retain or train on your data (most free models become unavailable as a result). This is the provider’s attested policy enforced by OpenRouter’s routing, not a guarantee we can independently verify; your OpenRouter account settings remain the authoritative, account- wide control, and both surfaces link there.
3. Peer-to-peer presence (no Hollwick server)
If you use a workspace folder shared with others (for example, a shared network or cloud-synced drive), the app writes a small presence heartbeat (your device identifier, display name, and a timestamp) into that folder about every 30 seconds so collaborators can see who is active. This is visible only to people who already have access to that folder. Nothing is sent to a central server.
4. Data we do handle: purchases and support
We receive limited personal data in three situations:
- Purchases — handled by our payment processor and Merchant of Record, Stripe (through its Managed Payments service), which is the seller of record; your purchase may be presented at checkout as “Sold through Link,” Stripe’s consumer checkout. Stripe collects your name, email, and billing information and provides us with order records (such as name, email, license, country, and amount). Hollwick never receives or stores your full payment-card details. Stripe’s privacy policy also applies: https://stripe.com/privacy.
- Licensing — license keys are issued, validated, and activated through Keygen, our licensing service. Keygen processes your license key, the email associated with your purchase, and a machine fingerprint (a one-way hash derived from a device identifier — it contains none of your files, content, or hardware serial numbers) so we can enforce activation limits and trials. Keygen’s privacy policy also applies: https://keygen.sh/privacy.
- Support — if you email us, we receive your message and contact details, and any diagnostics or log file you choose to attach.
We use this data to deliver licenses, provide support, handle refunds and chargebacks, prevent fraud, and meet our tax and accounting obligations.
5. Marketing website
Our website (buildperch.com) is separate from the app and may use cookies or analytics governed by the notices shown there. The app itself does not use web analytics or tracking cookies.
6. Legal bases (where GDPR / UK GDPR applies)
- Contract — processing purchase and license data to deliver the Software you bought.
- Legitimate interests — responding to support, preventing fraud, and securing our systems.
- Legal obligation — tax and accounting record-keeping.
- Consent — the location feature, which is revocable per use.
For content processed on your device or sent to third parties you chose, you determine those purposes; Hollwick is not the controller of that content.
7. Retention
- On-device data is retained until you delete it or uninstall the app. Uninstalling the Software does not automatically delete your workspace content — those are your files and remain on your device until you remove them.
- Purchase and order records are retained as required by applicable tax and accounting law (generally up to seven years) and are held by Stripe under its policy; license and activation records are held by Keygen under its policy for as long as your license is active.
- Support correspondence is retained for up to 24 months.
8. Sharing and disclosure
We do not sell your personal data. We share the limited data in Section 4 only with our Merchant of Record and payment processor (Stripe) and our licensing service (Keygen); service providers that help us operate (such as email and support tools); and authorities where required by law or to protect rights and safety. We do not hold your content to share.
9. International transfers
Purchase and support data may be processed in countries other than yours (for example, by Stripe or Keygen in the United States). Where required, such transfers rely on appropriate safeguards, such as Standard Contractual Clauses. Your content is not transferred by us; any transfer happens between you and the service you chose.
10. Security
Credentials are stored in your operating system’s keychain; integration secrets are restricted so the application’s web layer cannot read them back. Network calls use TLS. The app ships a strict content-security policy. No system is perfectly secure; you are responsible for securing your device and your accounts.
11. Your rights
Depending on your location (under Canada’s PIPEDA, Quebec’s Law 25, the GDPR or UK GDPR, and similar laws) you may have rights to access, correct, delete, port, or object to the processing of the personal data we hold (the purchase and support data in Section 4). Most of your content is on your own device and under your direct control. To exercise rights over data we hold, contact us at contact@buildperch.com.
We have designated a Privacy Officer responsible for our compliance; you can reach our Privacy Officer at contact@buildperch.com. You may also complain to your data protection authority — for example, the Office of the Privacy Commissioner of Canada, the Commission d’accès à l’information du Québec, or your EU/UK supervisory authority.
12. Children
The Software is not directed to children under 16, and we do not knowingly collect their personal data.
13. Changes
We may update this policy; material changes will be posted with a new effective date and, where appropriate, notified in-app or by email.
14. Contact
Hollwick Technologies Inc. — contact@buildperch.com