BooBar Privacy Policy

Who We Are

This policy applies to the BooBar website, license backend, macOS app, and optional browser extension. For privacy, license, or data processing questions, contact boobar@yeah.net.

Information We Process

Depending on the features you use, BooBar may process website request data, the email address you enter at checkout, DoDoPayments order and payment status, license keys, license plan, activated device identifiers, device names, activation times, and last verification times.

Inside the Mac app, BooBar may store your preferences, watched folders, archive rules, action logs, file metadata, file names, paths, file types, summaries, OCR snippets, keywords, and File Cards locally. API keys are intended to live in macOS Keychain.

Local-First Processing

File watching, write-stability checks, basic classification, device status, action logs, and island notifications run on your Mac by default. BooBar does not automatically upload complete files simply because you install or open the app.

Cloud AI and Third-Party Models

When you enable Codex or an OpenAI-compatible model, BooBar may send the necessary File Card snippets, summaries, OCR text, or context you configured so the model can suggest categories, names, archive locations, or explanations. You can disable cloud AI or require manual confirmation for sensitive folders.

Third-party AI services process requests under their own terms and privacy policies. Avoid sending content to cloud AI that you do not want an external model provider to process.

Payments, Licenses, and Email

Checkout is processed by DoDoPayments. The BooBar backend creates and verifies orders, and stores only the information needed to issue licenses, enforce device limits, handle refunds, and provide support. We do not receive or store full payment card details.

After successful payment, BooBar sends the license key to the email address you entered. Email is used for license delivery, order-related notices, and necessary support communication.

Device Activation

To enforce 1 Mac, 2 Mac, or 3 Mac license limits, the BooBar backend stores the license key, device identifier, device name, activation status, activation time, and last verification time. If the license is full, you must deactivate an old device before activating a new one.

Browser Extension, Mail, and Web Monitoring

If you enable Chrome download or web change monitoring, the extension sends download status, page titles, URLs, selected regions, or change summaries to the local BooBar app so they can appear in the AI Dynamic Island. If you configure email code or mail monitoring, BooBar reads only the necessary snippets according to your settings and handles them locally unless you choose otherwise.

Retention and Deletion

You control local data and can remove it through app settings, system files, or uninstalling the app. Server-side license, order, and activation records are retained as long as needed to provide the service, handle disputes, and meet financial or legal obligations. You may contact us to request access, correction, or deletion of data associated with your email address.

Security

We use HTTPS, DoDoPayments webhook signature verification, license device checks, and SMTP delivery. Sensitive deployment values should be managed through protected environment variables or a secured config.yaml, and database/backend access should not be exposed publicly.

Children and Regional Rights

BooBar is not directed to children, and we do not knowingly collect children’s personal information. Depending on your location, you may have rights to access, correct, delete, export, or restrict processing of your personal information. Contact boobar@yeah.net to exercise those rights.

Updates

If product features, payment flows, or data processing practices change materially, we will update this page and, where appropriate, notify users through the website or email.