Encrypted store keys
Every API key, password and token a merchant gives us is encrypted with AES-256 before it is stored. The API never returns it.
Zikkio holds API keys to your customers’ stores and a copy of their catalogs. This page lists what we store, where it lives, how it is protected and how to reach us about a vulnerability.
Last updated 27 October 2026
Six rules that apply to every connection, on every plan.
Every API key, password and token a merchant gives us is encrypted with AES-256 before it is stored. The API never returns it.
Every request is checked against the account that owns the store. One customer can never read or change another customer’s connections.
Calls to Zikkio, and from Zikkio to the stores, use TLS with certificate checks. Store domains are validated before any call.
Zikkio reads products and orders and writes prices and stock. Card numbers never reach Zikkio: the platforms do not expose them.
Application logs are kept for five days. Store keys and request bodies never go into logs or alerts.
Rate limits per API key and per account keep one busy integration from slowing down the others.
Zikkio keeps a copy of each catalog so reads are fast and stores are not overloaded. This is everything we hold, and for how long.
| Data | What it is | How long we keep it |
|---|---|---|
| Store keys | What it is: API keys, passwords and OAuth tokens for each connected store, encrypted with AES-256. | How long we keep it: Deleted when the store disconnects |
| Catalog copy | What it is: Products and variants: name, price, cost, stock, brand, category, GTIN, SKU and image links. | How long we keep it: Deleted within 30 days of disconnecting, backups included |
| Account users | What it is: Name and email of the people who use the Zikkio account. | How long we keep it: While the account is open |
| Your API keys | What it is: The keys your application uses to call Zikkio, stored as hashes. | How long we keep it: Until you revoke them |
| Application logs | What it is: Errors and request metadata, without store keys or request bodies. | How long we keep it: 5 days |
| Job records | What it is: Status of catalog downloads and price updates. | How long we keep it: 30 days |
Card and payment details never reach Zikkio.
The companies that process data on our behalf. We tell customers 30 days before adding a new one.
| Provider | What they do for us | Location |
|---|---|---|
| Amazon Web Services | What they do for us: Servers, database and cache for the API and the catalog copy. | Location: United States |
| Sentry | What they do for us: Error tracking, configured not to receive personal data. | Location: United States |
| Slack | What they do for us: Internal error alerts for the team, without store keys or request bodies. | Location: United States |
Shopify, WooCommerce, Magento, PrestaShop, BigCommerce, Wix and Google are the merchant’s own platforms, not sub-processors.
Certifications, hosting, contracts and what happens to data when a store leaves.
Free plan with 5,000 API calls a month and unlimited stores. No card, and no sales call unless you ask for one.
curl -X POST https://api.zikkio.com/v1/connect/sessions \ -H "Authorization: Bearer zk_test_••••" \ -d '{ "platform": "shopify" }'
{ "connect_url": "https://connect.zikkio.com/s/ses_3kd9" }