Dimloom: Privacy Policy
Dimloom is a browser-based dimensional weight and shipping cost estimator. Publisher: Quietcog (a sole-proprietor business name). Contact: gb1@mail.grokbot.com Quietcog's general privacy policy (orders, payments, support messages), terms and refund policy are on this website. This page describes what Dimloom itself does. It is written in plain language and is not legal advice.
What stays on your device
Dimloom runs entirely in your browser. The package sizes, weights, rate cards and CSV files you enter are processed in the page and are never sent to us or to anyone else. There is no account, no analytics, no advertising and no third-party scripts, and the Dimloom page and our license service set no cookies (Stripe's hosted checkout page is run by Stripe and may use its own). Your settings and, if you buy Pro, your license key are saved in your browser's local storage on your own device; clearing the site's data removes them. The page's content-security policy (connect-src 'none') tells the browser to block network requests made by the page's own scripts, and our automated tests check both that policy and that the page makes no external requests.
What is sent over the network
Nothing, unless you choose to buy Dimloom Pro. The free version makes no network requests of its own. If you click a Buy button, your browser opens our license service (a small Cloudflare Worker) and then Stripe's hosted checkout page. Payments are processed by Stripe under Stripe's privacy policy; Stripe collects your email, billing and payment details to complete the purchase, and we can see purchase records, including your email, in our Stripe account. After you pay, the license service asks Stripe whether that checkout session was paid (and, for the annual plan, whether the subscription is active) and, if so, shows you a license key. The response the license service receives from Stripe is the full checkout session record, which includes your email and name. The license service does not use, log or store your email, name or other customer details, and never receives your card number. It uses only the payment status, the price, the subscription status and period end, and (for the "Manage subscription" link) the Stripe customer identifier. The key contains a product code, a plan, a one-way hash of your Stripe checkout session identifier, an issue date and (annual plan only) an expiry date, and no personal content; it is checked on your device against a public key, with no request sent. For the annual plan, the "Manage subscription" link on your order page opens Stripe's customer portal, using that customer identifier. Like any web request, the buy, order and manage pages are requested from your IP address. The license service's code does not use, log or store it, but it runs on Cloudflare, which processes requests and IP addresses to operate its network under Cloudflare's privacy policy. No package, rate or CSV data is ever part of any of these requests.
Purchases and refunds
Dimloom Pro is sold as a one-time lifetime license or an annual plan. Under the refund policy, you can request a refund within 14 days of purchase (for the annual plan, within 14 days of the first payment) and we will refund it; contact us with the email used for your order. After that, the annual plan can be cancelled at any time through the link on your order page or by emailing us; access continues until the end of the period you already paid for and you will not be charged again. A license key cannot be remotely revoked, so if refunded, please stop using the key. Where Stripe is the merchant of record, the refund is issued through Stripe.
Carrier information
Dimloom is independent and not affiliated with any carrier or marketplace. It does not send your data to carriers, and it shows only the divisor rules (with source links) that you can edit; you enter your own rates. All figures are estimates.
Questions and requests
Contact gb1@mail.grokbot.com Order records are held in our Stripe account; you can ask us to access or delete them. Because the app itself collects nothing, there is nothing else for us to delete.
Changes
We will update this page if our practices change; the date above shows the latest version.