The short version

Dion Software, LLC does not collect, receive, store, sell, or share your FaveNest data. The app has no accounts, no servers of ours, no analytics, no advertising and no third-party code. Everything you save lives on your device and, if you choose, in your own private iCloud database.

The one way a save can reach a third party is a choice you make yourself: FaveNest Pro lets you add your own OpenAI, Anthropic or OpenAI-compatible API key, and with one set, the text of a save goes straight from your device to that provider so its model can write the title, summary and tags. Nothing passes through us. We never see the key or the request, and the key itself lives in your iCloud Keychain.

This public website uses Visitors to measure website traffic and performance. That analytics service is not included in the FaveNest app and never receives your library, iCloud records, saved content, or activity inside the app.

What FaveNest stores, and where

The items you save (links, notes, images, documents, places, categories and tags) are written to a database on your device. That copy is the original.

On a signed build with iCloud available, the same records sync through your private CloudKit database, inside the iCloud account already signed in to your device. Apple documents records in a user’s private database as readable and writable only by that user; they are not visible to the developer. We cannot read, browse, export, or recover them.

If you sign out of iCloud or turn iCloud Drive off for FaveNest, the app keeps working locally on that device.

Apple Intelligence and generated content

FaveNest uses Apple Intelligence to write short titles, factual summaries and tags for what you save. These models run on the device. Unless you add your own API key, described in the next section, the contents of your library are not sent to an online AI service by FaveNest. FaveNest has no AI provider account of its own and ships no third-party AI library.

On a device that does not support Apple Intelligence, the app falls back to local plain titles and to the page’s own description, with no change to what leaves your device, unless you have added a key.

Using your own API key

FaveNest Pro lets you add your own API key for OpenAI, Anthropic or any service that speaks the OpenAI-compatible API, under Settings > Intelligence > Cloud Model. It is off until you add a key. It exists for devices that cannot run Apple Intelligence, and for anyone who would rather a larger model wrote their summaries. On a device with Apple Intelligence, you choose whether the cloud model is used only as a fallback, where Apple Intelligence cannot answer, or for every save; on a device without it, the cloud model is used whenever a key is set.

When the cloud model is used, the request goes directly from your device to the provider you chose, over HTTPS and authenticated with your key. There is no FaveNest server in between: neither the key nor the request passes through us, and we cannot read either. The request carries the title, site and text of the save being described (page text, your notes, and text recognized in images and PDFs), together with FaveNest’s instructions to write a title, summary, category and tags. It carries nothing else from your library. Like any web request, the provider also sees your IP address, and it uses the key to bill your own account. Test Connection sends a one-line test message that contains nothing from your library.

What the provider does with that content is governed by its own terms and privacy policy, not by ours: Anthropic’s Privacy Policy, OpenAI’s Privacy Policy, or the policy of the compatible service you configured.

The key is stored in your device’s keychain and carried to your other devices by iCloud Keychain, end-to-end encrypted, the way your Safari passwords travel. FaveNest never writes it to its settings, to a library backup, to a diagnostics report or to a log, the share extension has no access to it, and it is sent to no one but the provider it belongs to. Remove Key, on the same screen, deletes it from your keychain and turns the cloud model off.

Network requests the app makes

FaveNest makes network requests only in direct service of something you saved:

Fetching a saved page in order to generate a preview image, a summary, and offline reading content. That request goes to the site you saved, exactly as a browser’s would.
Loading map artwork, Look Around imagery, and geocoding through Apple’s MapKit when a saved item resolves to a place.
Synchronizing your records with your own iCloud account through Apple’s CloudKit.
Sending the text of a save to OpenAI, Anthropic or an OpenAI-compatible service, only if you have added your own API key for it, as described above.

A website you choose to save receives the same standard request information it would see if you opened it in a browser, and that website’s privacy policy applies. MapKit and CloudKit are operated by Apple and governed by Apple’s Privacy Policy, and a cloud model provider you added a key for is governed by its own policy, linked above. We receive no data from any of those requests about you.

Analytics in the FaveNest app

There are none. The FaveNest app and its extensions include no analytics library, no advertising library and no third-party tracking code. The only crash reports we can ever see are the ones Apple provides if you have chosen to share them with developers. The privacy manifests shipped inside the app and its extensions declare no tracking and no tracking domains.

Analytics on this website

The marketing website at favenest.app loads Visitors, a third-party web analytics service. We use it only to understand how the public website is found, used, and performs. It is not connected to the FaveNest app or to iCloud.

When you visit the website, Visitors processes the page URL, referring page, browser, operating system, device type, pageviews, session activity, outgoing-link events, clicks on the App Store download buttons, and Core Web Vitals. Like any web request, it initially receives your IP address. Visitors says it uses the address to derive an approximate city, region and country and to create an anonymous signature, then discards the address except for temporary abuse-prevention records.

This website enables Visitors’ persist mode. Visitors therefore sets a first-party visitor cookie containing a unique identifier so it can recognize the same browser across visits. We do not use Visitors’ identify feature, do not send names or email addresses, and do not send custom event properties. Visitors says its script sends no analytics events when Global Privacy Control or Do Not Track is enabled in the browser.

Visitors processes and stores analytics event data in the European Union. Its policy says most analytics data is retained while the project remains active, performance measurements are deleted after one year, and website analytics data is not sold or used for Visitors’ own business purposes. Read the Visitors Data Policy for the full processing, retention, and subprocessor details.

Purchases

FaveNest Pro is bought through the App Store using Apple’s StoreKit, which is built into iOS, iPadOS and macOS rather than added to the app as a third-party service. Apple processes the payment. We never see your payment details, and we receive nothing from the transaction that identifies you. What the app itself keeps is a single flag on your device recording that Pro is active, stored alongside the app’s other settings.

Apple gives us the aggregate sales and download reports every developer gets, which cannot be traced back to a person. Buying Pro, or not buying it, changes nothing on its own about what leaves your device: the models run in the same place either way. The only thing that adds a destination is a key you add yourself, described above, and that is a separate choice from paying.

Location

FaveNest does not request access to your current location. Place data comes from the Apple or Google Maps links you choose to save, and from the addresses inside them.

The share extension

When you save something through the system Share sheet or menu, the extension writes the item to a shared container on your device that the main app reads. Nothing is transmitted anywhere as part of that hand-off.

Your data is portable

FaveNest can write a complete backup of your library as a plain JSON file, which you can store wherever you like and restore later. Deleting the app removes its local data from that device; deleting the records from iCloud removes them from your account.

Children

FaveNest is not directed at children under 13 and does not knowingly collect information from them. The app collects no library data from children or anyone else. The website does not ask visitors for a name, email address, or account. You can remove app data from your device and iCloud yourself at any time.

Your rights

Regulations such as the EU’s General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) give you rights to access, correct, port, erase, or object to certain uses of personal data held by a company. Dion Software, LLC holds no library data from the FaveNest app, so there is no app data for us to produce or erase. You retain full direct control of your library on your device and in your iCloud account. A request about content sent to an AI provider with your own key goes to that provider, which holds it under its own policy. For a question or request concerning website analytics, contact us at the address below.

Changes to this policy

If the FaveNest app ever adds analytics, an owned backend, a third-party service, or any other change to how app data flows, this page will be updated before that version ships. If the website changes its analytics provider or practices, that will be reflected here too. The date at the top will change whenever this policy changes.

Contact

FaveNest is built and operated by Dion Software, LLC. For privacy questions, write to support@favenest.app.