Current model
0
External servers storing shopping data
Guide
Shoplytics privacy, explained in plain English.
The current product promise is simple: Shoplytics is meant to be useful without a login, and all shopping data stays on your device. This guide explains what that means in practical terms.
No login required
The core fetch-and-analyze flow does not require a Shoplytics account in the current product model.
User-triggered
The extension becomes active when the user opens it, selects platforms and dates, and clicks “Fetch Orders.”
What the current model does
- Processes supported order history after the user triggers a fetch.
- Shows analytics such as total spend, order count, trends, and average order value.
- Allows export when the user explicitly chooses that action.
What the current model does not do
- It does not require a separate login for core use.
- It does not use external servers or cloud storage for shopping data in the current flow.
- It does not pretend to be an official banking or financial-accounting product.
Where to read the formal version
Why this matters
Privacy should not be hidden in a footer promise. It should be visible in the architecture, the workflow, and the claims the product makes publicly.