Local tool inputs
The hub does not ask you to upload the files or text you use inside local-first tools. A tool must tell you before data leaves your browser.
PRIVACY
A small-data approach to useful tools.
This notice explains the DMRIO Pro Hub. Individual tools may add a focused notice when a feature needs different data handling.
Versioned legal release recordPaid legal release version: 2026-08-06.v1Effective date: 2026-08-06Operator / controller: Ahmet Demir — Individual sellerPublic legal contact: mailto:dmr@dmrio.com
Service delivery data
Hosting and security infrastructure may process request details such as IP address, browser information and timestamps to deliver and protect the service.
Account identity
Google sign-in requests only openid, email and profile. The Hub receives Google's stable account identifier, verified email and optional profile name; it uses the identifier and email to authenticate the account and match subscription entitlements, and uses the name only for the signed-in experience. Google may make a profile image available under the profile scope, but the Hub does not parse, use or retain it. ChatGPT sign-in may provide the equivalent verified email and optional name. Google access and ID tokens are not retained after the callback. An encrypted and authenticated app session keeps the minimum sign-in fields for its configured lifetime; billing D1 stores an email HMAC and opaque subject reference, not the raw email or profile. Google identity data is not sold or used for advertising and is shared only with hosting or security infrastructure and service providers required for authentication, billing or digital delivery.
Measurement
No product-analytics migration is authorized in this source release. If first-party measurement is activated later, it must remain aggregate and must not build an advertising profile across subdomains.
Payments and subscription records
This paid-service data notice remains visible whether new checkout is available, disabled or the payment provider is unreachable.
Payment provider data
When paid checkout is activated, Lemon Squeezy processes checkout, customer, payment, receipt and billing information under its own notices. The Hub does not store card details or complete webhook bodies.
Hub billing records
D1 stores checkout session state and expiry; opaque subject and provider references; order, subscription and invoice status; variant and test-mode markers; total and refunded amounts; billing reason; lifecycle timestamps; webhook payload hashes and coarse processing results; and audit event class, app and timestamps.
Retention, legal basis and operator details
The owner-approved retention and legal-basis statements bound to this exact release are: Retention: Google sign-in app sessions retain the Google subject, verified email and optional name only for their configured session lifetime; Google access and ID tokens are not retained after the callback. Checkout sessions carry an expiry timestamp. Pseudonymous identity, billing, entitlement, webhook and security/audit records are retained while required to provide and secure DMRIO Pro, resolve billing or refund disputes, and comply with applicable tax, accounting or legal duties; no automatic deletion schedule is currently implemented. Legal basis: Google or ChatGPT sign-in and account, checkout, subscription and entitlement processing are necessary to authenticate the user and perform the DMRIO Pro contract; billing retention supports applicable tax, accounting and other legal obligations; security, fraud prevention and service integrity rely on legitimate interests. Product analytics is not activated in this release.
Your choices
You can use public core tools without signing in. You can also clear device-local tool data through your browser controls.
Questions
Use the operator or controller and public contact channel shown in the approved release record above for privacy questions.