Marea
Privacy policy
This policy explains how Marea processes information for its authenticated passenger and boat-provider marketplace prototype. Marea is not an emergency service and does not currently process payments or provide completed automated identity verification.
Information processed
- Account and security information such as email address, display name, identifiers, authentication provider, sessions, recovery and policy-acceptance events.
- Foreground passenger search location and provider location, accuracy, observation time, availability, and nearby-search security evidence. Provider locations are published only after the provider deliberately goes online.
- Passenger and provider profiles, vessel details, amenities, verification status and evidence, bookings, messages, ratings, blocks, reports, support cases, and notification records.
- Optional push-notification installation identifiers and provider tokens. Provider tokens are not returned to users and are removed on opt-out, sign-out, invalidation, or account deletion as applicable.
- Technical and security records needed to operate, diagnose, and protect the service.
How information is used
Information is used for authentication, provider eligibility, nearby discovery, booking and communication workflows, notifications, safety and abuse prevention, support, service security, and legal or operational recordkeeping.
Location safeguards
Nearby discovery requires a fresh foreground observation and returns only eligible, online providers with fresh locations. Search coordinates are used for the request and are not intended for general analytics or notification payloads. The latest account location may remain on the server until it is overwritten or the account is deleted; visibility and freshness rules determine whether it can be discovered.
Sharing and service providers
Data is shared only as needed with marketplace participants for a requested workflow and with infrastructure, email, authentication, notification, map, and secure-storage providers. Private provider evidence, exact search coordinates, credentials, and notification tokens are not public profile fields.
Retention and security
Retention depends on the record and operational need. Active account, booking, communication, safety, and support records may remain until deletion or the end of an applicable operational, legal, fraud-prevention, or dispute period. Production traffic uses HTTPS and native sessions use platform secure storage. No system can guarantee absolute security.
Your choices
You can stay offline as a provider, deny location and notification permission, control push preferences, block users, sign out, and request account deletion. Some records may be restricted from immediate deletion where a legal claim, safety investigation, fraud-prevention need, or statutory duty applies.
Contact
Email support@rolutec.com. See the Marea account-deletion page.