Skip to main content
Product Pricing Migration Legal Support
Start your store

Product

  • Home
  • Pricing
  • Cost sheet
  • See it running

Migration

  • Free dry run
  • Export checklist
  • Shopify notice
  • Who we host

Legal

  • Terms
  • Data processing
  • Acceptable use
  • Hosting policy
  • Privacy
  • PCI

Support

  • Hours & credits
  • Email support

Version 2026-10-01

Data Processing Addendum

How Standfast handles the personal information of a merchant’s shoppers and staff: service-provider terms, the sub-processor list, security measures, breach notice, and the deletion and export schedule.

Last updated 1 October 2026

Legal

  • Terms
  • Data processing
  • Acceptable use
  • Hosting policy
  • Privacy
  • PCI

Key terms at a glance

To notify you after confirming a security incident affecting your data. Section 6
72 hours
Notice before a new sub-processor handles your data. Section 4
30 days
Longest time from termination to deletion from primary storage. Section 7
60 days
Sale or sharing of your customers’ personal information. Section 3
None

A summary for orientation. The numbered sections and schedules below are the addendum.

On this page

  1. 1Parties and roles
  2. 2What is processed
  3. 3CCPA and comparable state service-provider terms
  4. 4Sub-processors and your own vendors
  5. 5GDPR and UK GDPR, where they apply
  6. 6Security incidents and breach notice
  7. 7Offboarding: return and deletion of your data
  8. 8Age-gate data retention
  9. 9Liability
  10. S1Schedule 1 — Details of processing
  11. S2Schedule 2 — Security schedule
On this page 11 sections
  1. 1Parties and roles
  2. 2What is processed
  3. 3CCPA and comparable state service-provider terms
  4. 4Sub-processors and your own vendors
  5. 5GDPR and UK GDPR, where they apply
  6. 6Security incidents and breach notice
  7. 7Offboarding: return and deletion of your data
  8. 8Age-gate data retention
  9. 9Liability
  10. S1Schedule 1 — Details of processing
  11. S2Schedule 2 — Security schedule

This Data Processing Addendum ("DPA") is between Standfast Commerce, Inc. ("Standfast") and the merchant on whose behalf Standfast processes personal information through the Platform ("Merchant"), and applies wherever the Terms of Service apply.

This attaches to, and is incorporated into, the Terms of Service. It makes no statement that the Platform conforms to any law or standard; it states what the Platform actually does and who actually touches your customers' and staff's personal information.

1 Parties and roles

#
  • Merchant is the business (CCPA) or controller (other laws, including GDPR where it applies) for the personal information of its own shoppers and staff.
  • Standfast Commerce, Inc. is Merchant's service provider (CCPA, Cal. Civ. Code § 1798.140(ag)) or processor (other laws, including comparable Colorado, Connecticut, Virginia, Texas, Oregon and GDPR requirements) for that information. This one addendum is drafted to serve those regimes together, since they impose materially the same core duties: purpose limitation, no sale, security, sub-processor flow-down, and deletion on instruction.
  • Shoppers and Merchant's staff are the consumers or data subjects.

2 What is processed

#
Categories of personal information processed on the Platform
CategoryExamples
Customer identity and contactName, email, phone, addresses, marketing consent, tags, notes
Age-gate data, where your catalogue needs itDate of birth entered at the age gate; an age-verification vendor's session id and verdict, where you connect one; the IP address at verification
Orders and paymentsLine items, totals, ship-to, tracking, address- and card-security-code check results, gateway transaction ids, the card's last four digits — never a card number (Schedule 2, item 4)
SubscriptionsPlan, schedule, gateway payment-profile id, the card's type and last four digits (the card itself is vaulted at your gateway), billing attempts
Account securityPassword hashes, session token hashes, login codes, failed-attempt counters
StaffName, email, password hash, two-step secret, hashed recovery codes, session hashes, actions taken
CommunicationsEvery email the Platform attempted for your store, with status and reason
Reviews, chat, analyticsReviewer name and text; your own chat, analytics and ads vendor accounts, on your own ids
LogsRequest logs at the infrastructure provider, with IP and user agent, retained on the provider's own cycle

Purpose: hosting, operating and supporting Merchant's store, migrating its data, connecting Merchant's own vendors on Merchant's instruction, backups, security, and billing Merchant. Duration: the term of the Agreement plus the 30-day read-only period and the deletion period in Section 7.

3 CCPA and comparable state service-provider terms

#

The numbered terms below track 11 CCR § 7051(a)(1)–(10) directly.

  1. No selling or sharing. Standfast will not sell or share (for cross-context behavioural advertising) any personal information it collects, receives or processes under the Agreement.
  2. Specified business purposes only. Merchant makes personal information available to Standfast only for: hosting and operating Merchant's storefront, checkout and admin; migrating Merchant's data from a previous platform; transmitting data to Merchant's own connected vendors on Merchant's instruction; sending Merchant's transactional emails; backups and disaster recovery; security, fraud prevention and debugging; support; and billing Merchant. Nothing broader.
  3. No retention, use or disclosure outside those purposes, except as the CCPA and its regulations permit.
  4. No retention, use or disclosure for any commercial purpose other than the business purposes in item 2, except as expressly permitted.
  5. No use outside the direct business relationship, and no combining of Merchant's personal information with personal information Standfast receives from another merchant or collects itself, except as permitted — for example, to detect security incidents, or to build aggregate, de-identified usage statistics that identify no consumer and no merchant.
  6. Same level of protection. Standfast complies with the CCPA and its regulations as they apply to service providers, provides the same level of privacy protection the CCPA requires of businesses, cooperates with Merchant in responding to consumer requests, and implements reasonable security procedures and practices appropriate to the personal information (Civ. Code § 1798.81.5), as set out in Schedule 2.
  7. Merchant's right to verify. Merchant may take reasonable and appropriate steps to check that Standfast uses personal information consistently with Merchant's obligations: a written security questionnaire once every twelve months, an uptime and incident report, and, on reasonable notice, an assessment by an independent assessor bound by confidentiality, at Merchant's cost unless it finds a material breach.
  8. Notice if Standfast can no longer meet its obligations. Standfast notifies Merchant in writing within five (5) business days after determining it can no longer meet its obligations under the CCPA and its regulations.
  9. Merchant's right to stop and remediate. On notice, Merchant may take reasonable and appropriate steps to stop and remediate any unauthorised use of personal information, including requiring written confirmation that Standfast no longer retains or uses the personal information of a consumer whose deletion request Merchant has honoured.
  10. Enabling consumer requests. Standfast enables Merchant to comply with consumer requests through the admin (a "delete my data" action, the customer CSV export, the marketing-consent field, address and contact correction, and the customer timeline), completes any request Merchant forwards that Merchant cannot complete itself within ten (10) business days, and forwards to Merchant within five (5) business days any request a consumer sends to Standfast directly — inside the CCPA's own outer forty-five-day consumer-response window, so Merchant has room to act on what Standfast forwards.

4 Sub-processors and your own vendors

#

Standfast engages a sub-processor only under a written contract that binds it to terms at least as protective as this DPA, notifies Merchant of the current list below and of any addition at least thirty (30) days before the new sub-processor processes Merchant's personal information, and gives Merchant the right to object; if an objection cannot be resolved, Merchant may terminate under the Agreement with the pro-rata refund it provides.

Standfast's sub-processors
PartyRoleWhat it processesLocation
Cloudflare, Inc. In use Infrastructure: application hosting, databases, file storage, queues, your hostname and TLS, request logs, and the network edge Everything in Section 2 United States and Cloudflare's global network. Store databases are created from the United States without a region hint, so Cloudflare places each one automatically; no narrower region is pinned or promised as of this version.
Resend In use Email delivery. A sub-processor only when a store's emails are sent through the Platform's own default sending domain; when Merchant's own mailbox or its own email vendor sends the store's emails, that vendor is Merchant's own, not Standfast's Transactional emails: recipient address, subject and message content, including order details United States
Authorize.net, on Standfast's own merchant account Not yet in use Billing gateway for Standfast's own invoicing of Merchant: Merchant's billing card, tokenised in the browser. As of this version Standfast does not charge a merchant's card through the Platform; the gateway is listed now so that it is already on this list when billing begins Merchant's billing contact and card token United States
An independent uptime monitor Not yet in use Not yet selected. Named here on request once it is, and added to this table when it goes live Public URLs only; no personal information To be stated when it is named

Merchant's own vendors — not Standfast's sub-processors. Every third-party service Merchant connects to run its own store (a marketing platform, a shipping/label service, an age-verification vendor, a tax engine, a loyalty or reviews tool, a chat widget, an analytics or ads tool, Merchant's own payment gateway and processor, the model provider behind the store's AI assistant, and any other app) runs on Merchant's own account, under Merchant's own contract with that vendor. Standfast transmits data to it only on Merchant's instruction and stores the API key Merchant pasted in to do so — a key Merchant can revoke at any time. Standfast is a conduit for that connection, not a party controlling it, and none of these vendors appears on Standfast's own sub-processor list because the account, the contract and the control are Merchant's.

5 GDPR and UK GDPR, where they apply

#

Standfast's infrastructure and staff operate in the United States, and Standfast does not today represent that it monitors the behaviour of, or offers goods or services specifically to, individuals located in the European Economic Area or the United Kingdom. To the extent the EU General Data Protection Regulation or the UK GDPR nonetheless applies to processing under this DPA — for example, because Merchant itself offers goods or services to individuals there through its store — the following applies in addition to Sections 3 and 4:

  • Merchant is the controller and Standfast is the processor (Art. 4(7), 4(8) GDPR) for that personal data.
  • Standfast processes personal data only on Merchant's documented instructions, including regarding international transfers, unless required to do otherwise by law that applies to Standfast, in which case Standfast informs Merchant before processing unless that law prohibits it.
  • Standfast ensures the people it authorises to process the personal data are subject to a duty of confidentiality.
  • Standfast takes the security measures in Schedule 2, assists Merchant in meeting its own obligations regarding data-subject rights requests, data-protection impact assessments and prior consultation with a supervisory authority, taking into account the nature of the processing and the information available to Standfast, at Merchant's reasonable cost for material assistance beyond what Section 3, item 10 already provides.
  • Standfast makes available to Merchant the information reasonably necessary to demonstrate compliance with this Section and allows for and contributes to audits, including inspections, conducted by Merchant or an auditor Merchant mandates, on the terms in Section 3, item 7.
  • Where a transfer of personal data subject to the GDPR or UK GDPR is made to Standfast in the United States, and no adequacy decision or equivalent mechanism otherwise covers it, Standfast will, on Merchant's request before such a transfer takes place, enter into the European Commission's Standard Contractual Clauses (Module 2: Controller to Processor) or the UK's International Data Transfer Addendum, as applicable, to cover that transfer.
  • Standfast deletes or returns all personal data to Merchant after the end of the provision of services, per Section 7, except where the law requires storage.

This section is written to be ready if and when it is needed. It does not, by itself, mean Standfast currently markets to or knowingly serves EU or UK consumers; check with Standfast before relying on this section for a specific merchant relationship that does.

6 Security incidents and breach notice

#

Standfast notifies Merchant in writing without undue delay and, in any event, within seventy-two (72) hours after confirming a security incident affecting Merchant's personal information. That first notice states the facts known at the time, the data and consumers affected as far as known, what Standfast has done, and what it recommends Merchant do; Standfast then updates Merchant as the facts develop, without waiting for a complete picture before saying anything. Consumer and regulator notices under Civil Code § 1798.82 (or, where the GDPR applies, Art. 33–34) are Merchant's to send, as the party with the direct relationship to its own shoppers; Standfast's own duty is to notify Merchant on the timeline above so Merchant can meet its own.

7 Offboarding: return and deletion of your data

#
Data deletion timeline after termination
WhenWhat happens
Any day, active or in read-onlyMerchant exports products, customers and orders as CSV from its own admin, and may request a full export of everything else (pages, blog, discounts, redirects, settings, images), supplied within ten (10) business days.
Day 0 — termination, either party, any reasonThe store moves to read-only: admin and export stay open, checkout and every write close. Nothing is deleted yet.
Day 0 to Day 30Merchant keeps read-only admin access and full export rights. This is Merchant's window to take a final export; Standfast does not shorten it for any reason short of a legal demand requiring immediate deletion.
Day 30 to Day 60Standfast deletes Merchant's personal information and the store's data from live database and file storage — within thirty (30) further days of the read-only period ending, so Merchant Data is fully deleted from primary storage within sixty (60) days of termination at the outside. Standfast confirms the deletion in writing on request.
BackupsBackup copies age out on their own independent thirty (30)-day cycle regardless of when live deletion runs, so a backup taken the day before termination is itself gone within thirty (30) days after Day 60 at the latest. No backup is retained solely because a store was cancelled.
Records the law requires keptA narrow set of records Standfast must keep regardless of a deletion request — for example, records of a payment dispute already in progress, or a record a specific statute requires retained for a fixed period — are kept only for that legally-required period and only for that purpose, never repurposed.

This table is the single source of the offboarding timeline: a thirty-day read-only-and-export window, then deletion within a further thirty days, backups aging out on their own independent thirty-day cycle after that.

8 Age-gate data retention

#

Where Merchant's catalogue needs one, the Platform stores the date of birth a shopper enters and any connected age-verification vendor's verdict, so an accepted customer is never asked again. Both are retained for as long as the customer account exists, and for the same period afterward as any other customer record under Section 7 — except where a restricted-category merchant's own state or federal recordkeeping duty (for example, a minimum-retention rule for a tobacco or vapor retailer) requires the verification record kept longer, which is Merchant's own duty under the Terms of Service, and Merchant tells Standfast if its category needs an exception to the default schedule.

9 Liability

#

Standfast's liability arising out of or relating to this DPA is subject to the limitation of liability in the Terms of Service, except to the extent applicable data-protection law does not permit capping that liability, in which case the cap does not apply to that extent. Each party remains responsible for its own compliance with the laws that apply to it as controller/business or processor/service provider respectively.

S1 Schedule 1 — Details of processing

#
Processing details required by Article 28 GDPR and comparable state law
Subject matterOperation of Merchant's online store on the Platform
DurationTerm of the Agreement, plus the 30-day read-only period, plus the 30-day deletion period (Section 7)
Nature and purposeSection 2 and item 2 of Section 3
Categories of data subjectsMerchant's shoppers (21+ where Merchant's policy requires it) and Merchant's staff
Categories of personal dataSection 2; sensitive: date of birth and age-verification verdict where applicable, and account credentials (hashed)
Merchant's instructionsThe Agreement, this DPA, and Merchant's own settings and actions in the admin

S2 Schedule 2 — Security schedule

#

Each item states whether it is built (running on the Platform today), a build commitment with its stated timing, or a procedure: something Standfast's people do, and commit to here, rather than something the software enforces. Nothing here is a statement of conformity to any named standard or certification.

  • Built running today
  • Build committed, not running today
  • Procedure done by people, not enforced by software
  1. 1. Vendor keys at rest

    Built

    Every third-party key Merchant pastes into the Platform is encrypted with AES-256-GCM under a key derived by HKDF-SHA-256 from a secret that is never written to the database, so a copy of the database alone opens nothing. A fresh 12-byte initialization vector is used on every write, and the key's own name is bound in as authenticated data, so a ciphertext moved under another name fails to open rather than opening as the wrong key. No route, list or screen returns a stored value in the clear; the screen shows the name, when it was set, by whom, and, to a store owner, the last four characters. Every set and clear is logged with the staff member and time.

  2. 2. Staff sign-in

    Built

    Password plus an authenticator-app code required by default on every staff account, enforced server-side so no client can skip it; eight recovery codes shown once and stored hashed; staff sessions live seven days from last use and never more than thirty days from sign-in, tokens stored as hashes; "log out" ends a session at once. Login attempts are rate-limited per account and per network address.

  3. 3. Shopper accounts

    Built

    Passwords hashed with PBKDF2-SHA256 at 100,000 iterations with a per-user salt; sessions run thirty days with hashed tokens; password reset and email verification are rate-limited the same way as staff sign-in.

  4. 4. Card data

    Built Build

    Built. Card numbers are tokenised in the shopper's own browser by the payment gateway's own script and never reach the Platform. The Platform stores the gateway's transaction and payment-profile identifiers and, because the gateway requires them for a later refund, the card's type and last four digits; it never stores a card number, an expiry date or a security code. Subscription cards are vaulted at the gateway. The Content Security Policy on store pages names the gateway's own script hosts explicitly, never by wildcard.

    Build, before the first outside merchant goes live. Moving the checkout to the gateway's own hosted payment form, so the card entry fields themselves belong to the gateway rather than the Platform's page.

  5. 5. Transport and browser controls

    Built

    All traffic terminates TLS at the infrastructure provider's edge. Every storefront and admin page carries a Content Security Policy restricting which hosts a script can connect to, to your own store's API and the specific vendors built into the page, so a script injection cannot send a session or cart to an arbitrary host; object embedding, base-URI, frame-ancestor and form-action directives are closed. Built, with the limitation that inline scripts are still allowed for pages that use inline handlers today — removing that is a planned refactor, not a header change.

  6. 6. Access control on the API

    Built

    Every admin route fails closed without a valid staff session or a break-glass master credential; drafts are not publicly listable; orders are not fetchable by sequential id; public stock counts are clamped so they cannot be used to infer exact inventory.

  7. 7. Audit and change logs

    Built

    Customer changes, order events, inventory events, subscription events, vendor-key events, and every email attempted are logged with the time and, where a staff member made the change, who made it.

  8. 8. Deletion

    Built

    An owner-only "delete my data" action: with no orders, quotes, subscriptions or reviews the customer row is deleted outright; otherwise personal fields are scrubbed (email, names, phone, notes, tags, date of birth, password, consent, address lines, order contacts, gift messages, label files, review names, timeline detail) and the record is marked so it is left alone going forward; an order stays on file as a tax record with the customer shown as a former customer by id; deletion is refused while an open order, an open quote or a live subscription exists.

  9. 9. Backups and restore

    Built Build

    Built. Each store database has thirty (30)-day point-in-time restore, provided by the infrastructure provider on its paid plan. Merchant's own CSV exports of products, customers and orders from the admin, any day; the product export uses the Shopify product-CSV column layout, the same layout the Platform's own importer reads, so it can be re-imported elsewhere.

    Build, committed before the first merchant pays under this DPA's terms. A nightly export of each store's database and files to separate storage, kept thirty (30) days, replicated to a second provider, with a quarterly restore drill.

  10. 10. Tenant isolation

    Built

    Each merchant store runs on its own database. Its files are kept under that store's own key prefix in the Platform's object-storage bucket, and its stored vendor keys are encrypted under a key derived for that store, so a row copied from one store's database cannot be opened in another's. A request for one store runs with access to that store's database and file prefix only. The separation of files is enforced by the Platform's code within one bucket, not by a separate bucket per store.

  11. 11. Incident response

    Build

    A public status page with an incident log, and written incident notes within two (2) business days of a severity-1 incident: build, committed before the first outside merchant goes live. Merchant notice on a confirmed incident follows Section 6 above regardless of the status page's own build status.

  12. 12. Personnel and access

    Procedure

    Standfast's own access to the Platform's control plane and to a store's admin is by a platform-level administrative credential held by Standfast (the break-glass credential in item 6), used for provisioning, support and recovery; it is not yet divided into individually named operator accounts.

    Procedure. Standfast binds each person it authorises to handle Merchant's personal information to a duty of confidentiality before granting access, and removes that access when the person's role ends.

  13. 13. Secure development

    Built Procedure

    Built. An automated test suite, including end-to-end tests that run against a real database and a test of the security headers above, and a read-only smoke test for a deployed environment.

    Procedure. The suite is run and each change is reviewed before it is released, and releases are made in a low-traffic window.

  14. 14. Data location

    Cloudflare's network. Store databases are created from the United States without a region hint, so Cloudflare places each one automatically and their primary location is expected to be North America; it is not pinned to a narrower region as of this version. See Section 4's sub-processor table for the same fact stated as the commitment it actually is.

Standfast updates this schedule when a "build" item lands and gives Merchant the dated, current version on request.

Version 2026-10-01 Questions: support@standfast.ai.

Back to top

A hosted commerce platform: your own database, storage and gateway, for a flat monthly fee.

Product

  • Pricing
  • Cost sheet
  • See it running
  • Your data

Migration

  • Free dry run
  • Export checklist
  • Shopify notice
  • Who we host

Legal

  • Terms
  • Data processing
  • Acceptable use
  • Hosting policy
  • Privacy
  • PCI

Support

  • Hours & credits
  • support@standfast.ai
Standfast Commerce, Inc., a Delaware corporation
2261 Market Street STE 93475, San Francisco, CA 94114

© 2026 Standfast Commerce, Inc.

We host stores for other merchants. We never hold merchant funds, and we are not a payment processor. Nothing on this site is legal advice. Prices are in US dollars. Last reviewed 9 October 2026.