Skip to content
HomeKnowledge BaseStatisticsChangelog GitHub Discord Email

Demyx Privacy Policy

Effective and last updated:

This Privacy Policy explains how the Demyx open-source project ("Demyx," "we," "us," or "our") collects, uses, discloses, and retains personal information through demyx.sh, Demyx product telemetry, managed redirects, and related communications. Rights and obligations described below apply where required by the law that applies to you.

Who Is Responsible For Your Information

The Demyx open-source project operates these services and acts as the controller of the information described in this policy. For privacy questions or requests, email info@demyx.sh.

Information We Collect

Website and infrastructure data

When you request a page or endpoint, Cloudflare may process network and request information needed to deliver and secure the service. This can include your IP address, request URL, date and time, browser or user-agent information, referring page, TLS and device metadata, approximate location, Cloudflare data-center information, and security signals.

Google Analytics data

When Analytics is enabled under the regional rules described below, Google Analytics receives information about your use of public pages, including page URLs and titles, referrers, interaction and session information, approximate location, browser and device information, and pseudonymous identifiers stored in _ga and _ga_* cookies. We do not send custom user IDs or information intended to directly identify you to Google Analytics.

Demyx product telemetry

Depending on the client and ingest method, telemetry registration and events may include:

  • Install ID, key ID, Ed25519 public key, identity status, registration time, last-seen time, and client version.
  • Event request ID, source, ingest method, version, and received time.
  • Raw IP address and user-agent string.
  • Cloudflare-provided city, region, country, latitude, longitude, and network or ASN organization when available.

Signed REST telemetry uses the install and key identifiers plus the public key to authenticate events. Legacy telemetry does not create a registered identity. Demyx does not intentionally store your WordPress content, credentials, domain names, private telemetry signing keys, or general server file contents in telemetry records.

Managed redirect data

Requests to managed redirects can record the requested path, hostname, raw IP address, user agent, referrer, click time, and Cloudflare-provided country, colo, city, region, and ASN. Incoming query parameters are forwarded to the configured destination but are not intentionally stored in the redirect_clicks record. The destination may receive and process those parameters under its own privacy practices.

Communications and administration

If you email us, we receive your email address, message, attachments, and any other information you provide. Restricted administrators authenticate through Cloudflare Access; verified administrator email addresses and administrative actions can be stored in audit records with action metadata and timestamps.

How We Collect Information

We obtain information:

  • Directly from you when you email us or make a privacy request.
  • Automatically from your browser, network connection, Cloudflare, and Google Analytics when enabled under the regional rules below.
  • From a Demyx installation when install or daily telemetry is enabled.
  • From administrators who manage telemetry data or redirects.

How We Use Information And Our Legal Bases

  • Service delivery and security: to deliver pages and endpoints, protect the service, rate-limit abuse, diagnose failures, and maintain reliable infrastructure. We rely on our legitimate interests in operating and securing Demyx.
  • Product telemetry: to understand active installations, version adoption, reliability, geographic and network trends, and compatibility needs. We rely on our legitimate interests in improving and maintaining the open-source project while limiting payloads and providing opt-outs.
  • Redirect measurement: to operate managed links, count usage, diagnose failures, and investigate abuse. We rely on our legitimate operational and security interests.
  • Website analytics: to understand public-site usage and improve content. We rely on consent where required, including for visitors located in the EEA, United Kingdom, and Switzerland, and on our legitimate interest in measuring and improving the public site elsewhere. You can disable Analytics at any time.
  • Communications: to respond to messages and requests. We process this information to take requested steps and for our legitimate interest in communicating with users.
  • Legal and compliance: to comply with legal obligations and establish, exercise, or defend legal claims where necessary.

We do not use this information to make decisions based solely on automated processing that produce legal or similarly significant effects. Automated security controls such as rate limiting may temporarily reject requests.

Telemetry Choices And Public Statistics

The installer sends a one-time active-install ping by default. To install without that ping and begin with telemetry disabled, download the installer and run bash install --no-ping. Daily telemetry is controlled by the host DEMYX_TELEMETRY setting; set it to false and restart the host stack to disable future daily events. See the telemetry documentation for instructions.

The public statistics page and API publish aggregated event totals, locations, versions, countries, network organizations, and activity trends. They do not publish raw IP addresses, install IDs, key IDs, public keys, or individual user-agent strings. Some map points use grouped Cloudflare-provided coordinates and location labels.

Analytics And Privacy Choices

For visitors Cloudflare locates in the European Economic Area, United Kingdom, or Switzerland, Google Analytics is disabled unless the visitor selects Accept Analytics. The same opt-in behavior applies when Cloudflare provides no recognized country code. We do not request Google's tag or send analytics consent-mode pings before acceptance in these cases.

For visitors Cloudflare locates elsewhere, Google Analytics loads by default unless the visitor previously declined or sends a Global Privacy Control signal. Country detection is approximate and can be affected by VPNs, proxies, or network routing. An explicit choice is stored in browser local storage under demyx:analytics-consent:v1 for 180 days. After it expires, the current regional default applies again.

When enabled, Google Analytics may set _ga and _ga_* first-party cookies for up to 180 days from the first Analytics-enabled visit. Cookie renewal on each page load, Google Signals, and advertising-personalization signals are disabled in the site configuration. User- and event-level Analytics retention is set to two months; Google may retain aggregated reporting data separately under its service controls.

Use the Privacy Choices button in the footer to change your selection. Declining or withdrawing consent stops future collection and triggers best-effort deletion of known Google Analytics cookies. It does not undo processing that occurred before the change. A browser Global Privacy Control signal keeps analytics disabled in every region.

How We Disclose Information

We disclose information only as needed for the purposes above, including to:

  • Cloudflare: hosting, network delivery, security, rate limiting, Access authentication, Worker execution, D1 database storage, KV caching, and operational logging.
  • Google Analytics: public-site measurement when enabled under the regional rules above. Google Signals, advertising personalization, and custom user IDs are not enabled by this site.
  • Service and professional providers: mailbox, security, legal, or technical providers when reasonably necessary.
  • Authorities or other parties: when required by law or necessary to protect rights, safety, service integrity, or against abuse.

Scheduled server jobs retrieve public project counts from GitHub, Docker Hub, and Discord without sending those services visitor information. If you follow links to GitHub, Docker Hub, Discord, DigitalOcean, or Buy Me a Coffee, those independent services receive your request and apply their own privacy policies.

We do not sell personal information, use it for cross-context behavioral advertising, or offer financial incentives for personal information.

International Processing

Demyx is available worldwide. Cloudflare, Google, and other providers may process information in countries other than the country where you live. The repository does not configure the existing D1 database with a guaranteed EU-only jurisdiction. Where required, providers use contractual protections such as data processing agreements and standard contractual clauses. You can review the Cloudflare Data Processing Addendum and Google Ads Data Processing Terms.

Retention

  • Raw telemetry events and raw managed redirect click records are automatically purged after 60 days.
  • Telemetry identities are retained while active or while operationally required to authenticate events, manage revocation, and preserve service integrity.
  • Redirect definitions, aggregate click counts, and cached aggregate public statistics are retained for their operational lifecycle or until replaced or deleted.
  • Administrative audit records are retained as reasonably necessary for security, accountability, troubleshooting, and legal claims.
  • Explicit analytics preferences and Analytics cookies last up to 180 days. Google Analytics user- and event-level retention is set to two months, subject to Google's separate treatment of aggregated reports.
  • Communications are retained until resolved and afterward only as reasonably needed for follow-up, security, recordkeeping, or legal obligations.

Backups and provider-controlled security logs may persist for their normal recovery, security, and deletion cycles.

Security

We use measures intended to protect information, including HTTPS, Cloudflare security controls, signed Ed25519 telemetry, request rate limits, prepared database statements, restricted administrative access, no-store admin responses, and scheduled deletion of raw analytics records. No transmission or storage method is completely secure.

Your Privacy Rights

Depending on your location and applicable law, you may have rights to access, correct, delete, restrict, or receive a copy of your personal information; object to processing based on legitimate interests; withdraw consent; and appeal a denied request. You may also have the right to complain to the data protection or privacy authority where you live or work.

Email info@demyx.sh to make a request. For an appeal, use the subject Privacy Appeal. We may ask for information necessary to verify your identity and locate records. Because Demyx does not maintain conventional user accounts, locating telemetry or redirect records may require an install ID, key ID, request ID, IP address, relevant path, and approximate date. We will not discriminate against you for exercising applicable rights.

Children's Privacy

Demyx is a technical open-source project and is not directed to children. We do not knowingly collect personal information from children. If you believe a child supplied personal information, contact us so we can review and delete it where appropriate.

Changes To This Policy

We may update this policy as the project, providers, or legal requirements change. We will post the revised policy here and update the effective date. Material changes may also be announced through an appropriate project channel.

Contact

For privacy questions, requests, or appeals, email info@demyx.sh.