Privacy Policy

Effective 21 Oct 2026. This policy covers the Infinihash App Store at apps.infinihash.com (the "Store"), its newsletter and Billing Hub, the web apps sold through it, and the desktop apps we publish, including Detether (the "Baicells 430H Converter"). It is operated by Infinihash LLC, Michigan, United States. Each app also describes the data it holds on its own /security page or product page; this policy applies to those apps for anything they do not cover.

In short

• Visiting the Store shows no ads and sets at most one cookie, described below. We do not sell your personal data and we do not share it for advertising.
• If you subscribe to the newsletter we keep your email address and when you confirmed it.
• Payments are handled by Stripe. Card numbers never reach us.
• Our desktop apps run on your computer. Your radio, its passwords, firmware files and logs stay on your computer. The only thing a desktop app sends us is your license token.

The Store website

• No accounts for visitors; one cookie. The Store has no login or sign-up for visitors. It sets one cookie, ihas_ab, which remembers which version of a page you were shown while we compare two layouts (it holds a variant letter and no identifier, and it expires after 180 days). The only forms are the app filter and the newsletter signup. The operators' admin area uses a signed session cookie and a short-lived confirmation-message cookie, both scoped to /admin.
• Page counts. Page views are counted server-side per day and page, without IP addresses or identifiers. When a link carries campaign tags (utm_source, utm_medium, utm_campaign) the tags are counted the same way, and a newsletter signup made from such a page keeps the tags next to the address. When you arrive from another site, the host name of that site (for example google.com) is counted the same way for the page you landed on, taken from the Referer header your browser sends; the full referring address, its path and its query are not kept.
• Server logs. Requests are written to the server's system log with a request id, method, path, status, timing and the address the connection came from (which may be a proxy or Cloudflare address rather than yours). Logs do not include cookies, authorization headers or passwords. Sending a newsletter confirmation also writes the recipient's email address to the log, and the single-use confirm or unsubscribe link appears in the log of the request that opened it. The log is a rolling system journal, rotated automatically; we do not export or archive it. Server error records (request id, path, status and message, no IP address) are deleted after 30 days.
• Rate limiting. Requests are limited per client IP address. The counters are held in memory only. Failed sign-in attempts to the operators' admin area record the IP address for seven days.
• Optional analytics. Google Analytics (GA4) is not enabled on the Store today. If we enable it, it will run with IP anonymization, without advertising features or advertising cookies, and the page's source will show the analytics script.
• Cloudflare. The Store, its apps and the license service for our desktop apps use Cloudflare as network provider (CDN, proxy and security). Cloudflare handles connection data such as IP addresses and request metadata in order to deliver and protect those services, under its own privacy policy. Cloudflare can add its own measurement script at its edge; the Store's content security policy only allows scripts from the Store itself, so it does not run in your browser.

Newsletter

The Store has an optional blog newsletter with double opt-in: you enter your email address, we email you a confirmation link, and you are subscribed only when you open it. If you did not ask for it, ignore the message and nothing more happens.

• What we keep: your email address (lower-cased), your status (pending, confirmed or unsubscribed), a random single-use token used in the confirm and unsubscribe links, the times you signed up, confirmed and unsubscribed, and the campaign tags (utm_source, utm_medium, utm_campaign) of the page you signed up from, if there were any. We do not store your IP address or browser details with the subscription.
• Unsubscribe: every message carries an unsubscribe link that works without logging in. We keep the address with an "unsubscribed" status so we do not mail it again; email us if you want the record deleted entirely.
• Use: only to send you the blog and to count confirmed signups by source. Operators can export the confirmed addresses and confirmation times as a CSV file. We do not sell the list or share it with advertisers. The Store itself does not pass subscribers to any other mailing service.
• Delivery: messages are sent through our Google Workspace SMTP relay, so Google processes the address and message to deliver it.

What the Billing Hub stores

When you subscribe to a paid plan in a web app, the app asks the Billing Hub to open Stripe Checkout. The hub then keeps:

• The app and account identifiers, and the email address given at checkout.
• Stripe customer and subscription identifiers, the plan, its status, the current period end and whether it cancels at period end.
• The Stripe webhook events it received (event id, type, time, outcome) and their payloads for 90 days, so a failed event can be replayed.

Card numbers, bank details and full billing addresses never reach us; Stripe holds them under its own privacy policy. Stripe is our payment processor and the only third party that receives billing data.

Web apps (AttestProof, BankChangeProof, ControlLedger and other Store apps)

Each web app stores the data you and your team enter, the files you upload (hashed with SHA-256) and an event log of actions in the account, including the time, IP address and browser of reviewer, vendor or client actions taken through links you send. Apps with sign-in set a session cookie (HttpOnly, SameSite=Lax and, in production, Secure) and use a per-session token to protect forms; they set no advertising or tracking cookies. Each app's /security page lists exactly what it holds, its retention setting and how deletion works. Data lives in a per-app database on servers operated by Infinihash LLC in the United States, backed up nightly with backups kept for 14 days.

Desktop apps (Detether, the Baicells 430H Converter)

Desktop apps are programs you download and run on your own Mac or Windows computer. This section applies to Detether and to any other desktop app we publish, however you get it: from our site, or through an app store such as the Microsoft Store.

• What stays on your computer. Detether finds your Baicells radio on your local network and converts it from there. The radio's address, the radio passwords the app tries or you enter, firmware files you choose, and the conversion log all stay on your computer and on your local network. We do not receive them. The app may write a temporary log file in your computer's temporary folder while it runs. For the optional direct mode, the app briefly runs a local DNS and management service on your computer for the radio to connect to; that traffic stays on your network, and your operating system asks for your computer password to allow it. The app does not read or send that password to us.
• What the app sends us. The only connection to us is the license check. Before a conversion the app sends the license token you entered to our license service (a Cloudflare Worker) to ask whether it is valid and has uses left; after a successful conversion it sends the token again to use up one conversion. Nothing about your radio, your network or your computer is included.
• What the license service stores. For each token: the token itself, how many uses remain, whether it is paid or free, a short internal note (for free tokens), the Stripe Checkout session id (for paid tokens), and the time it was created and last used. It does not store your name, your email address, your IP address or anything from your computer. Like any internet service, Cloudflare, which runs the service, may process connection metadata such as IP addresses to operate and protect it, under its own policy.
• Paying for a license. Paid licenses are bought through Stripe Checkout (a Stripe Payment Link). Stripe collects your email address and payment details under its privacy policy; card numbers never reach us. After payment Stripe sends you back to our license service, which asks Stripe whether that Checkout session is paid and then shows you your token. Any email address, receipt or billing detail we see about a purchase comes from Stripe, and we keep it only in our Stripe account for accounting and support.
• Optional firmware download. You can choose a firmware file from your computer. If you instead enter or use a firmware URL, the app downloads the file from that address, and the site that hosts it sees your IP address and request under its own policy.
• No tracking. The desktop apps contain no analytics, telemetry, crash reporting or advertising, and make no network connections other than the license check, the optional firmware download you choose, and your local radio.
• App stores. If you get a desktop app through the Microsoft Store or another app store, that store processes your account, download and purchase data under its own privacy policy. We receive only what the store reports to us about the download or sale, if anything.

Products listed in the Store but run separately

Some products listed in the Store (for example ScanRelay, FeeHawk, HomeRoom, Omni Receptionist, Oryah Mail, ScopeSnap and the KYT/KYC suite) are operated on their own websites. A product operated on its own site may have its own privacy policy, linked from its page. This policy applies to the Store listing itself, and to any such product that does not publish a policy of its own.

Email

Apps send transactional email only: verification, password reset, reviewer or vendor links, reminders and digests you configured. Every emailed link is also shown in the app so email is never required. Store and app email is sent through Google Workspace's SMTP relay. Apart from the newsletter you chose to join, we send no marketing email.

Your rights

You can export your data from each web app and delete records yourself. To delete an app account, email us from the account owner's address: the account's records and files are removed within 30 days, and the backups that contain them expire 14 days later. For anything else, including access, correction, deletion or export of your data held by the Store, the newsletter, the Billing Hub or the desktop license service, email [email protected], from the address on the account or subscription where there is one, or with your license token for a desktop license. You have these rights under the law that applies to you, which may include the rights described in the GDPR and CCPA. We answer within 30 days. We do not sell personal data and we do not share it for advertising.

Retention

• App data: your retention setting, then removed by a scheduled job; account deletion is immediate for records and uploads, and generated PDFs are purged after 30 days unless downloaded.
• Billing Hub: customer and subscription records for as long as a subscription exists and for seven years afterwards where tax law requires; webhook payloads 90 days.
• Newsletter: for as long as you are subscribed; afterwards an "unsubscribed" record until you ask us to delete it. Backups hold it for up to 14 more days.
• Desktop license tokens: for as long as the license service runs, so that a token keeps working and cannot be reused after it is used up. Records tied to a purchase are kept as tax law requires.
• Server error records 30 days; admin sign-in attempts 7 days; the rolling server log is rotated automatically and not archived.
• Nightly backups: 14 days.

Where data is processed

Store, newsletter and web app data is stored on servers operated by Infinihash LLC in the United States. Cloudflare, Stripe and Google process data on their own infrastructure, which can be in other countries.

Children

The Store and the apps are business and technical tools for adults and are not directed at children under 16.

Changes

We will post changes here with a new effective date and, for material changes, email account holders in the apps and newsletter subscribers.

Contact

Infinihash LLC, Michigan, United States · [email protected]