Privacy Policy

1. Who We Are

Nibblr ("the App," "we," "our," or "us") is an independent macOS application developed and distributed by a sole developer ("Developer"). If you have questions about this policy, please contact us at the address listed in Section 10.

2. Information We Do Not Collect

Nibblr is designed from the ground up to operate without collecting any personal information. We do not collect, store, process, transmit, or share:

• Your name, email address, or any contact information
• A user account or credentials of any kind
• Device identifiers, IP addresses, or advertising IDs
• Usage analytics, crash reports, or telemetry
• Your reading habits, article history, or bookmark lists
• Your notification keywords
• Location data
• Any information through third-party SDKs or analytics frameworks

3. Information Stored Locally on Your Device

All application data is stored exclusively on your Mac using Apple's standard system APIs. This data never leaves your device except as described in Section 4.

3.1 Feed Data (SwiftData / Core Data)

Your feed sources, feed groups, articles, read/unread status, and bookmarks are persisted in a local SwiftData store on your Mac. This database is protected by macOS's standard file-system permissions and app sandboxing.

3.2 Preferences (UserDefaults)

App settings — including your chosen auto-refresh interval, reader font size, default reader mode, and notification keywords — are stored in your Mac's local UserDefaults database. This data is scoped to Nibblr and is not accessible to other applications.

3.3 Notification Keywords

Keywords you define for article notifications are stored locally in UserDefaults as a JSON string. Matching against these keywords occurs entirely on-device. The keywords are never transmitted anywhere.

4. Network Requests

Nibblr makes outbound network requests solely to provide its core functionality. These requests are initiated by you (by adding a feed or opening an article) or by the auto-refresh schedule you configure. All requests originate from your device.

4.1 RSS / Atom Feed Fetching

When you add a feed or when auto-refresh runs, Nibblr sends an HTTP GET request to the feed URL you provided. The remote server receives your device's IP address as part of the standard TCP/IP connection — this is an inherent property of the internet and is outside the App's control. The server's privacy policy governs how that information is handled.

All feed URLs are automatically upgraded from http:// to https:// where possible, to protect your connection from passive interception.

4.2 Favicon Fetching

To display feed icons, Nibblr makes a request to the root domain of each feed URL (e.g., https://example.com/favicon.ico). This request is made once per feed source and only exposes your IP address to that site's server, under that site's own privacy policy. No other identifying information is sent.

4.3 Article Content (WKWebView)

When you open an article, Nibblr displays the content either in Reader Mode (extracted locally via Readability.js running entirely on your device) or by loading the original article URL in a sandboxed WKWebView. In the latter case, your Mac connects directly to the article's website, which may set cookies or log your visit under their own privacy policy. Nibblr does not intercept, modify, or record that traffic.

4.4 No Developer-Controlled Servers

None of the above requests are routed through servers owned or controlled by the Developer. Nibblr has no backend infrastructure.

5. Local Notifications

Nibblr uses Apple's local notification framework (UserNotifications). Notifications are generated entirely on your device based on your keyword list and newly fetched articles. They are never transmitted to Apple Push Notification Service (APNs) or any remote server. Notification permission is requested only when you add your first keyword; you can revoke this permission at any time in System Settings → Notifications.

6. Third-Party Services

Nibblr does not integrate any third-party SDKs, advertising networks, analytics platforms, or crash-reporting services. The App contains no code from any company other than the Developer and Apple's own system frameworks.

The RSS feeds and websites you choose to follow are third-party services with their own privacy policies. The Developer has no control over and assumes no responsibility for the content, privacy practices, or policies of those services.

7. Children's Privacy

Nibblr is a general-purpose RSS reader not directed to children under 13 (or the applicable age of digital consent in your jurisdiction). Because the App does not collect any personal information from any user, no special measures regarding children's data are required. However, the Developer does not knowingly market the App to children.

8. Data Security

All data generated by Nibblr resides on your Mac and is protected by:

• macOS app sandboxing — other apps cannot access Nibblr's data container
• macOS user-account permissions — only your user account can read the data
• macOS FileVault (if enabled by you) — full-disk encryption at rest
• HTTPS for all outbound feed requests (enforced via App Transport Security)

Because the Developer never receives your data, the Developer cannot be the source of a breach of your Nibblr data. The security of your local data depends on the security of your Mac and your Apple Account.

9. Disclaimer of Liability for Third-Party Content

Nibblr is a passive aggregator — it displays content published by third-party RSS feeds that you select. The Developer:

• Does not author, endorse, or verify any feed content displayed in the App
• Is not responsible for the accuracy, legality, or appropriateness of any third-party content
• Cannot guarantee the availability, security, or privacy practices of any third-party website or feed you subscribe to
• Is not liable for any damages resulting from your access to or reliance on third-party content through the App

Your use of third-party feeds is entirely at your own discretion and risk.

10. Your Rights and Choices

Accessing or Deleting Your Data

Because all data is stored locally on your device, you are in complete control at all times. You can:

• Delete all app data by uninstalling Nibblr and removing its data container via Finder → Go → Library → Application Support
• Remove individual feeds using the App's built-in feed management interface
• Remove notification keywords in Settings → Notifications
• Revoke notification permission in System Settings → Notifications → Nibblr

There is no account to delete, no server-side data to request, and no need to contact the Developer to exercise any of the above rights.

Residents of California (CCPA)

Nibblr does not sell personal information. Because no personal information is collected, the California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) disclosure obligations regarding data categories, sale, or sharing do not apply. No opt-out mechanism is required or provided.

Residents of the European Economic Area and United Kingdom (GDPR / UK GDPR)

Nibblr does not process personal data as defined under the GDPR or UK GDPR. No legal basis for processing is required because no processing occurs. No Data Processing Agreement, Data Protection Impact Assessment, or appointment of a Data Protection Officer is required in connection with the App.

11. Changes to This Policy

The Developer reserves the right to update this Privacy Policy at any time. If material changes are made, the "Last updated" date at the top of this page will be revised. Because Nibblr does not collect contact information, the Developer cannot notify you directly; it is your responsibility to review this policy periodically. Continued use of the App after a revised policy is posted constitutes your acceptance of the revised policy.

12. Limitation of Liability

To the maximum extent permitted by applicable law, the Developer shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from or related to your use of Nibblr, including but not limited to:

• Any unauthorized access to data stored on your device
• Any third-party content accessed through the App
• Any interruption or cessation of the App or its features
• Any bugs, viruses, or harmful code introduced through third-party feed content

Nibblr is provided "as is" and "as available," without warranty of any kind, express or implied. The Developer makes no warranty that the App will be uninterrupted, error-free, or free of harmful components.

13. Contact

If you have questions, concerns, or requests regarding this Privacy Policy, please contact the Developer at:

Email: info@nibblr.cc
Website: nibblr.cc

The Developer will make reasonable efforts to respond to any inquiry within 30 days.