Product Privacy Notice

1. About this notice

This notice explains how Artisafe ("Artisafe," "we," "us" or "our") handles information in connection with the Artisafe service, including Protofilter, its administrative console, command-line tools, APIs and Artisafe Test Drive (together, the "Service").

It does not cover the artisafe.com website itself. The website has its own, shorter notice at https://artisafe.com/privacy.html.

Capitalized terms not defined here have the meanings in the Artisafe Terms of Service at https://artisafe.com/legal/terms (the "Terms") and, for Beta Offerings, the Artisafe Beta Terms at https://artisafe.com/legal/beta-terms.

2. Our role: processor and controller

Artisafe's customers are organizations. How we handle a piece of information depends on whose it is.

• For Customer Data, we are a processor. Customer Data is what your organization, its Users and its Agents put into the Service: your policies and configuration, the credentials you connect, and the Audit Log of what your Agents did. We process it on your organization's behalf and under its instructions, as set out in the Terms. Your organization is the controller and decides how that data is used. If you are an individual whose data appears in a customer's Audit Log, please contact that organization first; we will help it respond.
• For account and usage information, we are a controller. We decide how to use the information we need to run Artisafe as a business: who has an account, how to reach them, how the Service is performing, and how to keep it secure.

3. Information we collect

3.1. Account and identity data (controller)

When you or your organization sign up, or an administrator invites you, we collect:

• your email address and a username;
• your organization name and the roles you hold in it;
• sign-in credentials and factors you choose, such as a password, passkey or authenticator app, or a sign-in through Google or Microsoft (in which case we receive your verified email address from that provider). We also send one-time codes by email, which we use only for email verification and account recovery;
• records of sign-in, verification and account-recovery events.

Our identity provider operates sign-in on our behalf and stores these credentials. We do not see your password.

3.2. Admin console and API activity (processor, and controller for security)

When Users change your Account through the console, the command-line tools or the API (for example adding an Agent, connecting a service, or editing a policy), the Service records who made the change, what changed and when. These records form part of your Audit Log. We also use them, as a controller, to keep the Service and your Account secure.

3.3. The customer Audit Log (processor)

The core of Protofilter is a record of what your Agents do. For each Agent request that passes through the Service, the Audit Log records:

• the time, your tenant identifier, and the Agent's identifier and display name;
• the Connected Service and the action the Agent called (for example, which tool or API method);
• the policy decisions applied, including which policy and rule matched and whether the request was allowed, denied or redacted;
• counts and pattern names for any content that was redacted;
• a summary of selected request fields, as defined for each kind of event;
• where available, an identifier for the person on whose behalf the Agent acted;
• latency and error information.

By design, the Audit Log does not record:

• the credentials used to reach Connected Services (only a reference to them);
• the original text of content that a policy redacted;
• full request or response bodies, unless your organization turns this on for a specific policy.

The Audit Log is written first to encrypted archive storage, which is the system of record, and then to a database that powers search in the console. It is retained as described in Section 8.

3.4. Connected-service credentials and configuration (processor)

When you connect a Connected Service, we store the tokens or keys needed to call it on your Agents' behalf. They are encrypted with keys specific to your organization and are never written to the Audit Log or to our operational telemetry. We also store your policies, Agent registrations and other configuration.

3.5. Operational telemetry (controller)

To run the Service reliably, our systems emit technical traces, logs and metrics: request identifiers, timings, error details, service names and your tenant identifier. We use these for monitoring, troubleshooting and capacity planning. This telemetry is separate from your Audit Log and is not a customer record.

3.6. Communications and support (controller)

If you email us, ask for support, or give feedback, we keep that correspondence and any information you include. Support and inbound email is received and handled through Google Workspace. We send transactional email, such as sign-in codes, verification, recovery and invitations, through an email delivery provider.

3.7. Cookies

The console uses cookies that are strictly necessary to keep you signed in and to protect sign-in flows. The Service does not use advertising cookies or third-party tracking pixels.

4. How we use information

We use information to:

• provide, operate and maintain the Service, including enforcing your policies and producing your Audit Log (processor purposes, on your organization's instructions);
• create and secure accounts, authenticate Users, and send transactional email;
• monitor, debug and improve the performance and reliability of the Service;
• detect, investigate and prevent security incidents, abuse and violations of the Terms;
• provide support and respond to requests;
• tell administrators about changes to the Service, the Terms or this notice;
• comply with law and enforce our agreements.

We do not sell personal information, and we do not share it for cross-context behavioural advertising. We do not use Customer Data to train artificial intelligence or machine-learning models made available to anyone other than the customer.

5. Legal bases

For individuals in the EEA, UK and similar jurisdictions, the legal bases for our controller processing are being finalized and will be stated here before final publication.

6. How we share information

We share information only:

• with subprocessors and service providers that help us run the Service (Section 7), under contracts that limit their use of it;
• within your organization, as your administrators configure (for example, Users with access to the Audit Log can see the activity it records);
• with Connected Services you choose, when your Agents call them through the Service;
• for legal reasons, when we believe disclosure is required by law, or needed to protect the rights, safety or security of Artisafe, our customers or others;
• in a business transfer, such as a merger or acquisition, subject to this notice;
• with your permission.

7. Subprocessors

We use the following third-party subprocessors to provide the Service. The contracting entities, locations and data-protection terms for each are being finalized before final publication.

8. How long we keep information

When retention ends, we delete or de-identify the information. Because the Audit Log is designed as a durable record, some personal information in it may be removed by redaction or other erasure techniques rather than by deleting whole archived records.

9. Security

We protect information with measures appropriate to a security product, including encryption in transit and at rest, encryption keys specific to each customer organization for connected-service credentials, managed encryption keys for the Audit Log archive, tenant isolation on every Audit Log query, strict access controls, and monitoring. No system is perfectly secure, and we cannot guarantee absolute security. If you believe you have found a security issue, contact [SECURITY CONTACT EMAIL].

10. International transfers

The Service is hosted in the United States. The transfer mechanisms we rely on for personal data from the EEA, UK and Switzerland, and for onward transfers to subprocessors, are being finalized and will be stated here before final publication.

11. Your rights and choices

Depending on where you live, you may have the right to access, correct, delete, restrict or object to the processing of your personal information, to receive a copy of it, and to withdraw consent where we rely on it. You also have the right to complain to your local data protection authority.

• Account and usage information (we are the controller): send your request to [PRIVACY CONTACT EMAIL]. We will verify your identity and respond within the time the law requires.
• Customer Data, including the Audit Log (we are the processor): contact the organization that uses the Service. If you contact us, we will refer you to it and help it respond.

We will not discriminate against you for exercising your rights.

12. Children

The Service is for businesses and is not directed to children. We do not knowingly collect personal information from anyone under 18.

13. Changes to this notice

We may update this notice. We will post the updated version at https://artisafe.com/legal/privacy and change the "Last updated" date. For material changes, we will give notice by email to account administrators or in the Service before they take effect.

14. Contact

Questions or requests about this notice: [PRIVACY CONTACT EMAIL]

Artisafe, [REGISTERED ADDRESS]