A merchant who entrusts us with their store and customer list deserves more than a privacy policy page. So the Digitalz platform is built so that it is technically impossible for a merchant to see another merchant's data, for a customer to see a tool account's credentials, or for your customers' chats to leave to an outside service.
Our commitment to you
Your customers are yours. Digitalz does not message them, sell their data, or use it for anything beyond running your store, and access stays limited to what operations and support require, at your request.
How we protect
Nothing to enable and nothing to buy. This protection is in every Digitalz store from day one.
Every store has its own database: its customers, orders, settings and chats. No shared table, no query crossing from one store to another, and no merchant sees a customer's name at another merchant.
Tools run through the cloud and the extension on Digitalz servers. The customer uses the tool without seeing a password, and the merchant never receives one to hand over, so nothing is shared, leaked or swapped.
Payment happens inside certified gateways (Stripe, PayPal and others). Card numbers never pass through or sit on our servers; we receive only the outcome.
Your customer lists, chat contacts and analytics belong to your store. Export them as CSV whenever you like; we use them for nothing beyond running your store and share them with no other merchant.
The chatbot writes with a model running on Digitalz servers with no API key and no outside provider, analytics are computed server-side with no outside tracking script, and emails leave from our servers in your domain's name.
Every domain and subdomain has an auto-renewing SSL certificate, passwords are hashed and never stored in plain text, and backups and security updates are part of running the platform and need nothing from you.
Where data goes
Transparency is part of trust. This is what actually happens to each kind of data in your store.
| Data | Where it's stored | Who sees it |
|---|---|---|
| Your customers' data (name, email, mobile) | Your store's isolated database | You and your team only |
| Card and payment details | The payment gateway only; never through us | The payment gateway |
| Tool accounts with the providers | Digitalz servers | No customer, no merchant; the Digitalz operations team |
| Chatbot conversations | Your store's database; the model on our servers | You and your team |
| Marketing emails and your lists | Your store's database; sent from our servers in your domain's name | You only |
| Visitor and sales analytics | Your store's database; no outside script | You only |
Red lines
In your hands
Customer lists and chat contacts as CSV at any time.
Accounts for your staff with set permissions; no single shared password.
Set per plan how many devices a customer may use their tools from.
Subscriber activity in front of you, and any suspicious account suspended with one click.
reCAPTCHA and WhatsApp verification codes for your customers' accounts.
Imported lists require a consent confirmation, and every message has one-click unsubscribe.
Shared responsibility
No. Every store is in a separate database, and no query or report crosses between stores. Even the store comparison is visible to Digitalz's administration only and is never shown publicly.
No. Payment happens inside the certified gateway, and we receive only the outcome and a reference number. Card numbers never pass through our servers.
No. The model runs on Digitalz's own servers inside our internal network, with no API key and no third party. The chats stay in your store's database.
Yes. Your customer lists and chat contacts export as CSV from the dashboard at any time, and the rest of your store's data is handed to you on request.
Only the operations and support team, and only as far as needed to run your store or resolve an issue you raised. No access for marketing or analytical purposes outside your store.
Start with Digitalz and use solutions that help you build your brand and grow your business.
