SellerHintWhat to include
- What you found, and where
- Steps to reproduce it
- What an attacker could achieve
- Any proof of concept, kept minimal
- How you would like to be credited, if at all
Security
Security at SellerHint
How the two products are structured, what is claimed, and — just as importantly — what is not claimed. Nothing on this page is stated unless it has been verified.
Overview
SellerHint applies reasonable technical and organisational safeguards to the information it handles. No product can guarantee absolute security, and this page does not claim that any product does. Specific properties such as encryption at rest, key management or regional storage appear here only once they have been technically verified; where a line below says a property has not been verified, treat it as not in place.
SellerHint for Mac architecture
- Local product data
- Product records, images, preferences, drafts and cached marketplace information are stored on your Mac.
- Authorisation
- eBay authorisation is handled through the SellerHint backend boundary. You sign in on eBay, not in SellerHint.
- Marketplace secrets
- The native application does not contain eBay application secrets and does not expose raw refresh tokens.
- Remote operations
- Marketplace reads and writes are performed through SellerHint services and processed in order.
- Store scoping
- Marketplace data is held against the store it came from. One store’s information is not shared with another.
- Local logs and diagnostics
- Logs and diagnostic reports stay on your Mac until you choose to send one. Review a report before sending it.
- Backups
- Local data is your responsibility to back up. The application provides backup and restore tools.
SellerHint Web architecture
- Account storage
- Not published.
- Application data storage
- Not published.
- Authentication
- Not published.
- Session management
- Not published.
- Data export
- Not published.
- Account deletion
- See the account deletion page for the routes that exist today.
Access and isolation
- Store isolation. Marketplace information is scoped to the connected store it belongs to, and is not merged across stores.
- User authorisation. Marketplace access depends on the authorisation you granted on eBay, and can be revoked there at any time.
- Least access, administrative controls, and production separation. Not described here, because they have not been documented and verified. They will be stated once they are.
Data transmission and storage
Traffic to this website and to SellerHint services uses transport encryption, which is a property of how the services are served rather than a claim about how data is stored.
Logging
Logs are intended to help diagnose faults, not to accumulate personal data. They should avoid secrets and unnecessary personal information, and diagnostic reports you send to support should be reviewed by you first — remove buyer names, addresses, phone numbers and email addresses that are not relevant to the fault.
Incident response
Where a material security incident affects users, SellerHint will notify affected users and any regulator required, in line with applicable law and the procedures in place at the time. Status and impact information for service incidents is published on the service status page.
Responsible disclosure
A security reporting address has not been published yet
Until it is, use the contact page and mark the message as a security report so it can be routed appropriately. Please do not post vulnerability details publicly.
What is in scope
- The SellerHint public website
- SellerHint services operated by SellerHint
- The SellerHint applications themselves
Third-party services, including eBay, are not in scope. Report those to their owners.
Third-party services
The services that process data on behalf of SellerHint are listed on the subprocessor page. That list is currently empty because the vendors have not been confirmed. Hosting providers are not named yet.
Certifications
Page details
- Last reviewed
- 2026-08-12
- Content owner
- Engineering