What CaseKit reads, and what it cannot do
Support tooling sits between your customers and your store, so the access model deserves a straight answer rather than a badge. Here is the actual boundary.
| Question | Answer |
|---|---|
| Reads the Gmail conversation currently open | Yes |
| Reads other threads or your mailbox | No |
| Uses Gmail API restricted scopes | No |
| Sends context to CaseKit's backend to resolve the order | Yes, over HTTPS |
| Logs raw email bodies | No |
| Stores full Gmail threads as its data model | No |
| Shopify access level | Read-only |
| Can refund, cancel, edit or fulfill orders | No |
| Can send email on your behalf | No |
Claims we do not make
A lot of extensions in this category say "nothing ever leaves your browser". For CaseKit that would be untrue, so we do not say it.
Resolving which Shopify order sits behind a conversation happens server-side. That means the minimum context needed for resolution is transmitted. Saying otherwise would be marketing rather than engineering.
What CaseKit is designed to do is use only the support context the current feature needs, and no more.
What is sent to resolve an order
- The sender's email address
- Any order reference found in the message
- A short snippet used to classify the request
Not the thread history. Not your attachments. Not your other conversations.
Questions about this feature
Does CaseKit read my whole mailbox?
Does data leave my browser?
Do you store my emails?
What Shopify access does it need?
Can CaseKit send an email on my behalf?
Try it on your next customer email
Free plan: unlimited Shopify order lookups and 25 replies a month.