Privacy notice

Seller and controller

VerifyMade is the trading name used by Manish Narani, India. Privacy questions and requests can be sent to support@verifymade.com.

Scope

This notice describes how VerifyMade handles information received through this website, first-party funnel measurement, Razorpay or PayPal checkout, invoicing, private product delivery, the personalised Evidence Workflow Review, the Shopify app, and the support address. The public website has no customer account, advertising pixel, or newsletter form.

Information we receive

When you purchase, VerifyMade receives transaction and billing information needed to confirm payment, issue an invoice, deliver the product or service, and process refunds. This may include your name, business name, email address, billing address, country, optional business tax ID, payment-provider order and payment references, amount, currency, payment and refund status, fulfilment status, download count, purchase-offer agreement version and acceptance timestamp, and other operational timestamps. VerifyMade does not receive or store your full payment-card number. If you email VerifyMade, we also receive the information you choose to provide. Hosting and security providers may process ordinary technical request information such as IP address, browser type, timestamps, and requested pages.

How information is used

Information is used to process payment, issue and retain invoices and credit notes, deliver the product, answer enquiries, provide support, handle refunds, reconcile accounts, maintain security, prevent abuse, and meet legal obligations. VerifyMade does not sell personal information.

Cookieless funnel measurement

VerifyMade counts four first-party events: page views, product views, completed evidence scores, and checkout starts. A page view records only the requested path and any UTM source, medium, campaign, content, or term parameters. A completed score records only the result band and whether the visitor met the stated Shopify, proof-workflow, role, and volume criteria; individual answers are never sent or stored. Product views and checkout starts contain the same path and UTM fields plus the stored score band and qualified flag, when a score was completed. Product views are counted at most once in a browser session for each recipient tag and qualification state, so a session can contribute at most one unqualified and one qualified product view for that tag. A checkout start means the visitor opened the purchase form; it is not a payment attempt. The event table does not store names, email addresses, billing details, free-score answers, cookies, device identifiers, or IP addresses.

Incoming UTM values use first-touch storage within the browser session, so later links do not overwrite an existing source, medium, campaign, recipient tag, or term. The attribution and score result can accompany later events and, if an order is started, the order record. Session storage is cleared by the browser when that browsing session ends. Checkout access tokens are held only in page memory and removed from the address bar; they are not stored in local or session storage. VerifyMade does not use third-party analytics. Hosting and security providers may still process ordinary technical request information, including IP addresses, in their own short-lived infrastructure or security logs.

Security rate limiting

To slow automated abuse of sensitive endpoints, VerifyMade derives a short keyed hash from the requesting IP address. The raw address is not stored in the application database, the hash cannot be used across days, and rate-limit rows expire within 26 hours. This control is used only for security and is not combined with funnel measurement.

Personalised review intake

Evidence Workflow Review buyers may email a completed Evidence Readiness Workbook and descriptions of their proof-to-delivery process and one order trail with customer details removed. Remove customer names, addresses, contact details, artwork, payment data, government identifiers, and other private order information before sending. VerifyMade uses that material only to prepare and support the purchased review. Review intake and working copies are deleted within 30 days after the 14-day support period ends, unless longer retention is required for a legal dispute or other obligation.

Shopify app

When a merchant connects a Shopify store, VerifyMade receives the shop domain and display name, Shopify shop, order, line-item, and fulfilment identifiers, order number, timestamps, item title, variant, SKU, quantity, the names of customisation fields (not their values), proof-required and evidence-status classifications, fulfilment status, carrier, tracking references, granted scopes, installation status, and webhook-processing metadata. VerifyMade does not ingest customer names, email addresses, phone numbers, postal addresses, payment details, message contents, or customisation values from Shopify.

A merchant may deliberately upload a PDF, PNG, or JPEG proof to a proof-required order. VerifyMade first places the file in private quarantine, enforces a 10 MB limit, checks that the file bytes match the declared format, and sends the file bytes over an authenticated encrypted connection to a VerifyMade-operated scanner using the open-source ClamAV engine. The scanner processes the bytes transiently and does not retain the file. A file becomes a permanent proof version only after the scanner returns an unambiguous clean result. Blocked files are deleted and never receive an approval link. If the scanner is unavailable, its malware definitions are stale, or it returns an unclear result, the file stays private and unavailable during a retry window of no more than 15 minutes. A five-minute cleanup sweep deletes uncleared quarantine files after that window. VerifyMade records the filename, media type, byte size, SHA-256 digest, scan state and fixed diagnostic code, scan attempts and timestamps. Clean proof records also include a version number and private approval-link status. The customer-facing link records only approve or request changes, without asking for the customer's name, email address, comment, or other identity. Merchants are instructed to remove customer names, contact details, and unrelated private order information before upload. Each new clean proof version supersedes the previous pending approval link; expired and superseded links cannot retrieve a proof. When the merchant releases an approved version to production, VerifyMade records the order, proof and approval identifiers, version number, filename, SHA-256 digest, release status and timestamp. This release record contains no additional customer information.

After release, the merchant may deliberately upload PNG or JPEG images of the finished item and packed parcel. VerifyMade applies the same private-quarantine, size, actual-format and malware-scanning process. Only clean images become permanent records tied to that release together with their evidence category, sequence number, filename, media type, byte size, SHA-256 digest and timestamp. Merchants are instructed to remove names, addresses, shipping labels and unrelated private information before upload.

VerifyMade keeps a per-store counter for proof and production-evidence upload attempts during a rolling one-hour window so abusive or accidental bursts can be limited. The counter contains the store domain, upload category, count and timestamps; it does not contain an IP address, device identifier or uploaded file contents. Expired counters are deleted after two hours.

To diagnose upload problems, VerifyMade also records the store domain, upload category, one fixed outcome code, one fixed reason code and a timestamp. The operator dashboard shows only aggregate seven-day counts. These diagnostics do not contain an order identifier, filename, file type, file size, file hash, file contents, protected link, IP address, device identifier, customer information or scanner response body. Upload diagnostics, processed webhook records, and blocked or expired scan metadata are deleted after 30 days.

After both evidence categories are complete, an authenticated merchant may generate a private evidence-dossier PDF containing the existing order, proof, approval, release, evidence-fingerprint and fulfilment metadata. The dossier is assembled on demand and is not stored by VerifyMade. VerifyMade records the shop and order association, dossier fingerprint, dossier-format version and generation time so the merchant can review export history and compare a previous export with the current order trail. This export record adds no customer identity or customisation values.

This limited information is used to import and classify eligible orders, display the merchant's evidence queue, quarantine and scan merchant uploads, preserve clean proof and production-evidence files, record the decision on an exact version, bind the production release and post-production evidence to that approved version, synchronise fulfilment status, verify dossier history, operate and secure the connection, and respond to Shopify privacy requests. Clean proof and production-evidence records remain available to the connected merchant until the relevant order or shop is redacted, the merchant asks for deletion, or the shop has been uninstalled for 48 hours. Shopify access and refresh tokens are encrypted at rest and isolated by shop. Uninstalling immediately disables the stored credentials; if Shopify's shop-redaction webhook has not already removed the app data, the retention sweep removes it 48 hours after uninstall. Shopify's mandatory customer-data request, customer-redaction, and shop-redaction webhooks are supported: customer redaction removes records, dossier-export history, quarantined files and private evidence files for the specified order identifiers, and shop redaction removes the connected shop's app records, dossier-export history, upload-rate counters, upload diagnostics, quarantined files and private evidence files. A merchant may also ask VerifyMade to disconnect or delete app data by emailing support@verifymade.com.

Shopify order-status write-back

When an approved proof is released to production, VerifyMade uses the write_orders permission to set one app-reserved metafield on that Shopify order. The metafield contains only the VerifyMade release state, approved proof version number, internal release-record reference and release timestamp. VerifyMade does not write proof hashes, production-file hashes, filenames, customer information, payment information, line-item changes or fulfilment changes to Shopify. If write-back fails, the internal VerifyMade release remains valid and the merchant can reconnect or retry.

Local production-file fingerprints

Before a new production release is recorded, the merchant may select the exact DST, EMB or EXP machine file on their device. The browser calculates its SHA-256 fingerprint locally. VerifyMade does not receive, upload, scan or store the machine-file contents. It receives and retains only the filename, format, byte size and SHA-256 fingerprint, tied to the approved proof and release record. Merchants should use a filename that contains no customer name, email address or other private information.

What not to send

Do not email customer names, addresses, order screenshots containing personal data, artwork proofs, raw approval messages, payment-card details, government identifiers, or other private order data. VerifyMade does not need that information to deliver the review, answer a product question, or assess a voluntary refund request.

Service providers and international processing

Website hosting, structured purchase records, and private file storage are provided through OpenAI Sites and its infrastructure providers. Shopify processes connected-store information, app subscription billing, authorised Admin API data and webhooks under its own terms and privacy notice. VerifyMade operates its open-source ClamAV scanning service and uses Tailscale's encrypted relay to carry merchant-uploaded file bytes to that scanner; the scanner processes the bytes transiently and does not retain them. VerifyMade does not send customer identity fields with the scan. Razorpay or PayPal processes checkout and payment information for the Starter Kit and Workflow Review under its own terms and privacy notice. Razorpay's and PayPal's checkout scripts load only after you open the purchase form, and are governed by their own privacy notices. The transactional-email provider processes buyer email, fulfilment messages, invoices, and credit notes. These providers may process information in countries other than your own.

Retention and requests

Purchase, invoice, credit-note, refund, and reconciliation records may be retained for the period required by applicable accounting, tax, fraud-prevention, and legal obligations. Other correspondence is retained only as long as reasonably needed. To request access, correction, or deletion where applicable, email support@verifymade.com. Records required by law cannot be deleted on request.

Changes

This notice will be updated before adding third-party analytics, newsletters, customer accounts, broader Shopify data access, or other material new data practices.