<!DOCTYPE html>
<html lang="en">

<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <link rel="icon" type="image/png" sizes="96x96" href="/favicon-96x96.png">
  <link href="https://fonts.googleapis.com/css2?family=Poppins:wght@200;300;400;500&display=swap" rel="stylesheet">
  <link rel="stylesheet" href="/assets/css/reallyGlobal.css">
  <link rel="stylesheet" href="/assets/css/secondary.css">
  <title>IMPERIAL | Privacy Policy</title>
  <meta name="description" content="Read IMPERIAL's privacy policy here.">
</head>

<body>
  <nav class="generic">
    <a href="/" class="noOpacity">
      <img src="/assets/img/Logo.png" alt="IMPERIAL Logo" class="logo" draggable="false">
    </a>
    <h2>Privacy Policy</h2>
  </nav>
  <br><br><br>
  <div class="content">
    <h2>Privacy Policy</h2>
    <span class="date">Last changed: 3/25/2021</span>
    <br>
    <p>Hello! This is IMPERIAL's privacy policy. You will be able to see what gets stored, how we store it, and why we
      store such data about documents, users, or anything else.</p>
    <br>
    <p>Before we get started, here a couple of things you should now,</p>
    <p>We are going to make these terms AS READABLE AS POSSIBLE, transparency is key with our users.</p>
    <br>
    <p>Here are all of our contacts, if you receive an email or contact regarding IMPERIAL that is not from one of these
      emails, it is NOT US</p>
    <ul>
      <li>Abuse Contact: abuse@imperialb.in</li>
      <li>Support Contact: support@imperialb.in</li>
      <li>No reply Contact: noreply@imperialb.in</li>
      <li>Creator Contact: hello@looskie.com</li>
    </ul>
    <br>
    <h2>Introduction</h2>
    <p>Now, allow us to introduce ourselves. When you see, "we", "us", "imperial", "imperialbin", or "our", and
      everything in between, we're referring to ourselves</p>
    <br>
    <h2>Accounts</h2>
    <p>When you create an account, we store the following data...</p>
    <ul>
      <li>Your _id: This is a unique identifier thats automatically generated by MongoDB</li>
      <li>Your user ID: What number of user you are to join IMPERIAL</li>
      <li>Your username: Another identifier of your account, so people can add you to documents to edit</li>
      <li>Your email: So we can confirm your account and prevent spammers</li>
      <li>Your beta code: We keep the beta code you sign up with just incase an incident happens and we need to track it
        by code</li>
      <li>Your banned status: This is so we can prevent you from logging in if need to be</li>
      <li>Your confirmed status: This is so we can confirm your email and prevent spammers</li>
      <li>Your IP address: We store this to prevent spammers and multi accounting</li>
      <li>Your codes/invite codes left: We store this to regulate how many codes you can create</li>
      <li>Your icon/profile picture: Via GitHub or Gravatar, we store this for a bit of personality :)</li>
      <li>Your password: We hash and salt your password, so its secure if we get a data breach, please refer to how we
        encrypt passwords</li>
      <li>Your member+ status: We store this so we can regulate permissions</li>
      <li>Your codes/invite codes: So you can see what codes you have available to give out to others</li>
      <li>Your number of documents made: Just a cool stat, and also helps us understand who is abusing our service</li>
      <li>Your number of never expiring documents made: We store this to regulate how many never expiring documents
        there are</li>
      <li>Your document settings: We store this so its seemless switching devices</li>
    </ul>
    <br>
    <h2>Documents</h2>
    <p>When you create a document, we store the following data...</p>
    <ul>
      <li>Documents URL: This is the documents ID</li>
      <li>Documents image embed status: This tells us if image embed is enabled</li>
      <li>Documents instant delete status: This tells us if instant delete is enabled</li>
      <li>Documents creator: We store this so we know who to give privileges to</li>
      <li>Documents content: welll.... this is self explanatory, but this is the documents text</li>
      <li>Documents date created: We use this to delete the document later</li>
      <li>Documents deletion date: We use this to actually delete the document in the future</li>
      <li>Documents allowed editors: We store the editors so we can give privileges to said users</li>
      <li>Documents encrypted status: We need this so we can tell if a document is encrypted or not</li>
      <li>Documents encrypted initialization vector: We need this so we can decrypt the encrypted document, is null if
        encrypted is false</li>
      <li>Documents views: We store this so we can tell you how many people viewed your document</li>
    </ul>
    <br>
    <h2>How do we encrypt documents?</h2>
    <p>We encrypt documents with AES-256 bit encryption. We do not store the password for the document, and instead use
      an initialization vector to actually check if the password is correct. This way its hard to decrypt without the
      password, and is very secure and no passwords are stored. Our decryption and encryption code is all open sourced,
      and you can view it at <a href="https://imperialb.in/git" target="_blank">here.</a></p>
    <br>
    <h2>What happens when I delete a document</h2>
    <p>When you delete a document, the following happens...</p>
    <ul>
      <li>The document instantly gets deleted and all of its contents</li>
      <li>If image embeds are enables, the image gets deleted</li>
    </ul>
    <br>
    <h2>What do we use to store information?</h2>
    <p>We use <a href="https://www.mongodb.com" target="_blank">MongoDB</a>, it is a document-based, no-sql, and general
      purpose database. We have it heavily secured, with 2FA and IP locked access.</p>
    <br>
    <h2>How do we encrypt users passwords?</h2>
    <p>We encrypt users passwords with a NodeJS package called <a href="https://www.npmjs.com/package/bcrypt"
        target="_blank">bcrypt</a>, its a library that helps people hash things, specifically passwords. We for the most
      part frequently update bcrypt, so we have the most up to date encryption. bcrypt, made in the late 90s, has earned
      its reputation over the years. Proving that its reliable and secure.</p>
    <br>
    <h2>Integrations</h2>
    <p>We offer integrations for Discord and Github. For Discord integration, we store the following</p>
    <ul>
      <li>Your Discord ID: This is so we can trace your stuff down if need to be.</li>
    </ul>
    <p>For Github integration, we store the following</p>
    <ul>
      <li>Your authorized access token: This is so we can make gists and edit gists as you or the person you've authenticated with.</li>
    </ul>
    <p>For Github, you can unlink your account, simply head over to the <a href="/account">account page</a>, scroll to integrations, and click "Unlink Github". We will remove your GitHub access token from your user schema, and if you just want to make sure that IMPERIAL has no trace of your account, you can head over to <a href="https://github.com/settings/applications">The application settings in your GitHub account</a> and revoke access there.</p>
    <h2>Our promise</h2>
    <p>We will not sell your user data. Plain simple as that. No matter if you're banned, not confirmed, or any other
      situation, we will not sell your data. We simply just don't have an interest in selling it. Also we're just not a
      dick</p>
    <br>
    <h2>Who sees our user data?</h2>
    <p>The following people would be able to see your user data...</p>
    <ul>
      <li>DEVLOOSKIE (Creator and developer of IMPERIAL)</li>
      <li>pxseu (Community developer and admin of IMPERIAL)</li>
      <li>Hexiro (Community developer and admin of IMPERIAL)</li>
    </ul>
    <br><br><br>
</body>

</html>