Pilot & Demo Data Handling Policy

1. Introduction

Dmytro Belykh (hereinafter "Benedict Corp.") respects your privacy and is committed to protecting your personal and enterprise information.

This document outlines how data is collected, processed, stored, and handled during pilot programs and demonstration sessions of solutions developed by Benedict Corp., including but not limited to:

• Benedict App
• Benedict Finance
• Benedict Invoice
• and other related tools and prototypes

This policy applies specifically to non-production environments used for testing, evaluation, and demonstration purposes.

Pilot and demo environments serve different purposes and operate under different conditions.

Pilot environments are:

• provisioned for a specific client or organization
• access-restricted to authorized participants
• intended to simulate real usage scenarios
• more controlled in terms of data access and visibility

Demo environments are:

• shared across multiple users and organizations
• not restricted to a single client
• intended for general product evaluation and demonstration
• not isolated between users

As a result, demo environments provide a lower level of data isolation compared to pilot environments.

By participating in a demo or pilot session of Benedict Corp. solutions, you agree to the terms outlined in this policy.

2. Purpose of the Demo

Demo environments are made available to demonstrate the features, user experience, and overall capabilities of Benedict Corp. solutions.

Access to demo environments may be shared across multiple users, organizations, or potential clients and is not restricted to a single entity. The demo environment is a shared, non-production environment intended solely for evaluation purposes.

Users should not treat demo environments as secure or isolated environments.

3. Purpose of the Pilot

Pilot environments are provided to:

• evaluate usability and functionality
• validate workflows and reporting accuracy
• test system performance under real-life scenarios
• collect feedback for further development

Pilot environments are not intended for production use. Pilot environments are provided on a per-customer basis, and data in such environments is accessible only to the customer's users and Benedict Corp. personnel responsible for development, maintenance, and support.

4. Data Collected

During pilot usage, the following types of data may be collected:

• personal data such as full name, business email, and phone number (for contacting during the pilot/demonstration)
• user-provided inputs (e.g., time logs, descriptions, comments)
• project and task-related data
• organizational structure references (e.g., projects, clients, entities)
• system-generated data (e.g., timestamps, calculated metrics, KPI values)

Benedict Corp. does not intentionally collect sensitive personal data unless explicitly required and agreed in advance.

5. Data Usage

Collected data is used exclusively for:

• operating and demonstrating the functionality of the solution
• generating reports, dashboards, and analytics
• testing integrations and workflows
• improving performance, usability, and system design

Data is not used for marketing, resale, or unrelated purposes.

6. Data Storage and Processing

Pilot data is stored in a controlled environment managed by Benedict Corp., typically using Microsoft 365 services, including:

• SharePoint
• Power Apps
• Power Automate
• Power BI

Data may be processed within these systems to support application functionality. Microsoft, as the underlying cloud infrastructure provider, acts as a sub-processor for any personal data processed within these services, under Microsoft's own data processing terms.

7. Data Access

Access to pilot data is restricted to:

• authorized participants involved in the pilot
• Benedict Corp. personnel responsible for development, maintenance, and support

Access is granted on a need-to-know basis and may be centrally managed during the pilot.

Access to demo environments is not restricted and may be granted to any user. Users participating in demo environments are strictly prohibited from uploading or entering any sensitive, confidential, or privileged information. Benedict Corp. shall not be liable for any loss, damage, or consequences resulting from the submission of such information, including any exposure to other users within the demo environment.

8. Data Retention and Deletion

Pilot data is temporary.

• Data will be deleted after the completion of the pilot phase, unless otherwise agreed.
• Benedict Corp. does not retain pilot data for long-term storage or reuse.
• Participants may request deletion of pilot data at any time.

Demo Data

Benedict Corp. will take reasonable steps to remove data entered during demo sessions after their completion. Due to the shared nature of demo environments, such data may be temporarily visible to other users during the demo.

9. Participant Responsibilities

Participants are responsible for:

• ensuring that no highly sensitive or confidential data is entered unless explicitly agreed
• using the system strictly for evaluation purposes

Pilot environments should not be used for:

• production operations
• legally binding or critical reporting

10. GDPR and Data Protection

Benedict Corp. is committed to handling data in accordance with applicable data protection laws, including the General Data Protection Regulation (GDPR).

During pilot and demo usage:

• data is processed on a limited, purpose-specific basis
• only data necessary for evaluation and testing is collected
• access to data is restricted and controlled where applicable

In pilot environments:

• data is typically isolated per client or testing group
• Benedict Corp. acts as a data processor, while the participating organization remains the data controller, with respect to any personal data the organization submits into the pilot environment for processing on its behalf

In demo environments:

• environments may be shared across multiple users and organizations
• data entered during demo sessions may be visible to other users within the same environment
• demo environments are not intended for processing personal or sensitive data

Participants are responsible for ensuring that no sensitive personal data is entered into demo environments.

Benedict Corp. will take reasonable steps to delete data after the completion of pilot or demo sessions, unless otherwise agreed.

Participants have the right to:

• request access to their data
• request correction or deletion
• raise concerns regarding data handling

11. Processor Obligations During Pilots

Where Benedict Corp. processes personal data on behalf of a participating organization during a pilot, and to the extent required by Article 28 of the GDPR, Benedict Corp.:

• processes personal data only on the documented instructions of the participating organization, including with regard to any pilot-specific purpose agreed with that organization
• ensures that any personnel authorized to process the data are subject to confidentiality obligations
• takes appropriate technical and organizational measures as described in Section 12
• engages Microsoft as a sub-processor for underlying cloud infrastructure, under Microsoft's own data processing terms, and will not otherwise engage a sub-processor without informing the participating organization
• assists the participating organization, where reasonably possible, in responding to data subject requests and in meeting its own obligations under Articles 32 to 36 of the GDPR
• deletes or returns pilot data at the end of the pilot, as described in Section 8, unless retention is required by law
• makes available to the participating organization the information reasonably necessary to demonstrate compliance with this section

For pilots involving personal data of a scale or sensitivity that warrants it, a separate, more detailed Data Processing Agreement can be provided on request. This Policy is intended to reflect the substance of that relationship for standard pilots; it does not replace a dedicated Data Processing Agreement where one is required or requested.

12. Security Measures

Reasonable technical and organizational measures are implemented to protect data within pilot and demo environments, including:

• access controls
• role-based permissions
• secure Microsoft cloud infrastructure
• restricted administrative access

In pilot environments:

• access is typically limited to authorized users within a defined testing group
• additional controls may be applied depending on the scope of the pilot

In demo environments:

• environments may be shared across multiple users and organizations
• access controls may be limited due to the shared nature of the environment

Accordingly, demo environments are not intended for storing or processing sensitive or confidential information.

While Benedict Corp. applies reasonable security measures, pilot and demo environments may not reflect full production-grade security configurations.

13. Pilot & Demo Limitations

During the pilot and demo phase:

• certain features (e.g., automation, reporting, integrations) may be partially restricted
• some processes may be centrally executed by Benedict Corp.
• performance may vary depending on test conditions

These limitations are part of the evaluation process.

14. Transition to Production

In a full production deployment:

• the solution is installed within the client's own Microsoft 365 tenant
• all data remains under the client's control
• full functionality, automation, and security configurations are enabled

15. Contact

For any questions regarding this policy or data handling practices, or to request a dedicated Data Processing Agreement for a pilot, please contact:

info@benedictcorp.com