Your radar should not become someone else’s data source.

Account and cloud information

Sign in with Apple and Supabase process your account identifier, your name if Apple provides it, and your email or Apple private-relay address. Magpye stores your display name, onboarding status, marketplace selections, Watch definitions, notification preferences, and synchronization version so those settings can be restored across authenticated sessions.

Supabase also stores source scan and run diagnostics and marketplace matches associated with your account. A match may include a public listing identifier and listing content, Magpye's derived valuation, whether you saved or dismissed it in your Inbox, and freshness and lifecycle timestamps.

Information on your device

Magpye maintains a local working copy of your profile and Watches. Listing analyses may include titles, source URLs you choose to save, seller-provided metal and weight details, acquisition costs, calculated valuations, and safety-gate results. This information is used to provide the app’s features.

Marketplace and market-reference data

Approved marketplace APIs may provide public listing information to Magpye. The app also requests a shared cached snapshot of gold, silver, platinum, and palladium reference rates. Metals.Dev receives scheduled requests from the Magpye backend rather than a separate request for every user or Watch.

Direct Etsy Watch searches, and any future direct eBay Watch searches, send search criteria to the provider's official API. Magpye does not send your Magpye user identifier or marketplace password with those search requests, and it does not collect marketplace passwords. If you open a listing, the destination marketplace handles that visit under its own privacy policy and terms.

Shared-catalog provider payloads are cached for no more than 5 hours and 45 minutes. At expiration, provider payload and valuation fields are redacted and the private shared-catalog row is deleted. If the listing had entered your Inbox, Magpye may retain a minimal account-owned tombstone plus save, dismiss, freshness, and lifecycle timestamps so your workflow remains coherent without retaining the expired provider payload.

Notifications

Notification permission is optional and can be changed in iOS Settings. During the private beta, remote marketplace-match push tokens and alerts are disabled. Magpye will update this policy and the App Store privacy disclosures before enabling them.

Service providers and network information

Apple provides authentication, Supabase provides account storage and backend infrastructure, Cloudflare provides the public website and related security services, Metals.Dev supplies shared metal-rate references, and approved marketplace APIs may provide public listing data. These providers may process standard network information for delivery, security, logging, and abuse prevention under their own policies.

No sale, advertising, or cross-app tracking

The private beta does not include advertising SDKs, data-broker sharing, or cross-app tracking. Magpye does not sell personal data.

Retention and deletion

Signing out removes that account's Magpye working cache from the device. Uninstalling the app also removes local app data. Cloud account information, Watch definitions, and account-owned workflow records remain until you delete the account; shared provider payload follows the shorter retention period described above. You can delete your account in the app or follow the instructions on the account-deletion page.

Children

Magpye is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

Changes and contact

This policy will change when Magpye adds new connectors, remote notifications, analytics, or other data processing. Material changes will be reflected here and in the App Store privacy disclosures.

Questions or privacy requests can be sent to [email protected].