Privacy Policy — dibs Agent Order Checks
Last updated: August 13, 2026
This policy describes what dibs Agent Order Checks (“dibs,” “the app”) collects, stores, and does not collect, when installed on a Shopify store.
What the app does
dibs verifies a cryptographic credential attached to an order. The credential proves that a person, using a passkey on their own device, approved that specific purchase — the merchant, the item, and a price ceiling. dibs checks the credential and shows the merchant the result.
Purchase approval requests
When an AI agent asks a person to approve a purchase, dibs stores only the terms the agent sent — seller, item description, amount, currency, limit, expiry, a short reason, and the agent’s public key — until the person approves or declines. The signed approval is handed to the agent once and then deleted. Requests are purged after 24 hours. No name, email, address, or conversation is stored.
What we access
When installed, dibs reads:
- The order ID
- The order amount
- The order's channel attribution (which sales channel the order arrived through)
- The contents of a single app-reserved order metafield, which may contain a purchase-authorization credential
dibs requests the minimum tier of protected customer data access (Level 1) and does not request or use customer name, email address, phone number, or shipping/billing address. We do not need these fields to function, and we do not ask for them.
What we store
For each order, dibs stores:
- An anonymous credential identifier (a "trip ID"), which is not linked to any customer name or contact information
- A timestamp
- The verification result (verified, flagged, refused, or unverified) and, if applicable, the reason
- The verification trail — the individual checks performed and their outcomes
We do not store customer names, email addresses, phone numbers, physical addresses, payment details, or the contents of what was purchased beyond the order amount already described above.
How long we keep it
Each credential carries its own expiry, set at the moment a person authorized the purchase. Once that expiry has passed, the corresponding stored record is deleted automatically. We do not retain records on a fixed calendar schedule — retention is tied to the credential’s own authorized window, which is short (typically well under 24 hours).
What happens if you uninstall
If a merchant uninstalls dibs, all stored records for that store — credential identifiers, timestamps, verification results, and trails — are deleted. The same deletion runs again if we receive a shop/redact request, Shopify’s data-erasure signal, as a guaranteed backstop.
Data subject requests
Because dibs does not store any customer-identifying information, a customers/data_request or customers/redact webhook has nothing customer-specific to return or delete. We acknowledge these requests and take no further action, since no such data exists in our systems.
Independent verification
A verification desk is available at mydibs-bot.com/verify that requires no installation. Anyone holding a credential can check it independently; merchants are not required to trust dibs’s judgment alone.
Sub-processors
dibs is hosted on Fly.io. Verification data is stored in a managed PostgreSQL database (Neon), encrypted at rest and in transit. No other third party receives the data described in this policy.
Changes to this policy
If what we collect or store changes, we will update this page and update the version submitted to the Shopify App Store.
Contact
Questions about this policy or your data: support.dibs@gmail.com