Legal information
Company details, an index of every document that governs a Serverlys service, and the order they take precedence in when two of them appear to disagree.
In effect from
Company details
Serverlys, LLC operates this website and the services described on it. Correspondence about any of the documents listed below reaches us at Support@serverlys.com or on (305) 671-1272.
For anything requiring formal service of process, write to us first and we will confirm the correct address for service. Do not rely on an address scraped from a directory.
Every document, grouped
Agreements bind both of us. Policies bind us. Each entry says what that document decides and when its current version took effect, so you can tell which one answers your question without opening four of them.
Agreements
Documents you enter into with us. These bind both sides.
- Terms of serviceThe agreement covering every service you buy from us, and the one the others sit under.
- Domain registration agreementRegistering, renewing and transferring a domain, and which obligations sit with the registry rather than with us.
- Data processing agreementWhere you are the controller and we are the processor: what we may do with the personal data your site handles, and what we must do if it is breached.
- AI services termsThe terms specific to ConvoAI and CallFlow: who owns the conversations, what the models are and are not trained on, and what an automated agent must never be relied on to do.
Policies
How we operate. These bind us.
- Privacy policyWhat personal data we hold, why we hold it, and what you can ask us to do about it.
- Cookie policyEvery cookie this site sets, what it does, and how to refuse the optional ones.
- Refund policyThe 30-day hosting guarantee, why domain registrations sit outside it, and the three exceptions.
- Acceptable use policyWhat you may not run on our platform, and what happens to an account that does.
- Abuse handling policyWhat we do with an abuse report once you send it — who reads it, how fast, and what we can and cannot do about it.
- Copyright and DMCA policyHow to send a takedown notice that we can act on, how a customer files a counter-notice, and what each of those obliges us to do.
- Information security policyThe controls we operate — access, encryption, backups, logging — and what we commit to doing when one of them fails.
- Responsible disclosure policyHow to report a vulnerability to us, what is in scope, and our undertaking not to pursue researchers who follow it.
- Customer service policyHow to reach support, what we aim to respond in, and what we will not do — including the retention scripts we do not run.
- Law enforcement and legal requestsWhat we require before disclosing customer data to an authority, and when we will tell the customer it happened.
- Accessibility statementThe conformance target for this website, what we know is not yet meeting it, and how to report a barrier.
Company
Who we are, and how to reach us formally.
Which document wins
Where two of these appear to say different things, they apply in this order. This is the one question a reader can only answer from a page like this, which is why it is stated here rather than left to be inferred.
- ICANN and the relevant registry's own policies, for anything concerning a domain name
- The terms of service
- The specific agreement for the service in question
- The specific policy for the matter in question
- Anything written on a product or marketing page
Marketing copy is last for a reason. A sentence on a product page describing what a plan does is a description; it is not a term, and it cannot quietly grant you something an agreement withholds or take away something an agreement gives you.
Where to send a formal notice
Each of these has its own document setting out exactly what a notice must contain. They are not restated here — a statutory procedure described in two places is a procedure that will eventually be described two different ways.
- Copyright infringement — the copyright and DMCA policy lists the six elements a notice needs under 17 U.S.C. § 512(c)(3), and the counter-notice route.
- Law enforcement, subpoenas and court orders — the law enforcement and legal requests page sets out what we require before we disclose anything, and when we tell the customer.
- Phishing, malware, spam and other abuse — use the abuse report form. The abuse handling policy explains what happens to it afterwards.
- Security vulnerabilities — the responsible disclosure policy, which also carries our undertaking not to pursue researchers who follow it.
Trademarks and brand use
The Serverlys name, wordmark and the ConvoAI and CallFlow product names are ours. You may use them factually — to say that you host with us, that you are comparing us, or that you are writing about us — without asking.
You may not use them in a way that suggests we endorse, partner with, or supply something we do not, and you may not use them in your own product name, domain or company name.
Third-party names elsewhere on this site — hosting platforms we migrate from, software we support, providers we compare against — belong to their owners and appear for identification only. Their appearance is not a claim of affiliation in either direction.
Third-party services
Parts of what we sell depend on third parties: domain registries, certificate authorities, payment processors, infrastructure providers and the model vendors behind our AI services. Their terms apply to their part of the service, and we cannot waive them on your behalf. Where one of them changes a fee or a policy in a way that affects you, we pass on the change and tell you rather than absorbing it silently.
Changes to these documents
Each document carries the date its current version took effect, shown at the top of the document and beside it in the index above.
Where we make a change that materially affects your rights or what you owe, we tell account holders rather than relying on you to notice a changed date. Corrections that do not change the substance — a typo, a clearer sentence, a fixed link — are made without notice.
Questions about this document
If you cannot tell which document covers your question, ask us rather than reading all of them. Pointing you at the right clause is faster for both of us.
Write to Support@serverlys.com.