1. Who we are
automate.business is operated by NZWE, Inc., a
Delaware C Corporation. The company contact address is
NZWE, Inc., 131 Continental Dr, Suite 305, Newark, DE 19713,
US.
For privacy questions and general questions, the contact is
info@nzwe.com, the
owner-designated contact.
2. What this service is
The service helps US small businesses with administrative work. It
is designed as a private preview for invited accounts. It is not a
public self-serve service at the effective date. Live work and
voice are temporarily paused. Authentication email for invited
accounts is active. Customer email replies and Gmail are not
available. No model inference is active. No model provider is
enabled at launch. Each model provider is added with the 30 day
subprocessor notice described under Change control on our subprocessors page.
The service can receive business records, instructions, documents,
messages, and other content that a customer chooses to provide. The
private runtime was retired on 2026-10-11 and no customer runtime
is active. When a service is enabled, it can use external model
providers to prepare outputs for the customer's review.
Nothing produced by the service is intended to leave the
customer's business without human approval. This is a product rule
and a safety control. The customer remains responsible for deciding
whether to send, publish, rely on, or act on an output.
3. Our roles and the customer's role
The customer decides what information to put into the service and
why. For customer business data, NZWE, Inc. acts as a service
provider or processor, as applicable, and processes that data to
provide the service under the customer's instructions.
For account, access, billing, support, security, and service
administration information about the customer's own personnel,
NZWE, Inc. may act as the business or controller, as applicable.
The customer is responsible for having the rights, notices,
permissions, and authorizations needed to provide customer business
data to the service and to connect any third-party source. The
customer should not provide data it is not authorized to use.
4. Information we may handle
The categories depend on the customer's configuration. They may
include:
-
account and invited-user details, such as name, work email, role,
workspace membership, and authentication records;
-
customer business content, such as instructions, documents,
records, messages, prompts, outputs, and work history;
-
business contact and transaction information supplied by the
customer or a connected source;
-
Gmail content and metadata if the customer connects Gmail and
grants the relevant OAuth access;
-
model inputs, outputs, usage, and cost records when a model is
enabled;
-
billing and subscription information, including invoice, payment
status, and payment metadata. Payment-card processing is handled
through Stripe under its own terms. Our systems are not designed
to store full payment card numbers.
-
technical and security information needed to authenticate
requests, prevent abuse, diagnose failures, and operate the
service; and
-
communications sent to us for support or legal requests.
Customers must not submit sensitive data or children's data,
including health information, government identifiers, or
payment-card numbers. Both are prohibited in v1.
5. How we use information
We use information to:
- provide, secure, maintain, and support the service;
- authenticate invited accounts and manage workspace access;
-
store and retrieve customer business data for the customer's
configured work;
-
generate drafts, summaries, classifications, transcripts, or
other outputs for customer review;
-
operate customer-authorized integrations and send an external
action only after the required human approval;
- process billing and subscription administration;
-
investigate errors, security events, misuse, and service
reliability; and
- comply with law or respond to valid legal process.
We do not use customer business data for our own model training. We
do not use it for aggregation or cross-tenant analysis. We do not
sell customer business data. These statements concern NZWE, Inc.'s
own use and do not state the terms of an external model provider. The provider-specific terms and configuration must be checked before we route data to any provider, and we will give customers prior notice before enabling a provider.
6. Where information is processed
The locations below are facts about the current configuration. They
are not a residency warranty.
-
The private application runtime was retired on 2026-10-11 and no
customer runtime is active.
-
The Supabase control plane is the US East project in us-east-1,
live since the 2026-10-25 cutover. The former Sydney Supabase
project was deleted in October 2026 after a final encrypted
backup.
-
The AWS Lightsail host and the S3 backup bucket are in us-east-1.
A scheduled job uploads daily encrypted backups of control-plane
account and sign-in data to the bucket, since 2026-10-27, and
objects expire after 30 days.
-
An Oracle Cloud host in Sydney, Australia is retired from
application use and is now used for CI only, with no active
processing. No customer data was found by file name on either of our Oracle hosts (Sydney and Singapore) when checked on
2026-11-04.
-
Netlify provides global site and application delivery. Its global
edge network is not a US-residency promise.
-
Resend is recorded as US East, us-east-1, but provider-specific
processing and retention details remain to be confirmed.
-
Sentry is used to detect and fix errors in our application. Our code does not send cookies, request contents or query strings to Sentry. Error message text is sent as written and is not scrubbed, so it could contain information from the page where the error happened. Error reports are stored in the United States.
-
Google Analytics (Google LLC): on our public website only, to
count visits and see which pages are read. It sets cookies with
random identifiers. It is not used in the customer application.
-
Stripe is recorded as US for the current sandbox. Live billing
entity and processing path remain undecided.
-
Infisical is used for operator secrets only. Its region is not
verified, and customer business data is not intended to be stored
there.
-
A connected Google account and an enabled external model provider
may process information outside US East, according to that
provider's service and account configuration.
No public claim of US data residency may be made on the basis of
these location facts. The subprocessor inventory on our subprocessors page
records each provider's current location and the provider links.
7. Security and access
We use encryption in transit. Stored data is protected by the
encryption our hosting and database providers apply. The service is
designed around one customer per instance. Access is limited by
authentication, workspace membership, service permissions, and
operational need.
The service is designed to keep customer business data separate
between customer instances. The control plane stores customer
account and operational metadata, not the customer's business
records. This is an architecture statement, not a certification or
compliance claim.
External actions are held behind a human approval step. OAuth
connections are customer-authorized and may be revoked. We do not
promise that any system is immune from every security event.
If we become aware of a confirmed security incident affecting
customer business data, we notify affected customers within 24
hours after awareness. Notices to individuals or regulators are the
responsibility of the customer as controller, unless law or contract says otherwise.
For customer business data we process on a customer's instructions, we notify the customer so they can meet their own obligations. For account data we hold as the controller, we notify affected people and regulators as applicable law requires, including US state breach laws and, for New Zealand personal information, the Privacy Act 2020. A notice describes what happened, the kinds of data involved, what we are doing about it and how to reach us.
8. Disclosure to providers and other parties
We disclose information only as needed to provide the service,
follow customer instructions, operate a customer-authorized
integration, process billing, maintain security, or comply with
law. The current provider set and purpose for each provider are on our subprocessors page.
Gmail is a customer-directed source rather than a provider we
select, and it is not active. We may disclose information to a model provider that we enable after the 30 day subprocessor notice described on our subprocessors page. We do not enable a provider for every customer by default.
We may disclose information to professional advisers, insurers,
acquirers, or authorities when reasonably necessary for a permitted
business purpose or required by law, subject to confidentiality and
legal limits.
9. Retention and deletion
We keep customer business data while the customer's account and
configured service require it. On termination, the customer may
export customer business data for 30 days. We then delete it from
active systems within the next 30 days, and backups are purged
within 30 more days.
We may retain limited account, billing, security, and legal records
for as long as required by law or needed to establish, exercise, or
defend legal claims. We will not retain customer business data
longer than the approved schedule merely for our own purposes.
10. Requests and choices
Depending on applicable law and the relevant role, an individual
may have rights to request access, correction, deletion,
portability, restriction, or information about processing. The
scope and timing of those rights depend on the law that applies.
This policy does not decide that question. Where a US state privacy
law such as the CCPA applies to us as a business, we will give the
notices and honor the rights that law requires.
Customer personnel may send a request to
info@nzwe.com. A person whose
information appears in customer business data should normally
contact the customer that supplied the data, because the customer
decides the purpose and context of that processing. We will
reasonably assist the customer with a request where required by an
applicable agreement or law.
11. Cookies and similar technologies
The service uses strictly necessary browser storage or cookies for
authentication, security, and operation. Our public website uses
analytics cookies from Google Analytics. You can block them in your
browser settings or with a browser privacy extension, and the site
works the same without them. No advertising cookies are used, and
the customer application sets no analytics cookies.
12. Children's data
This is a business service for invited business accounts.
Children's data is prohibited in v1, and customers must not
knowingly provide it.
13. Changes
We may update this policy as the service, providers, or law
changes. We give account owners 30 days email notice before a
material change takes effect.
14. Contact
Privacy, data requests and general contact:
info@nzwe.com.
Company contact address: NZWE, Inc., 131 Continental Dr, Suite 305,
Newark, DE 19713, US.