Security overview
Bidson checks access to Shopify and the connected CRM. Application data is kept separate for each store.
Automatic messages from Shopify, called webhooks, are verified before processing. Background tasks are designed so that receiving the same message more than once does not create duplicate tasks or CRM records.
Data protection
CRM Sync reads the customer details and selected business information needed for synchronization. Optional groups include order summaries, customer tags, marketing status, customer history and language, and country, region and city.
Complete Shopify customer, order and webhook data packages are not intentionally stored as synchronization data. The database keeps technical IDs, task status and limited audit information needed to operate the service, check synchronization and delete data safely.
Connections and credentials
Each CRM connection uses a supported method, such as approving access through OAuth or entering an API key. Shopify access details and CRM credentials are encrypted before database storage and linked to the correct store and connection. They are used only for the requested integration.
Disconnecting or uninstalling removes access for normal synchronization. Credentials needed for an outstanding privacy obligation are kept separate and used only to fulfil that obligation.
Infrastructure and availability
CRM Sync handles web traffic and background tasks separately. PostgreSQL stores queued tasks and synchronization progress. The production database has daily, weekly and monthly backups, and can be restored to a specific point in time.
After a restore, recovery tools can pause normal tasks, check connections and compare data with the current Shopify state before processing resumes. These controls improve recovery but do not guarantee availability, how much data could be lost (RPO), or how long recovery takes (RTO).
Reliability and monitoring
Bidson limits how many tasks run at once and uses temporary locks and duplicate checks to avoid conflicting or repeated updates. It checks current data and retries in a controlled way. Shopify and CRM limits on API requests are respected. Temporary failures are retried later.
The app records whether background processes are working, queue delays and error types. Logs do not contain customer data packages or access tokens.
Access and operational security
Access keys and production settings are kept outside source code. Two-factor authentication is enabled for the current Railway project member. App logs use only approved technical fields and support IDs that do not contain personal data.
Code changes are checked with automated code analysis, type checks, tests, builds and security tests relevant to the change. Infrastructure access and account permissions are reviewed separately.
Incident response
Bidson maintains a documented process to investigate, contain and recover from suspected security or personal-data incidents. It covers credential rotation, evidence preservation, impact assessment, required notifications and post-incident improvements. No fixed response-time commitment is made here.
Vendors and subprocessors
Bidson documents service providers appointed to process personal data. Shopify and the merchant-selected CRM are also part of the data flow, but are services selected and contracted by the merchant for the requested synchronization.