Dmitry VerkhoturovandGitHub
fb7b6c2cdd
* Serve the build-independent web assets from the backend `privacy.html`, `markdown-help.html` and the `400x400.jpeg` it embeds carry no template variable, link no script or stylesheet, and are imported by nothing in the widget. They now live in `backend/app/webassets/assets`, embedded there, and are served under `/web` alongside the frontend build. `/web` reads the frontend build first and falls back to them, which is what lets an operator replace one by dropping a file into `--web-root`. That is what `privacy.html` needs: it describes remark42.com, while the authorization guide tells operators to hand its URL to Google and Facebook as their own application's privacy policy. Only a missing file falls through. An unreadable file in the web root keeps reporting as unreadable rather than being silently replaced by the embedded copy, and a name the filesystem rejects reports as missing rather than as a server error, both matching what `http.Dir` did. The dev server serves the same directory, so the Markdown help link in the comment form resolves on the dev port as well as in production. The two pages are served as they are written. `markdown-help.html` was minified before, and its formatted inline stylesheet is most of its 8.5 kB; that is 2.4 kB more over the wire, behind the hour-long cache header the file server already sets. Drops `copy-webpack-plugin`, which had no other pattern, and the stylelint entries that only ever matched these files. * Make pnpm dev:app start again The dev server has been failing to start on two counts, so the flow the contributing guide documents does not run at all. `webpack-cli` 4 drives `webpack-dev-server` 5 through the argument order of an older major, handing it the compiler where it expects the options object. It rejects that against its schema and exits, complaining about an unknown `_assetEmittingPreviousFiles` property, which is a field of the compiler. `webpack-cli` 7 is the release that declares `webpack-dev-server` 5 as a peer. Past that, `http-proxy-middleware` resolves to 4.1.1, which no longer accepts the two-argument call `webpack-dev-server` makes, so the `/api` and `/auth` proxies throw on startup. It is pulled in by the security override for CVE-2025-32996, the only override in the file with no upper bound: `>=2.0.10` matches every later major. Bounding it to the 2.x line keeps the fix and the API `webpack-dev-server` calls. With both in place `pnpm dev:app` serves the widget and the pages under `/web` on port 9000.
96 lines
4.8 KiB
HTML
96 lines
4.8 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="UTF-8" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
||
<title>Privacy Policy</title>
|
||
</head>
|
||
<body>
|
||
<h1>Privacy Policy</h1>
|
||
<p>
|
||
Umputun operates the website remark42.com, which provides the SERVICE. This page is used to inform website
|
||
visitors regarding our policies with the collection, use, and disclosure of Personal Information if anyone decided
|
||
to use our Service. If you choose to use our Service, then you agree to the collection and use of information in
|
||
relation with this policy. The Personal Information that we collect are used for providing and improving the
|
||
Service. We will not use or share your information with anyone except as described in this Privacy Policy.
|
||
</p>
|
||
<p>
|
||
The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which is accessible
|
||
at https://remark42.com, unless otherwise defined in this Privacy Policy.
|
||
</p>
|
||
<h3>Information Collection and Use</h3>
|
||
<p>
|
||
For a better experience while using our Service, we may require you to provide us with certain personally
|
||
identifiable information, including but not limited to your name and email address. The information that we
|
||
collect will be used to contact or identify you.
|
||
</p>
|
||
|
||
<h3>Log Data</h3>
|
||
<p>
|
||
We want to inform you that whenever you visit our Service, we collect information that your browser sends to us
|
||
that is called Log Data. This Log Data may include information such as your computer’s Internet Protocol (“IP”)
|
||
address, browser version, pages of our Service that you visit, the time and date of your visit, the time spent on
|
||
those pages, and other statistics.
|
||
</p>
|
||
|
||
<h3>Cookies</h3>
|
||
<p>
|
||
Cookies are files with small amount of data that is commonly used an anonymous unique identifier. These are sent
|
||
to your browser from the website that you visit and are stored on your computer’s hard drive. Our website uses
|
||
these “cookies” to confirm user identity. You have the option to either accept or refuse these cookies, and know
|
||
when a cookie is being sent to your computer. If you choose to refuse our cookies, you may not be able to use some
|
||
portions of our Service.
|
||
</p>
|
||
|
||
<h3>Service Providers</h3>
|
||
<p>We may employ third-party companies and individuals due to the following reasons:</p>
|
||
<ul>
|
||
<li>To facilitate our Service</li>
|
||
<li>To provide the Service on our behalf</li>
|
||
<li>To perform Service-related services</li>
|
||
<li>To assist us in analyzing how our Service is used</li>
|
||
</ul>
|
||
|
||
<p>
|
||
We want to inform our Service users that these third parties have access to your Personal Information. The reason
|
||
is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the
|
||
information for any other purpose.
|
||
</p>
|
||
|
||
<h3>Security</h3>
|
||
<p>
|
||
We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable
|
||
means of protecting it. But remember that no method of transmission over the internet, or method of electronic
|
||
storage is 100% secure and reliable, and we cannot guarantee its absolute security.
|
||
</p>
|
||
|
||
<h4>Links to Other Sites</h4>
|
||
|
||
<p>
|
||
Our Service may contain links to other sites. If you click on a third-party link, you will be directed to that
|
||
site. Note that these external sites are not operated by us. Therefore, we strongly advise you to review the
|
||
Privacy Policy of these websites, read more. We have no control over, and assume no responsibility for the
|
||
content, privacy policies, or practices of any third-party sites or services.
|
||
</p>
|
||
|
||
<h3>Children’s Privacy</h3>
|
||
<p>
|
||
Our Services do not address anyone under the age of 13. We do not knowingly collect personal identifiable
|
||
information from children under 13. In the case we discover that a child under 13 has provided us with personal
|
||
information, we immediately delete this from our servers. If you are a parent or guardian, and you are aware that
|
||
your child has provided us with personal information, please contact us so that we will be able to do necessary
|
||
actions.
|
||
</p>
|
||
|
||
<h3>Changes to This Privacy Policy</h3>
|
||
<p>
|
||
We may update our Privacy Policy from time to time. Thus, we advise you to review this page periodically for any
|
||
changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are
|
||
effective immediately, after they are posted on this page.
|
||
</p>
|
||
|
||
<h3>Contact Us</h3>
|
||
<p>If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us.</p>
|
||
</body>
|
||
</html>
|