# Welcome to Known.Email The nice little email secret in town! Known.Email is a specialized, free email service to help you access merchants' websites/apps *without passwords.* Such merchants have to integrate our simple API first to get the password-less capability. If you are wondering who a "merchant" is? ... Well, a *merchant* is anyone who has setup a "*gated*" website or app or desktop application. By "*gated*" we mean, a website/app/application where a membership is needed to enter and use it. It is important that you read our general FAQ before reading this documentation. Here is the link: Here is a 1 minute video explaining the advantages for all users: {% embed url="" %} Advantages for all users {% endembed %} ... and here is another 1 minute video explaining the advantages for all merchants: {% embed url="" %} Advantages for Merchants {% endembed %} Even if merchants are not yet aware of us, as a user you have nothing to worry! ***ALL websites/apps that allow registrations with an email address can also use our system. It is after all a specialized email service.*** Feel free to use the 5 free aliases as email addresses you can setup in your account to register and login to conventional websites/apps! You will miss the advanced features here but yet you can have a much more easier life than using your regular email. Simply add ***@my.known.email*** to the alias to convert it into an email address. *Psst... why don't you convince those sites/apps to implement our system? It will save both you and the merchant, a ton of headaches!* This documentation assumes that you have fully read our FAQ. We have two FAQs: one is the [general one here](https://known.email/faq). It is in nice digestible chunks. Reading at least that general FAQ is ***important***. This documentation will assume you know generally how our system works. Yes, you can understand our system by reading that FAQ. If you have deep questions regarding the technology, do read the faq at our special [inbox we give to each of our users.](https://inbox.known.email#faq) {% hint style="info" %} *Note: In this docs, we use the male gender only for readabilty. Wherever the male gender is used; other genders are equally applicable* {% endhint %} # Quick Start Eager to get going? Just do 3 steps! If you do not like reading much; do the following 3 steps 1. Get yourself an account here. You can get a free one in almost 2 minutes. Follow instructions on this [registration page](https://known.email/reg). Once you got an account, ***memorize*** the "*Account Secret*" given to you.
2. Create an *alias* for yourself, by clicking on this [link](https://known.email/commands#Alias). Try to use a strange word (all small letters only) as an alias -- so that hackers/spammers cannot guess it. The *alias* command sent via that link is used to set such aliases into the current configuration of your account. \ \ You can now use that *alias* as an email address by simply attaching *@my.known.email* at the end of the alias. You can set five free aliases for your account. Extra can be purchased.\ \ *NOTE: your account needs to be configured. Instead of giving you one large form for configuring your account; we use a simpler method: Each configuration in your account is set by a "command" that you give us at our commands page:* [*https://known.email/commands*](https://known.email/commands) *That page has explanations for all the various commands you can use for your account configuration.*
3. Lastly go to your own special inbox here: Give your *Account Secret* in there and press the *Refresh* button. That special inbox is the main place where all the emails sent to you would be received {% hint style="danger" %} **To reduce chances of someone guessing your *****alias*****, choose one that is reasonably obscure and does not reflect you in anyway. Of course if you get unwanted messages you can always block the sender or the domain** {% endhint %} That's it. You are reasonably sorted! Please follows us on Twitter here or on our [Discord community](https://discord.gg/VQu5tMgvpw)\ \ Now test your special @my.known.email email address, by trying to register at some SaaS application - *even those who do not know about our system.* *Hmmm...* try to create a Facebook account? Yes, you could try that using that email address except that we do not permit registrations/sign-ins to social media sites, dating sites, etc. Here is the complete [banned list.](https://known.email/banned) \ \ So you could try something else. Maybe [Trello](https://trello.com)? [Notion](https://notion.so)? [Basecamp](https://basecamphq.com)? [Slack](https://slack.com)? *If you see any merchant on the Internet that uses our password-less system, entering those sites/apps would be a lot easier:* You don't have to provide your *my.known.email* email address. Instead just provide your alias there. That merchant will send you an encrypted OTP message! Click on the message and you are in! So your registration experience as well as the login experience to such merchant sites/apps are all one and the same! \ \ Wherever you sign-up all the registration and marketing emails will now appear at your own special inbox Encrypted OTPs will be seen in the "encrypted" tab of your special inbox. ![The special inbox we provide is extremely easy to use](https://138462250-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MTRxFo6dGOYd3G7wJD-%2F-MWJ2cwR1Yy72szSjXbj%2F-MWJ3OC4BvPBfXjtIWkR%2Fimage.png?alt=media\&token=53861eef-df2d-4d61-9d8d-a55fe1407708) See this *youtube* video on how easy it is to use our special inbox, if you want to see a live action {% embed url="" %} Using the special Inbox from known.email {% endembed %} **Next steps?** *Ideally, you must go through the* [*extensive FAQ we have here* ](https://known.email/faq)*-- it is broken down into nice readable chunks.* *If you have detailed technical doubts our second FAQ at* [*https://inbox.known.email*](https://inbox.known.email#faq) *would help you. You can set up your PGP private keys as explained there.* Now return back confidently, and read the rest of this documentation fully! Regular users can skip the topics written for merchants. But don't skip them if you are a merchant and want to use our API in your own Internet offering! Enjoy! # Configuration Configuring your account is very easy! Instead of giving a big form with lots of check-boxes, input-fields, etc we used another approach: You simply *command* us to tweak each part of the configuration. So, we have given a very simple form here: Just provide the command you want to execute thru that form. Of course, you need to enter the "*Account Secret*" in that form. For that is the only way we can identify you. Instead of talking, let me show a short video on how to configure your account. You can use it to reduce your labor of reading here! {% embed url="" %} # known.emails can be used to enter almost everywhere\* \*Some merchants may not know about our system or refuse to integrate and you can still use our system there too! We do have a small banned list -- websites/apps on that list are not permitted. After taking an account with us, you may wonder *where can I use this system?* The short answer: Practically EVERYWHERE on the Internet -- which requires you to sign-up/sign-in processes using an email address. Such as a web application, mobile app, etc. ***Note:** We do not allow those sites where there is a chance people may use our system to create fake accounts. See our* [*current banned list of domains.*](https://known.email/banned) **Why?** \ Because on the Internet today; it is quite commonplace to use an email address to create an account.\ \ **How?**\ Once you become a user; get yourself a free *alias.* That can be done by sending a [configuration command to our server here. ](https://known.email/commands#Alias) ***Every alias can be used as an email address by simply attaching @my.known.email next to it.*** So you can use that email address wherever you want to register/login. **Entry into your solution/app can be password-less**\ *For those merchants who have implemented our password-less system; you can simply give the alias in their entry form. Users would be allowed in without a password as the merchant would send an OTP link which the user click to get in. You can try this password-less way of entry at our "demo" merchant here* [*https://demo.known.email*](https://demo.known.email) *Here is a simple 2 minute video explaining how easy it is for your users to get into your website/app!* {% embed url="" %} The simplest way to enter any website/app {% endembed %} **But what to do if that merchant have not implemented our system?** You can easily turn any *alias* you had created for yourself in your account into an *email address.* For example; if you had setup *xxxx* as an alias for your account, magically you are automatically given this email address too: ****** That means now you can simply use that email address to sign-up and sign-in into various offerings that merchants give you on the Internet! Of course; as those merchants have not integrated our password-less system; you would need to usually set a password in those systems and do all that is needed. But one thing is for sure: ALL merchants would be able to send all their registration emails, marketing material, support emails into your special inbox [here](https://inbox.known.email). Enjoy! *Psst.... why don't you write to those merchants who are unaware of us and request them to implement Known.Email as way to get membership on their solutions? It would save both you and those merchants a ton of headaches!* # How do we charge? Koyns! All accounts here are free. We only charge tiny amounts as per the features you use! We invented a simple system of payment that helps you use your account really well and keep it recharged easily. We have our own "internal currency" It is called "*Koyns"* Remember the coin-slot game machines you used as a child at a mall or video parlour? Usually a child would carry with him/her a bunch of these tokens so that when the video game halts inbetween, the child can insert another token. "*Koyns" are like those tokens.* Another example: In some *udipi* Restaurants at Bangalore, before ordering you are instructed to go to the cashier's table and exchange your actual money for some plastic tokens. Then you exchanged the plastic token for the exact morning dish you wanted to eat, which caught your fancy that morning. Well, *Koyns* are like those plastic tokens. *You buy enough Koyns and credit your account with the amount your account needs to function. Each bunch of Koyns are represented by one special, unique **Koyn code.*** Once those *Koyns* run out, you can purchase more and credit them into your account. Here is [our payment gateway page](https://pages.razorpay.com/koyns) to buy any number of *Koyns*. Once you make a payment, make sure you get your *Koyn Code* that represents that particular set of *Koyns* you purchased. Just follow the instructions here: [https://koyns.limenleap.com](https://koyns.limenleap.com/)​ ![It is really easy to recharge your account using "Koyns"](https://gblobscdn.gitbook.com/assets%2F-MTRxFo6dGOYd3G7wJD-%2F-MUmh3NGt8QWFG9VjTyA%2F-MUxr__ZnhwPpSzs4zuK%2FhowToUseKoyns.png?alt=media\&token=a0b09629-6736-4362-a8f3-4f56e427bcd0) ## More details on *Koyns* ***As stated before; Koyns*** **are our internal credits system.** One can say, it is the "internal currency" that we use. We not only use it here in this solution. But we use it in ALL the solutions and services offered by us at *Limen Leap Labs.* **The value of One** ***Koyn*** **is ALWAYS 1/100th of an Indian Rupee (i.e. 1 paisa) As on Feb 15, 20121 it is approximately 0.00014 USD** *Koyns* allow fine-grained control on the charges we levy in all the products and services given by our company; Limen Leap Labs. So all our system works on a simple principle: You keep your account charged and loaded with sufficient amount of *Koyns* credited into it. **As you keep using your account, these** ***Koyns*** **keep reducing based on the amount of** ***Koyns*** **we charge when you use the features of our system.** You can purchase one packet of a suitable number of *Koyns* from our [payment gateway here](https://rzp.io/l/koyns) *.* You can then credit those *Koyns* to your account using a *Koyn Code.* The correct *Koyn Code* for your purchase can be generated by you at [https://koyns.limenleap.com](https://koyns.limenleap.com/) The concept of a "*Koyn Code*" is explained later below. ## **What is a "*****Koyn Code*****"?** Each packet or set or bunch *(or whatever term you want to use for the group!)* of *Koyns* is represented by a unique "*Koyn* code". Think of the *Koyn* code as the code you see at the bottom of a currency note. And the number of *Koyns* in the packet as the denomination of that currency note. But unlike currency notes; you can buy a *Koyn* packet in any denomination you want; from [our payment gateway](https://rzp.io/l/koyns). Let me repeat: The correct *Koyn Code* for your purchase can be generated by you at [https://koyns.limenleap.com](https://koyns.limenleap.com/) ## Crediting your account Each of the solutions and services from Limen Leap Labs has its own method to credit the purchased *Koyns* into your account. ***The way to credit Koyns into your account will be clearly seen in this solution too.*** ## Advantages of Koyns *Koyns* allow you to use some parts of our systems elastically i.e. as per usage. If you had gone out on a holiday -- you don't lose out with monthly subscriptions. It is only when you actually use our system that *Koyns* are deducted. That too only for the features that you used. *Koyns* can easily be transferred to anyone and even gifted to others. The only restriction is that once a set of *Koyns* is credited to one account, the same *Koyn Code* that represented that set cannot be used to credit someone else's account too! That means; ***you cannot do "double-spend"*** If you have *Koyns* left in your account; you can ask our system to return you those *Koyns.* Our system will generate a *Koyn Code* that represents your balance. Once that is done, your account balance would again become zero -- as now those balance *Koyns* you had are now captured inside that one neat *Koyn Code*. As mentioned earlier; let me repeat: We at *Limen Leap Labs* have other offerings too... so you could use the *Koyn Code* in an account in any of those offerings. ## **Free** ***Koyns*** We sometimes give out Free *Koyns* to our users. Those cannot be returned back as a *Koyn Code* to be used in other solutions. These free *Koyns* are just incentives that we give so you have less friction when using a particular solution from us. They can be consumed in the solution where those incentives were given. ## Koyns are NOT regular currency or cryptocurrency! Thse "*Koyns*" form a closed currency -- that means; it works ONLY in our organization *(Limen Leap Labs Prtivate Limited, India)*. You can ONLY get these *Koyns* from our own [payment gateway](https://rzp.io/l/koyns) and nowhere else. You ***cannot convert Koyns back to regular fiat currency or cryptocurrency of any type. Koyns cannot be traded in any currency exchange.*** # Start using our API Start using Known.Email at your website or application *This topic is only for those who are merchants. If you are a regular user -- i.e. one who uses our special inbox as a user only, then this topic is not for you.* {% hint style="info" %} The word "you" here indicates you as a merchant i.e. the person who is using our API\ The word "offering" means whatever SaaS/Software/Application/App etc where you allow entry of users from *known.email* {% endhint %} ## The following 2 simple steps are mandatory for all API users **First step:** \ Create a free account at *known.email* Go to [https://known.email/reg/ ]()and choose one of the methods on how to get yourself a free account. *Make sure you remember the Account Secret given to you.* You can check the strength of the account secret here: If you think you got a weak password, you can remake the secret by sending in a command using the Commands page described in the next step. As your intention is to use the API and not really to enjoy using the special inbox given by us; you can ask a responsible senior person in your development team to create the account. **Second step:**\ You need to inform us that you are indeed a merchant and you would need to use our API at a particular domain. Go to and use the "*MakeMerchant*" configuration command. You would need to give 2 parameters. First one is the domain where you will use the API. The second is the static IP address of your server; from where the API would be called. {% hint style="warning" %} ### *Important:* You must be the legal representative or the owner of the domain name where you use our API. If not, you risk getting banned {% endhint %} **Common concepts applicable for ALL merchants:** * All users that come from our system to your offering are guaranteed to get the same unique ID from us. This unique ID is specific to your domain where the API is used. If you have multiple domains, each domain would get a different; yet unique ID, possibly for the same user. To protect the privacy of our users; these user IDs are uniquely crafted for each domain where the users can potentially enter. But within that domain, the same user will get the same user ID
* You can always send both regular messages and encrypted messages to any user. But make sure that you send such messages ONLY to those users who actually did become members of your offering. The only message that you are allowed to send *before* the user becomes a member at your offering, would an OTP message. *If the user does NOT proceed with the entry despite you sending the OTP, you should NOT send any other message to such a user* **For ALL API calls, our REST end point is:** ``` https://known.email/api/v2/ ``` Our API is a well tested REST system. All the API calls use the "POST" method. All API calls MUST have the following two headers. So the API should ONLY be called from a server. If if the API is used from a browser, then you will risk losing your account, as your account secret would be seen in the browser source code. > X-KNOWN-DOM: yourdomain.com\ > X-KNOWN-ACC: your account secret # Allow users to enter without passwords! All Internet offedrings ... a SaaS application, desktop application, mobile app, etc. can benefit from our system! *This topic is only for those who are merchants. If you are a regular user -- i.e. one who uses our special inbox as a user only, then this topic is not for you.* {% hint style="info" %} The word "you" here indicates you as a merchant i.e. the person who is using our API\ The word "offering" means whatever SaaS/Software/Application/App etc where you allow entry of users from *known.email* {% endhint %} **Introduction**\ If you are coding your own offerings, integrating the API from *Known.Email* is very easy. It is quite easy if you are offering someone else's code too -- we have a separate topic on that. In either case, reading this particular topic is mandatory. Also, before you read this topic you must have finished reading and understanding the [previous topic](/merchants/start-using-our-api). **Video Tutorial** {% embed url="" %} **Preparation**\ Here is a demo of the extremely simple API that we have: Play around with it and you will notice that you are able to send both regular messages as well as encrypted ones. At the end of that page; there is a link which will reveal the entire PHP source code for you. You can suitably modify it as per your needs and use it at your own server. There are after all just 3 API calls that you need to learn (and an optional 4th one, if you want to use our API to do the PGP encryption. Not recommended, but it can save you coding time)\ \ Even if you ar*e* NOT using PHP -- it should be quite easy for you to understand how we use the API calls. As indicated before, they are simple REST calls, using the "POST" method. Make sure that your code is hosted at the a server whose IP address was used to register the domain; when you used the ["MakeMerchant" command](https://known.email/commands#MakeMerchant) to configure your account. You can also check this demo "merchant" site and check for yourself indeed an encrypted OTP does get sent to you when you are user: **Strategy for a new SaaS/application/app you want to create** 1. Create a entry HTML page at your domain website with just one input box. \ \ Ask user to enter their *alias* they had created at *Known.Email* Make sure you give a link to so that the user can create an account with us; if they don't have one.
2. Once the user enters the alias, make an API call to our system to retrieve the user's public PGP key. This will also check if that user exists in our system or not. If indeed the user is in our system; you will get a unique ID (UID) which is guaranteed to be the same for the same user at your domain. If the user is NOT in our system (i.e. the alias was wrong) then you would get an error message.
3. If the user did exist (i.e. the alias was valid), you will get the following JSON object:\ \ `{` \ `"msg":"hello",`\ `"userid":"rearerereerwerwer",`\ `"origin":1,`\ `"data":"PUBLIC KEY",`\ `"success":true,`\ `"errtype":0,`\ `"freekoyns":0,`\ `"paidkoyns":111`\ `}`\ \ \ ***IMPORTANT: You should never store the alias that the user gave when entering your system, as a form of identifying the user. Instead you should use the userid that is returned in this object. The user is free to change his alias anytime! But the userid of that user will never change!***\ \ In the above JSON object; the "origin" field can be useful to you. It gives the code for the method used by the user to originally get his account. As you may know; you can become a member at known.email in several different ways (5 on last count. More are being added) \ \ But as a merchant; you may decide that you would ONLY allow those users of known.email who had registered (as an example) only using Telegram. In that case, you should check if the origin has a value of 1 -- for that is the code for those who got an account using Telegram. But some merchants may ignore this origin field as they may not mind if one person takes up multiple accounts.
4. If the user had saved his public PGP key at his account at Known.Email; you would get it in the "data" field in the above JSON. Or you would get a URI to that Public key (in the same "data" field) -- in which case, retrieve it from that indicated URI. Either way, your code would obtain the PGP public key of the user.\ \ It is possible that the user has forgotten to save the public PGP key. In such a case, you should exit the rest of the steps gracefully with a message asking the user to follow the steps to save his public PGP key from the special inbox page we have given him. The link is always: 5. Once your code has located the public PGP key of the user, the code should now proceed to generate a one time use password (OTP) for that user. If the user was NOT part of known.email, you should give some helpful instruction and end the process. We have written a separate topic on how to craft such an OTP. Read that for ideas.
6. Use the user's PGP public key and encrypt the OTP. This is done using the GPG utility via the bash command line (in Linux) or some other means -- most programming languages have a module to do the GPG encryption using the PGP public key. If you do not have such a code, you can make a system call to a sample Linux bash script which we have given in the *testapi.php* source code. \ \ If nothing works, you can use our helper API (seen in the testjson.php code) to do the encryption via REST https call. But if you use that last method please be noted that the encryption is being done at our end -- which means your super-secret OTP can theoretically get exposed to us. *Though we do not monitor that helper API at all, it is our duty to inform you.*
7. Craft a useful subject line; and that encrypted OTP message becomes the "body". Send both to the user using our API to send an encrypted message to that user who had given the alias.
8. At this point the entry page would change. The new can have an input box for where the OTP has to be entered by the user (or there is an alternative -- see below)\ \ Your HTML page will now have to wait. \ \ If you want; you can set a timeout on that page... for example; if you had crafted the OTP to expire after some timeout. \ \ Alternatively, you can just show a message (instead of an OTP input box) asking the user to *click* on a link that would be in the encrypted email. In that case, it is not the plain OTP that would be in the encrypted message; but a properly crafted HTML link (using the \ tag) which has the OTP buried in the *query\_string of the href of that link*.
9. Note that the user may be doing the clicking of the HTML link stated in previous step; on one device which may NOT BE THE SAME as the device where the user is actually entering your offering! So your code should be able to accommodate all such possibilities.
10. At this stage; we assume that the user has indeed either clicked on the OTP link; or supplied the OTP into the input box at the waiting page. \ \ And your code is convinced that the OTP was correct. \ \ It is at this point you need to check your own database and either create a new user (if that person was using your offering for the first time i.e. it is a *sign-up aka registration* ) OR if that person was previously already a user of your offering -- in which case the entry would be regarded as a *sign-in aka login*
11. Now at this stage, it is up to you to decide what happens to the user. If the user is a new one (i.e. it was a sign-up) then your code will go in one direction. But if it was a sign-*in* then the code would take a different route. How those two routes would work out is totally upto your offering you are providing. It is your intellectual property from this point onward. If you notice carefully, we have suggested a workflow where the user carries out *exactly the same steps* whether he was using it for the first time (i.e. for sign-up at your offering) OR if he was a repeat user (i.e. it was a login) This is deliberate: *ALL user ends up getting the **SAME** smooth, friction-less user experience! Be it a first time user who came to use your solution -- or one who had already become your user!* # Integrating known.email on top of other solutions What to do if you as a merchant was using another solution? *This topic is only for those who are merchants. If you are a regular user -- i.e. one who uses our special inbox as a user only, then this topic is not for you.* {% hint style="info" %} The word "you" here indicates you as a merchant i.e. the person who is using our API\ The word "offering" means whatever SaaS/Software/Application/App etc where you allow entry of users from *known.email* {% endhint %} We already explained in the previous topic how to use our system if you are coding your own offering from scratch. \ \ But then you could be a SaaS provider for a software/solution already written by someone else. Or your code is already hardened and there is already a user membership system in place. This topic explores what you could do. **Prerequisites**\ Integrating known.email into a previously existing membership system is not difficult. There are two mandatory preconditions that your existing system must satisfy * It should be possible to create a new registration into the membership of the earlier solution using an API call or by editing the back-end database * It should be possible to change the password in that membership of the earlier solution using an API call or by editing the back-end database If the previous system did not have the aforesaid two conditions, then kindly pardon us: You will find it difficult to integrate the known.email system into your existing solution. Luckily, in most well written SaaS applications, the above two conditions are usually met! Even old ones. Nowadays, many modern solutions have much more open-ended membership systems built-in; with lots of integration capabilities. You should be able to integrate Known.Email quite deeply into those very seamlessly. We are expanding this documentation; as and when we find ways to integrate those modern applications. {% hint style="success" %} Do contact us on our[ Discord community](https://discord.gg/DDgFDjC5), if you were able to integrate Known.Email into some previously written solutions. We will reward you with additional *Koyns*; and make your usage of our Known.Email system practically free for you. {% endhint %} In this topic, we are explaining how to integrate an old SaaS solution which only meets the above 2 prerequisites. The strategy we are offering here is one built on top of a reasonalby inflexible *old* solution. But realistically, it would be much more easier than this. **Integration strategy** Do the following steps 1. To handle the correspondence between Known.Email users and members of your earlier systems, create a database or if you do not have many users, your existing file system could itself be a useful "database"- just create suitable files for each user. Let's call this the "UN-database"
2. Do all the steps as explained in the [previous topic](/merchants/allowing-users-to-enter-a-new-saas) -- Pretend that the "new application" here is to maintain the aforesaid UN-database! That means, the *entry* page where users enter their alias would be seen first; and it is used to check the user or enter the user into the UN-database. \ \ *The login page of your existing solution would come in at a later step.*
3. Once a known.email user becomes a member of your UN-database, invoke a procedure to check for the correspondence between the user in the UN-database and the member in the previous membership system. Your UN-database could have a name-value table to do this correspondence.\ \ If such a user is new even in the previous solution; silently register a new account by calling the previous solution's API/code. If the same user was existing in the previous solution, silently reset the password to say "yyyy" (this just an example. You should choose something the user can use; and is secure). If your previous system also needed a username or email address for the login; note that down. Let's call that as xxxx
4. At this point when your code is sure that the user from Known.Email can proceed entering your previous system, inform the user on the HTML page:\ \ *"This page will shortly redirect. You should now use xxxs as the username and yyyy as the password . Click to continue..."*
5. When the user clicks, redirect the HTML page to the login page of your previous system. As the password was reconfigured by you silently to "yyyy", the user can easily login there.
6. There is one small disadvantage: Ideally; you should reset that password silently once the user logs out from the system. That means, your code should replace the password "yyyy" with something else the moment a user has logged out-- that way the user is forced to once again start with the first entry page of Known.Email as explained in step 2. \ \ But often, it is hard to detect the "logout" of a software -- because the user may simply close the browser window (or the application) without really going thru a proper "exit" route. That means, the same "yyyy" password would remain valid for a future session too in your existing solution. # Terms of Service How to use our service responsibly and legally. When you register an account with us, it is assumed that you have read these simple terms of service and have agreed to all the conditions we have placed here. If you do not agree with any part or whole of these legal terms and conditions, you should delete your account. The "*DeleteAccount*" command can be sent to [our server here](https://known.email/commands#DeleteAccount). It will totally wipe out your account. Any changes to these legal pages would be announced on our [Twitter account](https://twitter.com/@knownemail) and/or our [Discord community](https://discord.gg/VQu5tMgvpw). *It is your responsibility to ensure that you keep yourself updated on the latest version of all the documents placed under the "LEGALS" section of our documentation here.* We do NOT allow any illegal use of the Internet; that can be deemed to have originated due to you having an account at our system. You can read the definitions of all the illegal usage as they are clearly defined by the Indian IT information act of 2000 (and its various revisions) \ \ Here is a[ website that explains this act ](https://www.meity.gov.in/content/information-technology-act-2000)-- we assume here that you agree that all the internal documents referred in aforesaid website; are deemed attached to this one you are reading now here -- and you agree never to perform any illegal activities using our system, as defined in those referred documents. Please pay special attention to this one: Our email addresses you get from our system can be used on merchant websites and apps; excepting those that can cause us credibility issues. So this will include social media systems such as Twitter, Facebook and dating sites such as Tinder, etc.You will not be able to register at those websites using our system. The list of banned domains is updated regularly and the list is [available through this link](https://known.email/banned). We simply will NOT allow our system to be used for the express purpose of setting up fake *identities* (or otherwise known as: *sock puppet accounts*) .We will also NOT allow fake identities to be used in whatever business you have; with the help of this Known.Email system.\ \ If you are a merchant who creates dating apps; for example, then this Known.Email system is NOT for you. If; as a user, you created this account only to do multiple registrations at the same merchant's website/app then this Known.Email system is NOT for you. When you take an account with us, please ensure that your behavior on various Internet systems which uses your account here to allow entry; is in such a manner that nobody registers a complaint about you with us. If we find that the complaint is genuine and also it would be in the interest of the well-being of others that your account has to be blocked; then we reserve the right to block your access to your account here. If we are asked by the Indian authorities to give them information about your account, we will be doing so -- after due consultation from our legal counsels. We take absolutely no responsibility for the emails and messages you may receive on your account here. We are only the messenger system -- we have no control on the contents of those emails/messages; as they are not generated by our system. Neither do we have taken any steps in our server to read them. We do NOT guarantee that these emails/messages that you receive in your account will be permanently available in your account. It is your responsibility to make backups of those messages that you believe are important. As our system allows you to change your PGP keys; it is possible that you may not be able to read the messages encrypted using an earlier PGP key you had set. That is not a flaw. That is how it is supposed to work. We charge for some parts of our service. You should keep yourself updated on the current pricing -- they are [published here](https://known.email/pricing). We use our own internal currency called "*Koyns*" as a method of payment. These *Koyns* are ONLY available for use at our site and other offerings from [Limen Leap Labs Private Limited](https://limenleap.com). We do not have any process to refund unused "*Koyns*" -- however you can invoke the[ "ReturnKoyns" command](https://known.email/commands#ReturnKoyns) to get back the unused *Koyns* of your account as a "*Koyn code*" - - that can be used in all places where such "*Koyns*" are accepted. "*Koyns*" cannot be converted back to fiat currency or even cryptocurrency. One part of our system here is based on MIT licensed open source software. You can get that software in the "About" page of the special inbox here [https://inbox.known.email ](https://inbox.known.email) ALL the functionality of our system, including our own code and modifications we have made to the aforeaid MIT licensed open source software are copyrighted to Mr Sabu Francis (son of VV Francis from Navi Mumbai, India) and it is proprietary to him. You must not reverse engineer our work here, distribute our software either by itself or bundled with some other software or use the features provided by us here for any purpose whatsoever without the explicit written permission from Mr. Sabu Francis Our system has been developed with the best possible efforts and standards of software development. We however will NOT accept any liability of any loss you may incur due to any issues/bugs/hardware failures/software failure/financial failure or force-majeure events; that may affect and/or disrupt our service. \ \ In no event shall we be responsible or liable for any failure or delay in the performance of its obligations hereunder arising out of or caused by, directly or indirectly, forces beyond our control, including, without limitation, strikes, work stoppages, accidents, acts of war or terrorism, civil or military disturbances, nuclear or natural catastrophes or acts of God, and interruptions, loss or malfunctions of utilities, communications or computer (software and hardware) services; it being understood that we shall use reasonable efforts which are consistent with accepted practices in the software industry to resume performance as soon as practicable under the circumstances. # Privacy Policy We are very serious about privacy We do NOT collect your regular email address so we do not have the capability to send you emails. We may occasionally send you important messages into your own special inbox you get here. We have several methods by which you can register an account here. Some of those methods may involve revealing some part of your identity to us (for example: when you send an SMS to us when you start an account, we will get to know your phone number) Such identifiable data would be used ONLY to create your account and nothing more. Our users are not really creating any data in our system. We are just a messenger system -- a middle man, if you like -- who ensure that emails and messages sent to you are received in your account. We have NO control over the standards (such as privacy policy) of those merchants who send you emails/messages via our system. We have given controls to you by which you can block those emails/messages/senders/domains as per your requirements. We do NOT use cookies in our system anywhere on our own servers. For some subdomains (such as this documentation) we use external services -- They may have their own privacy standards which we have no control over. We may implement some statistical analysis system such as Google analytics. There could be cookies that those systems may set in your browser. Please note that those are NOT cookies created by our server. If you want to completely delete your account with us, you can do so by sending the "*DeleteAccount*" command into your configuration. Use this link # Simplifying life using known.email We keep your regular emails pure and personal. Non-human emails/messages get diverted into our special inbox. ![Don't get caught in an endless cycle!](https://138462250-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MTRxFo6dGOYd3G7wJD-%2F-MUABppYfFbB3lF5mgNo%2F-MUAvaDGi0Jjn0DosWLi%2FtheClutterCircle\(6\).png?alt=media\&token=719c5fe9-569f-4f57-9c0b-a171cadb0b3a)