Terms of service
TL;DR: Use CookieVault for any lawful purpose on unlimited devices. Don’t phish, impersonate, attack the service, or resell our hosted plan as your own. The service is provided as-is, our liability is capped at 12 months of fees or US$50, and the open-source code is governed separately by the MIT license.
Terms of service are the contract that sets out the rules for using a hosted product — your rights, the limits on those rights, and how disputes are handled. CookieVault’s terms govern the hosted service (the website, accounts, and Pro/Team sync), while the open-source code is governed separately and more permissively by the MIT license, so self-hosters get broader freedoms than the hosted-service rules alone would imply.
Your rights
In short: Use CookieVault broadly and freely — unlimited devices, commercial use, self-hosting, and forking under MIT. The hosted service adds convenience (sync, history, team features); the code gives you independence.
What you are explicitly permitted to do:
- Install and use the extension on unlimited personal and work devices
- Use CookieVault for commercial development, QA, and privacy work
- Enable end-to-end encrypted sync on a Pro or Team plan
- Self-host the sync server from the open-source code
- Fork, modify, and redistribute the code under the MIT license
- Export your data at any time in an open format
- Cancel at any time, with a 30-day money-back guarantee on first purchase
What you may not do
In short: No phishing, impersonation, fraud, unauthorized access, or attacks on the infrastructure, and no reselling our hosted service as your own. Acceptable-use limits like these are standard; cookie tooling is dual-use, and these rules draw the line at illegal or abusive use.
| Prohibited use | Why it is prohibited |
|---|---|
| Phishing, impersonation, or fraud | Illegal and harms users |
| Accessing accounts you don’t own | Unauthorized access is unlawful in most jurisdictions |
| Circumventing paywalls unlawfully | May breach the publisher’s terms and applicable law |
| Attacking or overloading the sync API | Threatens availability for everyone |
| Reselling our hosted Pro/Team service | The MIT code is yours to host; our service is not yours to resell |
Cookies are dual-use infrastructure: the same export feature that helps a QA engineer capture a test fixture could, in the wrong hands, move a stolen session. These rules exist to keep the lawful, legitimate uses open while drawing a clear line at abuse.
Liability
In short: The service is provided “as is.” Our total liability for any claim is capped at the greater of the fees you paid in the prior 12 months or US$50. Liability caps like this are normal for software services and keep a small independent team viable, without waiving non-waivable consumer rights.
The limitation, stated plainly:
- The service is provided as is and as available, without express or implied warranties
- Our aggregate liability is capped at the greater of (a) fees you paid in the prior 12 months or (b) US$50
- We are not liable for indirect, incidental, or consequential damages to the extent the law permits
- Nothing here removes rights that consumer-protection law makes non-waivable in your jurisdiction
Changes
In short: We give at least 30 days’ notice of material changes and email subscribers. Using the service after the effective date means you accept the new terms; if you disagree, cancel and export before then.
How changes work:
- We draft the change and set an effective date at least 30 days out
- We post the updated terms with a visible change summary and a new
lastUpdateddate - We email Pro and Team subscribers directly
- You may accept by continuing to use the service, or decline by cancelling and exporting before the effective date
Governing law and disputes
In short: The governing-law and arbitration details are being finalized with counsel and shown here as placeholders. Small-claims actions and intellectual-property claims are excluded from any arbitration requirement.
Governing law and venue will be specified in the counsel-reviewed version. Disputes will be resolved by binding arbitration, except that either party may bring an individual action in small-claims court, and either party may seek injunctive relief for intellectual-property claims. The MIT license, which carries its own disclaimer of warranty, governs any dispute about the open-source code itself.1
See also
- Privacy policy — what we collect and your data rights
- Security — how sync data is encrypted end-to-end
- No-sale pledge — our binding commitment never to sell data
- Pricing — Free, Pro, and Team plans and the refund window
Footnotes
-
The MIT license text and its warranty disclaimer are published by the Open Source Initiative: https://opensource.org/license/mit. ↩