Prefer Prepaid — Privacy Policy & Data Disclosure
Last Updated: August 2026
1. Title / Introduction
Prefer Prepaid ("the Application", "we", "us", or "our") is operated by Brainfoods Studio ("Brainfoods"). Prefer Prepaid is an embedded Shopify application designed to help Shopify merchants evaluate Cash on Delivery (COD) Return-to-Origin (RTO) risk and optimize checkout payment-method presentation.
Checkout adjustments are executed natively within Shopify checkout using deterministic Shopify Payment Customization Functions. The Application operates exclusively within the boundary of each merchant store using merchant-scoped order evidence.
2. Scope of This Policy
This Privacy Policy and Data Disclosure applies to:
- Shopify merchants who install, configure, or use the Prefer Prepaid application.
- Order, delivery, and payment metadata processed through merchant stores when Prefer Prepaid is installed.
- Prefer Prepaid application compute, storage, and synchronization infrastructure.
Prefer Prepaid processes order and checkout data on behalf of merchants to provide the application functionality described in this policy. Merchants remain responsible for maintaining their own storefront privacy disclosures and fulfilling their direct obligations to end customers. Shopify maintains its own independent platform privacy practices governing merchant and customer accounts.
3. Data We Process
Prefer Prepaid adheres strictly to data minimization principles. The Application accesses and stores only the discrete data points necessary to calculate empirical RTO risk, compile checkout rules, and present operational reports.
A. Order Data
When orders are placed, updated, or fulfilled on a merchant's store, the Application processes:
- Shopify Order Identifier: Unique numeric order identifier assigned by Shopify.
- Order Timestamps: Creation and update timestamps for order lifecycle sequencing.
- Financial Values: Order total value and currency code.
- Fulfillment & Financial Status: Status transitions used to determine delivery outcomes.
- Payment Gateway Names: Payment method names (e.g. "Cash on Delivery") to identify payment type.
- COD Classification: Binary indicator identifying whether an order was placed via Cash on Delivery.
- Delivery Outcome State: Discrete outcome category (
pending,delivered,rto,cancelled, orreturned). - Manual Outcome Overrides: Outcome statuses recorded by authenticated merchant administrators via the administrative interface.
Purpose: Used as canonical evidence for empirical RTO rate calculation, decision snapshot verification, and merchant analytics.
B. Geographic Data
- Destination Country Code: Two-letter ISO country code (e.g.,
IN). - Destination Postal / ZIP Code: Destination postal code (e.g., PIN or ZIP).
address1, address2), apartment/suite numbers, and recipient contact names are discarded in transient memory immediately upon webhook receipt and are never written to database tables, persistent storage, or application logs.C. Customer Identity Data
- Registered Shopify Customers: Identified using the persistent Shopify Customer ID (
shopify_customer_id) as a merchant-local reference. - Guest Customers: For guest orders, email or phone may be processed briefly in memory to create a one-way, merchant-scoped HMAC-SHA256 identifier. The raw email address or phone number is not stored by Prefer Prepaid.
Guest identifiers are derived by combining the merchant store identifier with the normalized contact string before computing a cryptographic hash. The resulting hash cannot be reversed to reveal contact information, nor can it be linked across different merchant stores.
D. Data We Do Not Request or Store
- No customer directory access scopes (
read_customers,write_customersare omitted). - No historical archive access scopes (
read_all_ordersis omitted). - No cross-merchant customer identity matching or pooling.
- No raw full street address persistence.
- No customer passwords, credit card numbers, CVVs, or payment card credentials (payment transactions are processed entirely by Shopify or merchant-selected payment gateways).
- No storage of Shopify merchant access tokens outside the standard, isolated session storage mechanism.
4. Purposes of Processing
All data processing is strictly purpose-limited to the following merchant-scoped operational objectives:
- COD / RTO Risk Estimation: Calculating empirical Bayesian risk estimates from historical delivery and RTO rates.
- Merchant-Specific Evidence Aggregation: Aggregating order and RTO counts per merchant-scoped postal region and customer reference.
- Payment Customization Policy Compilation: Compiling compact, deterministic policy metafields for Shopify checkout.
- Shopify Function Execution: Evaluating compiled policy rules at checkout to reorder or restrict payment methods.
- Shadow-Mode Evaluation: Generating observational evaluation metrics to assess policy impact prior to live checkout enforcement.
- Merchant Analytics & Reporting: Providing embedded dashboard charts displaying outcome mixes, regional RTO rates, and decision histories.
- Compliance & Privacy Fulfillment: Managing statutory data access, data export, and customer redaction requests.
- Security, Auditing, & Integrity: Maintaining metadata-only access audit logs and executing automated data retention purges.
5. Automated Decision-Making & Payment Customization
Prefer Prepaid generates deterministic recommendations to help merchants manage Cash on Delivery shipping losses. Based on merchant-configured economic thresholds and empirical evidence, recommendations may include:
ALLOW_COD: Present COD normally (default fail-open behavior).PREFER_COD: Move COD to the top of the payment method list.PREFER_PREPAID: Reorder payment methods to highlight prepaid options while keeping COD accessible.RESTRICT_COD: Hide Cash on Delivery for high-risk delivery regions with sufficient evidence.BLOCK_COD: Restrict COD exclusively when matching an explicit merchant-configured manual blocklist.
These recommendations are compiled into compact policy metafields and executed by a Shopify Payment Customization Function running in Shopify's WebAssembly sandbox. The Function executes deterministically in real time, makes zero external network requests, and introduces zero third-party network latency.
Payment-method presentation and availability may be adjusted based on merchant-configured rules and merchant-specific order evidence. This functionality does not constitute credit scoring, creditworthiness assessment, or fraud detection.
6. Shadow Mode & Observational Analytics
When a merchant installs Prefer Prepaid or configures shadow mode, the Application evaluates risk and logs recommendations without modifying the checkout payment method presentation.
Analytics reports generated in shadow mode are strictly observational. They compare actual order outcomes against model recommendations to evaluate calibration. Prefer Prepaid makes no causal return-on-investment (ROI) or savings guarantees from shadow-mode observational data.
7. Data Storage & Infrastructure
Application data is stored in isolated PostgreSQL infrastructure hosted by Supabase. Stored data and backups are encrypted at rest, and data in transit is protected using encrypted TLS connections.
- Environment Separation: Production and development environments are strictly separated across dedicated database instances and configuration environments.
- Secret Isolation: Production credentials and encryption keys are injected via environment variables and are never committed to source control.
- No Production Data in Development: Production order and customer data is never copied to or stored in test or development environments.
8. Subprocessors & Service Providers
Prefer Prepaid engages trusted service providers to deliver hosting, database storage, and runtime capabilities. Each provider processes data solely to deliver the specified infrastructure function:
| Provider | High-Level Purpose | Data Processed |
|---|---|---|
| Shopify Inc. | Merchant e-commerce platform, webhook delivery, and checkout Function runtime | Order lifecycle events, delivery addresses, compiled policy metafields |
| Supabase Inc. | Managed PostgreSQL database hosting and persistent storage | Order events, aggregate statistics, configuration settings, access audit logs |
| Vercel Inc. | Application serverless hosting and HTTPS delivery | Admin interface delivery, webhook ingestion, API routing |
| Cloudflare Inc. | DNS routing and edge network infrastructure | Encrypted network traffic routing |
We may replace infrastructure providers with functionally equivalent providers while maintaining appropriate data-protection and security controls.
9. Data Retention & Disposal Schedule
Prefer Prepaid operates a formal, automated data retention schedule. Records are purged automatically upon reaching their approved maximum age:
| Data Category | Retention Horizon | Automated Disposal / Purge Mechanism |
|---|---|---|
| Completed Webhook Payloads | 0 days (Immediate) | Raw webhook payloads are sanitized to immediately upon domain transaction commit. |
| Failed Dead-Letter Payloads | 7 days (168 hours) | Payload bodies are scrubbed to after 7 days; operational metadata is preserved. |
| Webhook Job Metadata | 30 days | Completed job metadata records are permanently purged after 30 days. |
| Order Events (Canonical Ledger) | 730 days (24 months) | Aged order records are permanently deleted by automated daily purge routines. |
| Customer Evidence Aggregates | Active installation duration | Derived statistical counts retained while the app remains installed; deleted on customer or shop redaction. |
| Postal Region Evidence Aggregates | Effective 730-day horizon | Derived directly from retained canonical Order Events; recomputed upon source data deletion to eliminate stale contributions. |
| Order Decisions Ledger | 365 days (12 months) | Immutable decision snapshots are permanently purged after 12 months. |
| Access Audit Logs | 90 days | Metadata-only audit records are permanently purged after 90 days. |
| Compliance Requests | 365 days (12 months) | Durable GDPR audit records are purged after the statutory verification period. |
| Shop & ShopSettings | Active installation duration | Retained while installed; permanently deleted upon receiving Shopify's mandatory shop/redact webhook. |
Derived Cache Integrity: Customer and postal aggregates are derived caches. When source order events are purged by the retention engine or deleted due to customer erasure, derived aggregates are automatically recomputed from the remaining canonical events so stale historical contributions are not retained.
10. Data Deletion & Shopify Privacy Webhooks
Prefer Prepaid implements automated, database-level handlers for all mandatory Shopify privacy webhooks:
- 1. Customer Data Request (
customers/data_request): When a merchant receives a statutory access request, Prefer Prepaid generates an on-demand export package containing matching order records, decision snapshots, and customer statistical profiles for authorized merchant fulfillment. - 2. Customer Redaction (
customers/redact): When a customer requests erasure, Prefer Prepaid permanently deletes all matching customer profiles, order event records, and decision snapshots. Affected postal aggregate statistics are dynamically recomputed to remove the erased customer's orders. Raw contact details are not available because they were never persisted. - 3. Shop Redaction (
shop/redact): When an uninstalled shop reaches Shopify's uninstall redaction lifecycle, Prefer Prepaid permanently deletes the merchant shop record, settings, historical ledger, decisions, evidence aggregates, compliance logs, and access audit records from Prefer Prepaid's application records.
11. Security Controls & Governance
Prefer Prepaid implements layered technical and operational safeguards:
- Tenant Isolation: Every database query enforces strict multi-tenant scoping by
shop_idwith foreign-key cascade protections. - Least-Privilege Access: Administrative access to cloud hosting, database instances, and repository settings is restricted to authorized personnel based on operational necessity.
- Mandatory Multi-Factor Authentication (MFA): MFA is strictly enforced across all administrative accounts, including GitHub, Supabase, Vercel, and Shopify Partner Dashboard.
- Secret Management: Credentials, HMAC keys, and database connection strings are stored as encrypted environment variables and never committed to source code repositories.
- Payload Sanitization: Incoming webhook payloads are stripped to empty objects immediately upon domain processing.
- Incident Response: Formalized detection, containment, credential rotation, and notification procedures are maintained in our incident response protocols.
12. Access Auditing
To protect merchant and customer data integrity, sensitive administrative access to customer-linked pages (such as customer detail views, compliance export downloads, and manual outcome adjustments) is recorded in an immutable, metadata-only access audit log.
Audit log entries record the merchant context, actor type, action category, resource type, timestamp, correlation identifier, and success/failure status. Audit records intentionally exclude raw contact information, customer hashes, tokens, and stack traces. Audit logs are retained for a rolling 90-day period.
13. Merchant Responsibilities
Merchants installing Prefer Prepaid are responsible for:
- Using the Application in compliance with all applicable local laws, consumer protection regulations, and e-commerce rules.
- Providing clear and accurate storefront privacy notices informing buyers about checkout payment options and delivery policies.
- Configuring risk thresholds, economic values, and manual blocklist rules in alignment with their business practices.
- Responding to direct consumer privacy inquiries and initiating data erasure requests where required.
14. Customer & Merchant Rights
Depending on jurisdiction, individuals whose data is processed may have statutory rights under privacy regulations (such as GDPR, CCPA, or applicable data protection laws), including:
- The right to access and receive an export of personal data.
- The right to request erasure / deletion of personal data.
- The right to rectify inaccurate records.
- The right to object to or restrict specific processing activities.
Rights vary by jurisdiction. End customers should submit data requests directly to the merchant whose store they purchased from. Prefer Prepaid fully supports merchant fulfillment via Shopify's mandatory privacy webhook APIs.
15. International Data Processing
Prefer Prepaid and its subprocessors may process data on cloud infrastructure located in regions different from the merchant or customer location. We rely on provider contractual safeguards, access controls, and encryption standards appropriate to the services used.
16. Children's Data
Prefer Prepaid is a business-to-business merchant application designed exclusively for commercial store operators. The Application does not knowingly solicit or collect data directly from children.
17. Changes to This Policy
We may update this Privacy Policy and Data Disclosure periodically to reflect changes in application functionality, infrastructure, or regulatory requirements. Material revisions will be reflected by updating the "Last Updated" date at the top of this document. Merchants are encouraged to review this policy periodically.
18. Contact Information
For privacy or data-protection questions, contact:
Application: Prefer Prepaid
Operator: Brainfoods Studio / Brainfoods
Location: India
Privacy Inquiries: privacy@brainfoods.in