DuvrinHistory stays local.
Download history is not sent to the licensing service.
Privacy policy
Your files.
Your business.
Understand what stays on your Mac, what your license needs, and how to exercise privacy rights.
Last revised 28 October 2026
Licensing stays narrow.
Purchase, activation, device and security data support your license.
Payments stay with the provider.
The licensing backend does not collect your card details.
Who this policy covers.
This policy explains how the Duvrin website, macOS app, browser companions, purchase fulfillment, licensing, and support handle personal information. The responsible operator and controller of Duvrin's own licensing, website and support data is Duvrin, based in Kenya. For privacy requests or correspondence, contact support@duvrin.com or use our privacy contact form.
The checkout provider and websites you choose to download from have their own privacy practices. Duvrin cannot control those services.
Download activity stays on your Mac.
Your downloads, selected sources, browsing captures, local download history, destinations, schedules, and saved files are managed on your Mac. Duvrin does not send that history to its licensing database. The browser companion passes selected download requests to the authenticated local app; it is not given your activation code, emailed verification proofs, or licensing-session credentials.
Source URLs, cookies, request headers and browser session information can be sensitive and may be needed locally to fetch files you ask Duvrin to download. Duvrin does not use that information for advertising or upload a history of it to the licensing service. The remote websites and networks involved in your downloads may still see normal connection details.
Information we receive.
Licenses and purchases: purchase name and email, product purchased, provider order identifiers and payment status, purchase and activation timestamps, license family and renewal information, registered device allocations, device-related public keys or pseudonymous identifiers, and records needed to prevent fraud or duplicate fulfillment.
Email verification and recovery: verification requests, expiring proof digests, authentication and anti-abuse records, and status of activation and notification emails. We do not need your device's private signing key.
Support: your name, reply-to email, chosen topic, and the message you submit, together with subsequent correspondence. Please do not send activation codes, passwords, payment details, browser cookies or private download links.
Website operations: standard hosting/security request data (which may include IP address, request time and browser information), anti-bot verification data, and your locally saved appearance preference.
Optional website analytics: if you allow analytics, Microsoft Clarity collects website interaction and diagnostic data, such as page addresses, clicks, scrolling, device and browser details, and session recordings. Page addresses can include query strings. Clarity masks input values and content in our device-management and support areas; interactions and page addresses can still be collected. Vercel Web Analytics measures page visits and collects information such as browser, device and approximate location. Vercel analytics does not use cookies; we remove query strings and fragments from its page addresses.
Why we process it.
We use purchase and license information to fulfill orders, issue and validate activation codes, enforce the two-Mac allowance, handle manual renewals and refunds, restore access, prevent abuse and answer support questions. Verification and security records protect customers from unauthorized license changes.
We use optional website analytics to understand and improve the website. We load Clarity only after you allow analytics, and we send it a denied advertising-storage signal. We also load Vercel Web Analytics only after you allow analytics.
Where applicable privacy law requires a legal basis, these activities generally support performing the purchase/license arrangement, meeting legal obligations and protecting the security and integrity of the service. We use a separate lawful basis where consent is required; we do not treat this policy itself as blanket consent.
Purchases and payment details.
Checkout is handled by Gumroad. Gumroad determines what card, payment, tax and receipt information it needs and provides its own privacy disclosures. The Duvrin licensing service receives purchase and payment-status references necessary for fulfillment; it does not hold your full card number, card security code or bank-login credentials.
Purchases and licenses are separate: a paid order is verified with the checkout provider before we issue an activation code to the purchase email.
Providers and international processing.
We use Vercel to host the website and service endpoints, Neon for licensing data storage, Gumroad for checkout and purchase records, Resend for transactional and support email delivery, Zoho for the support mailbox, and Cloudflare Turnstile to check automated form abuse. If you allow analytics, we use Vercel Web Analytics and Microsoft Clarity to understand website usage. See the Microsoft privacy statement.
These providers may process limited information on infrastructure outside your country. Their own policies and applicable safeguards govern their processing. We share only the information needed for those functions, or as required by law; we do not sell customer personal information for advertising.
How long we keep information.
We retain the minimum transaction, purchase and licensing records needed for payment accounting, fraud prevention and license verification for a minimum of two years where those ongoing purposes justify retention. Lifetime entitlement records and necessary trial or device allocation history may remain longer while needed to honor nonexpiring licenses and the minimum ten-year licensing-service commitment, prevent duplicate trials or fraudulent reinstalls, resolve disputes or comply with law. This two-year baseline is not a blanket minimum for every item of personal data, nor a promise to delete active entitlement records after two years. We periodically review whether identifiable records remain necessary, and applicable privacy and deletion rights still apply.
The licensing service has an operational cleanup process designed to remove expired verification and device-proof challenges more than one day after expiry, processed payment notifications and issued-permission records after 90 days, and encrypted contents of completed or canceled delivery-outbox messages after 30 days. These periods are measured from the applicable event and rely on the cleanup task running successfully. Undelivered message contents, delivery metadata and records needed for license accounting can remain longer.
Support correspondence and infrastructure logs are retained according to the time needed to address the request, detect abuse and meet provider or legal obligations. We review deletion or correction requests individually where retention is still necessary for a valid entitlement or a legal requirement.
Protecting your information.
We limit access to licensing records and use transport encryption, server-side credentials, short-lived verification proofs and secure authenticated sessions. A lost activation code can be replaced after email verification; requesting replacement invalidates the previous code for new activations. No system can guarantee that data is never exposed, and you should keep your purchase email and recovery messages secure.
Your choices and privacy rights.
Depending on applicable law, you may request access to your information, correction, deletion, restriction or objection to certain processing, and details of providers or international transfers. You may also have a right to complain to a privacy regulator. Send a request through privacy support or support@duvrin.com.
We may ask you to verify control of the purchase email or provide other proportionate proof before disclosing or changing records. Some information may need to be retained to meet legal obligations, defend transactions, or maintain the integrity of licenses and trials.
Changes and questions.
We may update this policy as the service changes. The revision date above identifies the text currently presented here. Material changes to how personal data is used will be communicated as required by applicable law. Contact privacy support for help or privacy questions.