Who Should Use Jomo
A wide range of businesses could benefit from Jomo's solution and get access to user data that are traditionally siloed on different platforms, and do so without worrying about harming user privacy and strict data regulations.
Below are a list of example areas that Jomo could help with via bringing in user data that weren't easily and verifiably available before:
Targetted Growth and Marketing
Fraud Prevention Using Richer and Cross-Platform Data
More Granular and Accurate Ads Distribution
Verifiable Reputation on Social/Recruiting Platforms
Feature/Product Gating and Personalization
Customized AI Agents with Verifiable User Data
If you are interested in any of the use cases above, or have new ideas on how we can collaborate, contact us via: https://forms.gle/v5xTXR16XanXc7C26
Example Usecases
Growth
Targetted Promotion to Users with Certain Trading Activities
Promotions or Incentives are great levers to encourage potential users to try out a fintech product and provides you a chance to earn the users using great product experiences. Historically these promotions are issued to the general public, or based on some rough user segmentations.
What really should happen is to only issue the promotion to your potential users, or at least give them a higher reward so a better incentive to switch over from their existing solutions. However this requires you to understand user activities on other platforms, sometimes competitors. And there were no easy ways to do that.
Now with Jomo, you can issue a promotion, which would only be available if the user can prove that they have a certain level of trading activities (amounts, frequencies, equity types, etc). Jomo's flow helps users generate a proof that they satisfy the requirements, without leaking or sharing any more than that.
Financial
Income and Asset Verification
This happens whereever we go. Leasing offices, loan officers, accredited investor checks, etc. Today when proving that I have a certain amount of asset or income, you hire a team to review the bank statements users uploaded. The process is slow and users can easily fake the uploaded documents. Not to mention that during the process a lot of credentials and information are shared, and users drop off when they don't want to leak so much information.
With Jomo, these verifications can be done without the need of a manual review team, as Jomo has proved it using cryptography. Besides, users would feel more comfortable because nothing else was leaked other than the user has a bank account with balance > $20k, or a W2 with more than $100k yearly income.
Web3
EVM Bluechip NFT Holder/Whale
Web3 social platforms can integrate with Jomo today and give their users a special UI, level, achievement badges etc, if the user verifies via Jomo that they hold certain amount of Bluechip NFTs aggregated across any of their wallets.
NFT whales typically have multiple asset wallets, and likely wouldn't sign in to a social platform with any of them. In addition, they may not even want anyone to know that their social account is associated with those asset wallets to prevent social engineering attacks.
Jomo allows users to connect and verify their wallet ownership, prove legitmacy of the results aggregated across wallets that they own, all while having nobody, including Jomo, know which wallets are owned by them.
The integration is simple for dApp developers as well. Jomo handles all the heavylifting over Zero Knowledge Proofs and user experiences, and dApp only need to hand the user off to Jomo, and wait for the verification results.
Gitcoin Donators, DAO Voters, etc
Similar to the use case above, a wide range of onchain activites can be aggregated in a way that does not expose user's wallet associations or holding details.
This could empower application builders to build on top of a user profile, customize experiences focusing on what the user has done in the past, regardless of what all wallets has the user used before and which wallet did they use to perform an action.
AI
Secure and Verifiable Data Connector
With the boom of AI agents, a lot of efforts have been made to make them more personal and helpful to each individuals. This requires data to be connected to each user's personal spaces. What happens today is that the agent developers ask users to get various API keys from different data sources, and give the API keys to the agent. The process is both complex and not secure.
Using Jomo, the AI agents can now ask the users to connect to a site of theirs, and grab data inside it via Jomo. The users don't have to deal with developer portals and complex flows. Further more, in some cases when the AI agents need verified data from the users, Jomo can help make sure of authenticity as well.
Last updated