{"id":283,"date":"2026-04-05T08:01:24","date_gmt":"2026-04-05T08:01:24","guid":{"rendered":"https:\/\/zanware.com\/?page_id=283"},"modified":"2026-04-09T18:52:34","modified_gmt":"2026-04-09T18:52:34","slug":"privacy","status":"publish","type":"page","link":"https:\/\/zanware.com\/es\/privacy\/","title":{"rendered":"Privacy Policy"},"content":{"rendered":"\n
\n

PRIVACY POLICY<\/h2>\n\n\n\n

Zanware Marine<\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\n

Privacy Policy<\/h2>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

1. Introduction<\/p>\n\n\n\n

This Privacy Policy explains how Zanware Marine (\u201cthe Service\u201d) collects, uses, and protects personal data in accordance with the General Data Protection Regulation and applicable laws.<\/p>\n\n\n\n

By using the Service, you acknowledge that you have read and understood this Policy.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

2. Nature of the Service<\/p>\n\n\n\n

Zanware Marine is a digital platform designed to support vessel management, crew coordination, and related operational workflows.<\/p>\n\n\n\n

The Service:<\/p>\n\n\n\n

\u2022 Is not a safety-critical or navigation system<\/p>\n\n\n\n

\u2022 Does not replace professional, technical, or legal judgment<\/p>\n\n\n\n

\u2022 Must not be used as the sole basis for operational or safety decisions<\/p>\n\n\n\n

Users remain fully responsible for their decisions.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3. Data We Collect<\/p>\n\n\n\n

Most of the data collected is associated with the user account and is used to provide core functionality of the Service.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.1 Account Data<\/p>\n\n\n\n

\u2022 Name<\/p>\n\n\n\n

\u2022 Email address<\/p>\n\n\n\n

\u2022 User role (owner, captain, crew)<\/p>\n\n\n\n

Purpose: authentication and access control<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.2 Personal Identification Data<\/p>\n\n\n\n

The Service may process personal identification data of users and third parties (such as crew members or guests), including:<\/p>\n\n\n\n

\u2022 Full name<\/p>\n\n\n\n

\u2022 Phone number<\/p>\n\n\n\n

\u2022 Date of birth (DOB)<\/p>\n\n\n\n

\u2022 Nationality<\/p>\n\n\n\n

Purpose:<\/p>\n\n\n\n

\u2022 identity management<\/p>\n\n\n\n

\u2022 operational coordination<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.3 Official Identification Data<\/p>\n\n\n\n

The Service may process official identification data where provided by the user, including:<\/p>\n\n\n\n

\u2022 Passport number<\/p>\n\n\n\n

\u2022 National ID number (e.g., DNI or equivalent)<\/p>\n\n\n\n

\u2022 Licenses and certifications<\/p>\n\n\n\n

Purpose:<\/p>\n\n\n\n

\u2022 compliance with operational and administrative requirements<\/p>\n\n\n\n

\u26a0\ufe0f Users are solely responsible for ensuring they have the legal right to collect and process such data.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.4 Operational Data<\/p>\n\n\n\n

\u2022 Vessels<\/p>\n\n\n\n

\u2022 Crew and guest profiles<\/p>\n\n\n\n

\u2022 Maintenance records<\/p>\n\n\n\n

\u2022 Budget and expenses<\/p>\n\n\n\n

\u2022 Port visits<\/p>\n\n\n\n

\u2022 Watchkeeping schedules<\/p>\n\n\n\n

\u2022 Contacts<\/p>\n\n\n\n

\u2022 Documents (PDFs, images, files)<\/p>\n\n\n\n

Purpose:<\/p>\n\n\n\n

\u2022 core functionality of the Service<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.5 Device & Technical Data<\/p>\n\n\n\n

\u2022 Device information<\/p>\n\n\n\n

\u2022 Log data<\/p>\n\n\n\n

\u2022 Usage events<\/p>\n\n\n\n

\u2022 Crash reports (Crashlytics)<\/p>\n\n\n\n

Purpose:<\/p>\n\n\n\n

\u2022 security<\/p>\n\n\n\n

\u2022 performance monitoring<\/p>\n\n\n\n

\u2022 debugging<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.6 Analytics Data<\/p>\n\n\n\n

The Service uses analytics tools to understand usage patterns, improve performance, and enhance user experience.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.7 Contacts Access<\/p>\n\n\n\n

If permission is granted, the app may access device contacts to import information.<\/p>\n\n\n\n

\u2022 Access is explicitly requested<\/p>\n\n\n\n

\u2022 It is optional<\/p>\n\n\n\n

\u2022 Controlled by the user<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.8 Location Data<\/p>\n\n\n\n

The app may use location services (maps, nearby places) when enabled by the user.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.9 Notifications<\/p>\n\n\n\n

Push notifications are sent using Firebase Cloud Messaging.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

3.10 Payments<\/p>\n\n\n\n

Payments are processed through:<\/p>\n\n\n\n

\u2022 Apple App Store<\/p>\n\n\n\n

\u2022 Google Play<\/p>\n\n\n\n

\u2022 Stripe (web only)<\/p>\n\n\n\n

\u2022 RevenueCat<\/p>\n\n\n\n

The Service does not store full payment details.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

4. Legal Basis<\/p>\n\n\n\n

Data is processed based on:<\/p>\n\n\n\n

\u2022 Contract performance<\/p>\n\n\n\n

\u2022 Legitimate interest<\/p>\n\n\n\n

\u2022 Legal obligations<\/p>\n\n\n\n

\u2022 User consent (where applicable)<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

5. Data Storage & Security<\/p>\n\n\n\n

Data is stored using Google Firebase infrastructure:<\/p>\n\n\n\n

\u2022 Cloud Firestore<\/p>\n\n\n\n

\u2022 Cloud Storage<\/p>\n\n\n\n

Security measures include:<\/p>\n\n\n\n

\u2022 Encryption in transit using secure protocols (HTTPS\/TLS)<\/p>\n\n\n\n

\u2022 Encryption at rest<\/p>\n\n\n\n

\u2022 Role-based access control<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

6. Data Sharing<\/p>\n\n\n\n

We do not sell personal data.<\/p>\n\n\n\n

Data may be shared with:<\/p>\n\n\n\n

\u2022 Cloud providers<\/p>\n\n\n\n

\u2022 Payment providers<\/p>\n\n\n\n

\u2022 Legal authorities when required<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

7. International Transfers<\/p>\n\n\n\n

Data may be processed outside the EU with appropriate safeguards.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

8. Data Retention<\/p>\n\n\n\n

\u2022 Account data: while active<\/p>\n\n\n\n

\u2022 Operational data: until deleted by the user<\/p>\n\n\n\n

\u2022 Backup data: temporary for security<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

9. User Responsibilities<\/p>\n\n\n\n

Users must:<\/p>\n\n\n\n

\u2022 Ensure data accuracy<\/p>\n\n\n\n

\u2022 Maintain backups<\/p>\n\n\n\n

\u2022 Use the Service responsibly<\/p>\n\n\n\n

During Early Access:<\/p>\n\n\n\n

\u2022 Data integrity is not guaranteed<\/p>\n\n\n\n

\u2022 Structures may change<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

10. Service Evolution<\/p>\n\n\n\n

Zanware Marine may:<\/p>\n\n\n\n

\u2022 Modify features<\/p>\n\n\n\n

\u2022 Change data structures<\/p>\n\n\n\n

\u2022 Update architecture<\/p>\n\n\n\n

without prior notice when necessary.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

11. Third-Party Infrastructure<\/p>\n\n\n\n

The Service depends on Google Firebase and other providers.<\/p>\n\n\n\n

Availability is not guaranteed.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

12. Limitation of Liability<\/p>\n\n\n\n

The Service is provided \u201cas is\u201d without warranties.<\/p>\n\n\n\n

To the extent permitted by law:<\/p>\n\n\n\n

\u2022 No liability for indirect damages<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

13. User Rights<\/p>\n\n\n\n

Users have the right to:<\/p>\n\n\n\n

\u2022 Access their data<\/p>\n\n\n\n

\u2022 Correct inaccuracies<\/p>\n\n\n\n

\u2022 Request deletion<\/p>\n\n\n\n

\u2022 Request restriction<\/p>\n\n\n\n

\u2022 Request data portability<\/p>\n\n\n\n

\u2022 Object to processing<\/p>\n\n\n\n

Requests can be made via:<\/p>\n\n\n\n

\ud83d\udce7 info@zanware.com<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

14. Early Access Notice<\/p>\n\n\n\n

\u2022 The Service is pre-release<\/p>\n\n\n\n

\u2022 Features may change<\/p>\n\n\n\n

\u2022 Bugs may exist<\/p>\n\n\n\n

\u2022 Backups are recommended<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

15. Relationship with Terms<\/p>\n\n\n\n

This Policy must be read together with the Terms & Conditions.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

16. Language<\/p>\n\n\n\n

In case of conflict, the English version prevails.<\/p>\n\n\n\n

________________________________________<\/strong><\/p>\n\n\n\n

17. Tracking<\/p>\n\n\n\n

The Service does not use data for tracking users across third-party apps or websites and does not engage in advertising tracking.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\n

Last updated: [fecha]<\/p>\n\n\n\n

Data Controller: Jose Zanon Rodriguez<\/p>\n\n\n\n

Contact: [info@zanware.com](mailto:info@zanware.com)<\/p>\n\n\n\n

Public URL: <https:\/\/zanware.com\/privacy\/><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n
\n

<\/p>

    <\/ul><\/div>\n
    \n
    \n<\/fieldset>\n