Privacy Policy
Last updated: 2026-09-24 · Version: pilot draft
This Privacy Policy explains how Mason, the provider of the Service ("Mason," "we"), collects, uses, and shares information when you use the Mason website and the Mason AutoProgrammer application (the "Service"). It is written for a business and professional audience. If you have signed a pilot agreement with Mason, that executed pilot agreement governs wherever it differs from this policy.
1. Information we collect
Information you provide
- Account information — name, work email, organization, and (if you create an account) authentication details. For paid plans, billing contact information.
- Requests for access and demos — the email address, the optional company name, and the consent text shown on the form at the time you submitted it.
- Communications — messages you send us (for example, support requests and emails).
Information you put into the Service ("Customer Data")
- Equipment and control inputs — the equipment descriptions, prompts, and any control/configuration data, palettes, drawings, or files you upload or create.
- Generated output — the wire sheets and export files the Service produces for you. You own this output; see the Terms.
Information collected automatically
- Usage data — how you interact with the Service (features used, actions, timestamps, approximate location from IP, device/browser information) and logs needed to operate and secure the Service.
- Cookies and similar storage — strictly necessary cookies and browser storage to run the Service (for example, to keep you signed in and to remember display preferences such as your theme). As of this version, the Service does not use third-party analytics or advertising cookies.
2. How we use information
We use information to:
- provide, operate, maintain, and secure the Service;
- generate the output you request and improve reliability and performance;
- communicate with you (service messages, support, and — with any required consent — product updates you can opt out of);
- handle billing for paid plans;
- detect, prevent, and address fraud, abuse, and security issues; and
- comply with legal obligations.
Nothing in this policy permits the use of Customer Data to train AI models; any such use must be stated in the executed pilot agreement.
3. AI processing and third-party providers
The Service uses AI and relies on third-party providers to function:
- Cloud infrastructure — the Service is hosted on Google Cloud, which processes data on our behalf to run the Service.
- AI model providers — to generate output, the Service sends the following to third-party large-language-model providers: your prompts and the prior turns of the conversation in that session; a summary of the current wire sheet (block names, ports, links, and configuration values); knowledge-base excerpts the model requests; the interface facts (block type names and port lists) of any palette you import; and facts extracted from drawings when you include them in a later build request. The drawings reader parses PDFs on our servers without calling a model provider. Imported archives are also parsed on our servers. Uploaded files are not sent verbatim; derived facts included in a user-initiated build may enter that build's model requests. Currently, Anthropic is the primary model provider. OpenAI is a failover provider: when the primary provider is unavailable (overloaded, unreachable, or timing out), a request may be restarted with OpenAI, and the same classes of content described above are sent to it. Failover requests are sent in stateless mode (we ask the provider not to store the conversation for later reuse). Each provider retains request data according to its own API terms. This section is subject to final legal review.
We share information with service providers (like the above) under contracts that limit their use of it to providing services to us. We may also share information to comply with law, enforce our terms, protect rights and safety, or in a merger or acquisition. Where the executed pilot agreement provides for a subprocessor list or a data-processing agreement, those documents form part of that agreement.
We do not sell personal information.
4. Data retention
We keep information for as long as needed to provide the Service and for legitimate business or legal purposes. Customer Data is retained for the retention periods stated in the executed pilot agreement; after termination we make it available for export for the period stated there and then delete or de-identify it, subject to backups and legal requirements.
5. Security
We use reasonable technical and organizational measures to protect information (such as encryption in transit, access controls, and logging). No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.
6. Your choices and rights
- Account information — you can access and update your account details, or ask us to do so.
- Marketing — you can opt out of non-essential emails at any time.
- Access, correction, deletion, portability — depending on where you live, you may have rights to access, correct, delete, or port your information, or to object to or restrict certain processing. To make a request, contact us (below).
- Customer Data — if you provided data on behalf of an organization, we act on the organization's instructions; direct requests to them where appropriate.
7. International data transfers
We may process and store information in the United States and other countries where we or our providers operate.
8. Children
The Service is not directed to children and is intended for business use. We do not knowingly collect personal information from children.
9. Changes to this policy
We may update this Privacy Policy. If changes are material, we will provide reasonable notice (for example, by posting the updated policy with a new "last updated" date). Continued use after changes take effect means you accept the updated policy.
10. Contact
Questions or privacy requests: hello@mason.software.