FeedFare · Clear, useful information
Privacy Policy
Updated and effective October 5, 2026
FeedFare turns steps into screen time. This policy covers native FeedFare, older installed subscription versions, TestFlight builds, and this website. Practices can differ by the version you use.
1. Who is responsible
FeedFare is developed by Nick Rae in Merced, California. For questions or privacy requests, email nick@nickrae.net. You do not need to create a FeedFare account to use the app.
2. Steps, progress, and app protection
With your permission, FeedFare reads step counts from Apple Health and uses your device’s Motion & Fitness data for step counting. This supports walking goals, earned screen time, history, and streaks. Apple Watch steps may be included after they sync to Apple Health. FeedFare does not write or change your Health records.
Your goals, preferences, progress, earned balance, and sessions are stored in the app’s local storage. In the native version, Screen Time provides opaque selection tokens for the apps you choose. The app and its protection extensions share selection and session state in an on-device App Group. The native app does not send those tokens or step history to a FeedFare server.
The native version may import existing FeedFare progress and keep a local migration backup. Device or iCloud backups are governed by your Apple backup settings; on-device storage does not mean that the operating system can never back it up.
3. Permissions and optional features
- Health: reading steps for progress and earned time.
- Motion & Fitness: live step counting on the device.
- Screen Time: selecting and protecting apps and managing timed access.
- Notifications: optional reminders that you can turn off.
- Sharing: when you choose to share a milestone, the information in that image goes to the app or recipient you select.
FeedFare does not need contacts or location to provide its walking features. You can revoke permissions in iOS settings. Features that need a revoked permission may stop working. See permission help.
4. Purchases: native app and older subscription versions
Apple processes App Store purchases and subscriptions. FeedFare does not receive your payment-card details. Older installed subscription versions use RevenueCat to validate purchases and determine access. This can involve purchase history, transaction or receipt information, subscription status, and a pseudonymous app user identifier. RevenueCat does not receive your step counts through FeedFare’s purchase integration.
Native FeedFare 2026.9.28 does not include the RevenueCat SDK, advertising SDKs, or a third-party analytics SDK. Its full app access does not require a subscription. Apple still handles app acquisition and any previous subscription records. FeedFare’s previous subscription plans have been retired and no longer renew; this is separate from installing an app update. People who continue using older versions may still use those versions’ purchase services.
See RevenueCat’s privacy policy and Apple’s privacy policy for their services.
5. Website, diagnostics, and support
This website is hosted on GitHub Pages. GitHub and its delivery providers process technical request information, such as IP address, browser details, and request logs, to serve and protect the site. See GitHub’s privacy statement. Fonts, styles, and images used by the page are served with the site. We do not add advertising pixels, analytics cookies, or a third-party website tracking SDK.
App Store links may include a campaign label identifying where the link was placed. Apple can provide campaign-level acquisition reports subject to its reporting rules. Those labels do not include your Health data, Screen Time selections, or a personal identifier generated by this website.
Apple may provide app diagnostics or TestFlight feedback according to your Apple sharing settings and any feedback you choose to send. If you contact support, we receive your email address and the information you include. Send only what is needed to explain the issue; private Health records are not required.
6. Sharing and use
We use information to provide the features you choose, handle purchase access in subscription versions, respond to support requests, and maintain the app and website. We do not sell personal information or use step data or Screen Time selections for advertising. Service providers process the information needed for their roles described above. Information may also be disclosed when required by law or to protect legal rights and security.
7. Retention, reset, and your choices
Local app progress remains until you reset it or remove the app and its data. The native app’s Reset local data control clears saved progress, preferences, migration backups, protection, and scheduled reminders. It does not delete Apple Health records, cancel subscriptions, or remove separate device backups. Manage those with Apple. Removing local data cannot recall a milestone that you already shared.
We keep support correspondence for as long as needed to handle the request and related follow-up, or meet applicable legal obligations. Purchase providers may retain transaction records under their own retention policies and legal obligations. Contact us to request access, correction, or deletion of information we hold about you, or to ask about applicable privacy rights. We may need to verify a request. We cannot retrieve step history that exists only on your device.
8. Children and security
FeedFare is a general-audience app and does not offer child accounts or a child-directed social service. A parent or guardian should supervise use by children and use Apple’s age, purchase, and permission controls. Contact us if you believe a child has sent personal information to us so we can address it.
We use the platform’s app storage and permission mechanisms and HTTPS for this website. No storage or transmission method is completely secure. Keep your device and operating system up to date.
9. Policy updates
We will update this page when the app’s practices change and revise the date above. Material changes will be explained here and, when appropriate, in the app or its release information. Where required, we will request consent before a new use of information.