Legal
Privacy Policy
How Netroforge handles information connected with the Bronom website, commercial checkout, licensing service, and desktop application.
Last updated: August 16, 2026
1. Who we are
Bronom is provided by Netroforge, operated by Yevhen Tienkaiev ("Netroforge", "we", "us"). For privacy, licensing, or support questions, contact hronom@gmail.com.
2. Information we handle
Website delivery
We do not currently add advertising trackers or marketing analytics to this website. Cloudflare processes ordinary technical request information, such as IP address, browser information, requested URL, security signals, and timestamps, to deliver and protect the site.
Purchases and subscriptions
When commercial checkout is available, Creem acts as Merchant of Record and processes customer identity, billing, payment, tax, invoice, subscription, and license-key information. We receive identifiers and subscription events needed to provide and support the commercial license. We do not receive or store full payment card details.
License activation
When you activate Bronom, the desktop application sends the license key and a random, non-personal installation label through our Cloudflare endpoint to Creem. Later checks send the key and Creem instance identifier. The endpoint does not return or intentionally log the key. Bronom stores the key locally using operating-system secure storage. Our database stores opaque Creem license, subscription, product, and customer identifiers, subscription status, relevant dates, and webhook event identifiers so canceled subscriptions can be denied. It is designed not to store license keys or customer email addresses.
Support
If you contact us, we receive the information you include in your message, such as your email address, order identifier, diagnostic details, and correspondence.
3. Bronom desktop data
Bronom is designed around a local browser profile. Tabs, browsing history, cookies, local storage, IndexedDB, cached data, saved permissions, and other browser-profile information remain on the device where Bronom runs unless you intentionally share, export, synchronize, or transmit information through a website or another tool. Websites you visit receive data under their own privacy practices.
4. Why we use information
- deliver and secure the website and licensing endpoints;
- create, validate, and administer commercial licenses and device activations;
- process subscription events, cancellations, refunds, and support requests;
- prevent abuse, investigate errors, and comply with legal obligations;
- communicate material service or policy changes.
5. Service providers and disclosure
We use Cloudflare for website delivery, security, Pages Functions, and D1 storage; GitHub for source code and software releases; and Creem for checkout, payments, taxes, invoices, subscriptions, and customer self-service. These providers process information under their own terms and privacy notices. We may also disclose information when required by law, to protect users or the service, or as part of a legitimate business transfer.
6. Retention and security
We keep information only for as long as reasonably needed for licensing, support, security, dispute handling, and legal compliance. Retention by Creem, Cloudflare, GitHub, and websites visited through Bronom is controlled by those providers. We use access controls, encryption in transit, secret storage, hashing, and data minimization, but no system can guarantee absolute security.
7. Your choices and rights
You may ask us to access, correct, or delete personal information we control, or object to or restrict certain processing where applicable. Some records may need to be retained for legal, fraud-prevention, accounting, or dispute purposes. Contact hronom@gmail.com. You may also manage payment and subscription data through the Creem Customer Portal.
8. International processing and children
Our providers may process information in countries other than yours and use lawful transfer safeguards where required. Bronom and its commercial service are not directed to children, and we do not knowingly collect personal information from children.
9. Changes
We may update this policy as the product or legal requirements change. The updated date above identifies the current version. Material changes will be posted on this page.