Bredo / Privacy
Bredo privacy policy
Draft for counsel review — not legal advice. Written from what the app actually does as of 16 September 2026, so that every sentence can be checked against the code. Placeholders in [brackets — to be confirmed] are facts only the owner can supply; the same placeholder is used everywhere it appears, so each needs filling in once.
Bredo is a Mac app for cataloguing and searching your own video footage. It is built so that your footage, and what Bredo learns about it, stays on your Mac.
What stays on your Mac
- Your footage. Bredo reads your files where they are. It never uploads them.
- Everything Bredo works out about your footage — transcripts, keyframes, visual search data, subjects, shoots, places, ratings and corrections — is stored in a catalogue in your user Library folder. It is never sent anywhere.
- Your licence. It is checked on your Mac with a digital signature. There is no activation, no account and no licence server.
- Your searches run on your Mac. When a search is written in another language, Bredo may use Apple's on-device translation — only with a language model already on your Mac; nothing is downloaded or sent for it.
- Spotlight. Clip titles, places, dates, transcripts and thumbnails are added to your Mac's own Spotlight index, so ⌘Space can find footage. The index stays on your Mac and follows your Spotlight settings; excluding the footage folders in System Settings → Spotlight keeps them out.
- Diagnostics. Crashes and hangs that macOS reports to Bredo are kept in your user Library folder, and go nowhere unless you copy and send them yourself.
What can leave your Mac, and when
| What | Where it goes | When | Can you turn it off? |
|---|---|---|---|
| The request for the update feed, with the app's name and version in its user agent. If an update is installed, also the download of the update and its release notes. The hosts, Vercel and Cloudflare, see your IP address with each request, as any website does; we do not store it. No system profile or identifier is sent. We count one check per version per day — see Statistics on this website | The Bredo website (via Sparkle) | When you choose Check for Updates, or once a day if you agree to automatic checks when Bredo asks on its second launch | Yes — nothing is checked automatically unless you say yes, and Settings → About turns it off |
| What you ask Siri or Shortcuts to find, when you use them with Bredo | Apple, as with any Siri or Shortcuts request; Bredo answers on your Mac | Only when you use Siri or Shortcuts | Yes — don't use them with Bredo |
| A clip's approximate location (rounded to about 1 km) | Apple's geocoding service | Only if you turn on Name places from GPS | Yes — off by default |
| A request for a speech-recognition language model | Apple | The first time Bredo transcribes in a language whose model is not yet on your Mac | Transcription only happens on your Mac; the model download is handled by macOS |
| Whatever your browser or mail app sends | The Bredo website, or your email provider | Only when you choose Bredo Website, Privacy Policy, Licence Agreement or Buy (opens your browser), or Contact Support (opens your mail app with a message you can read before sending) | Yes — these only happen when you choose them. What the website itself counts is in Statistics on this website below |
Nothing else. Bredo itself sends us nothing. There is no analytics in the app, no crash reporting service, no advertising, and no telemetry of any kind — the only request the app makes to anything of ours is the update check in the first row above, and it carries the app's name and version and nothing more. The statistics described below are the website's, and the app is not part of them. Crashes and hangs are recorded by macOS on your Mac and kept there (see Diagnostics above); if you have chosen to share analytics with app developers in System Settings, what Apple does with that is covered by Apple's privacy policy, and [whether Apple makes any of it available to us for an app distributed outside the Mac App Store — to be confirmed].
Statistics on this website
The app sends us nothing at all except the update check described above. The website is a different thing: it is a website, and it is counted. Here is all of it.
Visits — always, and cookieless
The site is hosted by Vercel and uses Vercel Web Analytics. It sets no cookie, stores nothing in your browser, and creates no identifier that could follow you between visits or between sites. What it records is the page you looked at, roughly where in the world the request came from, and what kind of device and browser it was — as counts, not as a row about you. Because there is nothing on your device and nothing that identifies you, it runs for everyone and there is nothing to consent to. The banner says this rather than implying otherwise.
Google Analytics — only if you say yes
Google Analytics 4 sets cookies and sends what you did on the site to Google, which acts as our processor. It is loaded only after you have chosen Accept on the banner, and choosing Only what’s needed loads nothing. You can change your answer at any time from — it is at the foot of every page, including this one. Changing it to Only what’s needed deletes Google’s cookies and reloads the page. Advertising features and cross-site signals are switched off.
Downloads — a count, and nothing else
The download button and the app’s own updater both fetch the release through api.bredo.app/dl/<version>/<file>, which adds one to a count of downloads of that version on that day and sends you straight on to the file. The whole record is four values — that it was a download, which version, which day, how many — and it is not a row per request. We do not store your IP address, anything derived from it, your browser’s user agent, or any cookie, session or identifier. There is nothing in it that could be traced back to a person, including by us.
Update checks — the same count, for the same reason
Bredo asks the update feed whether there is a new version, when you ask it to or once a day if you agreed to that. That request adds one to a count of checks from that version of Bredo on that day, read out of the app’s name and version in the request — the same information the app has always sent. Again: no IP address, no identifier, no time of day, no row per request. A browser opening the feed is served it and counted as nothing.
We use these two counts to know whether a release is reaching people. They cannot tell us who you are, and they are not capable of being made to.
Purchases
Purchases are handled by our reseller and merchant of record, Paddle (Paddle.com Market Ltd), which processes your payment details and billing address under its own privacy policy. Paddle holds your name, email address, billing address and country, the payment details you give it, and the record of the transaction, VAT and any refund or chargeback. We never see your card details. We receive your name, email address and order number so that we can send your licence and support you.
Support
If you contact us, we keep your messages to answer them. If you send the diagnostics Bredo can copy for you (Help → Copy Diagnostics for Support), they contain version numbers, counts, settings and any crashes or hangs macOS reported to Bredo on your Mac (the kind of problem, when, and where in Bredo's code), and no file names, drive names or personal details.
Who is responsible
The controller of the personal data described here is Baustad Digital, organisation number [organisation number — to be confirmed], [postal address — to be confirmed], [support address — to be confirmed].
Who processes data for us
These companies handle personal data on our behalf, or as independent controllers where noted. Where a transfer leaves the EEA, the basis is named.
| Provider | Purpose | Personal data | Location | Transfer basis |
|---|---|---|---|---|
| Vercel | Serves the website and the release notes, and counts visits with Vercel Web Analytics (cookieless — see above) | IP address, user agent, requested address and time, in server logs; aggregated visit counts, which name nobody | [Vercel region — to be confirmed] | [transfer basis — to be confirmed] (none needed if served and logged in the EEA; otherwise e.g. the EU–US Data Privacy Framework or the EU Standard Contractual Clauses) |
| Google Analytics 4, only after you choose Accept. Not loaded at all otherwise | What you did on the site, and the cookies Google sets to join those events together | [Google Analytics data region — to be confirmed] | [transfer basis — to be confirmed] (Google offers the EU–US Data Privacy Framework and the EU Standard Contractual Clauses) | |
| Cloudflare | Serves the update feed, the download redirect and the release zips, and runs the ordering and licence endpoint. Keeps the counts described above | IP address, user agent, requested address and time, in transit and in its own logs; name, email address and order number in the licence ledger. The counts themselves contain none of this | [Cloudflare region — to be confirmed] | [transfer basis — to be confirmed] |
| Paddle (Paddle.com Market Ltd) | Sells the licence, takes payment, handles VAT, refunds and chargebacks. An independent controller for payment data, under its own privacy policy | Name, email address, billing country and address, order number, payment details (we never see card details) | [Paddle location — to be confirmed] | [transfer basis — to be confirmed] |
| [email and support provider — to be confirmed] | Sends licence keys and answers support email | Name, email address, order number, messages and any diagnostics you send | [email provider location — to be confirmed] | [transfer basis — to be confirmed] |
| Apple | Only if you use the features in the table above: place names from GPS, speech model downloads, Siri and Shortcuts. An independent controller under Apple's privacy policy; not a processor of ours | Approximate location (about 1 km), the language requested, what you ask Siri or Shortcuts | Apple's services | Apple's own terms with you |
Crash or problem reports: none. Bredo uses no crash reporting or problem-report service; diagnostics reach us only if you send them yourself, and then through the email provider above.
We do not sell personal data, and we do not use it for advertising.
Why we hold it, and for how long
| Data | Why (legal basis under the GDPR) | How long |
|---|---|---|
| Name, email address and order number | To deliver your licence and honour the purchase (performance of a contract, Art. 6(1)(b)) | For as long as the licence can be used, and at least as long as bookkeeping law requires (5 years in Norway) |
| Support messages and any diagnostics you send | To answer you (legitimate interest in supporting the product, Art. 6(1)(f)) | Until the conversation is resolved, then deleted within 12 months |
| Update requests and website visits seen by the web host | To deliver updates securely and keep the site running (legitimate interest, Art. 6(1)(f)) | Server logs kept for [log retention — to be confirmed], then deleted by the hosting provider |
| Counts of downloads and update checks, per version per day | To know whether a release is reaching people (legitimate interest, Art. 6(1)(f)). They contain no personal data, so there is nothing here to ask us about | Kept indefinitely. There is nothing in them to delete: no address, no identifier, no row about anybody |
| Cookieless visit counts (Vercel Web Analytics) | To know which pages are read (legitimate interest, Art. 6(1)(f)). No cookie, no identifier, no personal data | [Vercel Analytics retention — to be confirmed] |
| Google Analytics events and cookies | Only with your consent (Art. 6(1)(a)), given on the banner and withdrawable from any page | [GA4 retention setting — to be confirmed] (Google’s shortest option is 2 months) |
Your rights
You can ask us for a copy of what we hold about you (at most: your name, email, order and support messages), to correct it, to delete it — subject to what bookkeeping law requires us to keep — or to restrict or object to how we use it. Contact: [support address — to be confirmed]. We answer within one month.
If you think we handle your data wrongly, you can complain to the Norwegian Data Protection Authority, Datatilsynet (datatilsynet.no), or the data protection authority where you live.
Changes
We will say what changed and when at the top of this page.
Baustad Digital · organisation number [organisation number — to be confirmed] · [postal address — to be confirmed] · Last updated [date — to be confirmed]