Delivery and updates

Getting the source

Before payment, your offer states the declared business country, GitHub recipient, agreed sources, licence and catalogue price. Stripe Checkout records the purchasing business and billing details, final amount, taxes and currency. Confirmed payment starts delivery of the agreed sources through GitHub Read access for that account. GitHub can grant access directly or send an invitation. Accept the invitation if GitHub requires one to access the repository. Repository access and eligible corrective updates end twelve calendar months after confirmed payment. The licence takes effect only after both confirmed payment and accessible delivery.

Access period and reminder

Dates use UTC. Access and eligible updates end at the same UTC time twelve calendar months after confirmed payment. If the anniversary month has no matching day, its last valid day is used; 29 February becomes 28 February. Alto Brio sends you a reminder thirty UTC calendar days before expiry. During those thirty days, you can obtain the latest version you were entitled to acquire. Outages and any legally required extension are assessed separately.

Corrective releases

Each eligible corrective release identifies its source version and includes release notes and migration instructions. You choose your updates, then apply and verify them in your application. There is no promised number of releases or commitment to supply major-version upgrades. Alto Brio does not promise custom features, automatic merges or individual project assistance.

Repository history and your copies

While you have repository Read access, you can see its available shared history. Your access to the repository ends with your commercial access period. Removing access prevents new downloads and can cause GitHub to delete private forks; it does not erase copies already downloaded. After expiry, you may still use versions lawfully acquired under their licence. Keep a lawful local copy and your accepted terms.

Refund requests and settlement

For a payment error, delivery problem or another refund request, contact contact@altobrio.com or Link transaction support. Alto Brio assesses goodwill requests individually; mandatory remedies and Stripe’s refund rules remain applicable. An ordinary request needs no project source, application-user data, card details or credentials. The source licence governs the effects on your own kit rights and the rights already granted for delivered applications.

A full refund returns the full amount actually paid, including charged taxes, with no deduction for payment fees. A refund request or confirmation that it was processed does not mean the funds have reached your bank account. Stripe and the payment institution handle settlement and any currency conversion. Timely claims under your accepted terms remain valid.

Security issues

If Alto Brio withdraws a release because of a security issue, it identifies the affected version, explains the reason and states the available remedy. You can distinguish a correction from your acquired version: it has its own release identity, and your acquired archive is not silently replaced. Report a suspected original-kit security issue to contact@altobrio.com with the kit version, affected component and a brief description or minimal example. Do not send credentials, client source code or application-user data.