Buyer Lens

Privacy

Buyer Lens reads a merchant's own PayBito payment data and shows it back to them. It is read-only, it stores almost nothing, and what it does store it forgets quickly.

What it reads

Only what the merchant grants at the PayBito consent screen, and only these scopes:

• payments.transaction.read
• payments.refund.read

In practice that is the merchant's transaction ledger — the customer id, name and email recorded against each order, the amount, currency, date, status and items — plus their refund records and their payment-history summary. This is the merchant's own data about their own customers. Buyer Lens does not read any other merchant's data, and PayBito would not permit it to: an app can only read the merchant that authorized it.

What it cannot do

Every operation on PayBito's App Store surface is read-only, and Buyer Lens asks for no exception. It cannot move money, take a payment, issue a refund, change a price, or alter a customer record. It has no ability to write anything, anywhere, in a merchant's PayBito account.

What it stores, and for how long

Nothing is stored in the browser except one opaque session identifier in an httpOnly cookie. It carries no personal data and cannot be read by JavaScript. Access tokens never touch the browser.

On the server, held in Redis:

• The session — the PayBito access token, refresh token and the identifiers needed to use them. Deleted after 7 days of inactivity.
• A cached copy of the buyer table — the merchant's transactions, grouped into customers, so that moving between screens does not re-read their whole ledger every time. Deleted after 5 minutes.

There is no other database. Buyer Lens keeps no long-term record of a merchant's customers, builds no profile that outlives the session, and does not retain data after a merchant disconnects.

What it never does

• It does not sell, rent or share merchant or customer data with anyone.
• It does not send data to any third party. There are no analytics scripts, no advertising pixels, and no tracking cookies — the only cookie is the session identifier above.
• It does not use anyone's customer data to train models, build audiences, or enrich any other dataset.
• It does not contact a merchant's customers. It never emails anybody.

How to make it forget

Click Disconnect in the header. That revokes the token with PayBito and immediately deletes the session and the cached buyer table. Uninstalling the app from the PayBito App Store has the same effect: without a token there is nothing left to read, and what was held has already expired.

Security

Tokens and the client secret live only on the server and are never sent to a browser. The session cookie is httpOnly and, in production, secure. Traffic to PayBito is over HTTPS.

Contact

Questions about this policy, or a request to delete anything, go to support@hashcashconsultants.com.