Privacy policy

1. Who this policy is from

This policy is issued by ArkeeTech (Indonesia), the developer and operator of Arkee Commerce. For any question about this policy, contact build@arkeetech.my.id.

2. What the platform stores

The application stores the following categories of data:

• Account data — the name and email address of each user ArkeeTech provisions, and a cryptographic hash of their password. Plain-text passwords are never stored.
• Organization and store configuration — the merchant business name, the storefronts it operates, and settings such as timezone.
• Marketplace authorization state — when a merchant authorizes a shop, the access and refresh credentials issued for that shop, the shop identifier, the granted scopes and their expiry. These are held per shop, encrypted at rest, and never displayed back through the interface or API.
• Order operations data — for each authorized shop, the order records needed to run the merchant's operations: order numbers, statuses, the sales channel, payment and placement times, product names, SKUs, quantities, prices, order totals, the assigned logistics provider and tracking numbers.
• Product and stock data — for each authorized shop, its product listings: titles, listing status, SKU codes, variation names, prices and stock levels.
• Automation records — the runs performed for the merchant, their per-order outcomes and their logs.
• Technical logs — application error and access logs generated in the ordinary course of running the service.

ArkeeTech does not store end-buyer personal data. Buyer names, phone numbers, email addresses and delivery addresses returned by a marketplace are not written to the database; only the operational order fields listed above are kept.

3. Why the data is processed

Data is processed for one purpose: to provide the merchant the service they signed up for — centralizing the orders of their own stores and running the operational automation they configured. ArkeeTech does not sell data, does not share it with advertisers, and does not use merchant or marketplace data to train models or to build products for anybody else.

4. Separation between merchants

Every store, order and automation record belongs to exactly one organization. Access is restricted to users who are members of that organization, and every query the application performs is scoped to the organization of the signed-in user. A merchant authorizing a store gives ArkeeTech access to that store only, and no other merchant can see it.

5. Sharing with third parties

Data is shared only with the infrastructure providers needed to run the service — hosting, database and email delivery — and only to the extent that running the service requires. Data is disclosed to a marketplace operator only through that marketplace's own API, in the merchant's own account context. Otherwise data is disclosed to a third party only with the merchant's instruction or where ArkeeTech is legally required to do so.

6. Retention and deletion

Data is retained while a merchant's account is active. A merchant can disconnect a shop from its store page at any time: ArkeeTech then deletes the stored credentials for that shop immediately and stops retrieving its data. Revoking the authorization in the marketplace's own seller center has the same effect on the next sync attempt. A merchant may request deletion of their account and its associated data by writing to build@arkeetech.my.id.

7. Security

The application is served over HTTPS. Passwords are stored as one-way hashes. Marketplace credentials are encrypted at rest, excluded from the application's serialized output and removed from error messages before anything is logged. Access to production systems is limited to the people who operate the platform. No system is perfectly secure, and ArkeeTech does not claim any security certification it has not obtained.

8. Merchant requests

A merchant may ask what data ArkeeTech holds about their organization, ask for it to be corrected, ask for a copy, or ask for it to be deleted. Requests are handled at the address above.

9. Changes to this policy

This policy will be updated as the platform changes — in particular whenever a new marketplace integration or a new category of data is added. The date at the top of this page reflects the most recent revision.