Product Perspective
Last updated
Last updated
This project is a brand new self-contained service. Because of the nature of its concept, it's designed to attract people who are interested not just in Web3, but rather the whole world as our target audience.
Diagram 1.1 illustrates the usage of iDateBabes system, starting from creating a new account, all the way down to revenue flow for the business. Keep in mind that this is a very rough overview, which is subject to change. A lot of details have been left out, in order to simplify the idea so you can understand better.
We know – any form of KYC sucks. We wish there was a way to avoid KYC and let everyone use the system without sharing any of their private information. But lets be realistic and ask ourselves; what if the registered user who wants to be assigned to the Girlfriend role (and therefore earn money):
Is a guy?
Is a girl, but underage?
Is someone who stole images from the Internet of some other girl?
Has stolen identity (e.g. someone's ID card), and impersonates that girl?
Has created multiple accounts all under different identities?
This would harm the business. The whole business would be in serious trouble if we don't regulate this. No Boyfriend would be interested to buy the Girlfriend's subscription if they aren't 100% sure who stands behind the Girlfriend's profile.
This is why only the Girlfriend role is required to complete the KYC verification in order to be registered in the system. The private documents sent by users who want to be assigned as the Girlfriend role, are strictly used for verification purposes, just to confirm that they are who they say they are, haven't stolen anyone's ID, are 18+ years of age and a female.
Those documents are stored in our system in case the regulators or the law enforcement wants us to prove that we are not breaking any law. Their documents are permanently deleted 30 days after they delete their account. Those documents are secure, safe and cannot be accessed by anyone after the staff team reviews them.
