Version 0.1, 25 October 2026
1. About this policy
1.1 This policy is issued by Glass Aviary Inc., a California corporation, whose address is 28141 Bluebell Drive, Laguna Niguel, CA 92677, United States ("Glass Aviary", "we", "us" or "our").
1.2 Glass Aviary provides a service that reads a Customer's Microsoft Azure environment with read-only access and produces documents, diagrams and, on some plans, infrastructure code (the "Service").
1.3 For the personal information described in clauses 3 to 7, Glass Aviary decides why and how it is processed, except as clause 1.5 says and except for information the DPA covers. For that information we are the responsible party, and this policy explains what we do with it.
1.4 When a Customer uses the Service to scan its Azure environment, the Customer decides why and how its Customer Data is processed. The Customer is the responsible party and Glass Aviary is its operator. Customer Data includes the records the Service keeps about the Customer's connection to Azure and its use of the Service. Clause 8 explains this, and the DPA governs it.
1.5 A Reseller is the responsible party for the personal information in its own account and seat records. That is: the names, email addresses, account roles and joining dates of the Reseller's people who use the Portal; and its seat records, which name its Customers' Organizations and record when each seat was assigned and ended. That information is held in the records clauses 3.1, 3.3, 3.4 and 3.6 describe. Glass Aviary processes it for the Reseller, as clauses 3 to 9 describe, to run the Reseller's account and record its seats. Glass Aviary is the responsible party for its own billing records about a Reseller: its invoices and payments, the records of payment problems and disputes in clause 3.7, with the evidence copied into a dispute record, and the signed Orders and agreements in clause 3.9, which it keeps for the contract and for its financial records. Some of these billing records copy information from the Reseller's account and seat records.
1.6 This policy covers people who have an Account, people who work for a Reseller, people who visit the Portal's pages, people who visit the Website, and people who contact us.
1.7 This policy is written for the Protection of Personal Information Act 4 of 2013 of South Africa ("POPIA").
2. Definitions
2.1 In this policy:
- (a) "Account" means a person's sign-in account for the Service, held by Clerk, and the Service's copy of it.
- (b) "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.
- (c) "Customer" means the organization that accepts the Customer Terms. The Partner Agreement calls a Customer whose Seat comes from a Reseller an End Customer.
- (d) "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.
- (e) "Customer Terms" means the terms a Customer accepts to use the Service.
- (f) "DPA" means the Data Processing Agreement between Glass Aviary and a Customer, accepted with the Customer Terms, which governs Customer Data.
- (g) "Drift email" means the email the Service sends an Organization's administrators when a scan's comparison with the previous scan, or the check of stored infrastructure code against Azure, finds a change or something it could not compare.
- (h) "Internal ID" means the identifier the Service gives each person. It is not a name or an email address.
- (i) "Member" means a person who belongs to an Organization.
- (j) "Order" means an order for seats that a Reseller and Glass Aviary sign under the Partner Agreement.
- (k) "Organization" means a Customer's or a Reseller's organization in the Service.
- (l) "Partner Agreement" means the agreement between Glass Aviary and a Reseller.
- (m) "Personal information", "processing", "responsible party", "operator" and "data subject" have the meanings POPIA gives them.
- (n) "Plan" means the tier an Organization holds: Trial, Lite, Standard, Pro, Scale or Enterprise. The Partner Agreement calls a Plan that a Reseller can buy a "Tier".
- (o) "Portal" means Glass Aviary's web application and its pages, through which people sign in and use the Service.
- (p) "Reseller" means a business that buys seats for the Service from Glass Aviary under a Partner Agreement and provides them to Customers.
- (q) "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.
- (r) "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.
- (s) "Service" has the meaning in clause 1.2. The DPA and the Sub-processor List call it the "Platform".
- (t) "Service provider" means a company Glass Aviary uses that receives personal information this policy covers.
- (u) "Sub-processor" means one of the four service providers the Service uses, listed in clause 5.1 and on Glass Aviary's Sub-processor List. The DPA treats two of them, Microsoft Azure and Resend, as "Sub-operators", because they process personal information in Customer Data.
- (v) "Website" means Glass Aviary's website at glassaviary.com.
3. The personal information we collect
3.1 Account information. When you sign up or sign in, Clerk runs the sign-in form for us. The Service keeps a copy of your Clerk user ID, one email address, your first and last name if given, and when the record was created and last updated. If you work for a Reseller, clause 1.5 applies to this information.
3.2 Your password goes to Clerk's form. The Service has no place to store it and does not hold it. Which sign-in methods are offered, and how they are secured, are settings in our Clerk account.
3.3 Organization and membership information. For each Organization we keep its name, its type, status and plan, and the Reseller it sits under, if any. For a Reseller we also keep its Stripe identifiers. For each Member we keep the Organization they belong to and their role. If you sign up yourself, your Organization is named from the domain of your email address. For an address at a common personal email provider, the name is built from the part before the @, so it can be your own name.
3.4 Records of actions. The Service keeps event records of named actions about Accounts, Organizations, memberships, seats and billing. They include: an Account or Organization created; a membership granted, changed or removed; and seat and billing changes. An event record identifies a person by internal ID. The record written when a person joins their first Organization also holds their email address. The event records about a Customer's Azure connection, scans, documents, downloads, schedules, infrastructure code and drift email are Customer Data, which clause 8.4 describes.
3.5 Azure connection information. When a Member connects an Azure environment, the Service keeps records about the connection, including which Member started it. Those records are Customer Data, and clause 8.4 describes them.
3.6 Reseller seat information. For a Reseller we keep the seats it buys, by plan; which Customer held each seat, from when and until when; and the person who gave it or took it back, with the reason it was taken back. Today no page in the Portal gives or takes back a seat. Clause 1.5 applies to this information.
3.7 Payment problems. If Stripe reports a payment problem, we record it with the amount, the currency, the status, Stripe's identifiers and, for a failed payment, Stripe's link to the invoice. If Stripe reports a dispute, we also copy evidence into the record: the Reseller's name and Stripe identifiers, its seat purchases and allocations with its Customers' Organization names, and each of the Reseller's Members' email address, role and join date. These are our own billing records, and we are the responsible party for them (clause 1.5).
3.8 Payment details. When a Reseller buys seats in the Portal, payment details are entered on Stripe's own hosted page and do not reach the Service. What Stripe's page asks the buyer for, such as an email or billing address, is decided by Stripe and by our Stripe account's settings. For an invoice we issue by hand from our Stripe account, the invoice says how it can be paid.
3.9 Orders and invoices outside the Portal. A Reseller may sign an Order or an agreement with us outside the Portal, and we may issue its invoice from our Stripe account by hand. We then keep the signed document and the invoice. They hold the Reseller's company details and the names and business contact details of the people who sign or receive them. These are our own records, and we are the responsible party for them (clause 1.5).
3.10 The drift email. On plans that include it, the Service sends the drift email to an Organization's administrators. To send it, we pass each recipient's email address to Resend with the message. The message's content, and the record of which administrators it was sent to and with what outcome, are Customer Data, which clause 8.4 describes. The drift email has no unsubscribe link.
3.11 When you contact us. If you write to us, we keep your message and your contact details so that we can answer. Clause 5.2 covers the providers that hold our mailboxes.
3.12 Whether you must give it. You do not have to give us personal information. But each Account holds an email address, so we cannot give you an Account without one. A Reseller that does not give its payment details on Stripe's payment page cannot make its first purchase in the Portal.
4. Why we use it
4.1 We use the personal information in clause 3 only to:
- (a) create and run Accounts and Organizations, and let Members sign in;
- (b) provide the Service to the Organization you belong to, including Azure connections, scans, documents and downloads;
- (c) sell seats to Resellers, record seats and payments, and deal with payment problems and disputes;
- (d) send the drift email to an Organization's administrators;
- (e) keep the Service working and secure, and investigate failures;
- (f) answer you when you contact us or make a request under clause 11; and
- (g) meet our legal obligations, such as keeping financial records.
5. Who receives it
5.1 The Service uses four sub-processors:
- (a) Microsoft Azure hosts the whole platform: the Portal, the database, the file storage, the secrets and the logs. It holds all the personal information in clause 3 that the Service stores.
- (b) Clerk runs sign-up, sign-in and Organization membership. It receives email addresses, passwords, names where given, Organization names and membership roles.
- (c) Stripe takes Resellers' payments. It receives the Reseller Organization's name and Glass Aviary's ID for it, the plan and number of seats bought, and what the buyer enters on Stripe's page. For an invoice we issue by hand, it also holds the details on that invoice.
- (d) Resend sends the drift email. It receives each recipient's email address and the message, which names the Organization and the Azure subscription.
5.2 Glass Aviary also uses service providers outside the Service: for its email, for keeping signed documents and for hosting the Website. They receive the messages people send us, the signed documents in clause 3.9 and the requests visitors' browsers make to the Website.
5.3 Each service provider processes personal information under its own terms.
5.4 When an Organization connects Azure, its administrator approves the Glass Aviary application on Microsoft's own page, in the Organization's own Microsoft directory. The Service then signs in to that directory through Microsoft's sign-in service and reads the Azure environment through Microsoft's own interfaces. That is the Customer's own Microsoft service, not a service provider of ours.
5.5 Every Member of an Organization can see that Organization's results and download its files.
5.6 If your Organization is a Customer of a Reseller, the Service holds commercial facts about your Organization that relate to that Reseller: its name, type, status, plan and creation date, the dates its seat was given and taken back, and the reason a seat was taken back. The code can return these to the Reseller, but today no page shows them to it. Glass Aviary may give the Reseller, on request, your Organization's name, Plan and status, and the dates its seat was given and taken back, as the Partner Agreement and the Customer Terms allow. A Reseller acting as the Reseller cannot see your scans, documents or infrastructure code. If your Organization adds a Reseller's staff as Members, they have the same access as any other Member.
5.7 Apart from the recipients in this clause 5, we disclose personal information only to our professional advisers, such as lawyers and accountants, and where the law requires it.
6. Where it is processed
6.1 The platform runs in Microsoft Azure's West Europe region. Its database, its file storage, and the services that run the Portal and the platform's jobs, are created there.
6.2 Clause 6.1 says where the platform's own resources are created. It is not a promise about where personal information is kept or processed. The region is a setting of the platform and could change. We will update this policy before it changes, as clause 13.2 says.
6.3 Clerk, Stripe and Resend process personal information in their own locations, under their own terms. Those locations may be outside South Africa and outside West Europe.
6.4 The Service reads a Customer's Azure resources where the Customer placed them, and stores what it reads in the platform.
7. Cookies and similar technologies
7.1 The Portal's own code sets no cookies. It uses no local or session storage in your browser.
7.2 Every page of the Portal loads Clerk's own browser script for sign-in. That script may set cookies and collect information from your browser. Which cookies it sets, and what it collects, is Clerk's behaviour, not our code's, and Clerk handles that information under its own terms.
7.3 Stripe's payment page is Stripe's own page. The Portal's pages load no Stripe script. Stripe handles what you enter on its page under its own terms.
8. Customer Data: where we act as operator
8.1 A Customer connects its Azure environment by approving the Glass Aviary application in its own Microsoft directory and assigning it Azure's built-in Reader role. The Service will not scan a subscription where it holds any role other than Reader.
8.2 For Customer Data, the Customer is the responsible party and Glass Aviary is its operator. We process Customer Data to provide the Service to that Customer, as the DPA sets out. The DPA, not this policy, governs that processing.
8.3 Scan Data holds the descriptions of the Customer's Azure resources as Azure returns them, their tags, the subscription's role assignments and a cost summary. Role assignments are stored by the ID of the user, group or application; the Service does not look up their names. Resource descriptions and tags can hold personal information, such as names, email addresses or user names, that the Customer's own people put there.
8.4 Customer Data also includes the records the Service keeps about a Customer's connection to Azure and its use of the Service. When a Member connects an Azure environment, the Service keeps the Microsoft domain or directory ID they type; if they paste an email address, it keeps only the domain. It records which Member started the connection. It does not receive or keep the identity of the administrator who approves the Glass Aviary application in Microsoft. It keeps the IDs, names and states of the Azure subscriptions the Service can see, and Microsoft's error text when an approval fails. The records of a scan schedule, a request for infrastructure code and each download link identify the Member by internal ID, and a download link's record also notes the scan, the file and when the link expires. The drift email's content, and the record of which administrators it was sent to and with what outcome, are Customer Data too.
8.5 If your personal information appears in Customer Data, please contact the Customer it belongs to first, because the Customer decides how the information is used. If you contact us, we will pass your request to the Customer and help the Customer answer it as the DPA sets out.
8.6 Today the Service deletes no Customer Data because of its age. The database records of a Customer's scans are deleted when the Customer's Organization is deleted. The files made from them are not deleted at that point.
8.7 A Customer can withdraw the Service's access at any time in its own Microsoft directory, by removing the Reader role or deleting the Glass Aviary application. The Portal has no disconnect button. Withdrawing access does not delete Customer Data already stored.
9. How long we keep it
9.1 We have not yet set fixed retention periods. Today the Service deletes no personal information because of its age, and none of its deletions depends on an Organization's plan.
9.2 We keep your Account information while your Account exists in Clerk. When your Account is deleted in Clerk, the Service deletes its copy and your memberships. A person who leaves every Organization keeps an Account record until the Account is deleted.
9.3 Some records keep copies of personal information after the original has changed or been deleted. The event record written when you joined your first Organization keeps your email address. If you signed up yourself with an address at a common personal email provider, your Organization's first name, which can be your own name (clause 3.3), stays in the record of the Organization's creation after the Organization is renamed. Other event records keep your internal ID, and so do these records, which are Customer Data (clause 8.4): the drift email's records, requests for infrastructure code, Azure connection links and scan schedules. Because the record of your joining holds both your internal ID and your email address, the other records can still be matched to you. For a Reseller's Members, dispute evidence keeps their email addresses, roles and join dates, and it keeps the names of the Reseller's Customers' Organizations after those Organizations are deleted. These records are deleted when the Organization that holds them is deleted.
9.4 When an Organization is deleted in Clerk, the Service deletes its records, including its memberships, event records, seats, billing records and dispute evidence. A deleted Reseller's Stripe customer record, which holds the Reseller's name and Glass Aviary's ID for it, and its subscription stay at Stripe.
9.5 Our service providers keep personal information for the periods their own terms set.
10. How we protect it
10.1 The Portal is served over HTTPS, and a plain HTTP request is redirected to HTTPS. The platform's file storage accepts only HTTPS with TLS 1.2 or later. The platform's database connection settings require TLS.
10.2 The Service holds no password, key or certificate for your Azure environment. It signs in to your directory as Glass Aviary's own application, using an identity that Azure manages for the platform. Each access token is requested when it is needed, held in memory for one operation, and never written to the database, the event records or the logs.
10.3 When something fails, its details, which may include your Organization's content, are kept in your Organization's own records and joined to the log only by a random reference.
11. Your rights
11.1 You have the right to:
- (a) ask whether we hold personal information about you, and for a record or description of it;
- (b) ask us to correct personal information about you that is inaccurate, out of date, incomplete or misleading;
- (c) ask us to delete personal information about you that we are no longer allowed to keep;
- (d) object, on reasonable grounds, to our processing of your personal information;
- (e) withdraw a consent you have given, where we rely on it; and
- (f) complain to the Information Regulator.
11.2 Your name and email address come from your Clerk Account. When they change there, the Service's copy is updated from Clerk.
11.3 The Portal has no deletion step of its own. An Account or an Organization is deleted in Clerk, and the Service then deletes its own records as clause 9 describes. If you ask us to delete your Account, we will do it this way.
11.4 Requests about personal information in Customer Data are covered by clause 8.5.
11.5 If you are not satisfied with our answer, you can complain to the Information Regulator of South Africa.
12. Children
12.1 The Service is for businesses. It is not meant for children, and we do not knowingly collect personal information about children.
13. Changes to this policy
13.1 We may change this policy. Each version carries a version number and a date, and we will publish the current version where this one is published.
13.2 We will update this policy before a new sub-processor receives personal information, and before the platform's region changes.
14. Contact us
14.1 For questions about this policy or your personal information, and for requests to our information officer, write to PrivacyMatters@