Security

Last updated: October 14, 2026

You're trusting us with your customer data to use this product at all, so here's exactly what's actually in place to protect it — not a generic checklist, a real account of what's built.

Encryption

✓ At rest

Your database and uploaded files are encrypted at rest with AES-256, including automatic backups, via our hosting provider.

✓ In transit

All traffic to and from customerDNA.ai is served over HTTPS/TLS — there's no unencrypted path to or from your browser.

Account security

Access is by invitation

During our pilot, a new account can only be created with a single-use invite code, so only people we've chosen can sign up.

Connecting your Shopify store

If you choose to connect a Shopify store, this is how that connection is protected:

Connecting your Square account

If you choose to connect Square, the same principles apply:

We're told about account activity

The site owner receives an email when someone creates an account, signs in, connects a Shopify store or Square account, runs their first analysis, or when one account has repeated failed sign-in attempts (a sign of password guessing). These alerts contain the account's email address, company name if given, the time, your store's web address or Square business name when one is connected, and simple counts. They never contain your uploaded or Shopify data, passwords, or IP addresses.

Your data is isolated from every other account's

This isn't just a claim — it's enforced on every request: every piece of data is tied to your account specifically, and every API endpoint that reads or downloads data checks that you actually own it before responding. A different account requesting your data by guessing or reusing a link gets nothing, not even an error that confirms the data exists.

We watch for problems actively, not just reactively

✓ Uptime monitoring

An external service checks customerDNA.ai every few minutes, so we know immediately if it goes down — not when a customer tells us.

✓ Error monitoring

Unexpected errors are reported to us in real time, configured not to send request headers, IP addresses, your uploaded data, or the values held in memory at the moment of an error.

Data retention — and how to control it

Full detail on what we collect and why is in the Privacy Policy.

Infrastructure and who else touches your data

We run on a small, deliberately short list of infrastructure providers — not a sprawling stack of trackers and third parties. Our hosting provider, Render, is independently SOC 2 Type II certified.

ProviderRole
RenderApplication hosting and database, SOC 2 Type II certified
ResendDelivers account emails (password reset, verification, reminders) and the owner activity alerts described above — never your customer data
SentryError monitoring, configured without request headers, IPs, file contents, or in-memory values
ShopifyOnly if you connect your store: we read your customer and order data from it, read-only, with permissions you grant and can revoke
SquareOnly if you connect your account: we read your customer and order data from it, read-only, with permissions you grant and can revoke

The SOC 2 certification above is Render's, covering the infrastructure we run on. customerDNA.ai itself hasn't pursued its own separate certification yet — we're in active pilot, and that's a step we'd expect to take as the product and customer base grow.

Found a problem, or have a question?

If you believe you've found a security issue, or just want to ask how something works before trusting us with your data, email us directly: hello@customerdna.ai. We'll respond promptly — this is a small team, and a real security report gets our full attention.