Security at StoreCopy

How we protect your store while we move it

To migrate a store or a CRM, you give StoreCopy access to it. This page explains what we do with that access, how we store it, and what our software will and will not do to your data.

Last reviewed , against the code that runs in production.

The short version

Seven things to know

Store access
OAuth wherever the platform offers it, so we never see your password. Every token and API key is encrypted with AES-256-GCM before it is saved.
Your migration
Only your signed-in store session, or a key issued to your browser, can start, read or cancel it. A pairing code alone is not enough.
Your records
We read from the source and create in the destination. A record your store already had is never overwritten or deleted.
Traffic
HTTPS everywhere, behind Cloudflare. Our servers accept no direct connections from the internet.
Payments
Handled by Paddle or by Shopify billing. Full card numbers never reach our servers.
Location
Our own servers in Spain, inside the European Economic Area.
Retention
Migration data is kept for up to 6 months after the migration ends. You can ask us to delete it sooner.

Store access

The access you give us

For Shopify, Wix, Square, Squarespace, HubSpot, Salesforce, QuickBooks and other platforms with an app install, you approve StoreCopy on the platform's own screen. We receive a token limited to the permissions shown there, and you can revoke it from your platform at any time. For platforms that work with an API key, such as WooCommerce, Freshsales or ActiveCampaign, you paste a key you created and can delete.

  1. 1

    You approve

    On the platform's own consent screen or with a key you created.

  2. 2

    We encrypt

    AES-256-GCM, with a fresh random nonce for every value.

  3. 3

    We store

    Only the encrypted form is written to the database.

  4. 4

    We use

    Decrypted in memory, only to call your store during your migration.

  5. 5

    You revoke

    Uninstall the app or delete the key and the access ends.

  • Authenticated encryption. AES-256-GCM detects any change to a stored value, so a tampered token fails to decrypt instead of being used. The key is derived with PBKDF2-HMAC-SHA256.
  • Keys kept apart from data. The encryption key and every other secret live in a secrets vault and are handed to the running service only. They are not in our source code or in the database they protect.
  • Short-lived tokens. Our Shopify apps use access tokens that expire after one hour and are renewed automatically. Squarespace, Salesforce, QuickBooks and Cafe24 tokens rotate on every refresh, and we save each new one at once.

Who can act on your migration

A migration connects two stores with a pairing code. That code appears in install links and redirects, so we treat it as an address, never as proof of who you are. Every action on a migration, such as starting it, reading its progress or disconnecting a store, needs one of these:

  • A Shopify session signed by Shopify for a store in that pairing.
  • A Wix app instance signed by Wix for a store in that pairing.
  • A pairing key that our server issued to the browser that created the pairing.

A request without one of them is refused. During an app install, the state value that travels through the platform and back is signed and carries a one-time random value, so a forged or replayed callback cannot attach a store to someone else's migration or replace a store that is already connected.

What a migration does to your stores

Security also means your live store is the same after we are done, plus the records you asked for.

  • The source is read only. We list and read your products, customers, orders and CRM records. We do not edit or delete them.
  • Existing records stay as they are. If the destination already has a customer with that email or a product with that SKU, we link to it unchanged. We do not update it.
  • A demo can be undone. The demo rollback removes the records the demo created and nothing else. Records it linked to stay in place.
  • No surprise emails. Imported orders and customers are created with notifications switched off wherever the platform allows it. Where a platform always sends one, the wizard tells you before you start.
  • Store addresses are checked. A store URL you enter must be a public address, and we check it again each time we connect. This keeps anyone from pointing our servers at a private network.

Your StoreCopy account

  • Three ways to sign in. Google, a password, or a 6-digit code sent to your email. A code works for 10 minutes and for 5 attempts, and we store only its hash.
  • Rate limits. Sign-in and code requests are limited per address.
  • Password reset. A reset signs out every other session of that account.
  • Verified linking. Google sign-in joins an existing account only when Google confirms the email address. A password that someone set on an address they never proved is removed first, so nobody can register your email ahead of you and keep access.

Network and infrastructure

  • No open doors. Our servers connect out to Cloudflare through a tunnel. They have no public IP address that accepts requests, so everything arrives through Cloudflare over HTTPS.
  • Browser protections. We send HSTS so browsers use HTTPS only, block content-type sniffing, and forbid other sites from framing our sign-in and app pages.
  • Rate limits at the edge for pages and API calls.
  • Signed webhooks only. Shopify webhooks are verified with HMAC-SHA256 and Paddle webhooks with Paddle's signature. A payment is marked paid only after Paddle's own API confirms the transaction.
  • A separate staging environment with its own database schema and test stores. We test there, never on customer stores.
  • Operator endpoints need an operator password, and error responses carry a reference ID instead of internal details.

How we keep it that way

  • OWASP Top 10 review. In November 2026 we reviewed the product against the OWASP Top 10 and fixed what we found. That work included moving every stored token to AES-256-GCM and requiring proof of ownership on every migration action.
  • Observe, then enforce. New security checks first log what they would refuse. We switch them to enforce once real traffic shows that no legitimate request is blocked.
  • Safe by construction. Database queries are parameterised, and secrets are compared in constant time.
  • Tested routes. Every migration route has automated tests that run before a release.

Privacy and deletion

StoreCopy's servers and databases are in Spain. We keep migration data, meaning record content, ID mappings and task logs, for up to 6 months after a migration ends so we can support it, and you can ask us to delete it earlier.

We honor Shopify's privacy requests: customer data export, customer deletion and shop deletion, each accepted only with a valid Shopify signature. Uninstalling the app starts the cleanup for that shop. The full list of providers that process data for us is in our privacy policy and on the GDPR compliance page.

What we do not claim

StoreCopy is a small company. We do not hold a SOC 2 or ISO 27001 certificate today. What this page describes is how the product is built and run, and we are glad to answer a security questionnaire for your team.

Report a vulnerability

Found a security problem? Tell us.

Write to [email protected]. A person reads every report and we answer each one.

Email us

Works with 37 platforms

  • Shopify
  • Wix
  • WooCommerce
  • Magento
  • PrestaShop
  • Squarespace
  • Square Online
  • Odoo
  • Shopware
  • GoDaddy
  • OpenCart
  • Tiendanube
  • Medusa
  • Bagisto
  • Vendure
  • Saleor
  • Spree
  • Sylius
  • Swell
  • BigCommerce
  • Gumroad
  • Payhip
  • Cafe24
  • Color Me Shop
  • BASE
  • Webflow
  • YouCan
  • ikas
  • SHOPLINE
  • HubSpot
  • Pipedrive
  • Zoho CRM
  • ActiveCampaign
  • Salesforce
  • ERPNext
  • Freshsales
  • QuickBooks