PRIVACY POLICY
Zanware Marine

Privacy Policy
________________________________________
1. Introduction
This Privacy Policy explains how Zanware Marine (“the Service”) collects, uses, and protects personal data in accordance with the General Data Protection Regulation and applicable laws.
By using the Service, you acknowledge that you have read and understood this Policy.
________________________________________
2. Nature of the Service
Zanware Marine is a digital platform designed to support vessel management, crew coordination, and related operational workflows.
The Service:
• Is not a safety-critical or navigation system
• Does not replace professional, technical, or legal judgment
• Must not be used as the sole basis for operational or safety decisions
Users remain fully responsible for their decisions.
________________________________________
3. Data We Collect
Most of the data collected is associated with the user account and is used to provide core functionality of the Service.
________________________________________
3.1 Account Data
• Name
• Email address
• User role (owner, captain, crew)
Purpose: authentication and access control
________________________________________
3.2 Personal Identification Data
The Service may process personal identification data of users and third parties (such as crew members or guests), including:
• Full name
• Phone number
• Date of birth (DOB)
• Nationality
Purpose:
• identity management
• operational coordination
________________________________________
3.3 Official Identification Data
The Service may process official identification data where provided by the user, including:
• Passport number
• National ID number (e.g., DNI or equivalent)
• Licenses and certifications
Purpose:
• compliance with operational and administrative requirements
⚠️ Users are solely responsible for ensuring they have the legal right to collect and process such data.
________________________________________
3.4 Operational Data
• Vessels
• Crew and guest profiles
• Maintenance records
• Budget and expenses
• Port visits
• Watchkeeping schedules
• Contacts
• Documents (PDFs, images, files)
Purpose:
• core functionality of the Service
________________________________________
3.5 Device & Technical Data
• Device information
• Log data
• Usage events
• Crash reports (Crashlytics)
Purpose:
• security
• performance monitoring
• debugging
________________________________________
3.6 Analytics Data
The Service uses analytics tools to understand usage patterns, improve performance, and enhance user experience.
________________________________________
3.7 Contacts Access
If permission is granted, the app may access device contacts to import information.
• Access is explicitly requested
• It is optional
• Controlled by the user
________________________________________
3.8 Location Data
The app may use location services (maps, nearby places) when enabled by the user.
________________________________________
3.9 Notifications
Push notifications are sent using Firebase Cloud Messaging.
________________________________________
3.10 Payments
Payments are processed through:
• Apple App Store
• Google Play
• Stripe (web only)
• RevenueCat
The Service does not store full payment details.
________________________________________
4. Legal Basis
Data is processed based on:
• Contract performance
• Legitimate interest
• Legal obligations
• User consent (where applicable)
________________________________________
5. Data Storage & Security
Data is stored using Google Firebase infrastructure:
• Cloud Firestore
• Cloud Storage
Security measures include:
• Encryption in transit using secure protocols (HTTPS/TLS)
• Encryption at rest
• Role-based access control
________________________________________
6. Data Sharing
We do not sell personal data.
Data may be shared with:
• Cloud providers
• Payment providers
• Legal authorities when required
________________________________________
7. International Transfers
Data may be processed outside the EU with appropriate safeguards.
________________________________________
8. Data Retention
• Account data: while active
• Operational data: until deleted by the user
• Backup data: temporary for security
________________________________________
9. User Responsibilities
Users must:
• Ensure data accuracy
• Maintain backups
• Use the Service responsibly
During Early Access:
• Data integrity is not guaranteed
• Structures may change
________________________________________
10. Service Evolution
Zanware Marine may:
• Modify features
• Change data structures
• Update architecture
without prior notice when necessary.
________________________________________
11. Third-Party Infrastructure
The Service depends on Google Firebase and other providers.
Availability is not guaranteed.
________________________________________
12. Limitation of Liability
The Service is provided “as is” without warranties.
To the extent permitted by law:
• No liability for indirect damages
________________________________________
13. User Rights
Users have the right to:
• Access their data
• Correct inaccuracies
• Request deletion
• Request restriction
• Request data portability
• Object to processing
Requests can be made via:
📧 info@zanware.com
________________________________________
14. Early Access Notice
• The Service is pre-release
• Features may change
• Bugs may exist
• Backups are recommended
________________________________________
15. Relationship with Terms
This Policy must be read together with the Terms & Conditions.
________________________________________
16. Language
In case of conflict, the English version prevails.
________________________________________
17. Tracking
The Service does not use data for tracking users across third-party apps or websites and does not engage in advertising tracking.
Last updated: [fecha]
Data Controller: Jose Zanon Rodriguez
Contact: [info@zanware.com](mailto:info@zanware.com)
Public URL: <https://zanware.com/privacy/>

