Afterwise Privacy Policy
Last updated October 30, 2026
Who we are
Asynpulse LLC operates Afterwise. For store claims, we process customer data on the merchant’s instructions to provide the service. The merchant determines its customer claim policy and is responsible for informing its customers. Contact us at privacy@afterwise.app about our processing.
What we collect
For a claim, we collect the order number, items, amount and delivery information; the customer's name and email address held by the store; the claim text; uploaded photos and live-capture frames; and file, browser and device information. Photos may include shipping labels, handwritten capture codes and personal information visible in the image. Claim text may also contain personal information entered by the customer. Structured shipping-address identifiers are kept as one-way hashes. Claim and rate-limit IP identifiers are hashed; hosting providers may separately process connection and security logs under their own policies. From the store, we collect staff identifiers associated with claim actions, store settings and plan information.
Why
To match a claim to an order, run the enabled photo checks, review the reported issue, provide risk signals, email the customer and store, recognise repeat claims within the same store, prevent abuse, and bill the store through Shopify. Checks depend on the configured providers and may be unavailable or inconclusive; they do not establish that a claim is genuine or fraudulent.
Processors
Service providers used by the configured service include Shopify for orders and billing, Fly.io for hosting, Neon for the database, Cloudflare R2 for photo storage, Resend or Postmark for email, Sightengine or Hive for AI image detection, Google Cloud Vision for reverse image search when enabled, and Alibaba Cloud Model Studio or Anthropic for model-based claim and photo review. We do not add structured customer name or email fields to model requests. Claim text and images are processed for the checks and may themselves contain names, addresses, email addresses or other personal information supplied by a customer. Processing locations depend on the provider and deployment configuration; contact us for the current processor and location details.
Store reporting
Claim-level signals, suggestions and decisions support the service and reporting for each store. Cross-store aggregate analytics are not enabled in this release. Personal data is not used to score claims across stores, and store-level claim data is not shared with other merchants or partners or sold.
Retention
Claim photos are deleted after the period chosen by the store (30, 90 or 180 days); photo metadata and check results remain with the claim. Unsent drafts are deleted after 7 days of inactivity. Claim records and decisions, including the customer's name and email, are kept for the life of the store's account and deleted within 30 days after uninstall. Email and shipping-address hashes help recognise repeat claims within the same store. Hashed rate-limit identifiers are removed by periodic cleanup after their counting window expires. Detection API image bytes are processed without being saved to photo storage. API request metadata and context, results, image metadata and fingerprints are retained for 90 days from request creation and then removed by scheduled cleanup once processing has finished. Lifetime and monthly usage counters, historical pricing, settlement records and deletion audit records are kept separately for quota enforcement and accounting; they do not contain API image bytes or request context. Deleting API check details does not reset free or monthly allowances or erase amounts already owed. Contact us to request access to or deletion of API check details; an authorised operator can preview and confirm deletion of completed or failed requests.
Choices and confirmation
Merchants explicitly confirm the Terms and Privacy Policy during setup; we record the version, time and a hashed staff identifier. Before uploading claim photos, customers confirm a notice explaining Afterwise, service providers and AI photo checks; we record the version, time and confirmation or withdrawal event. Clearing the choice stops new photo uploads and checks initiated from those uploads; it cannot undo processing already completed or in progress. Customers can contact their store to withdraw a submitted request or request access or deletion. A customer may ask the store to decide personally before submitting a claim. Photo checks still support that review, but automatic refunds are disabled for that claim. This choice does not change the merchant’s fees or claim policy. We do not use claim information for advertising or sell it.
Security access records
We record authorised access through the merchant app, customer claim API, signed photo and evidence links, Detection API, owner portal and processing/email workers. Access records contain time, access channel and action plus keyed hashes of the operator and resource identifiers; they do not contain photo bytes, email addresses, names, raw IP addresses, query strings or access tokens. Access records expire after 90 days through scheduled cleanup. An authorised operator records direct production support access separately and reviews the trail for unexpected access.
Your rights
Customers can ask the store, and the store can ask us, to access, correct or delete personal data. We honour Shopify's customer data request and redaction webhooks automatically.
Contact
privacy@afterwise.app