DashForDevsDocs
DocsNewsAPI v1
dashfordevs.comSign in

© 2026 DashForDevs

DocsNewsdashfordevs.comLegalStatus
DocsSecurityCustomer Data
Introduction
Getting Started
Authentication
Products
Categories
Cart
Checkout
Blog
Reviews
Webhooks
Customers
Orders
Inventory
Shipping
Discounts
Affiliates
Email
Media & Files
Analytics & Tracking
Locations
Tax
Global Data
SEO
Error Handling
Geography
Finance
Automations
Page Types
Surveys
Billing & Subscriptions
Storefront Payments
SDK Reference
REST API
Storefront Architecture
Notifications
Security
API Key SecurityCORS & Allowed OriginsWebhook SignaturesCustomer DataRate Limiting
Team & Permissions
Migrations & Import
Calendar & Appointments
Contact Forms
AI Bots
Dashboard API
Deployment
Changelog
Troubleshooting
Recipes
CLI & Deployment
Image Pipeline
White-label Platforms
Records Engine
Platform Modules
Platform Security
Site Keys & Client Sites
Use Cases
Operations

Customer Data

How customer data is stored and encrypted.

Updated March 29, 2026

On this page
  • Data Protection
  • Data Access
  • Next Steps

Data Protection

  • All API communication uses HTTPS/TLS
  • Customer passwords are hashed with bcrypt
  • Payment data is tokenized — raw card numbers never stored
  • Access tokens expire after 24 hours
  • API keys can be rotated at any time

Data Access

Customer data is only accessible with:

  • A valid Bearer token (customer's own data)
  • A secret key sk_* (admin access to all customers)

Public keys (pk_*) cannot access individual customer data.

Next Steps

  • API Key Security
  • Rate Limiting
PreviousWebhook SignaturesNextRate Limiting

On this page

  • Data Protection
  • Data Access
  • Next Steps