Refund Policy

Last updated 7 August 2026

Transfers are charged from service credits. This page explains when you are charged, when you are not, and what happens to money that is already in the system.

1. You are only charged for successful transfers

When you start a transfer, the estimated cost is held against your credit balance rather than spent. What happens next depends on how the job ends:

• The job succeeds — the hold is captured. You are charged for the bytes actually transferred, not for the size the source claimed.
• The job fails — the entire hold is released back to your balance automatically. You do not need to ask.
• You cancel before delivery starts — the hold is released in full.
• You cancel after delivery has begun — the bytes already written to your destination are charged; the remainder is released. Those bytes have been delivered and cannot be taken back.

Every one of these movements appears on your Credits page as a ledger entry, so the arithmetic is auditable rather than something you have to trust.

2. Credit top-ups

Purchased credits are non-refundable and cannot be withdrawn as cash, as set out in the Terms of Service. They remain available to spend on the service.

We will refund a top-up to the original payment method where the charge was duplicated, where it was unauthorised, or where a technical fault on our side prevented the credits from being issued. Contact [email protected] within 30 days.

3. Subscriptions

Subscriptions renew monthly and can be cancelled at any time from your profile. Cancelling stops the next renewal; it does not refund the current period, which remains usable until it ends.

If you cancel within 14 days of a first subscription and have not materially used the paid storage, contact us and we will refund that first period.

4. What is not refundable

• Transfers that completed successfully, including ones where you later decided you did not want the file.
• Charges arising from limits published on the pricing page — for example a job that cost more than expected because the source served more data than it declared. The transfer stops at the amount held, so this is bounded.
• Credits remaining on an account terminated for breach of the terms.
• Loss of files stored on a tier documented as temporary. Free Beta storage is deleted after 7 to 30 days by design.

5. Failures caused by a third-party service

If a source or destination provider is unavailable, rate-limits us, or revokes an authorisation mid-transfer, the job fails and the hold is released in full. You are not charged for our inability to reach someone else’s service.

6. Chargebacks

Please contact us before opening a dispute with your bank — most billing questions are resolved faster directly, and the ledger gives us a complete record of what happened. Accounts with an open chargeback may be suspended until it is resolved.

7. Contact

Billing questions: [email protected]. Include the job ID from your transfer history where relevant.