Privacy Policy

1. Who this policy covers

Zero-Natural AI is operated by Team Zero-Natural Co. ("we", "us"). This policy describes how we handle information submitted through zero-natural.com and data processed through the Zero-Natural service.

This policy is governed by the laws of Singapore. Questions about it may be sent to info@zero-natural.com. It is the only address at which correspondence about this policy is accepted.

2. Information submitted through this website

What the inquiry form collects

The inquiry form asks for the following:

• Organisation type
• Organisation size, as a headcount band
• Organisation or company name, or your own name if you apply as an individual
• Contact name
• Email address
• Telephone number (optional)
• Country
• Intended models and use case, as free text
• Annual budget, in USD millions
• Up to three website addresses (optional)

No other information is asked of you. The anti-abuse measures described in section 7 also process technical details of the request itself when a submission is made.

How a submission is handled

A submission is transmitted to us by email. This website does not store it in any database — there is no inquiry record kept on the site itself. Once the message reaches us it is held in our mailbox and reviewed as part of the two-stage review process.

Two providers handle a submission on its way to us. Cloudflare serves this site and processes the request in transit as our infrastructure provider. Resend, which delivers through Amazon Simple Email Service, then carries the submission to our mailbox as email. Both act on our behalf, and both are inherent to running the form.

3. Data processed through the service

This is the section prospective customers should read most carefully: the scope is broad.

Standard Enterprise and Upper Enterprise contracts

All customer data passing through the service is collected. That includes prompts, uploaded and generated files, outputs, and the material handled during desktop control and tool use — whatever is sent to or produced by the models under the contract. We do not offer a reduced-collection variant of these tiers, and there is no setting that turns collection off.

Restricted (Nova) contracts

The collection scope is agreed case by case and recorded in the contract. It is settled in writing before access is issued, and the terms of that agreement govern what is collected for that engagement.

4. Why we use this data

We use data collected through the service for three purposes, and no others:

• Provision to YYMT and other affiliated organisations.
• Training of our own models.
• Safety monitoring.

We consider these purposes part of the commercial basis on which the service is offered, which is why they are stated here rather than buried in a contract annex.

5. How long we keep it

Data is kept for a minimum of two weeks. There is no fixed maximum: we do not commit to deleting data after any particular period, and it may be retained indefinitely.

6. Analytics and cookies

This site uses Cloudflare Web Analytics for aggregate traffic measurement. It sets no cookies and does not fingerprint visitors.

That is why you will not see a cookie banner here.

7. Security

Traffic between your browser and this site is encrypted in transit, and the same applies to submissions sent from the inquiry form. Access to inquiry email and to service data is restricted to the people who need it for the purposes described in section 4.

On the site itself, the inquiry form is protected by Cloudflare Turnstile and by rate limiting to reduce automated abuse.

These are descriptions of measures, not accreditations. We claim no security certification, no external audit, and no compliance attestation on this site.

8. What we ask of prospective customers

The inquiry form is a first point of contact, not a secure channel for sensitive material. When completing it, organisations should not include:

• Personal data about third parties, including staff or customers who are not the named contact.
• Confidential information, credentials, keys, or other secrets.
• Regulated data, such as health, financial, or similarly restricted records.

Describe the intended use case in general terms. Anything requiring detail beyond that belongs in the later stages of the process, under the terms of an agreement.

9. Changes to this policy

We may revise this policy. Revisions are published on this page, and the date shown at the top is updated when they are. The version published here is the current one; continued use of the site and the service follows the policy as published.

For organisations already under contract, the data handling scope recorded in that agreement governs the engagement.