Terms of service
Status of this document
These terms are published in good faith and have not been reviewed by qualified legal counsel. They deliberately make no commercial commitment: pricing, purchase terms, refunds, support levels and service guarantees for the paid tier are not settled here. Anything of that kind will be issued separately, after review, before the first paid licence is sold. See section 7.
1. What these terms cover
They cover two things: this website, and SkimMail as it is published by LyQuyDuong — the binaries, the container images and the licence under which it is made available.
They do not govern any particular installation of SkimMail. If you are using a SkimMail instance that somebody else runs, your relationship is with that operator, and whatever terms they have set apply between you and them.
2. There is no SkimMail service
LyQuyDuong distributes software. It does not host SkimMail for anyone, does not operate a hosted or managed edition, and has no account system. Nothing on this site is an offer of a service, and no uptime, availability or support commitment is made or implied anywhere on it.
The practical consequences for personal data are set out in the privacy policy, and the short version is that LyQuyDuong receives nothing from any installation.
3. The software licence
SkimMail's source code is licensed under the Business Source License 1.1. That licence, and not this page, is the operative grant — where the two ever appear to differ, the licence text governs. Read it in full in the repository.
SkimMail's own LICENSE file is the text that governs. Other projects
using a licence of the same name set its parameters differently, so do not read
this summary against a copy obtained elsewhere.
In summary, and without replacing the text:
- You may copy, modify, create derivative works from, redistribute and make non-production use of SkimMail.
- You may use it for your own internal purposes, including inside a commercial organisation.
- You may not offer it to third parties on a hosted or embedded basis in a way that competes with LyQuyDuong's own products or services — in particular, you may not run SkimMail, or a substantially similar email reader, as a SaaS, cloud or embedded offering for other people.
- On 2030-07-23, the Change Date, the same code becomes available to you under the GNU Affero General Public License v3.0 or later.
The Business Source License is not an Open Source licence today. The project says so plainly rather than describing itself as open source.
4. If you run an instance
Installing SkimMail makes you the operator of that instance, and a number of things become yours rather than the publisher's. This is not a disclaimer dressed up as a feature; it is what self-hosting means.
- You are the data controller for the mail, credentials and settings in your instance, and for any other person's mail you connect to it. Telling those people, and honouring their data-protection requests, is your obligation.
- You secure the instance. Master-key handling, the unlock secret, network exposure, TLS, backups and their encryption, and keeping the software updated are all under your control and none of them under the publisher's.
- You keep your own backups. The software can make encrypted snapshots; whether they exist, where they go and whether they restore is yours to verify.
- You comply with your mail provider's terms and with the law where you operate. Connecting a mailbox you are not entitled to read is not something the software can prevent, and doing so is a breach of these terms.
5. Your mail provider, and your own OAuth application
SkimMail reads mailboxes that other people operate. Those providers — Google, Microsoft, or whoever runs your IMAP server — are independent of LyQuyDuong, and their terms and privacy policies continue to apply to your mailbox in full.
If you connect Gmail or Outlook over OAuth, you register your own application with that provider; SkimMail ships no shared OAuth client. That application is yours: its consent screen, its authorised domains, its verification status, its usage limits and its compliance with the provider's developer policies are your responsibility, and LyQuyDuong has no visibility of or control over it. Where Google is concerned, the Google API Services User Data Policy and its Limited Use requirements apply to you as the developer of that application; the privacy policy sets out how the software behaves so that you can meet them.
6. No warranty, and limitation of liability
These follow the Business Source License's own terms, restated here so that they are not a surprise:
SkimMail is provided on an "as is" basis. LyQuyDuong disclaims all warranties and conditions, express, implied, statutory or otherwise, and specifically disclaims any implied warranty of merchantability, fitness for a particular purpose, and non-infringement.
In no event will LyQuyDuong be liable to any party for any damages of any kind — including direct, indirect, special, incidental, punitive or consequential damages — arising out of the use of or inability to use SkimMail, even if it has been advised of the possibility of such damages.
Nothing here excludes or limits liability that cannot lawfully be excluded or limited — in particular liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or under any mandatory product-liability or consumer-protection rule that applies where you are.
7. Paid tiers — not covered here
Community Edition is free and needs no licence key. Sponsor and Pro licence keys are verified offline by the software itself; no licence server is contacted, and a key expiring never deletes, hides or locks data you already have.
Beyond that, this page makes no commercial commitment of any kind — no price, no term, no renewal, refund, support or service-level promise. Commercial terms for Sponsor and Pro are a separate document, not yet issued and still under legal review. They will be provided in writing before any paid licence is issued, and once issued and agreed they govern the paid tiers — this page does not.
8. The SkimMail name
"SkimMail" identifies this project and its official distributions, and the name is not covered by the source code licence. There is no registered trademark; this is a lightweight, good-faith notice rather than an enforcement posture.
- If you publish a fork or derivative, please choose a different name, so nobody is confused about where support, security fixes and official updates come from.
- Referring to the project by name — "built on SkimMail", "based on SkimMail", comparisons, compatibility statements — is fine and welcome. This is about brand identity, not about restricting mention of the project.
9. Contributions
Contributions are welcome and are accepted under a Contributor License Agreement,
published in the repository as CLA.md. In short: you keep your
copyright, and you grant LyQuyDuong a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable licence to use your contribution in SkimMail and to
sublicense it under the project's current or future licence, including AGPL-3.0+
after the Change Date, together with a licence to any patent of yours that your
contribution necessarily infringes. Please email
skimmail@base101.app before writing
code, so the change can be discussed first.
10. This website
These three pages are static files. They set no cookies, load nothing from a
content delivery network, and carry no analytics or tracking. They are provided
for information, and the repository's wiki is the authoritative source for
technical detail. Two exceptions: the LICENSE file governs the licence
grant, and the privacy policy on this site is the
operative privacy statement for SkimMail.
11. Changes, and contact
These terms may be updated; the "last updated" date above changes when they are.
A change applies to your use of this website from the date it is published. It does
not change the licence under which you received a copy of the software: that is the
LICENSE shipped with the release you have.
Questions about these terms: skimmail@base101.app. Security reports should go to the same address and follow the repository's security policy rather than a public issue.