Request managed DNS

Tell us about your deployment. We will email a verification code to confirm your address before creating your tenant.

Your name Organisation Work email How will you use managed DNS? Fleet size (number of devices) I accept the terms of service (2026-11).

Read the terms

> **Draft and enablement requirements.** These terms describe proposed self-service and are not evidence that those features are implemented or that the terms are ready for publication. The historical comments below describe an older revision; check current operations and obtain legal review before use.  # BAYTON Managed DNS terms of use These terms cover BAYTON Managed DNS, the managed DNS filtering service from BAYTON, and set out what your organisation may and may not do with it. Last updated: 11 November 2026 These terms of use ("Terms") govern access to and use of BAYTON Managed DNS, including the DNS-over-TLS resolvers, the device enrolment and policy service, the sign-up and Dashboard pages, and the BAYTON Managed DNS Android app (together, the "Service"), provided by BAYTON ("BAYTON", "we", "us", or "our"), a community project published at bayton.org. By signing up for, accessing or using the Service, you agree to these Terms on behalf of your organisation. If you do not agree, do not use the Service. ## Contents 1. About the Service 2. Who can use the Service 3. Your organisation's responsibilities 4. Acceptable use 5. Prohibited use 6. Limits 7. Availability and changes 8. What filtering does and does not do 9. Review, suspension and removal 10. Codes and keys 11. Intellectual property 12. Data and privacy 13. Ending your use 14. No warranty 15. Limitation of liability 16. Changes to these Terms 17. Governing law 18. Contact ## 1. About the Service BAYTON Managed DNS filters DNS on Android devices your organisation manages. Your EMM points each device's Private DNS at a Managed DNS hostname and delivers the Managed DNS app with your blocked or allowed domains as managed configuration. The app reports that configuration to the Service, which works out each profile's policy from what its devices report and publishes it to the resolvers that answer those devices' DNS lookups. When you sign up, we create an organisation (a "tenant") for you and issue an enrolment key, a management code and a device limit. Policy is authored and changed through your EMM. The Service stores the policy your devices report so it can apply it, but offers no separate place to edit it. ## 2. Who can use the Service The Service is for organisations filtering DNS on Android devices they own, or manage through an EMM as fully managed devices. By signing up you confirm that you have the authority to agree to these Terms for your organisation, that the details you give us are accurate, and that the devices you enrol are managed by your organisation. The Service is not for personal or unmanaged devices, and must not be run, offered or shared as a public or open resolver. ## 3. Your organisation's responsibilities You are responsible for the policies you set, the domains you block or allow, the devices you enrol, and how you configure your EMM. You must have the right to manage and filter the devices you enrol, and you must give the people who use them any notice that the law or your own policies require. You must comply with the requirements of any platform or device management system through which you deploy the app or the Private DNS setting, including Android, Android Enterprise and Google Play. You are responsible for testing your configuration before you roll it out, and for keeping a way to remove or change the Private DNS setting through your EMM (see section 7). ## 4. Acceptable use The Service is provided in good faith for legitimate use. You must use it only for lawful purposes and in a way that does not misuse the Service, harm others, or put BAYTON, any platform or any third party at risk. ## 5. Prohibited use You must not use the Service, or any device or policy you manage through it, to do, enable or facilitate any of the following, including by using it to look up, reach or deliver the content or services described: - Anything unlawful, or that delivers, promotes or facilitates unlawful content or activity. - Pornographic, sexually explicit, obscene or other adult content, or any content that is inappropriate for a general audience. - Gambling or betting, including online casinos, sportsbooks and any other gaming for money. - Malware, spyware or ransomware, or any content or service designed to deceive, defraud, phish or harvest credentials or data without informed consent. - Hate speech, or content that incites or promotes violence, terrorism, discrimination or self-harm. - Infringing anyone's intellectual property, including reaching pirated or counterfeit content. - The covert monitoring, surveillance or control of any person without lawful authority and appropriate notice, including harassment, stalking or coercive control. - Filtering devices that are not owned or managed by your organisation, or that belong to people who have not been given the notice the law requires. - Running, offering or sharing the Service as a public or open resolver, or reselling or sublicensing access to it, without our written permission. - Sharing your enrolment key outside your organisation and its EMM, or using it to enrol devices you do not manage. - Any content or conduct that sexualises, endangers or exploits children. This is not tolerated in any form and will be reported to the relevant authorities. - Abusing the Service itself, including generating query volumes beyond normal use for your fleet, attempting to overload, probe, scan, reverse engineer, circumvent limits on, or gain unauthorised access to the Service or the systems behind it, or interfering with other organisations' use of it. - Breaching applicable sanctions, export controls or trade restrictions. These restrictions apply to how your organisation's devices use the Service, whatever your policy blocks or allows. Using a policy to block this content is a permitted use. ## 6. Limits Every organisation has a device limit. For organisations created through sign-up it is set from the fleet size you give, with some headroom for replacements; for others we set it with you. Rate limits apply to queries, connections and enrolment. Separate limits apply to the number and size of the policies an organisation stores, whatever its device limit. Registrations that have not been revoked and have had no accepted report or enrolment for 30 days are retired automatically in batches under the Service's current configuration, which frees their seats; this does not erase every record about a device at that moment. You can ask for more seats by contacting support. We may change limits to keep the Service available to everyone. ## 7. Availability and changes The Service is provided on an "as is" and "as available" basis. We do not guarantee that it will be available, uninterrupted or error free, and we give no uptime or service level commitment. Android's Private DNS, when set to a specific hostname, uses that server and does not fall back to another resolver. If a device cannot reach the Service, for example on a network that blocks TCP port 853 or during an outage, lookups that use the Service fail until the device reaches the Service again. Moving to another network or changing the setting through your EMM may restore them. Plan for this before you roll the Service out. We may change, limit, suspend or withdraw any part of the Service, or the whole Service, at any time. Where we can, we will give reasonable notice of a planned withdrawal so you can switch your devices' Private DNS setting first, but we cannot promise to. ## 8. What filtering does and does not do The Service filters lookups made through the device's system resolver. It does not filter apps that use their own encrypted DNS, connect to IP addresses directly or use hard-coded addresses, and cached answers may outlast a policy change. Blocking known encrypted DNS services narrows this but is not complete. A policy change takes effect once devices on that profile have reported it and the Service has published it. That depends on Android running the app, which it may delay, and on what the profile's other devices report, so it is not immediate. The Service is a filtering tool, not a guarantee. It does not replace your own safeguarding, security or compliance controls, and you should not rely on it as the only measure that keeps any person safe. ## 9. Review, suspension and removal We review new organisations after they are created, and very large fleets need our approval before an organisation is created. We may decline a sign-up, and may restrict, suspend or remove an organisation, at our discretion and with or without notice, where we reasonably believe that these Terms have been breached, that the Service is being used outside the scope in section 2 or abused, or that continued use may expose BAYTON, any platform, any user or any third party to legal, security, operational or reputational risk. Suspension or removal causes the Service's resolvers to refuse that organisation's lookups once they receive the change. A resolver cut off from the rest of the Service may keep serving the last policy it had until it reconnects, so this is not an immediate cut-off on every resolver. Refusal affects lookups that use the Service as described in section 7. Where we believe use is unlawful, we may report it to the relevant authorities. ## 10. Codes and keys Your enrolment key lets devices join your organisation. Your management code, with your tenant ID, lets you manage the organisation, including rotating the enrolment key, seeing your devices and deleting the organisation. Both are shown once and are not emailed. Keep them safe and share them only with the people and systems that need them. If you lose them, contact support; we may need to confirm that you are entitled to the organisation before helping. You are responsible for anything done with your codes until you tell us they have been compromised. ## 11. Intellectual property BAYTON, or its licensors, own the Service and the BAYTON name and branding. Nothing in these Terms transfers any of those rights to you, and you may not use the BAYTON name or branding without our permission. The Service includes open-source components, which remain subject to their own licences. Your policies and configuration remain yours. ## 12. Data and privacy **What we hold about your organisation.** The details you give at sign-up (your name, organisation, work email, intended use and fleet size), the version of these Terms you accepted and when, and records of actions taken on the organisation. Sign-ups that are never verified are deleted within about 90 minutes of starting. A verified application waiting for our approval is kept for up to 7 days, and an approved one for up to 7 days more if it is not completed. We review the intended use you gave each year and delete it after 12 months. **What we hold about devices.** For each enrolled device: an installation identifier generated by the app and a device identifier generated by the Service, its public key, its attestation result and the reasons for it, when it registered and last reported, its profile, whether it has been revoked, and the policy it reports (as received, in normalised form, and as fingerprints). We do not ask for or store the names of the people who use the devices. **DNS lookups.** The resolvers answer lookups from your devices and forward the ones they do not block to an upstream DNS-over-TLS provider to resolve them. The offered providers are Cloudflare (the default), Google Public DNS and Quad9. Your organisation can select an offered provider for each profile. We do not keep a log of the names your devices look up. We keep aggregate counters, such as the number of queries answered, to run the Service. Each upstream provider handles the lookups it receives under its own terms and privacy policy, which are published on its website. **Network addresses.** We use the network address a request comes from to apply rate limits. Raw addresses are kept only for as long as the relevant rate limit needs them, at most 24 hours; shortened or pseudonymous forms used for rate limiting are kept for at most 30 days; security audit records are kept for 90 days and then deleted in routine cleanup, apart from the minimal deletion record described under Deletion. Copies in encrypted backups expire within 30 days. **Deletion.** When you delete your organisation, we erase its contact and sign-up details and its management code verifier from the Service once the deletion is complete, and resolvers refuse its lookups once they receive the change (see section 9). We keep a minimal record that the organisation existed and was deleted, without personal details, so that it cannot be brought back by mistake. Copies in encrypted backups expire within 30 days. **Your responsibilities.** Do not put personal data in your policies or in the intended-use field. You are responsible for any notice your organisation must give to the people who use the devices. ## 13. Ending your use You can stop using the Service at any time by removing the Private DNS setting and the Managed DNS app through your EMM, and you can delete your organisation from the Dashboard. Remove the Private DNS setting from your devices before you delete the organisation, or lookups that use the Service on those devices will fail (section 7). ## 14. No warranty To the fullest extent permitted by law, the Service is provided without warranties of any kind, whether express or implied, including any implied warranties of satisfactory quality, fitness for a particular purpose, or that it will block or allow any particular domain. ## 15. Limitation of liability To the fullest extent permitted by law, BAYTON will not be liable for any loss or damage arising out of or in connection with your use of, or inability to use, the Service, including loss caused by DNS being unavailable on your devices, by content that was not filtered, or by content that was blocked, and including any indirect or consequential loss, loss of data, loss of profit or business interruption. Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under applicable law, including liability for death or personal injury caused by negligence, or for fraud. ## 16. Changes to these Terms We may update these Terms from time to time. The current version is always published at this page, with the date last updated shown above, and the sign-up form records which version you accepted. Your continued use of the Service after a change means your organisation accepts the updated Terms. ## 17. Governing law These Terms, and any dispute or claim arising out of or in connection with them, are governed by the laws of England and Wales, and are subject to the exclusive jurisdiction of the courts of England and Wales. ## 18. Contact For any question about these Terms, to report misuse of the Service, or for support with your organisation, contact: BAYTON - a community project at bayton.org project-support@bayton.org

BAYTON Managed DNS