Privacy Policy

1. Our approach

buckets.ninja is operated by Moula World LLC, which is the controller of the personal data described here; full company details are on the imprint. This policy explains what information we handle when you use the website, the customer portal, and the storage API at s3.buckets.ninja, and why. It should be read alongside our Terms of Service and Acceptable Use Policy.

Our guiding principle is data minimisation: the less we collect, the less there is to lose, leak, or ever be asked to hand over. We do not require your name, your address, or any identity document, and we do not try to work out who you are behind your email. Where we can avoid collecting something, we do.

2. Information we collect

Account. A single email address. It is used to sign in, to recover your account, and to send essential service notices such as low-balance warnings and overdue invoices. You may use any address you control, including an alias or a masked address.

Wallet and billing. A ledger of your top-ups and charges in Euros, the payment method used, and the invoices we raise. When you top up by cryptocurrency, card, or PayPal, the payment is processed by a third-party payment provider (see section 5); we receive confirmation that a payment succeeded and its amount, but we do not store your card number or wallet addresses on our systems.

Operational metadata. Running an S3 platform necessarily produces technical records: the IP address a request comes from, timestamps, the operation performed (for example a PUT or GET), the bucket and object key, response size and status, and aggregate per-account counters used for metering and billing. These are inherent to operating and securing the service and to charging you correctly.

The data you store. The objects you upload and their names are yours. They are encrypted at rest (see section 7). We do not index, scan, or inspect their contents, except where strictly necessary to protect the service, investigate a specific abuse report, or comply with a valid legal obligation.

Support. If you open a ticket, use live chat, or send the contact form, we keep what you write and the email address you use, so we can help you and keep a record of the exchange.

3. Cookies and anti-abuse

We use only strictly-necessary cookies: a session cookie that keeps you signed in, and a security cookie that protects forms against cross-site request forgery. There are no advertising or analytics cookies, and there is no consent banner to click through because there is nothing non-essential to consent to.

To keep automated abuse off the sign-up and contact forms we use hCaptcha. When a captcha is shown, hCaptcha receives your IP address and basic request information in order to tell a human from a bot. This happens only on those forms.

4. Security and encryption

Data in transit is protected with TLS. Data at rest is encrypted twice over: the underlying disks are full-disk encrypted, and each stored object is additionally encrypted by the storage layer. The disk encryption keys are not stored on the storage machines, so a lost or seized drive is unreadable.

Because we manage the object-encryption keys so that we can serve your data back to you on demand, we are technically capable of reading object contents. We do not do so outside the narrow circumstances in section 2. If you require a guarantee that goes beyond our word — true zero-knowledge storage — encrypt your data on your own machine before uploading, or use client-side (SSE-C) encryption where you hold the key. Both are fully supported, and we recommend them for anything sensitive.

5. Lawful access and disclosure

We comply with valid legal process from authorities with jurisdiction over us. We do not, however, give any party bulk or standing access to customer data, and we do not volunteer information absent a lawful obligation to provide it.

6. How long we keep it

Account and wallet records are kept for as long as your account is open, and, after closure, for the limited period we are required to retain billing and accounting records by law. Objects you delete are removed permanently and are not held in any backup. If an invoice remains overdue for 7 days, the associated buckets and their contents may be permanently deleted, as described in the Terms.

Operational logs that contain IP addresses are kept only as long as they are useful for security, troubleshooting, and billing reconciliation, and are then discarded. Support conversations are kept while they remain relevant to your account.

7. Your rights

You can change your account email, delete any or all of your data, and close your account entirely. On request we will tell you what account information we hold about you and, subject to the retention obligations above, delete it.

Depending on where you live you may have additional statutory rights over your personal data, including the right to lodge a complaint with your local data protection authority. We will honour valid requests to the extent the law requires.

8. Children

The service is not directed to anyone under 18, and you must be at least 18 to hold an account.

9. Changes and contact

We may update this policy as the service evolves; the effective date at the top will change and material changes will be reflected here. Continued use after an update means you accept the revised policy.

Questions about privacy, or a request concerning your data: [email protected].