Terms and Conditions

1. Purpose and Scope

The System supports official PSAU Tilapia Hatchery work, including harvest records, monitoring records, pond and batch information, forecasting datasets, forecast results, operational recommendations, task follow-up, reports, notifications, backups, and administrative account management.

2. Authorized Use

Use is limited to authorized personnel and approved accounts. The System must be used only for legitimate hatchery, administrative, reporting, research-support, and decision-support purposes connected with PSAU Tilapia Hatchery operations.

3. User Accounts and Access

• Accounts may be created by administrators or requested through registration when public registration is enabled.
• Registration requires email confirmation and administrator approval before sign-in.
• Access is controlled by account status, assigned role, and permission rules configured in the System.
• Users are responsible for protecting their account credentials and for reporting suspected unauthorized access.
• Users must not share accounts, impersonate another person, bypass access controls, or attempt to use permissions not assigned to them.

4. User Responsibilities

Users must use the System carefully, keep account details accurate, follow assigned responsibilities, and handle System information only for authorized work. Actions performed through an account may be attributed to that account holder.

5. Hatchery Records and Data Accuracy

Users who enter or update hatchery records are responsible for providing accurate information based on available source records and field observations. Records should not be fabricated, concealed, altered, archived, rejected, approved, imported, or exported in a way that misrepresents hatchery operations.

6. Forecasts and Decision Support

The System uses stored hatchery information and configured forecasting or decision-support logic to generate forecasts, warnings, recommendations, resource estimates, and related reports. Results depend on the available data and the assumptions built into the System.

The forecasting results, warnings, and recommendations generated by the system are decision-support information and do not replace the professional judgment and operational decisions of authorized PSAU Tilapia Hatchery personnel.

Final decisions about hatchery operations, interventions, harvest planning, and resource use remain the responsibility of authorized personnel who can consider field conditions, technical standards, available resources, and current operational priorities.

7. Acceptable Use

Users must not misuse the System, attempt unauthorized access, disrupt service, introduce malicious code, remove or interfere with audit records, extract information without authority, upload unnecessary personal information, or use System information for unrelated, deceptive, unlawful, or private commercial purposes.

8. Account and System Administration

Authorized administrators may manage users, roles, permissions, account status, facility profile details, system settings, audit logs, backups, and related administrative functions according to assigned permissions. Accounts may be deactivated or access may be changed when required for operations, security, role changes, or account management.

9. System Availability

The System may be unavailable or limited during maintenance, configuration changes, backup or restore work, technical issues, or security response. Forecasting and reporting functions may also depend on configured services, available records, and current system state.

10. Changes to These Terms

These Terms may be updated when the System or operational requirements change. The Last Updated date on this page identifies the current version presented by the System.

PRIVACY NOTICE

This Privacy Notice supports transparency under Republic Act No. 10173, the Data Privacy Act of 2012. It describes the personal and account-related information processed by the System based on the current implementation. It does not claim privacy practices or legal compliance measures that are not evident from the deployed application.

1. Information We Process

The System may process the following information depending on the user's account, role, and activity:

• name, email address, email verification status, account status, assigned role, and permissions;
• password credentials handled through Laravel password hashing, not plain-text password storage;
• registration acceptance details, including Terms version, Privacy Notice version, acceptance timestamps, and acceptance IP address;
• last login time, session-related information, IP address, and browser or device user-agent information used for authentication, security, and auditability;
• optional Google sign-in linkage information when Google authentication is configured and used, including Google identifier and avatar URL stored against an existing approved account;
• MFA preference/status fields and temporary email verification-code records used when the MFA feature is enabled;
• user-created or user-managed hatchery records, including harvest, monitoring, pond, batch, forecasting dataset, recommendation, task, notification, report-export, backup, and administrative records where applicable;
• audit logs that may include the user, action, module, affected record type or record ID, previous and new values, IP address, user-agent, and timestamps.

2. Purpose of Processing

The System processes this information to create and administer accounts, verify email addresses, authenticate users, apply role- and permission-based access, attribute records and approvals, support hatchery operations, produce reports, generate forecasts and recommendations, send operational or account messages, maintain auditability, and support backup, restore, security, and administrative functions.

3. How Information Is Used

Information is used inside the System to show authorized screens, record operational activity, evaluate submitted records, support forecasting datasets and results, assign or update recommendations and tasks, display notifications, export reports, and help administrators review account activity and system changes.

4. Access and Disclosure

Access is controlled by authenticated sessions, active account status, assigned roles, and permission checks. Authorized administrators and users with the appropriate permissions may view or manage information needed for their assigned functions. The current implementation does not show advertising, analytics tracking, public user directories, data sales, or general third-party sharing features.

5. Data Security

The System implements authentication, email verification for registration, role- and permission-based access control, active-account checks, password hashing, request throttling on selected authentication routes, audit logging for many significant actions, and administrative controls for users, roles, backups, and settings. MFA support exists in the application, but whether MFA is enforced depends on current configuration. No system can guarantee absolute security.

6. Data Retention

The System stores user accounts, operational records, audit logs, backups, and related system records for ongoing hatchery operations and accountability. Account deactivation is implemented; automatic deletion of user accounts, audit logs, or operational records was not identified in the current implementation. Backup retention settings exist for database backups, but exact institutional retention periods must be confirmed by administrators or researchers.

7. Privacy Rights

Subject to applicable law and lawful limitations, users and data subjects may have rights under Philippine data-protection law, including the rights to be informed, access, object, correct or rectify, request erasure or blocking where legally available, data portability, file a complaint, and claim damages. Some requests may require identity verification and may be limited when records must be retained for official operations, accountability, security, or legal requirements.

8. Contact / Privacy Concerns

Privacy questions, correction requests, or concerns about account information should be raised with PSAU Tilapia Hatchery through the administrator-configurable official contact for this System. If a dedicated privacy officer or official contact is required, it should be configured by the responsible administrator or institution.

9. Changes to This Notice

This Notice may be updated when the System, data processed, or responsible administrative arrangements change. The Last Updated date on this page identifies the current notice presented by the System.