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
- Passwords are hashed with bcrypt — we never store, or can see, your plain-text password
- Password reset requires clicking a one-time link emailed to your actual inbox, not just knowing an email address
- Login, signup, and password-reset attempts are rate-limited, to deter brute-force and automated abuse
- You can permanently delete your account, all your data, and your full activity log at any time, directly from your account menu
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.
- Each code works for one account, once, and expires if unused
- We store only a scrambled (hashed) form of each code, so a copy of our database can't be used to read working codes
- The tools that create codes respond only to the site owner's own verified account — anyone else just gets a plain “not found”
Connecting your Shopify store
If you choose to connect a Shopify store, this is how that connection is protected:
- Read-only. We ask Shopify for read-only access to your customers, orders and products. We can't change anything in your store.
- You approve it, on Shopify's own screen. The connection starts from Shopify's authorization page, and every response is verified with Shopify's cryptographic signature, so a forged request can't attach a store to your account.
- The access token is encrypted before it's stored. It's sealed with authenticated AES encryption, using a key kept in our hosting provider's secure settings — not in the database. A copy of the database on its own can't be used to reach your store.
- Fails safe. If that key were ever missing, we refuse to save a connection rather than store it unprotected.
- You stay in control. Disconnect any time from your account and the stored token is deleted immediately. You can also revoke access from your Shopify admin by removing the app.
- No raw copy. Your Shopify records are read when you ask for an analysis and aren't saved as raw records. What's kept is the analysis and the lists it generates, deleted after 30 days like any other analysis.
Connecting your Square account
If you choose to connect Square, the same principles apply:
- Read-only. We ask Square for read-only access to your customers, your orders and your business profile. We can't take payments, change customers or change anything in your account.
- You approve it, on Square's own screen. The connection starts from Square's authorization page. Each attempt carries a single-use, short-lived code tied to your signed-in session, so a forged or replayed link can't attach an account to you.
- Both tokens are encrypted before they're stored. Square gives us an access token and a renewal token; each is sealed with authenticated encryption using a key held in our hosting provider's secure settings, not in the database.
- Access renews itself. Square access expires after 30 days, so we renew it automatically. If you remove us in Square, the next attempt fails safely and asks you to reconnect.
- You stay in control. Disconnecting deletes the stored tokens immediately and tells Square to end our access. You can also remove us from your Square account's connected apps.
- No raw copy. Your Square records are read when you ask for an analysis and aren't saved as raw records. What's kept is the analysis and the lists it generates, deleted after 30 days.
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
- Any analysis you run, and the files it generates, is automatically deleted 30 days after it runs
- You can delete any single analysis immediately, any time, well before that
- You can delete your entire account — everything, immediately, permanently — whenever you choose
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.
| Provider | Role |
|---|---|
| Render | Application hosting and database, SOC 2 Type II certified |
| Resend | Delivers account emails (password reset, verification, reminders) and the owner activity alerts described above — never your customer data |
| Sentry | Error monitoring, configured without request headers, IPs, file contents, or in-memory values |
| Shopify | Only if you connect your store: we read your customer and order data from it, read-only, with permissions you grant and can revoke |
| Square | Only 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.