Skip to content
LynxDockMenu

Legal

Privacy notice

How this website, lynxdock.app, handles information. Last updated 9 November 2026.

In short

  • There are no accounts on this website, no advertising and no advertising trackers.
  • Page views are counted with Cloudflare Web Analytics. Cloudflare states that it does not collect or use visitors’ personal data.
  • If you send one of our forms, what you type is sent to Formspree, the site’s form-handling service.
  • We do not sell personal information.
  • LynxDock community servers are run by the communities that use them. LynxDock LLC has no access to what they hold.

Who we are

This website is run by LynxDock LLC. For questions about privacy, contact [email protected].

Hosting and downloads

The website and the installer downloads (beta-dl.lynxdock.app) are served by Cloudflare. To deliver pages and files and to protect the service, Cloudflare processes technical details of each request, such as your IP address, your browser details and the page or file requested.

Cloudflare also asks browsers that support network error reporting to tell it when a request to this site fails, for example when a page does not load. It asks for no reports about requests that succeed. A report goes from your browser to Cloudflare (a.nel.cloudflare.com), not to LynxDock, and describes the failed request: the address, the type of error and technical details such as the server address and protocol. Like any request, it reaches Cloudflare with your IP address.

Cloudflare handles these request records as its privacy policy (opens in a new tab) describes.

Page-view analytics

The public site loads Cloudflare Web Analytics (a script from static.cloudflareinsights.com) to count page views and measure how quickly pages load. Cloudflare states that Web Analytics does not collect or use visitors’ personal data. We use the totals to understand which pages are read.

Each page loads the script once, from the website’s own code; the hosting service does not add a second copy. Copies of the site made for review before publication load no analytics at all. Page views are counted for all visitors, including visitors in the European Union and the European Economic Area.

Retention: Cloudflare keeps the unsampled data for 7 days, then aggregates it to about a tenth and keeps the reports available for the previous six months, as its Web Analytics FAQ (opens in a new tab) describes. The site works normally if a content blocker stops the script.

Forms: demo, beta access, business enquiries and the beta participation acknowledgement

When you send one of these forms, what you enter is sent to Formspree, a form-handling service, which stores the submission in LynxDock’s Formspree account and emails a notification of it to LynxDock’s monitored mailbox. Each submission also says which form it came from and the page you sent it from. Depending on the form, what you enter can include your name, email address, organisation or community, the option you chose and your message. A beta access request also includes your confirmation that you are 18 or older.

The beta participation acknowledgement on the tester hub sends your name, your email address, the community you are joining, your declaration that you are 18 or older, and your acknowledgement of the beta participation requirements. It has no message field.

Formspree also records technical details such as your IP address and browser type, and processes data in the United States. Its handling is described in its privacy policy (opens in a new tab).

We use what you send to reply to you, to handle your request and to keep a record that you acknowledged the beta participation requirements. We do not use it for anything else and keep no mailing list. An acknowledgement is not shared with the community’s administrator. Retention: demo, beta access and business enquiries, including their email notifications, are deleted within 90 days after the enquiry is resolved. We delete each submission from Formspree within 30 days of its arrival and keep the email notification as our record. Formspree removes a deleted submission from its active systems within minutes, and its backups can keep a copy for up to 30 more days. A beta participation acknowledgement is kept, as its email notification, while your participation is active, and afterwards for one year.

Nothing is sent until you press the form’s send button. A form that is not connected to the service says so and sends nothing.

Beta access keys

If you take part in a keyed beta build, LynxDock emails your personal access key to you; a community’s administrator never receives or relays it. LynxDock keeps an issuance record for your key — your email address, the only contact detail in it, alongside the key’s ID and other key and retention metadata — together with the emails about your key, while your participation is active and afterwards for up to one year: when your participation ends, the end date is recorded on the record, and records are deleted at the monthly review in the eleventh month after that date, so no link is kept past the stated year. The key stored on your device carries no name, email address or device identifier, and key checks happen only on your device; nothing is verified online and no key information is sent. Replacement keys come the same way: write to [email protected], and the replaced key stops being accepted by builds released afterwards — nothing changes on an installed copy.

Email

Links that start an email only open your own email app; nothing is sent until you send it. Email sent to a lynxdock.app address is received by Cloudflare Email Routing: the domain’s mail (MX) records point there. [email protected], the only address this site gives, is forwarded to a monitored mailbox at Google (Gmail), where it is kept as long as needed to deal with it, then deleted.

Beta access keys are emailed from [email protected] through Resend, an email delivery service, which sends them using Amazon Web Services in the United States. To deliver a key email, Resend processes the recipient’s email address and the message, and keeps delivery records as its privacy policy (opens in a new tab) describes.

What this website does not do

  • It does not set cookies of its own. Cloudflare’s bot protection, challenge rules and rate-limiting rules are not turned on for this site, and no cookies were seen on requests to the site during testing. If Cloudflare ever shows a visitor a security check, it sets strictly necessary cookies, such as cf_clearance, which records that the check was passed.
  • It does not show advertising or load advertising or social-media trackers.
  • It loads its fonts from this site, not from a third-party font service.
  • It does not sell personal information.

Beta participants and age

Everyone in the LynxDock beta must be 18 or older. That includes people who request access on this site, people a community invites directly, people who run a community server with LynxDock Host, and members who join with the older 0.2.6 app. That is an eligibility rule, met by each person’s affirmative self-declaration; it is not age verification. On this website, the beta access form and the beta participation acknowledgement ask you to tick a box declaring that you are 18 or older. LynxDock does not independently verify age, and nothing asks for a date of birth or proof of age. This website is not directed at children.

From LynxDock 0.3.0, the LynxDock app and LynxDock Host ask for this declaration when they first start, as part of accepting the terms for those builds, and will not record the acceptance without it. That happens in the app, not on this website. The app keeps the record on your device only, for your Windows account: the identifier and version of what you accepted, a fingerprint of its text, your 18+ declaration, the time and the app version. When the app starts, it compares this record with the build; nothing is checked online. The record is kept in your Windows user profile; it contains no name, account, email address or device identifier, and it is never sent to LynxDock or to any server.

If we learn that a request or acknowledgement came from someone under 18, we delete it and ask the community not to invite them.

The LynxDock apps and community servers

Apart from the in-app record and the beta access key records described above, this notice covers the website only. Community servers are run by the communities that use them: their accounts, messages, voice and records stay on infrastructure each community controls, and LynxDock LLC has no access to them unless someone sends us information, for example in a problem report.

The LynxDock apps send no unsolicited usage or crash telemetry. The app’s bug-report feature sends a report only after you have reviewed and approved it, and only if a report destination has been set on that PC; none is set by default. An approved report that has not yet been delivered is retried when the app next starts, at most five attempts in all, and goes to the destination set at that time.

When a member joins voice, their app also contacts the connection helpers the community server gives it: by default Google’s public STUN server, which sees the member’s IP address, and the community’s TURN relay if it has one. The apps do not check for or download updates. What LynxDock Host contacts is described on the LynxDock Host page.

Your requests

You can ask us to see, correct or delete an enquiry you sent by contacting [email protected]. We respond within 30 days.

Changes to this notice

When what the website processes changes, we update this notice and the date at the top. See also the terms.

Request a demo

We’ll walk you through LynxDock with demonstration data and answer questions about running it for your community. Invited testers looking for installers can go to the tester hub instead.