Version 0.1, 25 October 2026
1. These Terms
1.1 These Customer Terms (the "Terms") are an agreement between Glass Aviary Inc., a California corporation ("Glass Aviary"), and the organization that accepts them ("you" or the "Customer").
1.2 You accept these Terms, for your organization, when a person accepts them in the Portal on its behalf. That person confirms that they are at least 18 years old and have authority to bind your organization.
1.3 The Service is for organizations, for their business use. It is not for personal or household use.
1.4 These Terms apply to a Trial, and wherever your organization's Seat is provided through a Reseller. If Glass Aviary agrees to provide the Service to you directly, a separate written agreement signed by both of us governs, to the extent it says so.
1.5 The Data Processing Agreement (the "DPA") forms part of these Terms. You accept the DPA when you accept these Terms. If these Terms and the DPA conflict about personal information, the DPA prevails.
1.6 Your agreement with your Reseller is separate, and Glass Aviary is not a party to it. Your Reseller is not Glass Aviary's agent. Nothing your Reseller says or promises changes these Terms or binds Glass Aviary, unless Glass Aviary agrees in writing.
2. Definitions
2.1 "Account" means one person's sign-in to the Portal. Accounts are provided through Clerk, Glass Aviary's sign-in provider.
2.2 "Account Data" means the information held about an organization and the people who belong to it: the organization's name, and each person's name, email address, membership and role, with the identifiers and dates kept for them. Where Account Data appears in a record or an output that is Customer Data, it is also part of that Customer Data.
2.3 "Administrator" means a Member whom the Service records as an administrator of your organization.
2.4 "Application" means the Glass Aviary application that an administrator of your directory approves on Microsoft's approval screen, and that then appears in your directory's Enterprise applications. Its name, publisher and permissions are set on Glass Aviary's application registration with Microsoft.
2.5 "Azure Connection" means the link between your organization and one Microsoft directory (tenant). Your organization can have one Azure Connection at a time.
2.6 "Customer Data" means Scan Data; the records kept about the Customer's connection to Azure and about its subscriptions, scans, schedules, downloads, requests for infrastructure code and failed requests, including the event records about them; and what is produced for the Customer from them: documents, diagrams, workbooks, JSON exports, infrastructure code with its manifest and plan text, drift results and the drift email. Account Data is not Customer Data, except where it appears in one of these records or outputs.
2.7 "Document Set" means the Word file, the PDF and the diagrams that the Service builds from a scan, with the workbook and the JSON export where they are produced.
2.8 "DPA" has the meaning given in clause 1.5.
2.9 "Drift Report" means the result of a drift check that the Service stores on a scan and shows on that scan's page in the Portal, and the drift email described in clause 7.7.
2.10 "Infrastructure Code" means the Terraform code for the azapi provider that the Service produces from Your Azure, delivered as a zip file with its manifest and plan text.
2.11 "Member" means a person who is a member of your organization in the Service. Membership is managed in Clerk.
2.12 "Outputs" means the Document Sets, Infrastructure Code and Drift Reports that the Service produces for your organization. They are the part of Customer Data that is produced for you.
2.13 "Plan" means the tier your organization is on: Trial, Lite, Standard, Pro, Scale or Enterprise. The Partner Agreement calls a Plan that a Reseller can buy a "Tier".
2.14 "Portal" means the Glass Aviary web application in which Members sign in and use the Service.
2.15 "Privacy Policy" means Glass Aviary's privacy policy, published with these Terms.
2.16 "Reader" means Azure's built-in Reader role.
2.17 "Reseller" means the company that provides your organization's Seat and bills you for it.
2.18 "Scan Data" means what is read from the Customer's Azure subscriptions and stored for the Customer: subscription details, resource descriptions and tags, role assignments, role-definition names, cost records, and records of what could not be read.
2.19 "Seat" means the right for one organization to use the Service on one Plan for a term that a Reseller has bought from Glass Aviary.
2.20 "Service" means the Glass Aviary service described in clauses 3 to 7, provided through the Portal. The DPA and the Sub-processor List call it the "Platform".
2.21 "Sub-processor List" means the list of Glass Aviary's sub-processors. The Privacy Policy names them.
2.22 "Trial" means the Trial Plan.
2.23 "Your Azure" means the Microsoft directory you connect and the Azure subscriptions in it that the Service can read.
3. The Service and your Plan
3.1 The Service reads your Azure subscriptions with the Reader role and produces documentation and diagrams of them. On some Plans it also produces Infrastructure Code, and compares later scans with earlier ones to report what has changed.
3.2 What your organization can use depends on its Plan:
- (a) every Plan, the Trial included: a Word document, a PDF, and one diagram for each resource group, as an SVG file and a draw.io file;
- (b) Lite and above: also an Excel workbook, with the subscription's cost figures;
- (c) Standard and above: also a JSON export, a comparison of each scan with the previous scan, scheduled scans, and Infrastructure Code: on Standard for one resource, on Pro for one resource or one resource group, and on Scale and Enterprise also for the whole subscription;
- (d) Scale and Enterprise: also the drift email and, after each scheduled scan, a check against Your Azure of the latest whole-subscription Infrastructure Code your organization has obtained, if there is one.
3.3 Each Plan has limits, among them the number of subscriptions selected for scanning, the number of scans in a calendar month, and the number of requests for Infrastructure Code in a calendar month and at once. On the Trial, scans are counted for the life of the Trial. When a limit is reached, the Service refuses the work or, for subscriptions, leaves the extra ones unselected. A subscription already selected stays selected after a move to a Plan with a lower limit, while the Application still holds only Reader on it. Glass Aviary can also record, for your organization alone, an exception that replaces some of what its Plan includes or allows, with or without an end date.
3.4 Where your organization's Seat comes from a Reseller, your Reseller arranges your organization's Plan and Seat with Glass Aviary. What a scan's Document Set includes is decided when it is built. When your Plan changes and the change leaves your organization active, the Service may build your latest documented scan's Document Set again, without a new scan, so that it includes what the new Plan adds. A workbook or JSON export already produced for that scan stays available.
3.5 Support. If your organization's Seat comes from a Reseller, contact your Reseller first for help with the Service. Your Reseller supports you, and Glass Aviary supports your Reseller. A Trial has no Reseller, and Glass Aviary makes no commitment to support a Trial. Clause 18.1 says where notices and questions about personal information go.
4. Connecting your Azure: consent, Reader only, and revocation
4.1 Any Member can start an Azure Connection. Connecting takes two steps, and you take both in your own Microsoft directory.
4.2 First, an administrator of your directory approves the Application on Microsoft's admin-consent page, through a link that works once and expires 30 minutes after it is issued. The permissions approved are the ones Microsoft's approval screen shows. They are set on Glass Aviary's application registration, not chosen by the link. The approval gives Glass Aviary no access to any of your Azure subscriptions.
4.3 Second, someone in your organization with the Owner or User Access Administrator role assigns Reader to the Application on each subscription you want the Service to read.
4.4 If you give the Application more than Reader, the Service refuses to scan that subscription and tells you which role it found. It does not remove the broader role. That access stays until you remove it.
4.5 Reads only. The Service's own requests to Your Azure are GET requests to Azure Resource Manager, with one exception: the Cost Management query, which Azure accepts only as a POST and records as a read. The Service makes no request to list your keys, secrets or connection strings. It sends the access token for your directory only to management.azure.com. What a token can read is decided by Azure, from the roles you assign.
4.6 Withdrawing access. You can withdraw Glass Aviary's access at any time in your own directory, without asking Glass Aviary. Removing the Reader assignment stops the Service reading that subscription. Deleting the Application from your Enterprise applications removes it entirely. The Portal has no button that disconnects your Azure Connection.
4.7 After you remove the Reader assignment, the next scan of that subscription stops before reading anything and is recorded as failed. After you delete the Application, scans fail and read nothing, and the Service marks your Azure Connection as revoked the next time a Member presses "Check again".
4.8 Withdrawing access does not delete scans, their Scan Data or their Outputs. After you remove the Reader assignment, the next "Check again" marks that subscription as having no access, or deletes its record if Azure no longer lists it; each scan keeps its own copy of the subscription's ID and name. When you delete the Application, the Service keeps your Azure Connection's record and its subscription records. If you connect again, the old subscription records are deleted and earlier scans are kept. Clause 16 says when Customer Data is deleted.
5. Scans and what is stored
5.1 A scan reads one subscription. It runs when a Member presses "Scan now", when a schedule set for the subscription fires, or when Glass Aviary queues one at your organization's request. Every scan counts against your Plan's allowance, scheduled scans included. Failed scans do not count.
5.2 A scan reads: the subscription's details; each resource's description as Azure returns it to a reader; the role assignments at the subscription and below it, and the names of the role definitions; and the subscription's actual cost for the 31 whole days ending the day before, with a breakdown by resource and by service.
5.3 Limits of a scan. Scan Data does not include role assignments in Your Azure made at a management group or at the tenant root; the scan records that as something it could not read. A resource type with no stable interface version is listed by name and not read in detail. A resource whose details could not be read is stored with its identity and tags only. The Service records each thing it could not read.
5.4 The Service stores Scan Data in its database. It stores role assignments by the object ID and type of each user, group or application, and does not look up their names. It reads and stores cost data on every Plan, and shows it only on Plans that include cost reporting, which the Trial does not.
5.5 A scan that fails, reaches its time limit or is given up keeps none of the resource data it read. Its record stays, marked as failed.
5.6 Personal information. Resource descriptions and tags in Your Azure can hold names, email addresses and other personal information. The Service's scrubber (clause 6.5) removes credentials, not personal information in general, so Scan Data can include personal information that Your Azure holds. The DPA applies to it.
6. What is not stored, and what the scrubber can miss
6.1 To sign in to your directory, the Service uses no credential of yours. Its record of your Azure Connection has no place for a password, key, certificate, secret or refresh token. Scan Data can still hold a credential-shaped value that the scrubber does not catch.
6.2 The Service never writes an access token to its database, its event records, its logs or its error messages.
6.3 The Service does not receive or store the identity of the administrator who approves the Application in your directory. It records only the Member who started the connection.
6.4 Where a Member signs in with a password, it is entered in Clerk's own form. The Service's own database has no password field.
6.5 Secret-shaped values. The Service does not ask Azure for the values of your keys, secrets or connection strings. But Azure can include a secret-shaped value in a resource description it returns to a reader, such as a container's environment values, and the Service then receives that value. Before anything is written, the Service's scrubber removes such values from every resource description, tag and role assignment. In a resource description or a role assignment, a marker stands where each removed value was; it records where the value was and which rule caught it, never the value. A removed tag value is replaced by a fixed text.
6.6 Infrastructure Code leaves out every resource the scrubber marked, and records why. Before Infrastructure Code is kept, every file to be delivered is searched for values shaped like credentials. If one is found, the request fails and no code is stored.
7. Documents, Infrastructure Code and Drift Reports
7.1 After a scan has completed, fully or in part, the Service builds its Document Set from the Scan Data it stored, without reading Your Azure again. An estate of more than 15,000 resources gets no Document Set; the scan is kept, and you are told why.
7.2 Whether a Document Set includes a workbook and a JSON export is decided when it is built, from your Plan and your organization's status at that moment.
7.3 Glass Aviary never applies Infrastructure Code to Your Azure: the Service runs no apply command. Whether, when and how to apply it is your decision. Review the code and its plan text before you use them.
7.4 Infrastructure Code reflects Your Azure as the Service read it for that request, and covers only the resources in the scope you chose. The zip holds, for each module, the Terraform files, an import file and the module's Terraform state file, with the plan text and the manifest. The state files describe your estate. Keep the zip as carefully as you keep your Azure configuration.
7.5 Drift checks. On Standard and above, after each completed scan, the Service compares it with the previous scan and stores the result on the scan. On Scale and Enterprise, after a scheduled scan, the Service also checks the latest whole-subscription Infrastructure Code your organization has obtained against Your Azure, and stores the result on the scan.
7.6 The Service reads Your Azure only when a Member presses "Check again", when a scan runs, when Infrastructure Code is requested and when a drift check runs. A Drift Report shows only differences between what those reads found.
7.7 The drift email. On Scale and Enterprise, after a scan in which a drift check found a change, or something it could not compare, the Service emails each Administrator. A difference in stored Infrastructure Code that earlier checks of the same code already found is not emailed again, unless the comparison with the previous scan found a change to the same object. The email names the subscription and your organization, gives counts, severity and the scan's date, and links to the scan's page. It carries no resource names and no values. It is part of the Service on those Plans and has no unsubscribe link.
7.8 Your Reseller. Members of your Reseller's organization, acting for your Reseller, cannot see your Customer Data through the Service. Glass Aviary may share with your Reseller your organization's name, Plan and status, and the history of its Seat.
8. Your responsibilities
8.1 Authority. You confirm that your organization is entitled to connect the directory and subscriptions it connects, and that each person who approves the Application, assigns Reader, or connects or scans for you has authority to do so.
8.2 Your Members. You are responsible for who you allow to be a Member. Every Member can take every action the Service offers your organization: connect Azure, check access again, start a scan, ask for Infrastructure Code, set a schedule and download files. An Administrator differs only in receiving the drift email. You are responsible for what your Members do in the Service.
8.3 Accounts. Each person must use their own Account and keep its sign-in details secure. If you think an Account has been misused, tell Glass Aviary promptly at PrivacyMatters@
8.4 People you invite. If you make a person from your Reseller or from Glass Aviary a Member, for example to get help, that person has the same access as any other Member, your Outputs included, until they are removed.
8.5 Download links. You are responsible for download links your Members share, which work for anyone who holds them until they expire, and for copies of Outputs once downloaded.
8.6 Your directory and Your Azure. You are responsible for your directory and subscriptions, including the roles you give the Application and removing them when you want access to end.
8.7 Using Outputs. You are responsible for how you use Outputs, including any Infrastructure Code you apply.
9. Acceptable use
9.1 You must not, and must not allow anyone else to:
- (a) connect a directory or subscription that your organization is not entitled to connect;
- (b) try to get around the Service's limits, its role checks or the separation between organizations;
- (c) try to reach another organization's data, or test, probe or attack the Service or the systems it runs on, without Glass Aviary's written permission;
- (d) interfere with the Service, or place an unreasonable load on it;
- (e) use the Service for anything unlawful, or in breach of export control or sanctions laws that apply to you or to Glass Aviary;
- (f) resell the Service or provide it to another organization, unless Glass Aviary agrees in writing; or
- (g) copy, modify or reverse engineer the Service's software, except to the extent the law allows despite this restriction.
9.2 If you breach clause 9.1, Glass Aviary may suspend your organization under clause 14 or end these Terms under clause 15.
10. Fees: your Reseller bills you
10.1 Under these Terms, Glass Aviary does not bill you and does not take payment from you. A Trial is free of charge. If your organization's Seat comes from a Reseller, your Reseller bills you for it, and the price, payment terms, invoices and taxes for your Seat are between you and your Reseller.
10.2 Glass Aviary bills your Reseller for your Seat under its own agreement with your Reseller. If your Reseller does not pay Glass Aviary for your Seat, or the period your Reseller has paid for ends and no other arrangement for your Seat is in place, clause 14 applies.
11. Personal information and the DPA
11.1 The DPA applies to personal information in Customer Data. It is written in the terms of South Africa's Protection of Personal Information Act, 2013. Under it, you are the responsible party and Glass Aviary is your operator.
11.2 Glass Aviary will use Customer Data only to provide, support and secure the Service for you, under these Terms and the DPA.
11.3 Account Data. Glass Aviary handles Account Data as its Privacy Policy describes.
11.4 Where the platform runs. The platform runs in Azure West Europe. Its database and its file storage, which hold Customer Data and Account Data, are created in that Azure region. This says where the platform runs. It is not a promise about where data is kept or processed. The services outside Azure that the platform uses are not placed by that setting. The DPA sets out the conditions for transferring personal information out of South Africa, and how Glass Aviary tells you before it moves the platform's database or storage account to another Azure region.
11.5 Sub-processors. Glass Aviary uses the sub-processors named on the Sub-processor List. The DPA says how Glass Aviary tells you about a change to that list.
11.6 Security. The DPA describes the security measures Glass Aviary takes, and how it tells you about a security compromise affecting your personal information.
12. Ownership, licences and third-party content
12.1 Your data. As between you and Glass Aviary, you own the Scan Data and the other Customer Data that records Your Azure, such as the records of your Azure Connection and its subscriptions. Clause 12.2 deals with Outputs. You give Glass Aviary a non-exclusive licence to host, copy, process and display Customer Data, Outputs included, as needed to provide the Service under these Terms and the DPA, and to hold it until it is deleted under clause 16.
12.2 Outputs. As between you and Glass Aviary, and subject to clauses 12.4 and 12.5, you may use the Outputs produced for your organization for any lawful business purpose, including after these Terms end. Clause 12.1 still applies to the Scan Data an Output contains. Glass Aviary keeps its rights in the design and structure of the documents.
12.3 The Service. Glass Aviary owns the Service and its software. These Terms give you the right to use the Service while they are in force, for your organization's own business. They give you no other right in the Service, or in Glass Aviary's name or marks.
12.4 Microsoft's Azure icons. Each diagram draws Microsoft's Azure architecture icons, unmodified. Microsoft owns them. Glass Aviary recorded Microsoft's terms for them when it downloaded them on 15 September 2026: "Microsoft permits the use of these icons in architectural diagrams, training materials, or documentation. You can copy, distribute, and display the icons only for the permitted use unless granted explicit permission by Microsoft." You may use the icons in the diagrams only as Microsoft's terms permit.
12.5 Fonts. Word files embed the fonts Fraunces, Inter and IBM Plex Mono. Glass Aviary's records state that all three are made available under the SIL Open Font License. That licence, not these Terms, governs the fonts.
12.6 Feedback. If you give Glass Aviary suggestions about the Service, Glass Aviary may use them without any obligation to you.
13. Confidentiality
13.1 Each party will keep the other's confidential information confidential, and use it only for these Terms. Customer Data is your confidential information. Non-public information about the Service is Glass Aviary's.
13.2 Information is not confidential if it is or becomes public through no fault of the party receiving it, was already known to that party, is received lawfully from someone else, or is developed independently. A party may disclose confidential information where the law requires, and will tell the other party first where the law allows.
13.3 Glass Aviary may disclose your confidential information to its staff, its sub-processors and its professional advisers who need it for these Terms and are bound to keep it confidential, and to your Reseller as clause 7.8 allows.
14. Suspension
14.1 Glass Aviary may suspend your organization's use of the Service, in whole or in part, if:
- (a) you or a Member breach clause 9;
- (b) Glass Aviary reasonably believes that suspension is needed to protect the Service, its other customers or Your Azure;
- (c) your Reseller's invoice for your Seat is still unpaid 30 days after Glass Aviary's notice to your Reseller;
- (d) the period your Reseller has paid Glass Aviary for your Seat has ended, your Reseller's order for your Seat or its agreement with Glass Aviary has also ended, and no other arrangement for your Seat is in place; or
- (e) the law requires it.
14.2 While your organization is suspended, the Service refuses new work: connecting Azure, checking access again, starting a scan, running a scheduled scan, producing Infrastructure Code, setting a schedule and sending the drift email. A Document Set for a scan already under way is still built, without a workbook or a JSON export. Members can still download the files already produced. Suspension deletes nothing.
15. Term and termination
15.1 These Terms start when you accept them and continue until they end under this clause.
15.2 You may end these Terms at any time by telling Glass Aviary in writing that you want your organization closed. Ending your arrangement with your Reseller, and any money due under it, is between you and your Reseller.
15.3 Ending these Terms does not remove the Application or its Reader assignments from your directory. Remove them yourself, as clause 4.6 describes.
15.4 Clauses 8.5, 8.7, 12, 13, 16, 17, 18 and 19 continue after these Terms end. Clauses 1.5 and 11 continue for as long as Glass Aviary holds Customer Data.
16. Your data after suspension, termination and deletion
16.1 While your organization exists in the Service, Glass Aviary keeps its Customer Data. The exceptions are the replacements and removals the Service makes as it runs: a failed scan keeps none of the resource data it read, a new Document Set or newer Infrastructure Code of the same scope replaces the files it supersedes for that scan, and the record of a subscription Azure no longer lists is deleted. The Service does not delete Customer Data because of its age or because of your Plan. Suspension and the end of a Trial delete nothing.
16.2 The DPA's terms on deleting and returning personal information also apply, and prevail if they conflict with this clause.
17. Warranties and disclaimers
17.1 Each party confirms that it has the power to accept these Terms.
17.2 Outputs describe what the Service could read from Your Azure when it read it. They can be incomplete or out of date. In particular:
- (a) Scan Data does not include role assignments made at a management group or at the tenant root;
- (b) resource types with no stable interface version are listed, not read in detail;
- (c) resources whose details could not be read appear with their identity and tags only;
- (d) the scrubber matches patterns, so it can remove values that are not secrets and can miss a secret that matches no rule;
- (e) a Drift Report shows only differences between what the Service read at different times; and
- (f) Infrastructure Code covers only the resources in the scope chosen, leaves out resources the scrubber marked, and reflects Your Azure when the request ran.
18. Notices
18.1 Notices to Glass Aviary must be in writing and sent to 28141 Bluebell Drive, Laguna Niguel, CA 92677, United States. Questions about personal information, and reports of a misused Account or a suspected security compromise, go to PrivacyMatters@
18.2 Glass Aviary gives notice to you by email to the addresses the Service holds for your Administrators. Keep your Administrators' email addresses up to date.
18.3 An email notice is received when it is sent, unless the sender receives a message that it was not delivered.
19. General
19.1 These Terms, with the DPA, are the whole agreement between you and Glass Aviary about the Service. They replace earlier discussions about it.
19.2 If a signed agreement under clause 1.4 and these Terms conflict, the signed agreement prevails to the extent it says so. Clause 1.5 sets out how the DPA relates to these Terms.
19.3 You may not transfer these Terms without Glass Aviary's written consent. Glass Aviary may transfer them to a company in its group, or to whoever takes over the Service, by notice to you.
19.4 Neither party is liable for a failure or delay caused by events beyond its reasonable control.
19.5 If a court finds part of these Terms unenforceable, the rest continues. A failure to enforce a right is not a waiver of it.
19.6 Only you and Glass Aviary have rights under these Terms. Your Reseller is not a party to them.
19.7 These Terms are written in English. The English version prevails over any translation.
19.8 The parties are independent. Nothing in these Terms makes either party the agent, partner or employee of the other.