Glac Terms of Service
Last updated: 28 October 2026. Effective from: 28 October 2026.
1. About these Terms
1.1 These Terms of Service (“Terms”) are a contract between you and GLAC PTY LTD, a company registered in Australia (ACN 680 390 130, ABN 27 680 390 130, registered address 5 Kalimna Ave, Campbelltown SA 5074, Australia) (“we”, “us”, “our”). They cover Glac: the website at glac.ai, the console, the API, our command-line tool, SDKs and MCP server, and everything you create with them (together, the “Service”).
1.2 If you accept these Terms for a company or another organization, you confirm that you may bind it, and “you” means that organization.
1.3 These documents are part of the contract:
- (a) the pricing page at https://glac.ai/pricing (the “Pricing Page”), which sets out prices, plan fees, included quantities and plan limits;
- (b) the Privacy Policy at https://glac.ai/privacy;
- (c) the Data Processing Agreement at https://glac.ai/dpa (the “DPA”), which applies whenever data protection law protects personal data that you put into the Service;
- (d) on Paid, the Service Level Agreement at https://glac.ai/sla (the “SLA”).
If they conflict, the DPA wins on personal data in Your Content, the Pricing Page wins on prices and quantities, the SLA wins on availability and service credits, and these Terms win on everything else.
1.4 You accept these Terms when you create an account or first use the Service.
2. Words we use
- Account: your account on the Service. It has one or more Projects and one or more members. Each member is an owner, an admin or a member; owners control billing and can close the Account.
- Project: a group of resources inside an Account. API keys belong to a Project.
- Sandbox: a virtual machine that we run for you. Each Sandbox is a Firecracker microVM that runs an OCI container image, yours or one we provide. A Sandbox can run commands and keep files, and it can sleep with its memory and disk kept and wake again.
- App: a program from an OCI image that we run as one or more instances behind a domain, adding and removing instances as requests come and go. Each deployment of an App creates a Version. App instances are Sandboxes. Apps are our Cube product.
- Managed Application: a product that we run for you on Cube, such as our Sandbox, Browser and Serverless Postgres. Its instances are Sandboxes.
- Volume: a disk that you can attach to Sandboxes; Volumes are part of our Cube product. Snapshot: a saved state of a Sandbox. Backup: a copy of a Volume at one moment, kept in object storage.
- Logs: what your App instances print, one line for each request your instances receive, and records of what the platform did with your App.
- Your Content: everything that you, your members or your users put into or run on the Service, including images, code, commands and their output, files, disks, memory, Volumes, Snapshots, Backups, environment variables, secrets, Logs, and the requests and responses that your Sandboxes and Apps send and receive.
- Plan: Free, or Paid, our paid Plan.
- Included quantities: the amount of each meter that your Plan includes in each period.
- Credits and balance: see Section 9.
- Region: one of the areas where we run Sandboxes and Apps: North America (
na), Europe (eu) and Asia-Pacific (ap).
3. Who may use the Service
3.1 You must be at least 16 years old. If you are under 18, or under the age of majority where you live, a parent or guardian must agree to these Terms for you.
3.2 We sell to businesses and to consumers everywhere we offer the Service. If you buy as a consumer in the European Economic Area or the United Kingdom, you also have the right to withdraw in Section 21.4.
3.3 You may not use the Service if you are a person, or are in a country or region, that is subject to sanctions administered by Australia, the United Nations Security Council, the United States, the United Kingdom or the European Union.
3.4 Each person who signs up gets one Account of their own. If you need another, ask us. Do not create Accounts to get around limits, included quantities or billing.
4. Your Account
4.1 Give us accurate information, and keep the Account’s email address and billing details up to date. We send notices about your Account to the Account’s email address.
4.2 You must verify your email address before you can create or change anything.
4.3 Keep your password, API keys and sandbox tokens secret. We show an API key only once, when it is created. You are responsible for everything done with your Account, its keys and tokens, and by its members.
4.4 Tell us at once at security@glac.ai if you think someone has used your Account without permission.
5. The Service
5.1 What it does. The Service runs OCI container images in Sandboxes and Apps; keeps data in Volumes, Snapshots and Backups; keeps Logs and can send them to endpoints you choose; and serves your Sandboxes and Apps on preview URLs and default domains under glac.run and on domains that you own.
5.2 How resources behave.
- (a) Sandboxes go to sleep when idle and wake when needed. Their memory and disk are kept while they sleep.
- (b) We create and remove stateless App instances as traffic changes. We remove a stateless instance once it has been idle for the time set on the App (one hour unless you change it), or earlier when its host needs the memory. Anything kept inside a stateless instance is lost when it is removed. Keep data you need in a Volume.
- (c) Sandboxes and keyed App instances stay until you delete them, until a deletion time you have set, or until Section 11 or 18 applies.
5.3 Where things run.
- (a) You can choose the Region of a Sandbox, a Volume or an App. If you do not, a Sandbox or Volume is created in the Region where our control plane runs (North America), and an App runs in every Region.
- (b) If the chosen Region cannot take a new Sandbox at that moment, we create it in the nearest other Region that can.
- (c) If a host fails, we may continue your Sandbox on another host, which may be in another Region.
- (d) Account, billing and usage records are kept by our control plane in the United States, with a standby copy in the United Kingdom. When you read your Logs, they are decrypted on the control plane’s machine.
The Privacy Policy and the DPA give the details.
5.4 Network defaults. Outbound connections to port 25 (email) are blocked by default. Sandboxes have no inbound public IPv4 address: visitors reach them through preview URLs, App domains and your own domains, and you reach them through the API, the console and our SSH gateway. You can restrict a Sandbox’s outbound traffic with egress rules.
5.5 Changes to the Service. The Service changes over time. If we remove a feature you use on Paid, we tell you at least 14 days in advance, unless we must act sooner for security or legal reasons. Features we call beta, preview or experimental are provided as they are and may change or stop at any time.
5.6 Availability. Paid comes with the SLA at https://glac.ai/sla: it sets out how available we keep the Service and the service credits you get if we fall short. Free has no service level agreement. We may interrupt the Service for maintenance and will try to keep interruptions short, and we announce planned maintenance at https://glac.ai/status/.
5.7 Software from others. Images we provide contain software from others: open-source tools and, in our coding-agent image, coding agents such as Claude Code, Codex and OpenCode. Each comes under its own license and terms, which you must follow. See Section 16.6.
6. Plans and included usage
6.1 Every Account is on one Plan. New Accounts start on Free. Paid is a monthly subscription (Section 8).
6.2 Each Plan includes, for each period, a quantity of each meter. On Free, the quantities of Volume data and Volume cache are how much you may keep at any one time, not amounts for each day. Included quantities are not money: they cannot be moved from one meter to another, do not carry over to the next period, are not refunded, and cannot be exchanged for Credits or cash. No Plan comes with Credits.
6.3 On Free, a period is a day (UTC). On Paid, a period starts when the subscription fee is paid and ends at the same day and hour of the next month.
6.4 The meters are:
- CPU: the time your virtual CPUs are busy, in CPU-ms (milliseconds of busy virtual CPU).
- Memory: the memory your Sandboxes and instances hold while awake, in GiB-hours.
- Requests: HTTP requests, and WebSocket connections, that our nodes accept for your Sandboxes and Apps. Requests we refuse ourselves are not counted.
- Volume data: data kept for you by sleeping Sandboxes, Backups, Volumes and Snapshots, measured by the bytes actually stored, over time, in GB-months.
- Volume cache: the part of your Volumes’ data kept on our hosts’ local NVMe disks, up to the cache size you set for each Volume, over time, in GB-months.
- Egress: bytes your Sandboxes and Apps send to the internet (Section 14).
- Logs: what your App instances print and our nodes keep for you, in GB-months: the bytes as printed, not as compressed for storage, for as long as they are kept. Request lines and the platform’s own lines are not counted, nor is output that is not kept. On Free, the included quantity counts the bytes printed each day.
6.5 On Paid, usage beyond the included quantities is charged at the prices on the Pricing Page and paid from your balance. On Free, nothing is charged: a meter stops when its included quantity is used up (Section 7).
6.6 Plans also have limits, for example on the largest Sandbox, how many Sandboxes can be awake at once, how fast you can create them, how many Apps, Volumes, secrets and Log export endpoints you can have, and how long Logs are kept. The current limits are on the Pricing Page[ and in our documentation at https://glac.ai/docs/]. Some can be raised on request.
6.7 We bill from the same usage records that you can read through the API and the console, so you can recompute every line of your bill.
6.8 A change to usage prices applies from the first calendar month that starts after the change takes effect. A change to a Plan’s fee or included quantities applies from the first period that starts after it takes effect. We give at least 14 days’ notice of any increase.
7. When included usage runs out
7.1 On Paid, if you have a balance, usage beyond the included quantities continues and is paid from it.
7.2 Each meter stops on its own when its included quantity is used up: on Free, whatever your balance; on Paid, if you have no balance and no Auto Reload payment is on its way:
| Used up | What stops |
|---|---|
| CPU or memory | Every Sandbox and App instance in the Account goes to sleep, keeping its data, and no new ones can be created. |
| Requests | Requests from visitors to your Sandboxes and Apps are refused. Your Sandboxes keep running. |
| Egress | Outbound traffic to the internet stops, and requests from visitors are refused because the answers would be egress. Your Sandboxes keep running. |
| Logs | New output from your App instances is no longer kept: you can still read and follow it while it is on the node, but it is not stored for later. Your Apps keep running, and their request lines are kept as usual. |
| Volume data or Volume cache | On Free, you cannot create new Volumes or Snapshots until you keep less. On Paid, neither can stop while data is kept: both keep accruing and are owed (Section 11). |
7.3 Stopped meters restart at our next check after a new period begins, after Credits arrive (on Paid), or after you move to a Plan that gives you more. Output printed while Logs were stopped is not stored afterwards.
7.4 We read usage every few seconds, so a little more may be used after an included quantity runs out. On Free, that usage is not charged. On Paid, any usage in that gap that your balance cannot pay for, other than Volume data and Volume cache, is written off: you do not owe it.
7.5 On Paid, if you have no balance and Auto Reload will not top you up, we email you when a meter reaches 80% and 100% of its included quantity. On Free, a meter that stops shows in your Account’s events and on your bill, and comes back at the next period.
8. Subscriptions
8.1 The subscription fee is charged to your card at the start of each period. It is not paid from your balance and does not become Credits: it gives the period’s included quantities (Section 6.2). The first period starts the moment the first fee is paid.
8.2 Cancelling (moving to Free) takes effect at the end of the period you have paid for. The current period is not refunded.
8.3 If a renewal payment fails, we retry and email you. For a grace period of 7 days, until the fee is paid, your usage counts against Free’s included quantities. If we still cannot collect the fee when the grace period ends, the Account moves to Free. Sandboxes and instances larger than Free allows then sleep, and cannot wake until the Account is on a Plan that allows their size. Nothing is deleted.
9. Credits, top-ups and Auto Reload
9.1 Credits. Your balance is counted in Credits. One Credit pays for one US dollar of usage beyond your included quantities, at the prices on the Pricing Page. Credits are a prepaid right to use the Service: they are not money that we hold for you, not a deposit and not a gift card, and they cannot be withdrawn, exchanged for cash or moved to another Account. Each Account has one balance. Credits are counted before tax; any tax on a top-up is added on top (Section 10).
9.2 Top-ups. You can buy Credits on any Plan. A top-up is at least US$20, in whole cents. Credits are added when we receive the payment. Buying Credits does not change your Plan, and on Free your balance pays for nothing until you move to Paid.
9.3 Auto Reload is off unless you turn it on. When it is on and your balance falls below a threshold you set (5 Credits unless you change it), we charge your saved card an amount you set (US$20 unless you change it). You need a saved card. If a reload fails, we retry once after an hour and email you. On Free, Auto Reload buys nothing.
9.4 Monthly limits. Your Account’s spend limit is the most that Auto Reload may charge in a calendar month. Unless you set it, it is US$50 on Paid, within the limit below, and you can change it. Separately, to protect against stolen cards, an Account can only top up a limited amount each month. The limit rises automatically 30 days and 90 days after your first payment if there have been no payment disputes or fraud warnings, and we can raise it on request. Your current limits are shown on your billing page.
9.5 Expiry. The Credits from each top-up expire 365 days after we receive that top-up. Credits that expire first are used first. We email you 30 days, 7 days and 1 day before Credits expire. If you ask us within 30 days after Credits expired, we can restore them. Credits that we give you, for example as compensation or as service credits under the SLA, expire in the same way unless we tell you otherwise.
9.6 Refunds. Credits are not refundable. Subscription fees are not refunded when you cancel. We refund a payment only if it was charged in error or the law requires a refund, for example when a consumer withdraws under Section 21.4. Nothing in this Section limits a refund that the law gives you.
9.7 If a payment is refunded or charged back, we remove the Credits it bought that you have not used yet (Section 13). Credits already used stay used.
10. Payments, invoices and taxes
10.1 Stripe processes our payments. You enter your card details on pages hosted by Stripe; they do not pass through our servers. We keep the card’s brand, last four digits, expiry date, issuing country, type (credit, debit or prepaid) and the fingerprint Stripe gives us for it, so that we can show you the card, charge it when you have asked us to, and prevent fraud.
10.2 Your first payment may need 3-D Secure authentication. We may refuse a card that already pays for several other Accounts.
10.3 Every charge (a top-up, an Auto Reload, a subscription fee or an amount owed) has an invoice issued through Stripe, and Stripe emails you a receipt. Your monthly statement in the console and the API shows each meter, what was included and what was paid from your balance.
10.4 Prices are in US dollars and do not include taxes.
10.5 Taxes. We are not registered for GST in Australia: our prices include no GST, and we do not charge it. Where we are registered to collect a tax such as VAT, we add it to the invoice, calculated when you are charged. We work out where you are from your billing address, your card’s issuing country and the location of the IP address you pay from. If these disagree, we may ask you to confirm your billing address, and in some cases we hold the Account until we have reviewed the payment. If you give us a VAT, GST or similar tax ID, we have it verified; where the law allows, we then charge no tax and the invoice says that the reverse charge applies. If a tax ID fails verification after we charged you as a business, we may hold the Account.
10.6 You are responsible for any taxes other than those we collect. If the law makes you withhold tax from a payment to us, you must increase the payment so that we receive the full amount.
11. Unpaid storage: debt and deletion
11.1 Only storage (Volume data and Volume cache) can take your balance below zero, because kept data keeps costing while it is kept (Section 7.2). If you owe less than US$0.50, the amount stays on your balance and is paid from your next top-up or added to your next subscription charge, and nothing else happens.
11.2 When you owe US$0.50 or more, your Account is in debt. Until you pay:
- (a) all Sandboxes and Apps are frozen, and requests to them are refused;
- (b) you can only view your Account, usage, events and bills; pay (top up, or change your Plan, spend limit or Auto Reload); change the Account’s email address; list and delete your Volumes, Snapshots, sleeping Sandboxes and Backups, so that the debt stops growing; and make a new Volume from a Backup, which you can attach once you have paid;
- (c) the amount owed keeps growing while you keep stored data.
11.3 We email you when the debt starts and send reminders 7, 14, 21, 27 and 29 days later. On your billing date (the day your subscription renews or, without a subscription, the day of the month your first top-up arrived) we try to charge the amount owed to your saved card.
11.4 If you still owe US$0.50 or more 30 days after the first notice was sent, we delete everything the Account stores: Sandboxes (including App instances), Snapshots, Volumes, Backups, templates built from your images, and Apps with their Versions. We then write off the debt. Deleted data cannot be recovered.
11.5 We keep the Account, its Projects, API keys, secrets, SSH keys, webhooks, domain registrations, events, audit records and billing records, and you can go on using the Account.
11.6 We only delete if our email provider accepted both the first notice and the last reminder. If you pay while deletion is under way, it stops; what was already deleted stays deleted, and nothing is refunded.
12. Spend limits on Projects and Sandboxes
12.1 You can set a spend limit per calendar month (UTC) on a Project or on a single Sandbox. It counts all of their usage at list prices, including usage that your included quantities cover.
12.2 When a limit is reached, the Sandboxes it covers are frozen: they sleep, keep their data and cannot be woken, and a Project at its limit cannot create new Sandboxes, Volumes or Snapshots. Storage cannot be frozen and keeps counting.
12.3 We check limits every few seconds, so usage can go slightly past a limit, and limits are not checked while our control plane is down.
12.4 Raising or removing the limit, or the start of a new month, unfreezes them.
13. Payment disputes and fraud warnings
13.1 If your card’s issuer warns that a payment to us may be fraudulent, or a payment to us is disputed (charged back), we put the Account on hold. While it is on hold, nothing in the Account runs or can be used, and we do not charge your card. Write to support@glac.ai and we will review it.
13.2 For a fraud warning, we may refund that payment at once and remove the unused Credits it bought. If a dispute is decided against us, we remove the unused Credits that the disputed payment bought.
13.3 After review, we release the hold where that is appropriate.
14. Outbound traffic (egress)
14.1 Each Plan includes an egress allowance for each period (Pricing Page). We count the bytes your Sandboxes and App instances send to the internet, every byte of the responses they send to visitors through preview URLs, App domains and your own domains, and the Logs we send to your export endpoints. We do not count inbound traffic, traffic to the shared-volume file service on our nodes, or traffic between your Sandboxes over your private network.
14.2 On Paid, egress beyond the allowance is paid from your balance at the price per GB on the Pricing Page for the Region it leaves from. On Free once the allowance is used, or on Paid when you have no balance, outbound traffic to the internet stops, while your Sandboxes keep running, until a new period starts, Credits arrive (on Paid), or you change Plan. Egress is never slowed down: it is either allowed or stopped.
14.3 You can set your own cap on egress for each calendar month. When the cap is reached, outbound traffic stops in the same way.
14.4 You may not use the Service as a proxy, VPN or exit for other people’s traffic.
15. Acceptable use
15.1 You may not use the Service, or let anyone else use it, to:
- (a) break the law, or help anyone break it;
- (b) store or distribute material that infringes the rights of others, or any material that sexually exploits children;
- (c) distribute malware, run phishing, or control malware or botnets;
- (d) attack, scan, probe or overload systems that you do not own or have no permission to test, including denial-of-service attacks;
- (e) send spam or other unsolicited bulk messages;
- (f) run a proxy, a VPN or an exit for other people’s traffic (Section 14);
- (g) mine cryptocurrency;
- (h) get around Plan limits, included quantities, spend limits, egress stops or billing, for example by using several Accounts or sharing one card across Accounts;
- (i) try to break out of a Sandbox, reach other customers’ data, observe other customers’ activity through shared hardware, or attack our infrastructure. Security research is welcome only under our security research policy at https://glac.ai/security;
- (j) give us, as a secret, in an egress rule or in an environment variable passed through our API, login tokens of a service whose terms forbid third parties to hold them, such as the tokens from logging in with a Claude.ai subscription;
- (k) harass people, or collect or use personal data unlawfully.
15.2 If you let your own users run code or keep files on the Service, for example by giving them Sandboxes, you are responsible for what they do, and you must make them follow this Section.
15.3 If you break this Section, we may remove or disable content, stop egress, freeze Sandboxes and Apps, or suspend or end the Account (Section 18). Where we reasonably can, we tell you first and give you a chance to fix the problem. Report abuse to abuse@glac.ai.
16. Your Content
16.1 You own Your Content. You give us a worldwide, non-exclusive, royalty-free license to host, store, copy, run, transmit and display Your Content, only as needed to provide, secure and support the Service for you.
16.2 We use Your Content only to provide the Service, and we do not sell it. Our staff access Your Content only when you ask us to for support, when it is needed to keep the Service running or secure or to investigate abuse, or when the law requires it.
16.3 You are responsible for Your Content and must have the rights to use it. You are also responsible for the security of the software you run. In our default image, commands run as root inside the Sandbox.
16.4 Keep your own copies of data that matters to you. We copy data to protect it, but we do not promise that it cannot be lost. Snapshots, Backups and Volumes are tools for you to protect your data.
16.5 Secrets and egress rules. We store secrets encrypted and never show their values again. If you add an egress rule that inserts a secret into requests to a host, or that filters HTTP requests to a host, our node ends the TLS connection to that host and opens a new one, so that it can read and change those requests. Your Sandbox trusts our node’s certificate authority for those hosts.
16.6 Coding agents and model credentials. Our coding-agent image includes coding agents made by other companies. We do not supply or pay for access to their models. You bring your own API key or account, you are bound by that provider’s terms, and the provider bills you for your use. If you log in to an agent inside a Sandbox, the agent keeps the login on the Sandbox’s disk, so Snapshots and forks of that Sandbox contain it.
16.7 Deleting. You can delete Sandboxes, Volumes, Snapshots, Backups, Apps and Logs at any time. Section 12 of the DPA sets out what happens to the copies that remain after you delete, and how long each kind lasts; Section 10 of the Privacy Policy does the same for the records about your Account.
17. Personal data
17.1 The Privacy Policy explains how we handle personal data about you, your members and visitors to our website.
17.2 If Your Content includes personal data, you are responsible for having a lawful basis to process it and for telling the people concerned what the law requires. The DPA sets out how we process that data for you. It applies automatically, as part of these Terms, whenever data protection law applies to that processing; you do not need to sign it.
17.3 Do not put personal data in names of Sandboxes, Apps or other resources, in metadata labels, or in other fields not meant for it. Our usage records keep metadata labels for 13 months, even after the Sandbox is deleted.
18. Closing, suspending and ending
18.1 Closing by you. An owner can close the Account from the console at any time, as long as the Account is not in debt, not on hold, and on Free. If you are on Paid, move to Free first; you can close once the paid period has ended. When you close the Account:
- (a) every member is removed, invitations and API keys stop working, and your domains are released for others to register;
- (b) we delete what the Account stores: Apps with their Versions and instances, Sandboxes, Snapshots, Volumes, Backups and templates built from your images;
- (c) we keep what we need for billing, tax, security and legal reasons: the Account and its Projects (closed), usage records, statements, the ledger, charges, audit records and the notices we sent. Secrets, SSH keys, webhooks and shared variables stay stored but can no longer be used. Section 12 of the DPA says what happens to the copies that remain;
- (d) any Credits stay on record until they expire, subject to Section 9.6;
- (e) a closed Account cannot be reopened. Your user login stays; you can delete it yourself in the console (not while you are the only owner of an Account), or write to privacy@glac.ai.
18.2 Suspension by us. We may suspend all or part of the Service for you at once if that is needed to stop a breach of Section 15, to protect the Service, other customers or anyone else, to comply with the law, or because of a fraud warning or a payment dispute (Section 13). In other cases we tell you first.
18.3 Ending by us. We may end these Terms for your Account if you materially breach them and do not fix the breach within [14] days after we tell you, or at once for serious or repeated breaches of Section 15 or where the law requires it. If we stop offering the Service altogether, we will give you at least [90] days’ notice. When these Terms end, Section 18.1(a) to (d) applies.
18.4 Sections 9.6, 10, 11, 16.1 (for Your Content still being deleted), 18, 21, 22, 23, 25 and 26 continue after these Terms end.
19. Support
19.1 The help you get with using the Service depends on your Plan:
| Plan | Support |
|---|---|
| Free | Our documentation at https://glac.ai/docs/ and our community forum at https://github.com/orgs/GlacAI/discussions. |
| Paid | Email support at support@glac.ai, with a first answer within 2 business days. |
19.2 A business day is Monday to Friday, except public holidays in South Australia, Australia. A first answer comes from a person and tells you what we are doing about your request; it may not solve the problem yet.
19.3 Whatever your Plan, you can write to support@glac.ai about your Account, billing, a payment or a hold, and to the addresses in Section 27 about security, abuse, privacy and legal matters.
20. Our property and your feedback
20.1 We and our licensors own the Service, its software and our trademarks. These Terms give you no rights in them except the right to use the Service.
20.2 If you send us feedback or suggestions, we may use them without any obligation to you.
21. Warranties and your rights under consumer law
21.1 We will provide the Service with reasonable care and skill.
21.2 Otherwise, to the extent the law allows, the Service is provided “as is” and “as available”, without any other warranty, including any warranty of fitness for a particular purpose, merchantability or non-infringement, or that the Service will be uninterrupted, error-free or secure, or that data will never be lost.
21.3 Nothing in these Terms excludes or limits any right you have under consumer protection law that cannot be excluded or limited, such as the consumer guarantees under the Australian Consumer Law. Where the law lets us limit our liability for failing to meet such a guarantee, our liability is limited to supplying the services again or paying the cost of having them supplied again.
21.4 Your right to withdraw, if you are a consumer in the European Economic Area or the United Kingdom.
- (a) You may withdraw from a purchase within 14 days without giving any reason. A purchase is a subscription to Paid, or a top-up (including one made by Auto Reload). The 14 days end at the end of the fourteenth day after the day of the purchase. The renewal of a subscription is not a new purchase.
- (b) To withdraw, tell us before the 14 days end. You can do it in the console: on the billing page, each purchase you may still withdraw from is listed with a button labelled “Withdraw from contract here”. The button opens your withdrawal statement, in which you give your name and the email address for our confirmation, and you send it with the button labelled “Confirm withdrawal”. You may also tell us by email to support@glac.ai, with the model form below if you like. We confirm your withdrawal by email without delay, with the date and time we received it.
- (c) When you make a purchase, we ask you to request, by ticking a box, that we start providing it at once, within the 14 days. A top-up made by Auto Reload carries the request you gave when you turned Auto Reload on. If you turned Auto Reload on without giving it (because you bought as a business, or from outside the European Economic Area and the United Kingdom, at the time), Auto Reload buys nothing while you buy as a consumer in the European Economic Area or the United Kingdom, and we tell you by email, until you turn it on again with the request. If you made that request and then withdraw, you pay for what we provided until you told us: for a top-up, the Credits you used; for a subscription, the share of its fee that the larger of two parts comes to, the part of its period that had passed and the largest part you had used of any one of its included quantities. If you did not make that request, we refund all you paid.
- (d) Once all the Credits of a top-up that you asked us to provide at once have been used, the top-up has been provided in full, and you can no longer withdraw from it. You acknowledge this when you tick the box.
- (e) We refund what you paid, less any amount under (c), with the tax we charged on it, within 14 days after you tell us, to the card you paid with, at no cost to you. When you withdraw from a top-up, we remove its unused Credits (Section 9.7) and turn Auto Reload off. When you withdraw from a subscription, it ends at once, and your Account is on the Free Plan from then.
- (f) This Section does not apply to purchases you make for a business.
Model withdrawal form (fill it in and send it only if you want to withdraw):
To GLAC PTY LTD, 5 Kalimna Ave, Campbelltown SA 5074, Australia, support@glac.ai:
I give notice that I withdraw from my contract for the following service: ……, ordered on ……
Name: …… Email address of the Account: ……
Date: ……
22. Limitation of liability
22.1 Our total liability to you for all claims about the Service in any 12 months is limited to the greater of the amounts you paid us in the 12 months before the event that caused the claim and US$[100].
22.2 To the extent the law allows, we are not liable for indirect or consequential loss, or for loss of profit, revenue, business, goodwill or data.
22.3 These limits do not apply to liability that the law does not allow us to limit, such as liability for fraud, or for death or personal injury caused by negligence.
22.4 If you are a consumer, Sections 22.1 and 22.2 apply only as far as the consumer law of the place where you live allows. We are responsible for loss you suffer that is a foreseeable result of our breaking these Terms or failing to use reasonable care and skill; we are not responsible for loss that was not foreseeable when you accepted these Terms.
23. Claims caused by your use
If you use the Service for a business, you will defend us against claims by others that arise from Your Content, from your users, or from your breach of Section 15, and you will pay the amounts awarded or agreed in settlement and our reasonable costs.
24. Changes to these Terms
24.1 We may change these Terms. We tell you by email and on our website at least 14 days before a change that reduces your rights or increases what you pay takes effect. Other changes take effect when we publish them. A change the law requires, or a change needed for security, may take effect sooner.
24.2 If you do not agree with a change, you can close your Account before it takes effect. If you go on using the Service after it takes effect, the change applies to you.
25. Governing law and disputes
25.1 These Terms are governed by the laws of South Australia, Australia. The courts of South Australia, and the federal courts of Australia, have exclusive jurisdiction over any dispute about them or about the Service.
25.2 Before going to court or arbitration, each side will first try to resolve the dispute by writing to the other and negotiating in good faith for 30 days.
25.3 If you are a consumer, you also keep any right to bring proceedings in the courts of the place where you live, and the protection of the mandatory laws of that place.
26. General
26.1 Notices. We send notices to the Account’s email address. You send notices to us at legal@glac.ai or by post to 5 Kalimna Ave, Campbelltown SA 5074, Australia.
26.2 Transfer. You may not transfer these Terms without our written consent. We may transfer them to a company in our group or to a successor of our business, and we will tell you if we do.
26.3 Events beyond our control. We are not responsible for failures caused by events beyond our reasonable control, such as failures of power, networks or providers, natural disasters, war, or acts of governments.
26.4 Whole agreement. These Terms, with the documents in Section 1.3, are the whole agreement between us about the Service. If a court finds part of them unenforceable, the rest still applies. If we do not enforce a right at once, we have not given it up.
26.5 Language. These Terms are written in English. If we translate them, the English version wins.
26.6 Export laws. You must comply with export control and sanctions laws that apply to your use of the Service.
27. Contact
GLAC PTY LTD, 5 Kalimna Ave, Campbelltown SA 5074, Australia. Support: support@glac.ai. Legal notices: legal@glac.ai. Abuse reports: abuse@glac.ai. Security: security@glac.ai. Privacy: privacy@glac.ai.