Access to the shop

Zorko reads shop data through the official marketplace API: supplies and acceptances, FBS postings, the error index, returns and products. The cost price of a product is entered by the seller — the marketplace does not report it.
Access rights are read-only. Zorko does not change data in the marketplace and does not act on the seller's behalf.
The access key is stored encrypted only (AES-256-GCM) and is never shown in the interface and never logged. When a shop is disconnected, the key is erased.

What is stored

Cases and their history: what a check found, which facts led to it and what the seller did about it.
Snapshots of marketplace responses — for investigating disputed cases and re-running checks. They are sanitized before being stored: recipient names and phone numbers and device identifiers are not kept.
Anonymized service metrics: the number of cases, reaction time, sync lag. Case and shop identifiers are not part of metrics.

What Zorko never does

It does not move money and does not manage payouts.
It does not change data in the marketplace.
It does not make financial decisions with neural networks: the rules are ordinary deterministic code that can be checked and explained.
It does not share shop data with third parties.

Who sees the data

The data belongs to the seller's organization: only its members see it. Organizations are isolated from each other — a request for someone else's object is indistinguishable from a request for a non-existent one.
The service operator sees the technical state of shops (for example, that a sync keeps failing) through an internal tool. Every such action is written to a journal.

Data deletion

The owner of the organization can delete it together with all data in the settings. Deletion is irreversible: shops, cases, history, products and marketplace response snapshots disappear together with the organization.

The operator action journal survives the deletion but loses the link to the organization: it keeps the fact of the action and the technical shop identifier.

Open settings

Questions

During the beta, questions about data are handled directly with the service operator — reply to the invitation email.