Privacy Policy
Last updated
This policy covers the website, the downloads and the update check. It is separate from the per-product pages in the documentation, which describe what each application stores on your own machine — those are technical notes, this is the policy.
Who we are: Pioneering, New Zealand. Contact: hello@pioneering.app.
The short version#
- Everything is free and needs no account, so there is no sign-up, no payment and nothing about you to keep on file.
- Perch asks whether a newer version exists. That request carries nothing about you or your machine — it is the same public release list the download page reads. No telemetry, no analytics, no usage counters, no record of what you did.
- The four extensions never contact us at all.
- The one other thing Perch can send is a crash report, and only when you press Send. There is no background uploader: Perch shows you the exact text first, sends a summary rather than the crash file, and sends nothing if you do not choose to. What is in it.
- We do not sell anything to anyone, and there is no advertising.
What we collect, and why#
| What | Why | Where it comes from |
|---|---|---|
| A salted hash of your IP address, temporarily | To rate-limit downloads and update checks so one caller cannot exhaust them | Your request |
| A crash summary, only if you press Send | To find and fix the crash | Perch, with your say-so |
What we deliberately do not collect#
- Your identity. There is no account to create, so we do not have your name or your email address unless you write to us.
- Payment details. Nothing is for sale.
- Device identifiers. Neither the update check nor a download carries one.
- Anything you do in the applications. Which files you opened, which windows you shared, what you typed. There is nowhere in any request for it.
Cookies and local storage#
The site sets no tracking cookies and uses no analytics. The one thing it stores in your browser is your light/dark theme choice, locally, and it is never transmitted. It is cleared when you clear site data.
How long we keep it#
| Data | Kept |
|---|---|
| IP rate-limit records | 24 hours |
| Crash summaries | Until the bug is dealt with, or until you ask us to delete one |
Accounts made before 28 October 2026#
Pioneering used to sell subscriptions, which created an account. If you had one, we still hold what that account was made of: your email address, a password hash, your plan and billing history, a salted device hash for each machine you signed in on, and a short account log. Payments went through Stripe, and account email through Resend; no new data reaches either now. If you still sign in with one, Perch checks it about once a day, sending a salted device hash, macos or windows, and its version number.
Ask and we delete the account and everything attached to it, except payment records, which tax law requires us to keep for 7 years.
Who else sees it#
The site, the downloads and any account data are stored on Cloudflare infrastructure, with the database located in Oceania. We use no advertising networks, no analytics providers and no data brokers.
Your rights#
Under the New Zealand Privacy Act 2020 you can ask us to:
- tell you what we hold about you;
- correct anything that is wrong;
- delete your personal data, subject to the payment-record retention above;
- export your data in a readable format.
Email hello@pioneering.app. We will respond within 20 working days, which is the statutory limit.
If you are in the UK or EU, the equivalent rights under UK/EU GDPR apply and the same address reaches us.
If you are unhappy with our response, you can complain to the New Zealand Office of the Privacy Commissioner.
Breach notification#
If we discover a breach likely to cause you serious harm, we will notify you and the Privacy Commissioner as required by the Privacy Act. We will tell you what happened, what was exposed, and what to do about it — in that order, and without waiting until we have a complete picture.
Changes#
If this policy changes materially, the change appears here with a new date. A privacy claim is only worth something if it is specific enough to be caught being wrong, so we would rather say exactly what changed than quietly edit.