Merchant Data Processing Terms

Version 2026-10-08.1 · Effective for each business upon its owner’s explicit acceptance.

1. Parties and effectiveness

These terms supplement the MakerBudget Terms of Service between the merchant identified in the selected MakerBudget business and the service operator identified in those Terms. Contact: support@makerbudget.com. The merchant is the controller of connected-store customer information and MakerBudget acts as its processor. These terms take effect for that business when its authorized owner explicitly accepts this version. Publication, signing in, testing, or authorizing a store connection does not constitute acceptance.

2. Processing instructions and scope

MakerBudget reads, stores, organizes and displays authorized store records for order tracking, product and inventory management, cost reconciliation and financial reporting. Processing is limited to the service, the merchant's authorized settings and verified written instructions. Subjects are customers whose purchases appear in the authorized records. Categories include store and order identifiers, purchased products, quantities, dates, amounts, refunds, recorded fees, fulfillment status and merchant-entered notes. Shopify privacy notices may also contain customer identifiers and contact information needed to resolve a request. Routine Shopify product/order queries do not request customer names, email addresses, telephone numbers or postal addresses. Payment-card credentials and special-category personal data must not be entered into the workspace.

MakerBudget will not sell these data, use them for unrelated advertising, or train general-purpose AI models with them. If an instruction appears to breach applicable data-protection law, MakerBudget will inform the merchant and suspend the affected operation while resolving it. Legally required processing will be disclosed where permitted.

3. Confidentiality, security and assistance

Access is limited to authorized personnel performing necessary duties under confidentiality obligations. Controls include encrypted transport, provider-managed storage encryption, encrypted integration credentials and privacy-request payloads, authenticated server-side business membership and permission checks, database row-level isolation, restricted service roles, and protection against replaying erased records after restoration. A dedicated sample-data review account is separate from ordinary customer access. MakerBudget will provide information reasonably necessary for security assessments and assist with rights requests, impact assessments and regulator inquiries. Confirmed breaches affecting merchant data will be reported without undue delay with available details and subsequent updates. This provision does not claim certification or guarantee uninterrupted service.

4. Subprocessors and international processing

For the current Shopify service, the merchant authorizes Cloudflare, Inc. for application delivery, request processing and secure database connectivity, and Supabase Pte. Ltd. for PostgreSQL storage, authentication and managed backups. The production database region is Paris, France (eu-west-3). Cloudflare operates a global network; an EU-only processing boundary is not represented. Applicable provider data-processing terms and transfer mechanisms, including standard contractual clauses where required, govern their processing. MakerBudget remains responsible for its obligations and for requiring appropriate duties from subprocessors.

Provider terms: https://www.cloudflare.com/cloudflare-customer-dpa/ and https://supabase.com/legal/customer-resources/data-processing-addendum.

Zoho is used for support correspondence, which should contain request references rather than raw customer datasets. Account notification and subscription payment services are described separately in the Privacy Policy. Store-customer exports will not be sent to payment or AI providers. Before adding a subprocessor receiving store-customer data, MakerBudget will notify the merchant at least 30 days in advance, unless an urgent security change requires shorter notice. The merchant may object on reasonable data-protection grounds; the parties will resolve the objection or end the affected processing.

5. Retention, return and erasure

Authorized records remain available while needed to provide the service. On termination, the merchant may request return or deletion, subject to mandatory platform rules and specific legal obligations. Shopify access and erasure requests will be acted on within 30 days of receipt. Removing a local connection does not authorize erasing unrelated shops or unrelated business records. A valid shop-erasure request covers the affected shop, including related history and replay records where required. Data will not be retained merely because it may be useful for future reporting.

For a legal-retention exception, MakerBudget will record the specific obligation, affected categories, restricted purpose and end date; no blanket accounting exemption applies. Temporary delivery copies must be restricted to the verified recipient and removed within 24 hours after delivery or expiry. Fulfillment may be operator-assisted; receipt of a webhook alone is not completion.

The current Supabase Pro database backup window is seven days. Recovery copies are isolated from customer traffic and remain subject to the same erasure obligations; they are not exempt archives. Before restoring service from a backup, the latest erasure restrictions must be reconciled and residual data checked. Erased records must not return to active use. An independently restored project does not automatically expire with the source backup and must be separately reconciled or removed.

Privacy-request payloads must be removed when no longer needed after verified fulfillment, within 30 days of completion unless a specific legal obligation requires retention. Minimal request identifiers, completion evidence and replay-prevention entries may be retained only for their documented compliance or security purpose and reviewed at least annually. They must not include the original customer dataset. Security logs must not intentionally contain customer payloads, credentials or exported records. Operational log retention follows the current provider plan and is reviewed when the plan changes; indefinite copies are not authorized.

6. Rights requests and delivery

MakerBudget will verify the request, shop scope and recipient. Customer access data will be provided directly to the verified store owner through an authenticated or appropriately encrypted channel. Customer identity, records outside supplied order identifiers, linked history, files and recovery copies must be considered. Partial order extracts must be described as partial and cannot be recorded as complete fulfillment. Requests to support@makerbudget.com should identify the business and request reference without sending passwords, API credentials or unnecessary customer information.

7. Accountability

MakerBudget will maintain the accepted version, content digest, business, accepting owner and acceptance time, together with proportionate evidence of request fulfillment. It will support reasonable audits subject to confidentiality, security and protection of other merchants' data. Material changes require a new version and notice; these terms do not waive mandatory rights or platform obligations.