Terms and Privacy vss.mineracks.com
Plain-language terms for the public VSS endpoint run by mineracks Pty Ltd (Brisbane, Australia). Effective 2026-09-17. By sending requests to vss.mineracks.com you accept them.
Terms of service
1. What the service is
A Versioned Storage Service (VSS) endpoint implementing the LDK VSS protocol. It stores the opaque values your wallet software sends, keyed by the secp256k1 public key your software proves on each request, and returns them on demand. It is intended for non-custodial Lightning wallets and their operators. We never hold Bitcoin, keys or funds; VSS is storage, not custody.
2. Public beta, no SLA
The service is offered as a public beta, as-is, without a service-level agreement. We aim for high availability and back the data as described below, but we do not promise uptime, latency or durability, and we may change limits, suspend, or discontinue the service. Where we can, we will give notice on this page and at the contact address below. If you rely on this endpoint as a wallet's primary store, keep a second store or a second provider; the protocol is designed for that.
3. Your responsibilities
- Encrypt what you store. The protocol expects client-side encryption; we treat everything you send as opaque bytes and cannot recover plaintext for you.
- Keep your keys. Access is by proof of a private key. If you lose it, nobody, including us, can retrieve or delete that data on your behalf.
- Stay within the published limits (request size, rate, connections) on the front page and at
/info. Exceeding them returns errors, not silent truncation. - Do not use the service to store or distribute unlawful content, to attack the service or others, or to probe it beyond ordinary client behaviour without asking first.
4. Acceptable use and enforcement
We may rate-limit, block or remove any tenant that abuses the service, harms other users, or exposes us to legal risk, without notice if necessary. We do not inspect stored values; enforcement is based on request behaviour and metadata.
5. Liability
To the extent permitted by law, mineracks Pty Ltd is not liable for any loss arising from use of, or inability to use, the service, including loss of data or funds. Nothing here excludes rights you have under the Australian Consumer Law that cannot be excluded. Where liability cannot be excluded, it is limited to re-supplying the service.
6. Changes and law
We may update these terms; the effective date above changes when we do. These terms are governed by the laws of Queensland, Australia, and disputes go to its courts. If you want a written agreement with an SLA, contact us.
Privacy notice
What we hold
- Stored objects. For each tenant: the public key you authenticate with, a store identifier, key names, the values you upload, version numbers and timestamps. Values are ciphertext produced by your software; key names are obfuscated by LDK clients by default. We cannot read either.
- Request logs. The front-end web server logs each request's client IP address (as passed to us by Cloudflare), path, timestamp, response code and user agent. These logs live on the server, rotate automatically (about 100 MB retained in total, typically a few days of traffic), and are not shipped elsewhere.
- Edge logs. Requests pass through Cloudflare, which processes connection metadata under its own privacy policy.
- Backups. The database is continuously archived, encrypted, to a backup host we control in Australia and mirrored, still encrypted, to object storage at a second provider. Backups are kept on a rolling schedule of roughly five weeks.
We do not use cookies, analytics or trackers on this site. The front page makes one request to /healthz to show live status.
Why we hold it
To provide the storage you asked for, to keep the service reliable (backups), and to protect it from abuse (request logs and rate limiting). We do not sell or share this data, and we do not use it for anything else.
Deleting your data
Your software can delete its own objects through the protocol at any time; deletions take effect immediately in the live database and age out of backups on the schedule above. Because access is by key and not by identity, we cannot act on deletion requests by email for a tenant we cannot verify. If you can sign a message with the tenant's key, contact us and we will help.
Disclosure
We disclose data only where the law requires it. Because stored values are ciphertext we did not produce, what we could disclose is the metadata listed above.
Contact
mineracks Pty Ltd, Brisbane, Australia · [email protected]