Privacy Policy

• Account information. Your email address (to create and sign in to your account). If you choose to sell books to BookToCash from the app, your name, mailing address and preferred payment method are collected to fulfil the order and pay you.
• Scans and app activity. The ISBNs you look up, your scan history and your trigger settings, so verdicts and history work across your devices.
• Location (optional). With your permission, your device location is used in the foreground only to sort nearby book sales by distance on the Sourcing Map. If you decline, the app falls back to your ZIP code area. We never track location in the background. On a helper seat (see Teams below) location is never kept: the app does not save it and our servers discard any coordinates on arrival.
• Camera and photos (optional). The camera is used on your device to read book barcodes. If you use Shelf Scan, the shelf photos you take are uploaded to our servers to identify the books in them.
• Amazon selling account (optional). If you choose to connect your Amazon selling account, we store your seller identifier and an encrypted authorisation token so RakeScan can ask, on your behalf, whether that account is allowed to list a book you scan. See Your Amazon selling account below for exactly what we ask for and what we never touch.
• Early-access list (this website). If you join the waitlist on rakescan.com, we store the email address you enter, solely to send you the beta invite and launch updates. No analytics or advertising trackers run on this site.

• No ads and no advertising SDKs in the app.
• We do not sell your personal information to anyone.
• No background location tracking.
• No access to your contacts, messages or files.

Connecting an Amazon selling account is optional. RakeScan works without it; when no account is connected the app reports that eligibility is unknown rather than guessing, because listing restrictions differ from one account to another.

• What we store. Your seller identifier, the marketplace you sell in, and an authorisation token that lets RakeScan act for you. The token is encrypted at rest with AES-256-GCM. It is decrypted only in memory at the moment a request is made and is discarded immediately afterwards.
• What we ask Amazon. One thing: whether your account may list a given book, and in what condition. RakeScan is scoped to the Product Listing role, which carries no personal information. It does not read your orders, your buyers, your payouts, your inventory or your financial reports, and the code that performs these calls is written to refuse any wider access.
• Short-lived working data. Access tokens live in server memory only, expire in about an hour and are never written to disk. Eligibility answers are cached for up to twelve hours so repeat scans do not re-query Amazon.
• Disconnecting. You can disconnect at any time from the Account screen in the app. Disconnecting removes the stored token and seller identifier from our servers. Deleting your account removes them as well.
• Not shared. Information obtained from your Amazon selling account is used only to answer the eligibility question inside your own app. It is not sold, not shared with other scouts, and not used to build any public data set.

An account owner can invite a helper to scan for them. The helper signs in with their own email; their phone then works as a helper seat on the owner's team. Three things are different on a helper seat, and this section is the record of them.

Activity

We record the books a helper scans and claims for the team — the ISBN, how many copies, and when — tied to the helper's seat and to the owner's team, along with an app-generated install id and the label the helper gives the phone. The owner sees that activity and the per-copy earnings it produces; the helper sees their own copies and earnings. The helper's phone is not sent the owner's prices, trigger settings, profit figures or ledger, and does not store them.

Location

A helper seat's location is never recorded. If a helper's phone includes coordinates in a request, our servers discard them before anything is stored: no sourcing trip is logged for a helper, under the helper's identity or the owner's, and the app on a helper seat does not save location on the device.

Retention

Claim records are part of the owner's team ledger — they are the record of what a helper is owed — and are kept while the owner's account is active, in the same way as records of completed book sales. Closing a seat stops new activity; it does not erase what was already earned. Either the owner or the helper can request deletion of their own account and associated data on the account deletion page; after a deletion request the requester's identity is removed, and the copies and amounts stay in the owner's ledger as anonymised bookkeeping records, like completed sales.