TERMS
Terms of service
This is the agreement between you and ACCA Gaming Productions. It is written to be read rather than survived, and where the law gives you a right that this cannot take away, it says so.
Who you are contracting with
CodeRook is owned and operated by ACCA Gaming Productions, a business name registered to a sole trader in New South Wales, Australia, under ABN 80 173 545 848. That ABN identifies the contracting party. Where these terms say "we", that is who is meant, and every commitment in this document is made by that person.
Business location: NSW 2259, Australia. Written notices may be sent to security@coderook.com, and a postal address will be provided on request where one is needed for a legal purpose.
These terms are governed by the laws of New South Wales, Australia, and the courts of New South Wales have jurisdiction. Nothing in this agreement excludes, restricts, or modifies any consumer guarantee or other right you have under the Australian Consumer Law that cannot lawfully be excluded.
We are not currently registered for GST, so prices do not include an amount for GST and no tax invoice showing GST is issued. If that changes, prices and invoices will say so before it takes effect.
The service is funded by subscriptions. Storage and infrastructure are paid for by the people using them, which is why nothing in this agreement needs to reserve a right to monetise your projects.
Your projects
You retain ownership of content you upload and must have the right to store and share it.
Every project has one of three visibility settings:
- Private — you and the people you invite. To everyone else it answers as though it does not exist, so its name cannot be found by guessing.
- Unlisted — readable by anyone who has the link, but not listed, not searchable, and not offered to anyone browsing.
- Public — readable and listed.
Visibility is set per project and applies to its whole history. Every version of a public project is reachable, and version numbers run consecutively — what you see published is the real history, not a curated view of it.
What we will not delete
CodeRook does not automatically delete completed Versions or code just because an account exceeds its storage allowance. Going over the limit stops you uploading more. It does not cost you anything you have already saved, on any plan, including after a subscription ends.
What is in your storage is yours to manage. We do not tidy it up, we do not decide which of your files were worth keeping, and we do not look at what is in them.
Content is removed only in these cases:
- You delete it yourself.
- A project you deleted reaches the end of its thirty-day recovery window.
- You close your account, and the seven-day recovery window ends.
- Stored objects that no version refers to are reclaimed during routine storage collection. These are working leftovers — an upload that never completed, a file replaced by a later version — and never part of a saved Version.
- Temporary files created while processing an upload are discarded once it finishes. They exist for seconds, are never part of a Version, and never count against your storage.
- Illegal content, or malware.
- Content removed after a copyright complaint, under the procedure on the copyright page.
- Content removed under a court order or other legal demand.
- Content removed for a severe breach of the acceptable use policy.
- Backup copies, once the backup rotation expires. Backups are kept for thirty days, so something you delete today stops existing everywhere within thirty days rather than instantly.
That last one is worth reading twice, because "deleted" means two different things either side of it. Deleting removes your content from the service immediately; the backups it already appears in roll off over the following thirty days.
Your account
You must be at least 16 years old to hold an account. One person or organisation per account; you are responsible for everything done with it.
Keep your password and any access tokens to yourself. We cannot tell you your password because we do not hold it in a form that can be read back. If you think somebody else has your credentials, change them and revoke your sessions and tokens in your account settings — both take effect immediately.
Where you add collaborators to a project, they act with the permissions you gave them and what they do with that access is your responsibility as the owner, not theirs alone.
Subscriptions, renewal and cancellation
Paid plans are billed in advance, monthly or yearly, in US dollars, and renew automatically on the same date each period until cancelled. We email you five days before a renewal, naming the date and the amount.
You can cancel at any time from your billing settings. Cancelling stops the next renewal and your plan continues until the end of the period you have already paid for — we do not cut access off at the moment you cancel.
If a payment fails, we tell you and Stripe tries again after five days. Your billing date does not move: paying late renews the date you have always had rather than starting a new cycle. If the second attempt also fails, the account moves to the free plan within 24 hours and we tell you before it happens.
Moving to the free plan never deletes anything. Every project stays where it is and remains downloadable. If you are over the free storage allowance, uploads pause until you subscribe again or remove enough to fit; downloading and deleting keep working either way.
Extra storage is sold in blocks on the same subscription, and you can change how many you have at any time from your billing settings. Adding one takes effect immediately and is charged for the remainder of the current period only. Removing one takes effect at your next renewal — the storage stays available until then, because you have paid for it, and the unused part is not refunded for the same reason cancelling part-way through is not.
Prices may change. Any change applies from your next renewal and never to a period you have already paid for, and we tell you before it takes effect.
Refunds
Nothing in these terms limits your rights under the Australian Consumer Law. If the service is faulty, not as described, or fails to do what we said it would, you are entitled to a remedy — a refund, a repair, or a replacement depending on how serious the failure is — and that right cannot be excluded by anything written here.
Beyond those rights: we refund duplicate charges, charges taken after a cancellation, and charges taken in error, without argument. We do not otherwise refund the unused part of a period you chose to cancel part-way through, because your access continues to the end of it.
If you think you have been charged wrongly, write to billing@coderook.com. It is easier to sort out than a chargeback and usually faster.
Responsible use
Do not upload unlawful material, malware intended to harm others, credentials you are not authorized to store, or content that infringes another person’s rights. Do not bypass quotas, access controls, or abuse protections.
Machine access and AI usage preferences
Each project carries the owner's answers to four questions: whether it may be read, contributed to, downloaded, or called by automated clients. Those answers are published with the project — in the Content-Usage header on every response, in the page itself, and in this site's robots.txt.
Those answers are terms of access, not merely preferences. Accessing a project by an automated client in a manner its owner has declined, including by circumventing or automating past a verification step, is use outside the permission granted and is a breach of these terms and of any licence the owner has attached. Permission is granted by the owner and not by the accessibility of a URL.
Where a project declares that it may not be used to train or fine-tune machine learning models, that declaration applies to the content however it was obtained, including via third parties and via copies.
What we do not do with your content
ACCA Gaming Productions does not use projects stored on CodeRook as training data for machine learning models, and does not sell, licence, or otherwise supply them to any other party for that purpose or any other. This applies to public and private projects alike. Making a project public makes it readable; it does not make it training material, and it grants us no right beyond what is needed to operate the service you asked for.
To be unambiguous about what could ever be sold: ACCA Gaming Productions may one day sell or transfer the service and the site itself — the software, the infrastructure, the name, the business of running it. It will never sell the projects stored on it. Those are two different things and only the first is ours.
Content stored on CodeRook belongs to the person who uploaded it and is not an asset of this company. It is excluded from any sale, merger, acquisition, investment, insolvency, or other transfer of the company or of the service — before, during, and after any such change. No purchaser acquires any right to the projects stored here, and no change of ownership can create one, because that right was never ours to pass on. A buyer would acquire a service with content on it that belongs to its users, on the same terms we hold it under.
If ownership or control of the service were ever to change, we would tell you before it took effect and in time for you to export your projects and close your account. That is a courtesy on top of the exclusion above, not the thing protecting you.
Authorship disclosure
You are never required to state whether AI tools were used to produce anything you publish here, and we will not ask. Any facility for displaying how a project was built is optional and controlled by its owner. The absence of such a statement carries no meaning and must not be represented as though it does.
We do not restrict, rank, or remove projects on the basis of whether AI tools were involved in making them.
Automated access
Automated clients are welcome within the published limits. Project and version listings are unrestricted; routes that serve individual stored files and archives carry a request budget, and exceeding it returns a temporary refusal that states how long to wait. Honouring robots.txt, the request budgets, and any declared verification step is a condition of automated use of the service.
Security, and its limits
No service can promise that stored content is completely secure, and we do not make that promise. What we provide is control: project visibility, per-project answers about automated access, immutable version history, and account controls over sessions and tokens. Those let you decide how exposed your work is.
You are responsible for keeping your credentials safe and for deciding what is appropriate to upload given that limit. Content you choose to publish is public, and no setting here retrieves it once it has been taken.
Suspension, and ending the agreement
You can leave at any time. Closing your account is in your account settings and takes effect immediately. Your projects are then held for seven days and permanently deleted, so a closure regretted the same week can still be recovered by writing to us. Export anything you want to keep before you close.
We may restrict or suspend an account that breaches these terms or the acceptable use policy. We use the smallest step that fixes the problem and, other than where something is actively harming people or systems, we tell you what the problem is and give you a chance to fix it first.
We may close an account for repeated or serious breaches. Except where the law requires immediate removal, you keep the ability to export your projects for seven days afterwards — the same window as closing the account yourself, and the same window after which the content is permanently deleted.
If we stop offering the service, or stop offering it to you for a reason that is not your breach, we will give you at least 60 days' notice and refund the unused part of anything you have paid.
Any suspension or closure can be appealed. Reply to the notice we sent, or write to support@coderook.com. You do not need a reason beyond disagreeing with it, and you do not need to argue it in a particular form.
Appeals are reviewed by our system moderators, and we aim to give you a decision within seven days. A decision made in error will be reversed, and where the account was restricted while we looked, the restriction goes with it. If the seven days would run past the point where your content is deleted, the deletion waits for the decision rather than the other way round.
Changes to these terms
We will give you at least 30 days' notice by email before any change that materially affects your rights, and we will say what changed rather than only that something did.
If you do not accept a change, you may cancel before it takes effect and we will refund the unused part of your current period. Continuing to use the service after that means you accept it. Changes required by law, and changes that only benefit you, may take effect sooner.
Liability
Our goods and services come with guarantees that cannot be excluded under the Australian Consumer Law. Nothing in this section limits those rights, and where a liability cannot lawfully be excluded, it is not excluded.
Subject to that, and to the extent the law allows: our total liability to you for any claim connected with the service is limited to the amount you paid us in the twelve months before the claim arose, or resupplying the service, whichever we choose. We are not liable for loss of profit, loss of opportunity, or loss that was not reasonably foreseeable.
Keep your own copies. CodeRook is a place to store and share work, and we take that seriously — but no service is a substitute for a backup you control. We are not liable for loss of data where you had no copy of your own.
Your responsibility for what you publish
You are responsible for the content you upload and for having the rights to store and distribute it. If somebody brings a claim against us because of content you published — a copyright complaint, a privacy complaint, or a claim that it caused harm — you agree to cover the reasonable costs we incur in dealing with it.
That does not extend to anything caused by our own act or omission, to claims arising from how we operated the service, or to amounts beyond what a court or regulator actually required. We will tell you promptly about any such claim and will not settle one at your expense without asking you first.
Complaints and disputes
Write to support@coderook.com first, or to legal@coderook.com for anything formal. We aim to acknowledge quickly and to resolve things without either side needing a lawyer.
If we cannot agree, you keep every avenue the law gives you — including the Office of the Australian Information Commissioner for privacy matters, the ACCC or your state consumer affairs body for consumer matters, and the courts of New South Wales. Nothing here requires you to give up a right to complain to a regulator or to go to court.
Availability
CodeRook is young. Features may change, and we do not yet publish an uptime commitment — when we do, it will say what happens if we miss it rather than only what we are aiming for. Current status is on the status page, which checks the service live rather than repeating something written earlier.
None of that affects the commitments in these terms. Your ownership of your projects, what we will not do with them, the notice you get before anything changes, and your rights under the Australian Consumer Law apply now and are not conditional on the service being finished.