Bondmark Supply Co.
Effective Date: August 15, 2026
Last Updated: August 15, 2026
This draft reflects the current Bondmark platform data flows: Supabase, Stripe, Printify, transactional email, client uploads, invoices, storefront orders, support, documents, royalties, and payout preparation.
Bondmark stores payment and invoice metadata, not full card numbers or raw bank account details in its own database.
This Privacy Policy explains how Bondmark handles information across its public website, client storefronts, cart and checkout flow, client portal, onboarding forms, design approval tools, admin workflows, support requests, document center, royalty and payout preparation, invoice pages, and related services.
Bondmark may collect identity and contact information, business information, account and authentication records, client onboarding details, logos, artwork, brand guidelines, trademarks, design files, design feedback, approval records, invoice information, order information, product and variant information, shipping information, transaction metadata, royalty information, payout-account status, support communications, and technical logs.
Client portal access uses Supabase Auth. Bondmark stores client memberships, roles, and account-scoped records so users only access records tied to their client account.
Clients may upload or submit logos, artwork, guidelines, reference files, slogans, trademarks, and other brand materials. These files are used to provide onboarding, design, mockup, production, storefront, document, and support services.
For merchandise storefront purchases, Bondmark stores order, item, customer, shipping, fulfillment, Printify routing, and royalty data needed to process orders, coordinate production, support customers, and maintain historical records.
Stripe processes merchandise checkout payments and Bondmark business invoices. Bondmark stores payment metadata such as Stripe object IDs, invoice status, amounts, timestamps, hosted invoice URLs, and refund or credit history. Bondmark does not store full card numbers in its own database.
Bondmark stores royalty ledger entries, payout review records, payout-account status, Stripe Connect account identifiers, and payout workflow metadata. Bondmark forms do not collect raw bank account or routing numbers.
Support requests may include category, subject, description, optional order references, status, resolution notes, and related transactional email logs. Bondmark sends transactional communications about accounts, orders, invoices, design approvals, support, documents, and platform administration.
Bondmark may process IP address, request headers, device/browser information, authentication cookies, route activity needed for security, and server logs. The cart uses browser storage for device-local cart state. The current codebase does not add advertising trackers as part of this policy.
Bondmark uses information to provide services, create client accounts, onboard businesses, create merchandise, manage design approvals, operate storefronts, process transactions, produce and fulfill merchandise, ship orders, send transactional communications, manage invoices, calculate royalties, facilitate payout workflows, provide support, prevent fraud, secure the platform, administer operations, comply with legal obligations, and improve the service.
Bondmark may share information with service providers when needed to operate the platform, including Supabase for database/auth/storage, Stripe for payments and invoicing, Printify and fulfillment providers for production and order routing, hosting infrastructure providers, and transactional email providers such as Resend when configured.
Bondmark may disclose information when necessary to comply with law, enforce agreements, protect rights or safety, investigate misuse, respond to disputes, support accounting/tax obligations, or complete a business transition.
Bondmark keeps information for as long as reasonably needed for the account, client engagement, order history, invoice and accounting records, fulfillment, royalty reporting, fraud/security needs, legal obligations, disputes, backups, and legitimate business administration.
Bondmark uses reasonable administrative, technical, and organizational safeguards, including server-side authorization, row-level security for tenant-owned records, private storage buckets for client files, signed webhook verification, and provider-managed payment handling. No internet service can be guaranteed to be completely secure.
Depending on your jurisdiction, you may have rights to request access, correction, deletion, portability, or limits on certain uses of personal information. Requests may be submitted through hello@bondmarksupply.com. Bondmark will evaluate requests according to applicable law and operational/legal retention requirements.
Bondmark's services are not directed to children under 13, and Bondmark does not knowingly seek to collect personal information from children under 13.
Bondmark and its providers may process information in locations where they operate. Provider processing is governed by their infrastructure, security, and legal obligations.
Bondmark may update this Privacy Policy as the platform, providers, or legal requirements change. The effective and last updated dates identify this version.
Privacy questions or requests may be sent through hello@bondmarksupply.com. Bondmark's exact legal entity name, mailing address, and dedicated privacy contact should be confirmed before final public launch.
See also: Terms of Service, Returns, and Shipping.
