Privacy policy

Updated 5 October 2026

Optional full collection backups

In a supported app build, choosing “Back up full collection” separately uploads your complete private collection: binders, pages and pocket positions, decks and allocations, import receipts and price history, private notes and costs, original binder-page photos and saved card images. Unsaved scans stay on your device. This choice is separate from saved-card copying, public sharing, diagnostics and training contributions.

Full backups use your existing account, encrypted connections, private account-scoped storage and verified file checksums. Accepted versions remain available until account deletion, within the service’s stated limits. Abandoned unfinished uploads expire and unreferenced uploaded files can be cleaned up after 48 hours. Downloading a backup does not replace your local collection; restoration uses a separate reviewed import. Account deletion removes these backups and uploaded files; local copies and exported recovery files remain under your control. This is not automatic cross-device editing. Keep a separate recovery copy.

Your private collection

Your collection and pending scans are stored on your device. If iCloud is available, collection records and binder photos sync to your private iCloud database. Exported collection backups contain your saved records and photos. Scryfall and configured price services receive requested card identifiers and network information when supplying images, catalogue data or prices. Optional Mac recognition sends captures to your configured local Mac.

Optional sign-in and saved-card uploads

In account-enabled iPhone builds, you can sign up or sign in with Apple, Google or email and password. Supabase Auth processes your email address, provider account identifier and authentication credentials to provide sign-in, email confirmation and password reset. We request basic identity access, not your Google mailbox or contacts. Transactional account emails are sent by Resend from accounts@notify.binderweave.com.

After signing in, choose Connect this collection to upload a private copy of saved cards and their accepted card images. A local recovery backup is created first. Subsequent saved-card changes upload while you use the app. The uploaded record includes card identity, printing, language, finish, condition, quantity, active status and physical-location IDs. It excludes private notes, purchase costs, pending scans and whole binder-page photographs. Per-card images have original metadata removed, but may still show sleeves or background details. Older holdings may have no retained card image.

Saved-card records use our existing Supabase database in Frankfurt. Private images and the account API use Cloudflare R2 and Workers. Images require account authentication and have no public sharing URL. These providers process network information to deliver and secure the service. Account uploads do not enrol you in recognition training, diagnostics or public trade sharing. We do not sell this account data or use it for advertising or cross-app tracking.

Account retention, export and deletion

Your saved-card account copy remains until you remove the records or delete the account. Unreferenced uploaded images are removed by hourly cleanup. In Your account, you can export account records, sign out, retry an upload or delete your account and uploaded data. Account export contains card records; use the app’s portable collection backup for a complete export including local photos. This saved-card copy is separate from optional full backups. Local saves and private iCloud remain the authoritative collection; no automatic collection merge is enabled.

Account deletion removes uploaded records and images and your Supabase sign-in identity. It also deletes connected trading data and revokes the Apple grant when that trading identity is linked. Local cards remain on your device. Keep the app installed while deletion is pending so interrupted cleanup can retry. Ordinary account access and uploads are blocked immediately after deletion begins. Minimal account-ID deletion markers prevent late writes; retry credentials are retained for up to seven days after expiry. Contact support if cleanup remains pending beyond that window. Uninstalling alone does not request deletion.

Optional usage and diagnostics

You can separately choose to share privacy-limited product usage counts and reliability results. These events cover app opens, collection activation and return use, account-upload outcomes, scan-to-save completion, trade-list publication and pod join/contribution outcomes. They include only allowlisted categories, counts, timings, app build and operating-system major version. They never include card names or identifiers, collection or location names, prices, photos, notes, email addresses, account identifiers, pod identifiers or free text.

The app uses a random identifier for each diagnostics consent period. Queued events expire on the device after seven days and uploaded events expire after 45 days, allowing seven- and 30-day retention to be measured. Usage and diagnostics are off until you choose to share them. You can stop sharing and request deletion in Portfolio → Privacy & recognition. A hash-only revocation record prevents delayed uploads from restoring deleted events. Diagnostics are not used for advertising or cross-app tracking.

You choose what to share

Personal trade lists publish only the cards and quantities you select, your chosen display name, printing, language, finish, condition and optional estimated market prices. Only confirmed printings are published. Your full collection, physical storage locations, notes, purchase costs and captured photos are not included.

Shared links and pods

Anyone with a personal trade-list link can view and forward it. Lists are excluded from search indexing, but a link is not a password. Public pods allow anyone viewing their card page to join in BinderWeave. Private pods require a separate invitation link and do not offer joining from the card page. Owners can change that setting without removing existing members. Anyone holding an active private invitation can use it until the owner replaces it. Contribute only cards you are comfortable sharing with the pod and its chosen audience. Leaving a pod withdraws your contribution.

Accounts and service providers

Updated apps use your BinderWeave account (Apple, Google or email) for trading and pods. Existing trading profiles are connected only with proof of ownership. Legacy random management credentials and Apple identifiers may be retained for compatible existing profiles until account deletion; no email-based identity matching is used. Choose a display name that you are comfortable sharing. Hosting and database processing use OpenAI Sites and its Cloudflare infrastructure.

Trade requests and notifications

Sending a request shares your chosen name or nickname, selected cards and any contact detail you choose to provide with their owners in the app. That optional contact detail may be an email address, phone number or another way to reach you. Requests and responses are available for 90 days and deleted when their owner deletes sharing data. Your private status link lets anyone holding it see the owners’ responses. Approval does not reserve or transfer cards. Optional notifications use Apple’s push service; device tokens are stored privately and removed when notifications are disabled in the app or sharing data is deleted. Lock-screen alerts contain no card names or requester details.

Withdrawal and deletion

In Collection → Cards for trade, withdraw your list, replace its link or pause trading. In Your account, deleting your BinderWeave account also removes published cards, pod memberships and pods you own, and revokes any retained legacy Apple trading grant. Your private collection remains intact. Irreversible hashes of deleted management credentials remain to reject late uploads; they contain no card list or Apple identifier. Recipients may retain screenshots or copied requests. Reports are retained to investigate abuse.

Availability and prices

Changes reach shared lists when the owner’s app successfully syncs. Check the update date and confirm availability with the owner. A request does not reserve cards. Estimated market prices are reference information, not an asking price, appraisal or guaranteed trade value. BinderWeave does not process payments, shipping or transfers between people.

Community rules

Only offer cards you own and accurately describe their printing and condition. Do not publish abusive names, misleading offers or another person’s private information. Public display names and pod names are screened before publication. Use Report this list on the web, or the report controls in the app, to report a problem. Signed-in members can block another member; their cards and activity are hidden from each other in signed-in trading views, and account-based trade requests are prevented. A blocker can reverse this in the app. Pod owners can also remove members and prevent them from rejoining with the same invitation. BinderWeave support aims to review abuse reports within 24 hours and may restrict sharing or accounts to protect users.

Recognition contributions are separate

Publishing a trade list does not consent to model training. Optional recognition photo contributions require a separate choice in the app. If you agree, cropped saved scans, predicted and selected card labels, reviewed fields, capture time, app build and random grouping identifiers help evaluate and train recognition models. Full binder pages, quantities, prices, private collection names, notes and original GPS/EXIF metadata are excluded. Crops may still contain background or sleeve details. Apple account identifiers are not attached to these contributions, and adding a card alone is not treated as a verified training label.

Recognition examples are private in Cloudflare storage and may be reviewed by authorised operators. The phone retains at most 100 crops for up to 7 days; uploaded examples expire within 90 days. Portfolio → Privacy & recognition lets you stop sharing and request deletion. Offline requests retry when the app reopens on Wi-Fi; keep it installed until completion. Released model weights cannot be individually edited to remove an example’s influence. Source deletion prevents its use in future training datasets. Minimal hashed revocation markers prevent late uploads. Contributions are not sold or used for advertising or cross-app tracking. Hosting providers process network information to deliver and secure both services.

Read the app’s recognition privacy policy

Optional price-history contributions

Importing a collection or price history remains private by default. If you separately opt in, BinderWeave uploads imported printing IDs, finish, language, condition, day, currency, amount and source platform for historical-price research. Quantities, folder names, filenames, notes, photos and account identifiers are excluded. A random installation credential supports updates and deletion. Candidate records are kept privately for at most 90 days and are not treated as verified market quotes without review and independent corroboration. Stopping sharing and requesting deletion removes that installation’s source records; previously published aggregate estimates may remain.

Questions and requests

Contact support@binderweave.com for support or privacy requests. Messages and optional report details are retained as needed to answer requests and investigate safety issues. Sharing deletion, account deletion and recognition-consent controls are also available inside the app without contacting anyone. Uninstalling alone does not send a deletion request.

This website and support

These public pages use OpenAI Sites and Cloudflare hosting. We do not add advertising analytics or tracking cookies. Hosting providers process network information to deliver and secure pages. Emailing support shares your message and sender address with the developer’s Google-hosted support inbox. Do not include passwords or sign-in codes.