How OnchainSuite uses your data.
We read the two lanes your customers leave a record in, join them into one record per person, and never hold funds or keys.
Your customers leave a record in two places. OnchainSuite reads both at source, adds the results of what you send, and puts them on one record.
What a customer does inside your application, such as registering, completing setup or using a feature.
- Signed up
- Finished setup
- Last opened the app
What the same customer's wallet does on the blockchain, such as depositing, withdrawing or transferring.
- Deposited 12,400 USDC
- Withdrew 9,800 USDC
- No activity for 60 days
Delivery and engagement from the emails and in-app messages you send, next to what each customer did in both lanes.
- Opened 3 of 4 emails
- Viewed an in-app message
- Clicked through
Inside the Lifecycle Intelligence Engine. Three systems turn raw records into customers your growth team can understand.
Deposit(0x667c…3fa1, 12400000000)Base · USDC · 12,400.00 · 14:02 UTCThe engine reads the chain from Atlas, which is why you start with history.
Atlas means you start from history. Not from an empty table.
Atlas is the blockchain data warehouse OnchainSuite reads from, built with Datum Labs. It holds backfilled, decoded records for lending, perpetuals and real-world-asset applications across EVM chains, going back to the first block. If your product is one of those, your customers arrive with their history already attached.
Once the history is in place, the next question is who on your team can see a customer's address.
ZK Shield lets your team message a customer without seeing their address.
- 01The customer submits their email through an OnchainSuite form.ZK Shield works with OnchainSuite forms only for now, so data captured in your own forms is not covered.
- 02They prove they belong to your audience without revealing who they are.A zero-knowledge proof, built on the open-source Semaphore library, confirms the fact without exposing the data behind it.
- 03They prove they control the wallet and the email address.The wallet by signing with it, and the address by entering a one-time code sent to it.
- 04The address is stored encrypted, and your team never sees it.When a campaign or a Loop sends, the delivery step resolves the address. Your team sees a wallet record and a delivered message.
What we never do.
- Hold your funds or your customers' funds, or any private keys.
- Sign or initiate a transaction. Our access to the chain is read-only.
- Find someone's email address by looking at their public wallet.
- Link a wallet to a person unless you already hold that link, or the customer makes it themselves.
The details are in our Data Processing Agreement, Privacy Policy and list of sub-processors.
Questions we get asked
Where does the on-chain data come from?
From Atlas, the blockchain data warehouse OnchainSuite reads from, which we built with Datum Labs. CNS and PNS then turn those records into actions on your customer records.
Do you support every application and chain?
No. CNS and PNS cover the chains and applications we support, and Atlas holds history for lending, perpetuals and real-world-asset applications on EVM chains. Before you sign up, we check which of your contracts and records we support.
Is ZK Shield live?
It is built and is being brought into the released product. Today it protects addresses from your own team; our backend can still decrypt an address in order to send. A later phase moves that step into a sealed processing area so our own staff cannot read it either.
Who controls the data in my workspace?
You do. You decide what to bring in and who to message, and we process it on your behalf under our Data Processing Agreement.