Terms of Service

Summary

These terms are the agreement between you and Aaron Gazzola, trading as Az Gazzola, for your use of gazzola.dev. You agree by signing in with GitHub, and the version you agreed to is recorded on your account.

The guide is free, and nothing is charged here. There is no balance, and no payment details are requested or recorded.

The application has read and write access to each repository you select, and read-only access to each Supabase project you connect. It reads both so the guide's instructions fit your app, and writes reference and configuration files into your repository. The application never writes your app code. Clause 5.1 sets out each access.

Az works on your app himself only where you ask him to, as paid work under clause 8. He uses the same repository access, and asks you to invite him to your Supabase organisation, your Vercel team, your Doppler workplace and any other service the work needs. He delivers on a separate branch, as a pull request for you to merge. Clause 5.2 sets out the arrangement.

Clause 6 sets two conditions. You need one particular development environment, because every instruction Az writes is tested in only that environment. Your app also has to be built on Next.js, with every part of it in an account of your own. Vite apps, or apps on a service controlled by Lovable, Replit, v0 or Bolt, are accepted but need to be migrated first.

The guide gives you prompts you run through an AI model on your own machine. The output can be wrong or insecure, and nobody sees the output before it reaches your repository, so reviewing every change is your responsibility, which clause 13 covers.

You must be 18 or over, and the service is not offered in the European Economic Area, Switzerland or the United Kingdom. Clause 4 explains why, and what happens if you signed up from there.

Your repository and everything in it stay yours. Az claims nothing over what you build, and everything in your own accounts is yours. What you write stays yours too, and using the service lets Az read what you write, to provide the service and nothing else. The application, the guide and the prompts belong to Az.

You can delete your account at any time, and revoke every access at the service that granted it. Az can refuse or block your direct messaging at any time, and can close your access to the guide only for the reasons in clause 15.

Az works on client projects on live broadcasts, and only on the ones you permit. The question for this permission once for each repository, you can withdraw your answer at any time, and declining changes nothing. A broadcast is kept as a recording. Clause 11 sets out the risk you accept.

The consumer guarantees under Australian law cannot be excluded. Nothing in these terms excludes them. Beyond those guarantees, the remedy for a service supplied at no charge is the service supplied again rather than a payment, which clause 19 sets out.

The rest of this document is the same agreement in full.

1. Agreement to these terms

Signing in with GitHub is the act of agreeing to these terms and to the privacy policy. The version of each document that was published at that moment is recorded on your account, with the date.

These terms also apply to reading the public pages, so far as a term can apply to somebody who holds no account.

If you do not agree to these terms, do not sign in and do not link a repository.

2. Who you are agreeing with

The gazzola.dev website is operated by Aaron Gazzola, sole trader, in Australia, trading under the registered business name Az Gazzola and referred to in these terms as "Az". Australian Business Number: 81 700 757 157. Postal address: Suite 4034, Shop 7, 290-306 Anakie Rd, Norlane VIC 3214, Australia.

3. Definitions

• The application is the gazzola.dev website, its database, and all of its functions and features, including the guide and the conversation with Az.
• The service is the application together with the work Az does himself. Clause 5 sets out which is which.
• Your app is the web app you are building. These terms call it your app, and call gazzola.dev the application.
• The guide is the chaptered conversation that gives you instructions and reads the GitHub repository you link and the Supabase project you connect.
• Your repository is a GitHub repository you have linked to the service and have the right to change.
• A scan is the reading of a linked repository, and of a connected Supabase project, that the guide runs at the start of a session once you have finished the chapters it depends on.
• Paid work is work on your app that you pay Az for, agreed outside the service.

4. Eligibility

You must be 18 or over to use this service. You confirm your age when you link your GitHub account, and the account is closed if the confirmation is discovered to be untrue.

The service is not offered to people in the European Economic Area, Switzerland or the United Kingdom. Az is a sole trader in Australia and does not seek work in those places. Nothing is advertised or proposed there. If you are in one of those places and signed up anyway, write to support@gazzola.dev, and your account and all of your account data will be deleted.

5. The service

gazzola.dev is a web development advisory platform for building web apps with AI.

5.1 What the application does

The application holds two accesses, and each is granted by you.

• Read and write access to each repository you select, granted by installing the GitHub App, and revoked by uninstalling it.
• Read access to the structure and settings of each Supabase project you connect, granted by an authorisation that cannot write to the project, cannot run a query of its own, and cannot read a row in any table.

The application uses both for two things and for nothing else. It reads your repository and your Supabase project in order to provide instructions informed by the state of your app. It writes reference and configuration files into your repository, so your own tools can read them. It never writes your app code. You write the code yourself, on your own machine, from the prompts the guide gives you.

Clause 10 of the privacy policy lists what each access can reach and what is kept from it.

5.2 What Az does

Az works on your app himself only if you ask him to and if he agrees. That is paid work under clause 8 rather than part of the free guide. Az does not promise a reply within any particular time, and a message he has not answered is not a refusal of the work.

For work inside your repository Az uses the access in clause 5.1, and asks you for access to a further repository where the work needs it. After Az has invited you to message him directly, the guide will ask you to send three invitations from Supabase, Vercel and Doppler. Az may also request additional invitations to external services in order to complete development tasks, resolve issues, or give you support and guidance. These invitations are sent directly from you to Az at the external service, and are not managed by the application. Invitations to the following external services are requested by the guide:

• Your Supabase organisation, at administrator level, so that he can change your database.
• Your Vercel team, as a member, so that he can deploy your app and fix a failed deployment.
• Your Doppler workplace, as an administrator or an owner, so that he can set the secrets your app runs on.

Az delivers the work on a separate branch, as a pull request for you to merge. When working on your database, he uses a Supabase preview branch when possible, so your production database is untouched until the work is approved. Clause 10.1 of the privacy policy describes the same arrangement, and clause 10.3 of that policy lists what access is provided by the three invitations.

6. What you need to use the service

These are conditions of the service rather than suggestions. All contents of the guide and all instructions provided by Az are designed and tested using one development environment and one stack.

6.1 Your development environment

• Claude Code, running inside VS Code.
• A local clone of the repository you linked containing your app code.

Neither is checked, and you are only asked whether your development environment matches these requirements. If you tell the guide it matches when it does not, the instructions you are given may not work.

6.2 Your stack

• Next.js is the destination framework. A Vite app is accepted but requires migration to Next.js in order to continue in the guide and to continue with direct collaboration with Az. Any other framework will also require migration to Next.js. Each one is considered case by case, and Az may refuse to migrate it.
• Every part of your app must be held in an account of your own. An app that depends on a service controlled by Lovable, Replit, v0 or Bolt is accepted but requires migration into your own accounts. This includes any database, authentication service, secret store, hosting, file store, payment system or other integration managed by these platforms. Only after migrating these services away from the platform and onto your own account at the service itself can you invite Az to collaborate directly at the service as described in clause 5.2.

7. Your account

Your account is created by signing in with GitHub, and the application holds no password of yours. Keeping your GitHub account secure is your responsibility, and anything done in the application through your GitHub account is treated as done by you.

One account belongs to one person. Do not share your GitHub sign-in with somebody else to give them access to the application.

You can delete your account whenever you choose, from the avatar menu, as clause 17 of the privacy policy describes.

8. What the service costs, and what is agreed elsewhere

The guide is free. Nothing is charged here, there is no balance and no card is asked for.

Paid work is a separate arrangement and is not governed by these terms. Where you found Az on Upwork, paid work is agreed and paid on Upwork. Where paid work is agreed any other way, it is agreed in writing before it starts.

9. If you found Az on Upwork

Two of Upwork's rules apply, both of which Upwork calls circumvention.

• Before a contract starts, every discussion stays on Upwork. Sharing any form of contact outside Upwork before a contract starts is circumvention, and discussions about goals, deliverables, costs, deadlines and the contract itself belong on Upwork. See Get to know each other before a contract.
• Payments go through Upwork. A twenty-four month non-circumvention period applies to the relationship, and the only route off the platform is Upwork's conversion fee. Nothing is charged here. See Circumvention, and why it's against the rules.

Upwork names an exception for sharing an email address to reach a code repository or a website host in order to scope a project. That is the access the application asks you for. Clause 12 of the privacy policy sets the exception out with the condition attached to it.

An invitation from Az is required to message him directly. Anyone can sign up and use the guide. Only an invited account can message Az, and Az does not invite a client who came from Upwork before an Upwork contract has started. Every discussion therefore stays on Upwork until the contract has started.

Until your account is invited, the application does not show Az the email address on your account. Az administers the database, so he can read the address there, and he does not write to you at that address before an Upwork contract starts. Clause 12 of the privacy policy says this too.

10. Third-party services

The guide tells you to create accounts at GitHub, Supabase, Vercel and Doppler, and it teaches you to use Claude Code. Those accounts are yours, on their terms, and anything they charge is between you and them: the guide says where a paid plan is needed and never buys one for you.

The invitations described in clause 5.2 are not granted inside the application. Each invitation is made at that service, under that service's terms, and each one is yours to decline, to withdraw or to remove later.

Az is not responsible for what one of those services does, for a change one of them makes, or for anything you lose through one of them. Where the guide links to a page somebody else publishes, that page and everything on it belong to them.

11. What you own

Your repository and everything in it stay yours, including the reference files written into it. Az claims nothing over what you build, and nothing in these terms gives Az a licence to reuse your code.

Everything in your own accounts is yours as well. Your Supabase project and every row in it, your deployments at Vercel, your secrets at Doppler, and whatever sits in any other service you invite Az to. His access to an account does not change your ownership of the account, and the access ends when you withdraw the invitation or revoke the membership. Where Az builds something on a service rather than in your repository, such as a migration, a database function, a storage bucket or a deployment, that work is yours on the same terms as anything he commits to your repository.

What you write in the application stays yours, and using the service gives Az a licence to read it. That covers your messages, your answers in the guide, and the title and description of each repository you linked. The licence is non-exclusive, it covers providing the service to you and nothing else, and it ends when you delete your account, except for a copy that has already left the application, which clause 14 of the privacy policy describes.

Permitting your app to be worked on a live broadcast carries a risk you accept. The permission is given and withdrawn at a step in the guide. It is put to you once for each repository you link, and only after Az has invited you to message him directly.

Clause 15.2 of the privacy policy sets out the precautions: a fork of your repository in Az's own account, a preview database holding no row of yours, and no production secret on screen. It also lists everything that can appear on screen and everything that never appears. The following will not appear on screen: your production database, your production secrets, your conversation with Az, and anything at all belonging to another client. Live work can still reveal something neither of you expected, and a broadcast cannot be recalled. By permitting it you accept that the precautions reduce that risk rather than remove it.

Nothing of yours is streamed unless you allow it. Declining changes nothing about the service provided by Az or the application. You can change your answer at any time by starting a new session and revisiting the step.

A stream is hosted on Vids.Tube, broadcast at the same time on YouTube, and kept as a recording on both. Withdrawal stops any further streaming of your app, and makes private any recording that is only about your app. A broadcast that has already gone out cannot be recalled. Az can make all of his published copies of the broadcast video private, but others may have made their own copies and he cannot enforce their removal.

If something sensitive appears in the broadcast, Az ends the stream as soon as he is aware of it and makes the recording private on Vids.Tube and on YouTube immediately. He tells you the same day what appeared and for how long. Anything visible on a stream is treated as exposed whether or not anybody used it, and Az rotates what he can reach.

If you request a non-disclosure agreement, then your live stream permission is immediately and automatically withdrawn for every repository on your account, and the guide stops asking you about the live stream permission, even if Az declines the agreement.

Nothing here excludes the consumer guarantees that cannot be excluded, and clause 19 states the limit on everything else.

Pathways and demonstrations need no permission from you. What Az learns from working on your app shapes the pathways he writes into the guide, so that the next client meets the same problem with the instructions already written. A pathway holds nothing of yours: not your code, not your data, and no reference to you, to your app or to your case. Only the generalised pattern is kept. Az keeps the general knowledge, skill and experience he gains from the work, you acquire no interest in a pathway or in a demonstration, and nothing is payable to you for either.

Az also builds a demonstration of a pathway from scratch, on a repository and a Supabase project of his own, and walks through that demonstration on a live broadcast or in a video. A demonstration holds none of your code, none of your data, no reference to you or your app, and no reference to your specific case. It is presented as a demonstration rather than as a client's case. Both happen whether or not you permit live work, and neither declining the live stream permission nor withdrawing it changes either. Clause 15.3 of the privacy policy describes both.

12. What Az owns

The service itself belongs to Aaron Gazzola: the website, the guide, the chapters, the instructions, the prompts and the way all of them are put together. Using the service gives you permission to use those materials for your own app, and nothing further.

Do not copy the guide, resell it, or present it as your own service. Running the prompts Az gives you against your own code, and using the reference files and instructions he provides, is what they are for, and nothing in this clause limits that.

13. The files written into your repository

The guide writes reference and configuration files into the repository you linked, on the branch you assigned, using the access you granted at GitHub.

Where Az works on your app himself, clause 5.2 covers what he writes and where he puts it.

Review every file written into your repository before you rely on it, in the same way you would review any change to your code. Merging a change, running a prompt and deploying the result are your acts, and what you build and deploy is yours. Where a file arrives that you do not want, delete it: the history is yours. Work Az does himself is a service supplied to you, and clause 18 keeps the guarantees that apply to it. Clause 17 says what is not promised, and clause 19 states the limit.

The application keeps no copy of your repository, only the observations a scan recorded, which clause 4.3 of the privacy policy lists.

14. Acceptable use

Use the service for your own app. Do not try to access another person's account or repository, do not probe the service for weaknesses, do not drive the service with a script or a bot, and do not use the service to build anything unlawful.

Link only repositories you have the right to change.

15. Suspension and ending your account

You can end your account at any time, from the avatar menu, and you can revoke the repository access from your GitHub settings whenever you choose. Neither act needs a reason and neither needs Az's agreement.

Blocking your direct messaging is Az's decision, and needs no reason. Direct messaging is access to Az himself rather than part of the guide, so Az can block it at any time. Blocking it stops any message reaching Az, and every chapter of the guide still runs.

Closing your access to the guide happens for one of these reasons, and for nothing else: a breach of clause 14, conduct towards Az that is abusive, harassing or threatening, use of the service to harm another person, use that puts an unreasonable load on the service, a confirmation of age that turns out to be untrue, or a legal requirement. Closing it stops every chapter running. Your account still exists, and nothing in it is deleted.

Neither measure reaches anything else. Your repository access is still yours to revoke at GitHub, and your data is still yours to see, correct or delete on the same terms as anyone else's, as clauses 16 and 17 of the privacy policy describe.

Nothing you wrote is deleted because your access changed. Your sessions, your answers in the guide, your messages and your project notes stay as they are. If your access is restored, every one of them is still there, exactly as you left it.

Whether Az collaborates with you is his decision alone. Nothing obliges Az to invite you to message him directly, and nothing obliges him to work on your app. He does not have to give a reason for either decision, and he can decline at any time. Work already agreed under clause 8 ends on that arrangement's own terms rather than on these.

Declining to collaborate does not close your account and does not stop you using the guide. The guide is open to every account holder on the same terms, and the reasons above are the only grounds for closing your access to the guide.

16. Availability and changes to the service

The application is under active development and changes often. A chapter may be added, reworded or removed, a feature may be withdrawn, and the way the guide works may differ from one session to the next. The application can also be unavailable, for maintenance or for a fault, and no particular level of availability is promised.

Your app is not the application, and a change to one is not a change to the other. Your code is in your GitHub repository, your data is in your own Supabase project, your hosting and your secrets are in your own Vercel and Doppler accounts, and any other service that provides your app is your own and is separate from the application. Everything the application has written into your repository is in your history and is yours. All of it stays yours whatever happens to the application, and nothing built with the application depends on the application continuing to exist.

What the application holds for you is a different matter. Your sessions, your answers in the guide, your messages, your project notes and your scan results are kept in the application's own database. None of it is deleted deliberately due to the application changing. A mistake during the development of the application can lose something kept in the database. A daily backup enables recovery from some mistakes, and some losses cannot be recovered from a backup.

In the case of a loss of data, or a significant change to the application, your repository and your own accounts are untouched, and clause 18 keeps the guarantees that apply to the service.

The application may close. Az is one person, and the application may permanently stop running. You are told before that happens, your repository and your own accounts are unaffected, and you can ask for a copy of what the application holds before it closes, as clause 16 of the privacy policy describes.

17. Disclaimers

No particular outcome is promised: not that your app will work, not that advice will suit your case, and not that the service will be available at a given moment.

The advice is general technical teaching rather than professional advice about your business, your finances or your legal position, and what you choose to build is your decision.

The instructions the guide gives you are prompts you run through an AI model on your own machine. An AI model can produce code that is wrong, that is insecure, or that does not do what the prompt asked. Nobody sees that output before it reaches your repository, so reviewing it is yours alone, as clause 13 says.

Work Az does himself is different. Az also works with an AI model, and the same mistakes are possible. Az reviews what he writes before he delivers it, and it arrives on a separate branch as a pull request, so nothing reaches the branch you assigned until you merge it. Merging is your act. That work is a service supplied to you, and clause 18 keeps the guarantees that apply to it.

What you build carries its own legal obligations, and they are yours. An app that holds other people's personal information, that sells something, that sends email or performs another function puts you under the laws that govern those things. The guide does not check your app against any of those laws, and meeting them is your responsibility.

Nothing in this clause excludes a right you have under the Australian Consumer Law that cannot be excluded.

18. Your rights under the Australian Consumer Law

The Australian Consumer Law gives you guarantees that cannot be excluded, restricted or modified, and nothing in these terms excludes, restricts or modifies them. Where these terms and those guarantees disagree, those guarantees apply.

Three of those guarantees cover a service, and all three cover everything Az supplies here, the free guide and his paid work alike:

• The service is supplied with due care and skill.
• The service is reasonably fit for any purpose you make known to Az, and can reasonably be expected to achieve any result you tell Az you want.
• The service is supplied within a reasonable time, where no time has been agreed.

The guarantee about your purpose and your result applies only where you relied on Az's judgement. Naming a purpose or a result is not enough on its own: you must have relied on Az's skill or judgement to reach it. Where Az tells you that something cannot be done, or cannot be done within your budget or your timeframe, and you decide to go ahead, you are not relying on his judgement for that outcome, and the guarantee does not apply to it.

Where one of those guarantees is not met, write to support@gazzola.dev. Clause 21 says how a complaint is answered, and clause 19 states the limit on what can be claimed beyond the guarantees. If that answer does not satisfy you, you can take the matter to the Australian Competition and Consumer Commission at accc.gov.au, or to the consumer protection agency of your state or territory.

19. Limitation of liability

Nothing in this clause limits the guarantees in clause 18.

If a guarantee in clause 18 is not met, the remedy Az offers is supplying the service again. That means doing the work again.

Two things have to be true before Az can hold you to that limit, both set by section 64A of the Australian Consumer Law. The service must not be the kind of thing people ordinarily buy for their home or personal life, and holding you to the limit must be fair and reasonable. If either is untrue, the limit falls away and you keep every right clause 18 gives you.

Az is not liable for indirect loss, as far as the law allows. Indirect loss is loss that follows on from a problem rather than the problem itself. Lost profit and lost revenue are the usual examples.

A change you make from a guide prompt is yours to undo. You run every prompt on your own machine, against a repository whose history is yours, so you can review the change and reverse it.

A change Az makes arrives as a pull request on a separate branch. Nothing reaches the branch you assigned until you merge it. Clause 18 keeps the guarantees that apply to that work.

20. Privacy

What is collected, who receives it, how long it is kept and how to see, correct or delete it are in the privacy policy. The database is in Singapore, the website is served from Sydney, several recipients are in the United States, and the support mailbox is in Switzerland, Germany or Norway. Clause 8 of that policy names each recipient and the country it is in.

Everything Az can access about you and your app goes through an AI model. The application sends nothing to an AI model provider. Az works with Claude, made by Anthropic in the United States, and that is how he works rather than something you choose. Clause 7 of the privacy policy describes what Anthropic receives and what it keeps.

A non-disclosure agreement does not change the export or the AI reading. The guide asks whether you would like Az to sign an NDA before you link a repository. The agreement is arranged with Az directly rather than inside the application, and Az cannot sign one that forbids the AI reading, the export to his own machine, or the pathways and demonstrations in clause 11. Clause 11 of the privacy policy explains all three.

21. Complaints and disputes

Write to support@gazzola.dev with a complaint about the service or about these terms. Say what happened and what you would like done about it. Az will answer within one month, and will give reasons where the answer is no.

If that answer does not settle it, either side may send the other a written notice saying what the dispute is about and what would settle it. Both sides then have thirty days from that notice to try to settle it in writing.

After those thirty days either side may start court proceedings. Neither side has to wait before asking a court for an urgent order, and nothing in this clause takes away a right you have under the Australian Consumer Law.

You can go outside this process at any point. A complaint about one of the guarantees in clause 18 can go to the Australian Competition and Consumer Commission at accc.gov.au, or to the consumer protection agency of your state or territory. A complaint about your personal information goes to the Office of the Australian Information Commissioner, as clause 25 of the privacy policy explains.

Where you found Az on Upwork and the dispute is about paid work, Upwork's own dispute process covers it, because that work is agreed and paid on Upwork under clause 8.

22. Governing law and jurisdiction

Az is a sole trader in Victoria, Australia, and the service is supplied from Victoria wherever you are.

These terms are governed by the law of Victoria, Australia, which is the law a court applies to a question about what these terms mean.

You and Az both accept the non-exclusive jurisdiction of the courts of Victoria, and of the courts that hear appeals from them. Non-exclusive means you are not required to bring a claim in Victoria: a court somewhere else can hear it, if that court will take it.

Some laws give you rights that no contract can remove, and nothing in these terms removes such a right. Where the law of the place you live gives you a right that cannot be given up by agreement, that right stands, and the law of Victoria does not displace that right. Consumer protection law is the usual case, and clause 18 sets out the Australian Consumer Law.

23. General

• Where one part of these terms cannot be enforced, that part is narrowed as far as needed to make it enforceable, or removed where narrowing cannot do it. The rest of the terms still apply.
• A delay by either side in enforcing one of these terms does not give up the right to enforce it later. Letting something pass once does not mean it has to be let pass again.
• You cannot transfer your account or these terms to somebody else. Az can transfer these terms to a company he controls, or to somebody who buys the business, and your rights under them stay the same. Az tells you before a transfer takes effect, and you can delete your account at any time before that date.
• These terms and the privacy policy are the whole agreement about your use of the service, and they replace anything said about the service before you signed in. This does not cover a statement that was misleading, which the Australian Consumer Law does not allow to be excluded.
• Some of these terms keep working after your account closes: clause 11 on what you own, clause 12 on what Az owns, clause 18 on the consumer guarantees, clause 19 on the limit, and clause 22 on governing law.
• Every notice these terms require is written, and goes to the addresses named here. A notice to Az goes to support@gazzola.dev. A notice to you goes to the email address on your GitHub account, or through Upwork if you found Az there and no contract has started.

24. Changes to these terms

Each version of these terms carries the date it took effect, shown at the top of this page, and the version you agreed to is recorded on your account.

A change to the wording takes effect when it is published. Correcting a mistake, rewriting a sentence or renaming a clause changes nothing you agreed to, so nothing is sent to you about it.

You are told before a change to what you are agreeing to takes effect for you. This includes a change to what the service is, to what you need under clause 6, to what you or Az own, to the grounds for closing your access under clause 15, to the limit under clause 19, to the dispute process under clause 21, or to the governing law under clause 22. The notice reaches you by the route in clause 23. If you do not want the change, delete your account before the change takes effect.

25. Contact

Write to support@gazzola.dev with a question about these terms or about the privacy policy. That mailbox answers questions about those two documents and nothing else.

The support address is not used for client communication, which means it is not a way to reach Az about work. A message asking to work together, or asking for an invitation to direct messaging, is ignored without a reply.

Direct messaging inside the application is the only route to Az about your app, and clause 15 says that the invitation is his decision. If you found Az on Upwork, every discussion stays on Upwork until a contract starts, which clause 9 explains.