Rip or Skip

Fueren · Rip or Skip

Privacy policy

Updated 14 November 2026

Use Rip or Skip without an account, or optionally sign in with Apple to back up your collection. Camera recognition stays on your device.

Controller

Fueren S.à r.l. - S., 6D, Route de Trèves, L-2633 Senningerberg, Luxembourg; RCS B307480. Contact riporskip@fueren.lu.

Local collection and camera

Quantities, preferences, analysis results and scanner features are stored locally. Camera frames are processed on your device; we do not upload or retain photos or video. Public artwork is downloaded and cached separately. Your device’s own backup settings may include local app data.

Optional account and collection backup

Apple is the only sign-in method. We do not request your name, email, Apple password or payment information. We store an account identifier, a hashed Apple sign-in identifier, your unique username, account/session dates, hashed session tokens and an encrypted Apple refresh token needed to validate or revoke authorization. Your app session is stored securely in the device Keychain.

Backups contain card/collection identifiers, recorded language and finish, quantities and change timestamps, including zero quantities to preserve removals during synchronization. Public artwork, card text, camera frames and price histories are not duplicated in your backup. Collection snapshots are compressed and encrypted in our database using server-managed encryption; this is not end-to-end encryption. Usernames and collections are not public profiles in this version. Future trading features will require a separate privacy update.

Network requests and hosting

Our service and image hosts receive normal request information, including IP addresses and requested card/set identifiers, to deliver catalogs, images and prices. Owned quantities and account credentials are not sent to catalog suppliers. Cloudflare hosts our API, image cache and these pages. Neon hosts our Postgres database, including optional accounts and encrypted collection backups, with the primary database configured in the AWS Frankfurt region in Germany. Network delivery, security processing and operational logs may occur internationally under provider agreements and applicable transfer safeguards. Contact us for information about those safeguards.

Scanner device wallet

Scanner credits and Apple transaction identifiers are stored in this device’s Keychain to deliver purchases once and track remaining credits. A temporary pending-scan record links the credit spend to your saved card quantity so interrupted saves can be recovered. This wallet is not uploaded to our servers or collection backups, does not synchronize across devices, and is independent of your optional app account. It records credited purchases, subscription transaction identifiers, signed period dates and allowances, revoked transaction identifiers and source-specific spent-credit totals to prevent duplicate delivery and reconcile refunds. These records remain on the device while the wallet is retained, including after credits are spent. Logging out or deleting your app account does not erase the wallet. Removing the app is not a guaranteed way to erase Keychain records; erasing or replacing the device can lose the wallet. Contact us for help with local wallet data.

Apple subscriptions and purchases

Apple processes purchases, trial eligibility, renewals and refunds. StoreKit verifies subscription access and scanner-credit transactions on your devices. We do not receive payment card details or billing addresses. Subscriptions do not require a Rip or Skip account or username and are not linked to one as a condition of access. Apple retains purchase records under its own policies.

Purposes and legal bases

We provide requested authentication, backup, restoration and purchase delivery, including local scanner-credit accounting, under GDPR Article 6(1)(b); safeguard the service under our legitimate security interest, Article 6(1)(f); and comply with legal obligations under Article 6(1)(c). Short-lived salted network hashes support rate limits. We do not sell personal data or use it for advertising. The app has no advertising or behavioral analytics SDKs, and these pages use no tracking cookies.

Retention and deletion

Cloud collection data remains while your account is active until you delete it. Authentication challenges expire after five minutes, sessions after 30 days and rate-limit records after two minutes; expired records are cleaned regularly. Operational logs follow the hosting service’s limited retention settings. Application logs do not contain session tokens or collection payloads.

Delete your account in Settings to revoke Apple authorization and remove the active account, username, sessions and cloud snapshots. Local cards remain. Infrastructure recovery copies expire under the hosting provider’s backup lifecycle and are not used as active account storage. Logging out clears local cards, account credentials, preferences and private analysis caches, while retaining the cloud account. Deleting the app may remove local data; without an account there is no server backup. These actions do not cancel an Apple subscription.

Your rights and choices

You can change your username, log out or delete your account inside the app. Contact riporskip@fueren.lu for applicable access, correction, erasure, portability, restriction or objection rights, or details about service providers and safeguards. We may request proportionate identity verification. The absence of an in-app collection export does not remove statutory data rights. You may complain to Luxembourg’s CNPD or another competent supervisory authority.

Changes

We will update this policy and provide appropriate notice when practices materially change.

Binders, Wishlist and optional sharing

Where available in your app version, binder layouts and Wishlist entries are stored on your device, separately from optional collection-quantity backup. Personal images you select for binder slots are resized and stored locally; the app does not upload them and excludes those image files from operating-system cloud backup. Other local binder data may be included in your device backup settings.

Sharing a binder requires an account and username and is optional. When you publish or refresh a shared binder, we store a readable snapshot containing its name, colors, card identities and whether you own each displayed printing. Personal images, purchase records and card quantities are excluded. Anyone with its nine-character code can view that snapshot and your current username. Codes are access links, not private encrypted backups: share them only with people you choose.

You can share up to five binders and stop sharing any of them in the app. Revocation removes access through that code; people may retain screenshots or information they already viewed. Deleting your account removes its shared snapshots. Trade highlights compare the snapshot with the viewer’s local ownership; that comparison does not upload the viewer’s collection. We process opt-in snapshots to provide the sharing service you request, and apply authentication, bounded requests and rate limits to protect it.