YOUR TRUST MATTERS

Privacy policy

Your library is personal. Sharing a plan is your choice.

Effective October 5, 2026. This policy describes the FaveSpark app, invitation website and support service. Questions and privacy requests can be sent through our support form, without creating an account.

What you choose to save

The app keeps saved links, titles, captions, recipe text, selected covers, notes, plans, grocery lists, ratings and cooking progress on your device. A profile name, bio and profile photo are currently stored on that device. FaveSpark does not import your address book.

Accounts and syncing

Creating an account provides your email address and authentication information to our account provider, Supabase. Signing in syncs your private library, planning records and selected cover images to account-scoped storage. Our service uses account identifiers to restrict access. Signing in or creating an account is required to enter the native app. Guests can reply and participate on an invitation website without creating an account.

Sources, recipes and device permissions

Opening or preparing a saved link can contact the original website for metadata, captions, covers or media. That website receives normal connection information, such as an IP address, and its own privacy practices apply. Embedded players may also make requests to their providers. Saving a link does not make the source private.

Automatic recipe-video transcription is optional and starts off. If you enable it and grant Speech Recognition access, supported video is temporarily downloaded and recognition is required to run on your device. Extracted text becomes part of your save and can sync with your account. You can turn automatic transcription off in You → Settings → Video transcription. Existing transcripts remain until edited or removed. You may also select a video for a separate manual transcription action.

Photo selection is used for covers, profile photos and screenshot extraction. Supported text recognition happens on your device. Apple Maps receives place searches and geocoding requests. If you grant location access, your position supports nearby suggestions and map features while the app is active; it is not deliberately stored in your library or invitation. Notifications are optional. You can manage permissions in device Settings.

Invitations and contributions

An invitation publishes selected titles, links, images, places, costs and group notes. Anyone who receives or is forwarded a valid invitation can view its published content. Invite links normally expire after 30 days and the organizer can turn them off. Private library notes, recipe corrections and device location are not included.

Guests provide a name, attendance reply, votes, availability and an optional private note. Private notes are visible only to the organizer. Hosts can enable a guest list and Activity for an invitation; in that case, guests who reply Going or Maybe can see other participating guests’ names and replies, share text or small GIFs, and react to messages. Guests see this disclosure before confirming. Declined replies are not listed. Other people’s guest lists and Activity are hidden until a current reply is recorded. Budget is no longer collected. Shared messages can be reported, hidden or blocked; the host can moderate them. Activity is stored with the invitation and removed when its underlying account/space is deleted. GIF uploads are limited to 96 KB, stored privately, and shown to other guests only after host approval; no GIF search provider or remote image tracking is used. Shared collection additions and contributor names are visible to people with the link. A random key in browser storage lets a guest edit their response; clearing that storage loses this access. Invitation URLs pass through hosting infrastructure, and other apps may cache link previews.

Coordinating and remembering plans

Hosts can explicitly share a day-of schedule, meeting point, travel instructions, shopping/bring list and latest host update with people who have the invitation link. Guests who have replied Going or Maybe can provide what they are bringing and optional travel notes. These stay private to the host unless the guest explicitly chooses to share coordination with other guests who have replied. Shared task claims require this choice and guest Activity participation. Dietary needs are optional and private to the host; they are not shared with other guests or used to infer preferences. Completed-plan feedback and optional written memories are also private to the host. These details are stored with the invitation response and have the same retention and account-deletion behavior as other invitation content. Saving an idea into your own FaveSpark library opens the native app and asks you to review the published original link before saving; it does not copy the host’s private notes.

Support and safety reports

Our support form collects your reply email, topic and message. If you include an invitation in the separate invitation field, we store a one-way reference to its token to help locate the reported space. Avoid putting passwords, payment details, sensitive personal information or private links in the message. Requests and staff replies are stored privately. A secret receipt link lets you check a reply without an account; keep it private.

The invitation and support website uses short-lived hashed connection identifiers for rate limiting. Technical providers also process request and security logs under their own retention settings. We use reports to investigate abuse, handle privacy requests and resolve app problems. Reported content may be retained for investigation and legal obligations.

Service providers and purposes

Supabase provides account, database and cover-storage services. The invitation and support website uses OpenAI Sites and its Cloudflare infrastructure. Apple provides system services such as Maps and device permissions. Original content sites process requests when their content is accessed. These services may process information in countries other than yours.

We use information to provide saving, syncing, planning, sharing, support and security. The current app has no advertising SDK and does not sell personal information or use your library for cross-app advertising. Enabling a new cloud extraction service or changing these practices requires updated disclosure.

Retention and your choices

Local content remains until removed from the device. Synced content is retained while needed for your account and service. Removing an item may leave a deletion record used to keep devices in sync. Deleting your account removes its active cloud records, published spaces, responses and stored covers. Provider logs, backups, security records and copies held by other people can persist for their retention periods or legal requirements; account deletion cannot erase their screenshots or cached previews.

Support requests are kept while unresolved and as needed for follow-up, safety investigations, disputes or legal duties. You can request their removal through support, quoting your request reference. We may need to verify a request before acting. We do not ask for your password.

To delete your cloud account, open You → Account & sync → Account deletion → Delete account. Your device's local library is separate. After deleting the cloud account, the retained library can only be exported or removed through Device data on the sign-in screen; it cannot be opened under a different account. Anyone using the unlocked device can use this recovery export. Removing this device’s library also clears its local profile and temporary copies. Library backups are not encrypted by FaveSpark; store them privately and delete exported copies yourself. You can request access, correction or deletion and other rights available where you live through support.

Children and changes

FaveSpark is not directed to children under 13. Contact us if you believe a child has supplied personal information. Linked websites and user-shared content have their own age restrictions. If this policy changes, we will update its effective date and provide additional notice where required.