Welcome to Twibooru! Anonymous posting only; no content restrictions beyond pony-related and legal; comments are disabled by default (Settings -> Comments). Read me!
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>
We collect only the <em>bare minimum</em> amount of information that is necessary to protect the service against abuse. We <em>do not sell</em> your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.
</p>
</div>
<div class="rule">
<h2>What information we collect and why</h2>
<h3>Information from server logs</h3>
<p>We collect the following information (in web server logs) from every visitor:</p>
<ul>
<li>The visitor's Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The user agent string of the visitor's browser</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain:</p>
<ul>
<li>A unique session token</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (<a href="#fingerprint">see below</a>)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service may contain:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>These data are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use these cookies.</p>
<h3>Information in user-submitted content</h3>
<p>
User-submitted content is considered to collectively refer to any content that you may submit to the site, which includes, but is not limited to: comments, images, messsages, posts, reports, source changes, tag changes, and votes.
</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (<a href="#fingerprint">see below</a>)</li>
<li>The browser user agent string</li>
<li>The page that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3 id="fingerprint">Browser fingerprints</h3>
<p>
Browser fingerprints are a tool used to identify users of the service. Fingerprints are generated and stored in such a way that <em>administrators will have no knowledge</em> of the individual components: They are <em>irretrievably hashed</em> (by a browser script) from the following attributes:
</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>If you <strong>create an account</strong> we require some basic information at the time of account creation. You will be asked to provide:</p>
<ul>
<li>a username, shown on your profile and generally only visible to you and site staff</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that we do not collect</h2>
<p>
<em>We do not intentionally collect personal information</em>, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.
</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties unless legally compelled to do so. We make public certain statistics about how users use the site (for example, <a href="/pages/stats">about uploads</a>), without personally identifying information.
</p>
<p>Most of the site is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>We take <em>all measures reasonably necessary</em> to protect account information from unauthorized access, alteration, or destruction.</p>
<p>
While in transit, your data are <em>always</em> protected by the latest version of <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" rel="external noopener" target="_blank">Transport Layer Security (TLS)</a> our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use <a href="https://en.wikipedia.org/wiki/HTTPS" rel="external noopener" target="_blank">HTTPS</a> with an elliptic <a href="https://en.wikipedia.org/wiki/P-384" rel="external noopener" target="_blank">P-384</a> key. To protect user data on our servers, we strictly limit access, and require the use of elliptic <a href="https://en.wikipedia.org/wiki/Curve25519" rel="external noopener" target="_blank">Ed25519</a> or 4096-bit <a href="https://en.wikipedia.org/wiki/RSA_(cryptosystem)" rel="external noopener" target="_blank">RSA</a> keys for server login.
</p>
<p>
HTTPS is required for <em>all connections</em> to our service. Our cookies use a "<a href="https://en.wikipedia.org/wiki/Secure_cookie" rel="external noopener" target="_blank">secure</a>" setting and may only be transmitted privately to us. We use a restrictive <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="external noopener" target="_blank">Content Security Policy (CSP)</a> to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS" rel="external noopener" target="_blank">Cross-Origin Resource Sharing (CORS)</a> policy to restrict third-party usage, a strict <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy" rel="external noopener" target="_blank">Referrer-Policy</a> to prevent leaking data for external links, and a frame policy to prevent clickjacking.
</p>
<p>Passwords are hashed using <a href="https://en.wikipedia.org/wiki/Bcrypt" rel="external noopener" target="_blank">bcrypt</a> at 2<sup>10</sup> iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make our best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way we are handling your personal information, please let us know immediately. You may contact us via email directly at <a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>
We collect only the <em>bare minimum</em> amount of information that is necessary to protect the service against abuse. We <em>do not sell</em> your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.
</p>
</div>
<div class="rule">
<h2>What information we collect and why</h2>
<h3>Information from server logs</h3>
<p>We collect the following information (in web server logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li> <li>The visitor's Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The user agent string of the visitor's browser</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain:</p>
<ul>
<li>A unique session token</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (<a href="#fingerprint">see below</a>)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service may contain:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>These data are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use these cookies.</p>
<h3>Information in user-submitted content</h3>
<p>
User-submitted content is considered to collectively refer to any content that you may submit to the site, which includes, but is not limited to: comments, images, messsages, posts, reports, source changes, tag changes, and votes.
</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (<a href="#fingerprint">see below</a>)</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain:</p>
<ul>
<li>A unique session token</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (<a href="#fingerprint">see below</a>)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service may contain:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>These data are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use these cookies.</p>
<h3>Information in user-submitted content</h3>
<p>
User-submitted content is considered to collectively refer to any content that you may submit to the site, which includes, but is not limited to: comments, images, messsages, posts, reports, source changes, tag changes, and votes.
</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (<a href="#fingerprint">see below</a>)</li>
<li>The browser user agent string</li>
<li>The page that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3 id="fingerprint">Browser fingerprints</h3>
<p>
Browser fingerprints are a tool used to identify users of the service. Fingerprints are generated and stored in such a way that <em>administrators will have no knowledge</em> of the individual components: They are <em>irretrievably hashed</em> (by a browser script) from the following attributes:
</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>If you <strong>create an account</strong> we require some basic information at the time of account creation. You will be asked to provide:</p>
<ul>
<li>a username, shown on your profile and generally only visible to you and site staff</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that we do not collect</h2>
<p>
<em>We do not intentionally collect personal information</em>, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.
</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties unless legally compelled to do so. We make public certain statistics about how users use the site (for example, <a href="/pages/stats">about uploads</a>), without personally identifying information.
</p>
<p>Most of the site is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>We take <em>all measures reasonably necessary</em> to protect account information from unauthorized access, alteration, or destruction.</p>
<p>
While in transit, your data are <em>always</em> protected by the latest version of <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" rel="external noopener" target="_blank">Transport Layer Security (TLS)</a> our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use <a href="https://en.wikipedia.org/wiki/HTTPS" rel="external noopener" target="_blank">HTTPS</a> with an elliptic <a href="https://en.wikipedia.org/wiki/P-384" rel="external noopener" target="_blank">P-384</a> key. To protect user data on our servers, we strictly limit access, and require the use of elliptic <a href="https://en.wikipedia.org/wiki/Curve25519" rel="external noopener" target="_blank">Ed25519</a> or 4096-bit <a href="https://en.wikipedia.org/wiki/RSA_(cryptosystem)" rel="external noopener" target="_blank">RSA</a> keys for server login.
</p>
<p>
HTTPS is required for <em>all connections</em> to our service. Our cookies use a "<a href="https://en.wikipedia.org/wiki/Secure_cookie" rel="external noopener" target="_blank">secure</a>" setting and may only be transmitted privately to us. We use a restrictive <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="external noopener" target="_blank">Content Security Policy (CSP)</a> to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS" rel="external noopener" target="_blank">Cross-Origin Resource Sharing (CORS)</a> policy to restrict third-party usage, a strict <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy" rel="external noopener" target="_blank">Referrer-Policy</a> to prevent leaking data for external links, and a frame policy to prevent clickjacking.
</p>
<p>Passwords are hashed using <a href="https://en.wikipedia.org/wiki/Bcrypt" rel="external noopener" target="_blank">bcrypt</a> at 2<sup>10</sup> iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make our best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way we are handling your personal information, please let us know immediately. You may contact us via email directly at <a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>
We collect only the <em>bare minimum</em> amount of information that is necessary to protect the service against abuse. We <em>do not sell</em> your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.
</p>
</div>
<div class="rule">
<h2>What information we collect and why</h2>
<h3>Information from server logs</h3>
<p>We collect the following information (in web server logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain:</p>
<ul>
<li>A unique session token</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (<a href="#fingerprint">see below</a>)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service may contain:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>These data are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use these cookies.</p>
<h3>Information in user-submitted content</h3>
<p>
User-submitted content is considered to collectively refer to any content that you may submit to the site, which includes, but is not limited to: comments, images, messsages, posts, reports, source changes, tag changes, and votes.
</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (<a href="#fingerprint">see below</a>)</li>
<li>The browser user agent string</li>
<li>The page that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3 id="fingerprint">Browser fingerprints</h3>
<p>
Browser fingerprints are a tool used to identify users of the service. Fingerprints are generated and stored in such a way that <em>administrators will have no knowledge</em> of the individual components: They are <em>irretrievably hashed</em> (by a browser script) from the following attributes:
</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>If you <strong>create an account</strong> we require some basic information at the time of account creation. You will be asked to provide:</p>
<ul>
<li>a username, shown on your profile and generally only visible to you and site staff</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that we do not collect</h2>
<p>
<em>We do not intentionally collect personal information</em>, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.
</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties unless legally compelled to do so. We make public certain statistics about how users use the site (for example, <a href="/pages/stats">about uploads</a>), without personally identifying information.
</p>
<p>Most of the site is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>We take all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p> <p>We take <em>all measures reasonably necessary</em> to protect account information from unauthorized access, alteration, or destruction.</p>
<p>
While in transit, your data are always protected by the latest version of <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" rel="external noopener" target="_blank">Transport Layer Security (TLS)</a> our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use <a href="https://en.wikipedia.org/wiki/HTTPS" rel="external noopener" target="_blank">HTTPS</a> with an elliptic <a href="https://en.wikipedia.org/wiki/P-384" rel="external noopener" target="_blank">P-384</a> key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic <a href="https://en.wikipedia.org/wiki/Curve25519" rel="external noopener" target="_blank">Ed25519</a> or 4096-bit <a href="https://en.wikipedia.org/wiki/RSA_(cryptosystem)" rel="external noopener" target="_blank">RSA</a> keys for server login. While in transit, your data are <em>always</em> protected by the latest version of <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" rel="external noopener" target="_blank">Transport Layer Security (TLS)</a> our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use <a href="https://en.wikipedia.org/wiki/HTTPS" rel="external noopener" target="_blank">HTTPS</a> with an elliptic <a href="https://en.wikipedia.org/wiki/P-384" rel="external noopener" target="_blank">P-384</a> key. To protect user data on our servers, we strictly limit access, and require the use of elliptic <a href="https://en.wikipedia.org/wiki/Curve25519" rel="external noopener" target="_blank">Ed25519</a> or 4096-bit <a href="https://en.wikipedia.org/wiki/RSA_(cryptosystem)" rel="external noopener" target="_blank">RSA</a> keys for server login.
</p>
<p>
HTTPS is required for all connections to our service. Our cookies use a "<a href="https://en.wikipedia.org/wiki/Secure_cookie" rel="external noopener" target="_blank">secure</a>" setting and may only be transmitted privately to us. We use a restrictive <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="external noopener" target="_blank">Content Security Policy (CSP)</a> to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS" rel="external noopener" target="_blank">Cross-Origin Resource Sharing (CORS)</a> policy to restrict third-party usage, a strict <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy" rel="external noopener" target="_blank">Referrer-Policy</a> to prevent leaking data for external links, and a frame policy to prevent clickjacking. HTTPS is required for <em>all connections</em> to our service. Our cookies use a "<a href="https://en.wikipedia.org/wiki/Secure_cookie" rel="external noopener" target="_blank">secure</a>" setting and may only be transmitted privately to us. We use a restrictive <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="external noopener" target="_blank">Content Security Policy (CSP)</a> to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS" rel="external noopener" target="_blank">Cross-Origin Resource Sharing (CORS)</a> policy to restrict third-party usage, a strict <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy" rel="external noopener" target="_blank">Referrer-Policy</a> to prevent leaking data for external links, and a frame policy to prevent clickjacking.
</p>
<p>Passwords are hashed using <a href="https://en.wikipedia.org/wiki/Bcrypt" rel="external noopener" target="_blank">bcrypt</a> at 2<sup>10</sup> iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make our best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way we are handling your personal information, please let us know immediately. You may contact us via email directly at <a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>We collect only the bare minimum amount of information that is necessary to protect the service against abuse. We do not sell your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.</p>
</div>
<div class="rule">
<h2>What information Twibooru collects and why</h2>
<h3>Information from webserver logs</h3>
<p>We collect the following information (in webserver logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain this information:</p>
<ul>
<li>The unique session token for the website</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (see below)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service will contain this information:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>We might add to this list in the future as needed.</p>
<p>These are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use cookies.</p>
<h3>Information in user-submitted content</h3>
<p>User-submitted content is considered by Twibooru to collectively refer to any content that you may submit to the site, which includes, but is not limited to, comments, images, messsages, posts, reports, source changes, tag changes, and votes.</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (see below)</li>
<li>The browser user agent string</li>
<li>The page on Twibooru that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3>Browser fingerprints</h3>
<p>Browser fingerprints are a tool used to identify users of the service in such a way that administrators will have no knowledge of the individual components of a fingerprint. They are irretrievably hashed (by a browser script) from the following attributes:</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>
If you
<strong>create an account</strong>
we require some basic information at the time of account creation. You will be asked to provide: We collect only the <em>bare minimum</em> amount of information that is necessary to protect the service against abuse. We <em>do not sell</em> your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.
</p>
</div>
<div class="rule">
<h2>What information we collect and why</h2>
<h3>Information from server logs</h3>
<p>We collect the following information (in web server logs) from every visitor:</p>
<ul>
<li>a username, shown on your profile and non-anonymous user-submitted content</li> <li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain:</p>
<ul>
<li>A unique session token</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (<a href="#fingerprint">see below</a>)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service may contain:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>These data are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use these cookies.</p>
<h3>Information in user-submitted content</h3>
<p>
User-submitted content is considered to collectively refer to any content that you may submit to the site, which includes, but is not limited to: comments, images, messsages, posts, reports, source changes, tag changes, and votes.
</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (<a href="#fingerprint">see below</a>)</li>
<li>The browser user agent string</li>
<li>The page that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3 id="fingerprint">Browser fingerprints</h3>
<p>
Browser fingerprints are a tool used to identify users of the service. Fingerprints are generated and stored in such a way that <em>administrators will have no knowledge</em> of the individual components: They are <em>irretrievably hashed</em> (by a browser script) from the following attributes:
</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>If you <strong>create an account</strong> we require some basic information at the time of account creation. You will be asked to provide:</p>
<ul>
<li>a username, shown on your profile and generally only visible to you and site staff</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that Twibooru does not collect</h2>
<p>We do not intentionally collect personal information, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2> <h2>Information that we do not collect</h2>
<p>
We do not in any way share individual account information with third parties except in response to court orders. We make public certain statistics about how users use Twibooru (for example,
<a href="/pages/stats">about uploads</a>),
without personally-identifying information. <em>We do not intentionally collect personal information</em>, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.
</p>
<p>Most of Twibooru is public-facing, and third parties may access and use it.</p> <p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties unless legally compelled to do so. We make public certain statistics about how users use the site (for example, <a href="/pages/stats">about uploads</a>), without personally identifying information.
</p>
<p>Most of the site is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>Twibooru takes all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>While in transit, your data are always protected by the latest version of Transport Layer Security (TLS) our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use HTTPS with an elliptic P-384 key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic Ed25519 or 4096-bit RSA keys for server login.</p>
<p>HTTPS is required for all connections to our service. Our cookies use a "secure" setting and may only be transmitted privately to Twibooru. We use a restrictive content security policy to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a cross-origin resource sharing (CORS) policy to restrict third-party usage, a strict referrer policy to prevent leaking data for external links, and an frame policy to prevent clickjacking.</p>
<p>Passwords are hashed using bcrypt at 2<sup>10</sup> iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make a best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2> <p>We take all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>
If you have concerns about the way Twibooru is handling your personal information, please let us know immediately. You may contact us by emailing us directly at
<a href="mailto:[email protected]">[email protected]</a>. While in transit, your data are always protected by the latest version of <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" rel="external noopener" target="_blank">Transport Layer Security (TLS)</a> our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use <a href="https://en.wikipedia.org/wiki/HTTPS" rel="external noopener" target="_blank">HTTPS</a> with an elliptic <a href="https://en.wikipedia.org/wiki/P-384" rel="external noopener" target="_blank">P-384</a> key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic <a href="https://en.wikipedia.org/wiki/Curve25519" rel="external noopener" target="_blank">Ed25519</a> or 4096-bit <a href="https://en.wikipedia.org/wiki/RSA_(cryptosystem)" rel="external noopener" target="_blank">RSA</a> keys for server login.
</p>
<p>
HTTPS is required for all connections to our service. Our cookies use a "<a href="https://en.wikipedia.org/wiki/Secure_cookie" rel="external noopener" target="_blank">secure</a>" setting and may only be transmitted privately to us. We use a restrictive <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="external noopener" target="_blank">Content Security Policy (CSP)</a> to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS" rel="external noopener" target="_blank">Cross-Origin Resource Sharing (CORS)</a> policy to restrict third-party usage, a strict <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy" rel="external noopener" target="_blank">Referrer-Policy</a> to prevent leaking data for external links, and a frame policy to prevent clickjacking.
</p>
<p>Passwords are hashed using <a href="https://en.wikipedia.org/wiki/Bcrypt" rel="external noopener" target="_blank">bcrypt</a> at 2<sup>10</sup> iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make our best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way we are handling your personal information, please let us know immediately. You may contact us via email directly at <a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>We collect only the bare minimum amount of information that is necessary to protect the service against abuse. We do not sell your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.</p>
</div>
<div class="rule">
<h2>What information Twibooru collects and why</h2>
<h3>Information from webserver logs</h3>
<p>We collect the following information (in webserver logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain this information:</p>
<ul>
<li>The unique session token for the website</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (see below)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service will contain this information:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>We might add to this list in the future as needed.</p>
<p>These are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use cookies.</p>
<h3>Information in user-submitted content</h3>
<p>User-submitted content is considered by Twibooru to collectively refer to any content that you may submit to the site, which includes, but is not limited to, comments, images, messsages, posts, reports, source changes, tag changes, and votes.</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (see below)</li>
<li>The browser user agent string</li>
<li>The page on Twibooru that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3>Browser fingerprints</h3>
<p>Browser fingerprints are a tool used to identify users of the service in such a way that administrators will have no knowledge of the individual components of a fingerprint. They are irretrievably hashed (by a browser script) from the following attributes:</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>
If you
<strong>create an account</strong>
we require some basic information at the time of account creation. You will be asked to provide:
</p>
<ul>
<li>a username, shown on your profile and non-anonymous user-submitted content</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that Twibooru does not collect</h2>
<p>We do not intentionally collect personal information, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties except in response to court orders. We make public certain statistics about how users use Twibooru (for example,
<a href="/pages/stats">about uploads</a>),
without personally-identifying information.
</p>
<p>Most of Twibooru is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>Twibooru takes all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>While in transit, your data are always protected by the latest version of Transport Layer Security (TLS) our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use HTTPS with an elliptic P-384 key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic Ed25519 or 4096-bit RSA keys for server login.</p>
<p>HTTPS is required for all connections to our service. Our cookies use a "secure" setting and may only be transmitted privately to Twibooru. We use a restrictive content security policy to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a cross-origin resource sharing (CORS) policy to restrict third-party usage, a strict referrer policy to prevent leaking data for external links, and an frame policy to prevent clickjacking.</p>
<p>Passwords are hashed using bcrypt at 2^10 iterations with a 128-bit per-user salt.</p> <p>Passwords are hashed using bcrypt at 2<sup>10</sup> iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make a best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way Twibooru is handling your personal information, please let us know immediately. You may contact us by emailing us directly at
<a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>We collect only the bare minimum amount of information that is necessary to protect the service against abuse. We do not sell your information to third parties, and we only use it as this document describes. We aim to be compliant with the EU GDPR.</p>
</div>
<div class="rule">
<h2>What information Floorbooru collects and why</h2>
<p>
<strong>Information from webserver logs</strong>
</p>
<p>We collect the following information (in webserver logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<br>
<p>
<strong>Information in cookies</strong>
</p>
<p>Our cookies for any users of the service may contain this information:</p>
<ul>
<li>The unique session token for the website</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (see below)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service will contain this information:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>We might add to this list in the future as needed.</p>
<p>These are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use cookies.</p>
<br>
<p>
<strong>Information in user-submitted content</strong>
</p>
<p>User-submitted content is considered by Floorbooru to collectively refer to any content that you may submit to the site, which includes, but is not limited to, comments, images, messsages, posts, reports, source changes, tag changes, and votes.</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (see below)</li>
<li>The browser user agent string</li>
<li>The page on Floorbooru that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<br>
<p>
<strong>Browser fingerprints</strong>
</p>
<p>Browser fingerprints are a tool used to identify users of the service in such a way that administrators will have no knowledge of the individual components of a fingerprint. They are irretrievably hashed (by a browser script) from the following attributes:</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>
If you
<strong>create an account</strong>
we require some basic information at the time of account creation. You will be asked to provide:
</p>
<ul>
<li>a username, shown on your profile and non-anonymous user-submitted content</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that Floorbooru does not collect</h2>
<p>We do not intentionally collect personal information, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties except in response to court orders. We make public certain statistics about how users use Floorbooru (for example,
<a href="/pages/stats">about uploads</a>),
without personally-identifying information.
</p>
<p>Most of Floorbooru is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>Floorbooru takes all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>While in transit, your data are always protected by the latest version of Transport Layer Security (TLS) our software supports. Between our data processor Cloudflare and our service, we use HTTPS with an elliptic P-384 key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic Ed25519 or 4096-bit RSA keys for server login.</p>
<p>HTTPS is required for all connections to our service. Our cookies use a "secure" setting and may only be transmitted privately to Floorbooru. We use a restrictive content security policy to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a cross-origin resource sharing (CORS) policy to restrict third-party usage, a strict referrer policy to prevent leaking data for external links, and an frame policy to prevent clickjacking.</p>
<p>Passwords are hashed using bcrypt at 2^10 iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make a best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way Floorbooru is handling your personal information, please let us know immediately. You may contact us by emailing us directly at
<a href="mailto:[email protected]">[email protected]</a>.
</p>
</div> <div class="rule">
<h2>The short version</h2>
<p>We collect only the bare minimum amount of information that is necessary to protect the service against abuse. We do not sell your information to third parties, and we only use it as this document describes. We aim to be compliant with the <a href="https://gdpr-info.eu/" rel="external noopener" target="_blank">EU <abbr title="General Data Protection Regulation">GDPR</abbr></a>.</p>
</div>
<div class="rule">
<h2>What information Twibooru collects and why</h2>
<h3>Information from webserver logs</h3>
<p>We collect the following information (in webserver logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<h3>Information in cookies</h3>
<p>Our cookies for any users of the service may contain this information:</p>
<ul>
<li>The unique session token for the website</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (see below)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service will contain this information:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>We might add to this list in the future as needed.</p>
<p>These are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use cookies.</p>
<h3>Information in user-submitted content</h3>
<p>User-submitted content is considered by Twibooru to collectively refer to any content that you may submit to the site, which includes, but is not limited to, comments, images, messsages, posts, reports, source changes, tag changes, and votes.</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (see below)</li>
<li>The browser user agent string</li>
<li>The page on Twibooru that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<h3>Browser fingerprints</h3>
<p>Browser fingerprints are a tool used to identify users of the service in such a way that administrators will have no knowledge of the individual components of a fingerprint. They are irretrievably hashed (by a browser script) from the following attributes:</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>
If you
<strong>create an account</strong>
we require some basic information at the time of account creation. You will be asked to provide:
</p>
<ul>
<li>a username, shown on your profile and non-anonymous user-submitted content</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that Twibooru does not collect</h2>
<p>We do not intentionally collect personal information, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties except in response to court orders. We make public certain statistics about how users use Twibooru (for example,
<a href="/pages/stats">about uploads</a>),
without personally-identifying information.
</p>
<p>Most of Twibooru is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>Twibooru takes all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>While in transit, your data are always protected by the latest version of Transport Layer Security (TLS) our software supports. Between our data processor <a href="https://www.cloudflare.com/" rel="external noopener" target="_blank">Cloudflare</a> and our service, we use HTTPS with an elliptic P-384 key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic Ed25519 or 4096-bit RSA keys for server login.</p>
<p>HTTPS is required for all connections to our service. Our cookies use a "secure" setting and may only be transmitted privately to Twibooru. We use a restrictive content security policy to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a cross-origin resource sharing (CORS) policy to restrict third-party usage, a strict referrer policy to prevent leaking data for external links, and an frame policy to prevent clickjacking.</p>
<p>Passwords are hashed using bcrypt at 2^10 iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make a best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way Twibooru is handling your personal information, please let us know immediately. You may contact us by emailing us directly at
<a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>We collect only the bare minimum amount of information that is necessary to protect the service against abuse. We do not sell your information to third parties, and we only use it as this document describes. We aim to be compliant with the EU GDPR.</p>
</div>
<div class="rule">
<h2>What information Floorbooru collects and why</h2>
<p>
<strong>Information from webserver logs</strong>
</p>
<p>We collect the following information (in webserver logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<br>
<p>
<strong>Information in cookies</strong>
</p>
<p>Our cookies for any users of the service may contain this information:</p>
<ul>
<li>The unique session token for the website</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (see below)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service will contain this information:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>We might add to this list in the future as needed.</p>
<p>These are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use cookies.</p>
<br>
<p>
<strong>Information in user-submitted content</strong>
</p>
<p>User-submitted content is considered by Floorbooru to collectively refer to any content that you may submit to the site, which includes, but is not limited to, comments, images, messsages, posts, reports, source changes, tag changes, and votes.</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (see below)</li>
<li>The browser user agent string</li>
<li>The page on Floorbooru that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<br>
<p>
<strong>Browser fingerprints</strong>
</p>
<p>Browser fingerprints are a tool used to identify users of the service in such a way that administrators will have no knowledge of the individual components of a fingerprint. They are irretrievably hashed (by a browser script) from the following attributes:</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>
If you
<strong>create an account</strong>
we require some basic information at the time of account creation. You will be asked to provide:
</p>
<ul>
<li>a username, shown on your profile and non-anonymous user-submitted content</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that Floorbooru does not collect</h2>
<p>We do not intentionally collect personal information, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties except in response to court orders. We make public certain statistics about how users use Floorbooru (for example,
<a href="/pages/stats">about uploads</a>),
without personally-identifying information.
</p>
<p>Most of Floorbooru is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>Floorbooru takes all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>While in transit, your data are always protected by the latest version of Transport Layer Security (TLS) our software supports. Between our data processor Cloudflare and our service, we use HTTPS with an elliptic P-384 key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic Ed25519 or 4096-bit RSA keys for server login.</p>
<p>HTTPS is required for all connections to our service. Our cookies use a "secure" setting and may only be transmitted privately to Floorbooru. We use a restrictive content security policy to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a cross-origin resource sharing (CORS) policy to restrict third-party usage, a strict referrer policy to prevent leaking data for external links, and an frame policy to prevent clickjacking.</p>
<p>Passwords are hashed using bcrypt at 2^10 iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make a best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way Floorbooru is handling your personal information, please let us know immediately. You may contact us by emailing us directly at
<a href="mailto:[email protected]">[email protected]</a>. <a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>
<div class="walloftext">
<div class="rule">
<h2>The short version</h2>
<p>We collect only the bare minimum amount of information that is necessary to protect the service against abuse. We do not sell your information to third parties, and we only use it as this document describes. We aim to be compliant with the EU GDPR.</p>
</div>
<div class="rule">
<h2>What information Floorbooru collects and why</h2>
<p>
<strong>Information from webserver logs</strong>
</p>
<p>We collect the following information (in webserver logs) from every visitor:</p>
<ul>
<li>The visitor Internet Protocol (IP) address</li>
<li>The date and time of the request</li>
<li>The page that was requested</li>
<li>The browser user agent string</li>
</ul>
<p>These items are collected to ensure the security of the service, and are deleted after 14 days to balance our "legitimate interest" (as mentioned in the GDPR) of security with user privacy.</p>
<br>
<p>
<strong>Information in cookies</strong>
</p>
<p>Our cookies for any users of the service may contain this information:</p>
<ul>
<li>The unique session token for the website</li>
<li>User preference for loading high-resolution images</li>
<li>User preference for loading video previews of animated images</li>
<li>User preference for website layout customization</li>
<li>User preference for filtering settings</li>
<li>One or more "flash" messages (temporary notifications of an action's success or failure, to be displayed at the top of the next page load and then deleted)</li>
<li>A browser fingerprint (see below)</li>
</ul>
<p>Additionally, cookies of users that are logged into the service will contain this information:</p>
<ul>
<li>An encrypted authentication secret unique to the user to persist their login</li>
</ul>
<p>We might add to this list in the future as needed.</p>
<p>These are required for authentication, user security, or customization, which are all "legitimate interests" as above, and thus we cannot ask for consent to use cookies.</p>
<br>
<p>
<strong>Information in user-submitted content</strong>
</p>
<p>User-submitted content is considered by Floorbooru to collectively refer to any content that you may submit to the site, which includes, but is not limited to, comments, images, messsages, posts, reports, source changes, tag changes, and votes.</p>
<p>User-submitted content by users (authenticated or not) may contain any or all the following information:</p>
<ul>
<li>The IP address at the time of submission</li>
<li>The browser fingerprint at the time of submission (see below)</li>
<li>The browser user agent string</li>
<li>The page on Floorbooru that initiated the submission</li>
</ul>
<p>These items are only used for the "legitimate interests" of identifying and controlling abuse of the service and are not shared with any external party.</p>
<br>
<p>
<strong>Browser fingerprints</strong>
</p>
<p>Browser fingerprints are a tool used to identify users of the service in such a way that administrators will have no knowledge of the individual components of a fingerprint. They are irretrievably hashed (by a browser script) from the following attributes:</p>
<ul>
<li>Browser version</li>
<li>Screen width, height, and color depth</li>
<li>Timezone offset</li>
<li>Browser support for storage API</li>
<li>Browser plugins</li>
</ul>
</div>
<div class="rule">
<h2>Information from users with accounts</h2>
<p>
If you
<strong>create an account</strong>
we require some basic information at the time of account creation. You will be asked to provide:
</p>
<ul>
<li>a username, shown on your profile and non-anonymous user-submitted content</li>
<li>a password, stored only as a cryptographic hash</li>
<li>an email address, used only for sending password resets or account unlocking instructions</li>
</ul>
<p>We also store your IP address whenever you log in for security reasons.</p>
</div>
<div class="rule">
<h2>Information that Floorbooru does not collect</h2>
<p>We do not intentionally collect personal information, but users may include it in user-submitted content. We will remove personal information if we deem it too sensitive. Inform us if you believe shared information is too sensitive.</p>
<p>This is especially important because information shared in public user-submitted content may be indexed by search engines or used by third parties without your consent.</p>
</div>
<div class="rule">
<h2>Information that may potentially be shared with third parties</h2>
<p>
We do not in any way share individual account information with third parties except in response to court orders. We make public certain statistics about how users use Floorbooru (for example,
<a href="/pages/stats">about uploads</a>),
without personally-identifying information.
</p>
<p>Most of Floorbooru is public-facing, and third parties may access and use it.</p>
</div>
<div class="rule">
<h2>How we secure your information</h2>
<p>Floorbooru takes all measures reasonably necessary to protect account information from unauthorized access, alteration, or destruction.</p>
<p>While in transit, your data are always protected by the latest version of Transport Layer Security (TLS) our software supports. Between our data processor Cloudflare and our service, we use HTTPS with an elliptic P-384 key. To protect user data on our servers, we strictly limit their access, and require the use of elliptic Ed25519 or 4096-bit RSA keys for server login.</p>
<p>HTTPS is required for all connections to our service. Our cookies use a "secure" setting and may only be transmitted privately to Floorbooru. We use a restrictive content security policy to protect against page hijacking and information leakage to third parties, an image proxy server to avoid leaking user IP address information from embedded images on the site, a cross-origin resource sharing (CORS) policy to restrict third-party usage, a strict referrer policy to prevent leaking data for external links, and an frame policy to prevent clickjacking.</p>
<p>Passwords are hashed using bcrypt at 2^10 iterations with a 128-bit per-user salt.</p>
<p>No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security; we only make a best effort.</p>
</div>
<div class="rule">
<h2>Resolving complaints</h2>
<p>
If you have concerns about the way Floorbooru is handling your personal information, please let us know immediately. You may contact us by emailing us directly at
<a href="mailto:[email protected]">[email protected]</a>.
</p>
</div>
</div>