Closio docs

Closio for Shopify

Security and data handling

Closio is built by Striveloom (Rioco LLC) and runs on Vercel with a Neon PostgreSQL database. This page states what is in place today, in plain words, and what is a plan rather than a fact.

Updated 2026-11-06

Transport and storage

All traffic between the shopper's browser, Shopify, Closio and the database uses TLS 1.2 or higher. The database volumes are encrypted at rest by Neon (AES-256). Secrets (Shopify API secret, model provider keys, email key, cron token) exist only as Vercel environment variables; none is ever sent to a browser, and the storefront widget talks to Closio only through Shopify's signed app proxy.

Key rotation policy

Policy, applied by the Closio team:

  • Model provider keys (OpenAI, DeepSeek, Anthropic) and the email provider key are rotated at least every 90 days, and immediately if exposure is suspected. Rotation is a Vercel environment change plus a redeploy; no merchant action is needed.
  • The Shopify API secret is rotated through the Shopify Dev Dashboard; both secrets stay valid during the swap so stores keep working.
  • The cron token is at least 16 characters, rotated with the provider keys, and accepted only as a bearer token on the nightly job route.
  • Webhook signing secrets for your own notification channels are generated by Closio with a CSPRNG, shown once, and can be replaced by deleting and re-adding the channel.

Webhook and request verification

  • Incoming Shopify webhooks (orders, billing, app lifecycle, GDPR) are verified with Shopify's HMAC-SHA256 signature over the raw body before any processing; unsigned or mis-signed requests are rejected.
  • Storefront requests (chat, voice, signals, offers, config) arrive through Shopify's app proxy and are accepted only when Shopify's signature on the request is valid, which also identifies the store.
  • Admin pages require an authenticated Shopify admin session (embedded App Bridge); every merchant write is recorded in the audit log with the acting staff member.
  • Outgoing notification webhooks carry an HMAC-SHA256 signature of the body and are only sent to public hosts (private, loopback and link-local addresses are refused, and the connection is pinned to the vetted address).
  • Imported Knowledge URLs go through the same host check before fetching.

Rate limits

Limits are per store and per shopper, in separate buckets, so a burst of one kind of request cannot starve another. Spend-creating limits (new conversations, voice starts) fail closed when the limiter store is unavailable. The table is generated from the running configuration.

What is limitedLimitBurst
Chat messages per shopper10 per minuteburst 5
Chat messages per store120 per minuteburst 60
Voice start/end/tool calls per store60 per minuteburst 30
Live-voice tool calls and transcript saves per store300 per minuteburst 120
Live-voice tool calls per shopper30 per minute—
Live-voice transcript saves per shopper60 per minute—
Feedback (thumbs) per store60 per minuteburst 30
Feedback (thumbs) per shopper30 per hour—
Storefront hesitation signals per store240 per minuteburst 120
Offer accept/dismiss per store60 per minuteburst 30
New conversations per client connection20 per hour—
Voice call starts per client connection10 per hour—
New conversations per store300 per hour—
New conversations per store (20 % of the plan's monthly allowance, min 10)60 per day—
Handoff emails per store20 per hour—
Inbox replies per store100 per day—
Inbox replies per shopper address5 per day—
Failed order lookups per shopper10 per hour—
Failed order lookups per store100 per hour—
Back-in-stock requests per shopper5 per day—
Back-in-stock requests per shopper email per store3 per day—
Agency console login links per email5 per hour—
Agency console login links per IP20 per hour—
Agency account creation per IP3 per day—

Burst = token bucket on a single instance; the window limit is the shared, multi-instance ceiling.

What we store, and what we mask

Shopper transcripts are masked before storage: emails, phone numbers, card numbers (Luhn-checked), IBANs and street addresses are replaced with placeholders. The unmasked text is used only during the turn in which it was typed (for example to look up an order by email). Voice audio is processed live and never stored. The client IP is never stored; a truncated hash is used for rate limiting only. Application logs carry no emails, IPs or order payloads.

Data retention and deletion

  • Shopper data (conversations, messages, voice sessions, offer events, signals, back-in-stock requests) is deleted after 12 months by a nightly job; merchants can shorten this to 3 or 6 months in Controls.
  • Health samples (Status page) are deleted after 30 days; they contain no shopper data. Audit log entries are kept for 12 months.
  • Uninstalling triggers Shopify's shop/redact webhook 48 hours later, which deletes every row Closio holds for the store, including credits and settings.
  • customers/data_request compiles a shopper's conversations and emails the summary to the store owner; customers/redact deletes that shopper's conversations, handoffs, voice sessions and signals and removes order references.

Access control

No Closio staff reads production data routinely. Access is incident-only, through the database console, with a logged reason. Merchants control who can open the app through Shopify staff permissions.

Incident process

  • Detect: health samples on every chat turn, voice connect and webhook delivery; platform logs; merchant reports to the security contact.
  • Triage within one business day; contain (revoke keys, pause the affected path, roll back the release).
  • Notify affected merchants by email within 72 hours of a confirmed incident involving their data, with what happened, what was affected and what we did.
  • Record a short post-incident note in the changelog once resolved.

Compliance status and roadmap

Closio honours Shopify's mandatory privacy webhooks and the protected customer data requirements, and offers a data processing addendum with a published sub-processor list. Closio does not currently hold a SOC 2 report or an ISO 27001 certificate; SOC 2 Type I is on the company roadmap and this page will say so when a report exists. No certification is claimed that does not exist.