Trust & data security
How BrandBinder protects brand and dealer data.
BrandBinder hosts dealer-ready product, pricing, asset, access, and communication workflows for brand teams. This page summarizes the operational safeguards, backup posture, app-device behavior, and compliance support available today.
Short version: brands own their workspace data, dealers keep control of claimed profile data, and access is permissioned, logged, and revocable.
Data we host
BrandBinder may store workspace settings, staff users, dealer companies and contacts, addresses, product catalogs, pricing, hosted files, published pages, feed settings, form submissions, campaign activity, app pairing records, support requests, and application logs needed to operate the service.
Access controls
Brand teams control which staff, reps, dealers, and app-paired devices can see workspace resources. Dealer and rep access can be narrowed or revoked from the web workspace, and app pairings use scoped device tokens rather than a shared password.
Encryption and transport
BrandBinder uses HTTPS/TLS for browser, portal, and app traffic. Production storage controls are reviewed before stronger storage-security claims are published; we do not market zero-knowledge or end-to-end encryption because the service needs to preview, index, publish, and route authorized content.
Backups and recovery
We maintain operational backups and release-artifact backups for service recovery. Backup coverage, off-site mirrors, and restore evidence are tracked internally, but customers should keep original source files outside BrandBinder because hosted assets are a distribution library, not a self-serve archive or disaster-recovery product.
Mac and iPhone apps
Approved Mac and iPhone apps may cache selected resources locally for faster access or offline use. Revoking an app pairing stops future access through BrandBinder, but files intentionally downloaded, exported, shared, or copied outside the app may remain on that device or in that user's storage.
Data location
Unless a customer agreement says otherwise, BrandBinder uses its standard production hosting environment. EU or dedicated-region hosting is not currently a self-serve feature; customers with data-residency requirements should discuss them during setup so the right agreement and deployment plan can be confirmed.
GDPR and international transfers
For customer workspace data, BrandBinder generally acts as a service provider or processor under the customer's instructions. Data Processing Addendum terms, appropriate transfer safeguards, and reasonable GDPR support are available for eligible customers by request.
Subprocessors and vendors
BrandBinder may use infrastructure, email, payment, analytics, support, storage, and app-distribution providers as needed to operate the service. A current subprocessor list can be provided during contracting or security review, and material vendor changes can be handled according to the applicable agreement.
Retention, deletion, and export
Workspace data is retained while an account is active and for a reasonable operational period afterward. Export, deletion, and account-close requests are handled according to the applicable customer agreement, legal obligations, backup-retention windows, and abuse-prevention needs.
Security contact
Security, privacy, and data-processing questions can be raised through BrandBinder support or during onboarding. We prioritize reports involving unauthorized access, exposed data, suspicious login activity, and incorrect dealer or file permissions.