Short version: Feedetta does not operate a cloud service, developer account system, advertising network, analytics pipeline, or third-party crash service. Your credentials and cached feed data stay on your device. Network requests go directly to the CommaFeed server and article websites you choose.
1. Scope
This policy applies to the Feedetta iOS application and this website. Feedetta is an independent client for self-hosted CommaFeed servers. It is not affiliated with or endorsed by the CommaFeed project.
2. Information the developer does not collect
Feedetta does not send the following information to a server operated by the developer:
- Your CommaFeed server address, username, password, or API key.
- Your subscriptions, feed groups, unread state, starred articles, or reading history.
- Your article content, browsing history, search activity, precise location, contacts, photos, or device advertising identifier.
- Analytics events, advertising profiles, or tracking identifiers.
There are no third-party advertising, analytics, tracking, or crash-reporting SDKs embedded in Feedetta.
3. Information stored on your device
Credentials
Your CommaFeed endpoint, username, and API credential are stored locally using Apple Keychain with the kSecAttrAccessibleWhenUnlockedThisDeviceOnly protection class. This makes the items device-bound and available to Feedetta only while your device is unlocked. They are not synced by Feedetta and are not included in a transferable backup by the app.
Secure Enclave clarification: an API credential is a Keychain password item; it is not a Secure Enclave private key. On supported Apple devices, Secure Enclave hardware participates in protecting the device key hierarchy and evaluating certain Keychain access controls. It would be inaccurate to claim that the text of the API key itself is stored inside Secure Enclave hardware.
Feed cache and preferences
Feedetta stores feed metadata, recent articles, read and starred states, pending offline actions, favicons, and app preferences in the application’s private on-device container. You control the offline retention period. You can clear cached articles in Settings.
4. Direct network connections
Your CommaFeed server
Feedetta connects directly to the CommaFeed server address you provide. Those requests do not pass through a Feedetta-operated service. Your CommaFeed host may process or log your IP address, account information, and requests according to its own configuration and privacy practices.
Article websites
When you select Full Webpage mode or open an external link, Feedetta connects directly to that publisher’s website. The website may receive your IP address, use cookies or similar storage, and collect information under its own privacy policy. Select RSS Excerpt mode if you prefer to read cached feed content without loading the publisher’s webpage.
5. Crash diagnostics
Feedetta contains no third-party crash-reporting service. Apple may collect crash, performance, and diagnostic information under Apple’s platform settings and privacy terms. When a user chooses to share analytics with app developers—or when using TestFlight—Apple may make diagnostic reports available to the developer through App Store Connect or Xcode. Feedetta does not add credentials, feed contents, or article contents to those reports.
6. Purchases
Apple processes the purchase of Feedetta and any optional in-app tip. Feedetta does not receive or store your payment-card information. Apple may provide the developer with sales and financial reports under Apple’s terms. Optional tips do not unlock features.
7. Support communications
If you contact support, the developer receives the email address and information you choose to include. Support messages are used only to respond to your request and maintain the app. Do not send passwords or API keys. Support messages may be retained as reasonably necessary to resolve the issue and maintain a record of the response.
8. Data removal
Use Clear Cache to remove cached articles. Use Logout to remove Feedetta’s saved credentials and cached application data. For the most reliable deletion of Keychain credentials, use Logout before deleting the app.
9. Security
Feedetta requires HTTPS and enforces TLS 1.3 for its CommaFeed API connection. Credentials are stored using Apple Keychain’s device-bound, unlocked-only protection class. Local application data is isolated by the iOS application sandbox. No system can be guaranteed perfectly secure, but Feedetta is designed to minimize what exists, where it is stored, and who can access it.
10. Children
Feedetta is a general-purpose RSS client and is not directed to children. The content displayed is determined by the feeds and websites selected by each user.
11. Changes to this policy
If Feedetta’s data practices materially change, this policy and the App Store privacy disclosures will be updated. The effective date at the top identifies the current version.
12. Contact
Privacy or support questions may be sent to [email protected].