Privacy Policy

1. Our privacy commitments

We design ShorePass around the following principles:

• We do not sell your personal data. We do not sell, rent, or trade personal data to data brokers or other third parties for their own marketing.
• We do not use your private messages for advertising. ShorePass does not currently operate third-party targeted advertising based on your private communications or profile activity.
• We use data for stated purposes. We collect and use data to provide ShorePass, secure it, improve it where permitted, comply with law, and support the features you choose to use.
• AI sharing is disclosed separately. When you use the AI Shore Leave Planner, information needed to generate the plan is sent to Anthropic through ShorePass's server-side integration. We provide a just-in-time disclosure and obtain the permission required before that transfer.
• Privacy controls matter. ShorePass includes controls for profile privacy, discovery, social features, analytics choices, and account deletion.
• Deletion means deletion by default. When you delete your account, ordinary account data is deleted under the process described in Section 11, subject only to narrow safety, legal, and compliance exceptions described in this Policy.

2. Personal data we collect

The data we collect depends on the features you use.

2.1 Account and authentication data

We may process:

• email address;
• username;
• authentication identifiers and session information;
• account creation and verification status;
• linked sign-in provider information when you choose Sign in with Apple or Google sign-in;
• records showing which sign-in methods are linked to your ShorePass account.

Your password is handled by our authentication provider. ShorePass does not need your plaintext password to operate the Service.

If you use Apple or Google authentication, the provider may give us identifiers and account information permitted by your provider settings, such as your name and/or email address. We do not receive your device biometric template from Face ID, Touch ID, or comparable device authentication mechanisms.

2.2 Profile and private account information

Depending on what you provide, ShorePass may process:

• first name, last name, and display name;
• profile photo or avatar;
• nationality and nationality display information;
• position and department;
• current ship and cruise line;
• year you first worked at sea;
• optional contact email;
• home currency and paid currency;
• profile privacy, discovery, and crossing-sharing settings.

Some profile information is designed to be visible to other ShorePass users according to the privacy and relationship rules described in Section 7. Other fields, including your account email, date of birth, private contact details, and currency information, are treated as private account information and are not part of the ordinary public profile.

2.3 Maritime work, contract, document, and certification information

If you use Crew Agent or related features, we may process information such as:

• cruise line, ship, department, and position;
• contract start and end dates;
• sea-service history;
• certification name, department, issuing authority, issue date, and expiry date;
• document-tracking metadata and expiry information supported by the current Service.

2.4 Planner and shore-leave preferences

When you use the Shore Leave Planner, we may process:

• port and itinerary context;
• shore-leave time window and timing choices;
• selected interests and activity preferences;
• budget range;
• meal or venue preferences;
• planner inputs you actively provide;
• relevant ShorePass venue information and community tips used to build the plan;
• generated plan results and related feature usage information.

The AI-specific transfer to Anthropic is described in Section 6.

2.5 Ports, tips, votes, saved places, and activity

When you use ShorePass's community and port features, we may process:

• tips and tip titles/content you submit;
• the port, venue, category, and other context associated with a tip;
• votes, reports, and moderation status;
• ports you save or mark as visited;
• feedback and corrections you submit;
• timestamps and identifiers needed to attribute and moderate community contributions.

Approved tips are community content and may be displayed to other users while your account remains active. Under the current deletion model, tips associated with your account are deleted when you delete the account, except for separate safety/legal evidence already captured under the narrow rules in Sections 10 and 11.

2.6 Friends, Crew Lounge, crossings, and social data

If you use ShorePass social features, we may process:

• friend requests and friendship state;
• blocks and removals;
• discovery and privacy settings;
• limited work context used for friend experiences and suggestions;
• ship/company/department context available to accepted friends under current product rules;
• future crossing information when the relevant sharing conditions are enabled;
• suggestion signals such as shared ship/company/department context or mutual connections, without exposing underlying private contract dates to strangers.

2.7 Direct messages

ShorePass currently supports one-to-one text messaging between eligible users. We process:

• message body;
• sender and recipient/conversation identifiers;
• timestamps;
• delivery/read-related state and conversation state;
• limited information needed for notifications and abuse prevention.

Private messages are not available through a general-purpose administrator chat browser. However, if a message or conversation is reported, a limited server-generated evidence snapshot may be created and made available to authorized Trust & Safety personnel as described in Section 10.

2.8 Reports, moderation, and safety evidence

If you report a user, message, or conversation, or if another user reports content involving you, we may process:

• reporter and reported-user identifiers;
• report type, category, reason, and details;
• moderation status and moderator notes;
• a bounded snapshot of relevant message context captured by the server at the time of a chat report;
• audit logs showing authorized access to report evidence.

For chat reports, the current system may capture a limited recent context of up to 20 messages so that an authorized moderator can understand the report. This evidence is separated from the live conversation and may survive later message or account deletion where necessary for safety, abuse prevention, disputes, legal claims, or compliance.

2.9 Notifications and device information

If you enable notifications, we may process:

• push-notification token and device association;
• notification event type and status;
• delivery ticket/receipt information;
• limited routing information needed to open the correct ShorePass screen.

We design social push notifications to avoid placing full private message content in push payloads.

2.10 Analytics and diagnostics

Where enabled and permitted, ShorePass may use product analytics to understand feature use and improve the Service. The current analytics implementation can associate events with a ShorePass user identifier, so we do not describe such analytics as anonymous. Optional product analytics are treated separately from the Terms and Privacy Policy acceptance and can be controlled through the Service where available.

We may also process technical diagnostics, such as app version, device/platform information, error traces, and crash information, for reliability and security. Our diagnostics implementation is designed to scrub common personal identifiers from error reports where technically feasible.

2.11 Support and communications

If you contact us, we process the information you provide, such as your email address, message, support history, and any attachments or screenshots you choose to send.

3. How we collect personal data

We collect personal data:

• directly from you, when you register, complete your profile, enter work information, send messages, submit tips, use the Planner, contact support, or adjust settings;
• automatically from the Service, such as account/session information, feature events where analytics is enabled, diagnostics, push-delivery status, and security logs;
• from authentication providers, when you use Apple or Google sign-in;
• from other ShorePass users, for example when they send you a friend request, message you, report content, or interact with your community contributions;
• from service providers and public/third-party data sources, for example venue, map, or itinerary information used to operate ShorePass. Such third-party data is not necessarily personal data about you.

4. Why we use personal data and our legal bases

The legal basis depends on your location and the specific processing. Where the GDPR applies, we rely on one or more of the bases below. Under the UAE Personal Data Protection Law, we process with consent where consent is required and may also rely on lawful statutory exceptions, including processing necessary to perform a contract, comply with legal obligations, protect rights, or establish or defend legal claims.

Purpose	Typical data	Legal basis where GDPR applies
Create and operate your account	Account, authentication, profile	Performance of our contract with you
Provide Crew Agent, port, social, messaging and planner features	Profile, work, tips, social, messages, planner data	Performance of contract; legitimate interests where appropriate
Send requested AI Planner data to Anthropic	Planner prompt/context	Your explicit permission/consent where required; performance of the requested feature after permission
Provide push notifications you enable	Push token, notification routing	Consent/permission and/or performance of requested service, depending on context
Optional product analytics	Usage events and identifiers	Consent where required; ShorePass treats this as a separate optional choice
Diagnose errors, maintain security, prevent abuse and fraud	Logs, identifiers, security events, reports	Legitimate interests; legal obligations; establishment/defence of legal claims
Moderate user content and investigate reports	Reports, relevant evidence, account identifiers	Legitimate interests in safety and integrity; legal claims; legal obligations where applicable
Respond to support and privacy requests	Contact and request data	Contract, legitimate interests, legal obligations
Comply with law and valid legal process	Relevant records	Legal obligation; legal claims; substantial/public interests where applicable

Where we rely on legitimate interests, those interests include maintaining a secure, reliable, useful community for maritime crew, preventing fraud and abuse, enforcing our Terms, protecting users and the Company, improving essential functionality, and defending legal rights. We consider the impact on your rights and use safeguards designed to limit processing to what is necessary.

Where we rely on consent, you may withdraw it for future processing at any time through the available setting or by contacting privacy@shorepass.app. Withdrawal does not make prior lawful processing unlawful.

5. Data minimization and information we do not want you to provide

ShorePass is not intended to collect special-category or highly sensitive information unless a specific feature clearly requires it and we provide an appropriate notice.

Please do not place the following in tips, messages to strangers, planner free text, support screenshots, or other general-purpose fields unless it is genuinely necessary and the feature specifically asks for it:

• passwords or authentication codes;
• full passport, national ID, seaman's-book, visa, or payment-card numbers;
• medical or health records;
• precise passenger or guest information;
• ship security procedures, access codes, restricted operational information, or confidential employer information;
• personal data about another person that you do not have a lawful right to share.

6. AI Shore Leave Planner and Anthropic

The Shore Leave Planner uses an artificial-intelligence service supplied by Anthropic.

When you choose to use the AI Planner, ShorePass sends the information needed to generate your request through a ShorePass-controlled server function to Anthropic's commercial API. The information may include your selected port, shore-leave time window, interests, budget, activity or meal preferences, other planner choices you provide, and relevant ShorePass venue/community context used to construct the plan.

ShorePass does not intentionally add your account email, date of birth, private messages, contact details, or document/certification records to the AI Planner prompt merely to generate a shore-leave plan. However, anything you personally type into a planner input can become part of the request, so do not enter sensitive personal information in Planner inputs.

Before personal data is transmitted to a third-party AI provider where required, ShorePass provides a clear disclosure identifying Anthropic and seeks the required permission. If you decline, ShorePass will not send that Planner request to Anthropic.

Anthropic processes API content under its applicable commercial terms and data-handling rules. Based on Anthropic's published commercial/API privacy information as of this Policy's effective date, Anthropic states that commercial API inputs and outputs are not used to train its models unless the commercial customer explicitly opts in, subject to its safety, abuse-prevention, and legal processes. Anthropic's policies and retention practices may change independently of ShorePass; we will update our disclosures when a material change affects ShorePass users.

AI output can be incomplete, inaccurate, outdated, or unsuitable. The Planner is an informational convenience, not a navigation, safety, immigration, medical, financial, or legal service. Always independently verify opening hours, transport, local restrictions, safety conditions, and your ship's official all-aboard time.

7. Who can see information in ShorePass

Visibility depends on the feature and your settings.

• Public/discoverable profile: certain profile fields may be shown to other ShorePass users when your profile is not private and discovery is enabled.
• Exact profile access: under current product rules, an exact known username or valid profile route may allow access to a limited non-private profile even if broad search discovery is disabled.
• Accepted friends: accepted friends may see additional limited maritime work context, such as current/next ship, company, and department. Contract dates are not exposed through that friend-context surface.
• Crossings: future crossing information is subject to the applicable friendship and sharing controls. ShorePass does not treat crossing sharing as permission to expose your full contract history.
• Tips: approved tips are community content and may be visible to ShorePass users.
• Messages: direct messages are visible to conversation participants, except for the narrow report/evidence and lawful-disclosure circumstances described in this Policy.
• Moderation: authorized Trust & Safety personnel may access report-bound evidence. ShorePass does not provide administrators with a general unrestricted chat-reading feature.

You are responsible for reviewing your privacy and discovery settings and for considering what you choose to share with other users.

8. When we share personal data

We do not sell personal data. We may share or make data available in the following circumstances.

8.1 Service providers and processors

We use suppliers to operate ShorePass. Depending on the feature and configuration, these may include:

• Supabase for database, authentication, server functions, and storage;
• Anthropic for AI Planner generation when you choose and permit that feature;
• Expo and platform push infrastructure for push-notification delivery;
• Sentry for diagnostics and error monitoring where enabled;
• PostHog for optional product analytics where enabled and consented to as required;
• Apple and Google for authentication, app distribution, and platform services you choose to use;
• Google Maps/Places or similar location/venue data providers for venue and map-related functionality;
• website, DNS, security, and communications providers necessary to host ShorePass and communicate with users.

These providers receive only the data reasonably necessary for their role. We require providers to handle personal data under applicable contractual and legal protections. Their independent services may also be governed by their own privacy terms.

8.2 Other users

We share profile, social, work-context, tip, crossing, and message information with other users only as necessary for the relevant feature and according to the applicable privacy/relationship rules.

8.3 Legal, safety, and rights protection

We may disclose information where we reasonably believe disclosure is required by applicable law, a binding court order, warrant, subpoena, regulatory demand, or equivalent lawful process; is necessary to protect the rights, safety, and security of users or others; or is necessary to establish, exercise, or defend legal claims.

Where lawful and appropriate, we may challenge requests that appear invalid, disproportionate, or overbroad. We may notify the affected user unless prohibited by law, court order, or a legitimate safety/investigative need.

We cannot disclose data that we no longer hold. A valid preservation request received before ordinary deletion may require us to preserve narrowly scoped material as described in Section 11.

8.4 Corporate transactions

If ShorePass or JP Aureon LLC is involved in a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, relevant information may be disclosed under confidentiality and data-protection safeguards. Where required, we will provide notice or obtain consent before data becomes subject to materially different privacy practices.

9. No sale of personal data and no data-broker business

If ShorePass later introduces advertising or other materially different monetization involving personal data, we will update this Policy and obtain any consent or provide any opt-out legally required before beginning that processing.

Third-party links may use ordinary referral or affiliate parameters when such commercial links are introduced. Clicking an external link may take you to a third party that collects information under its own privacy policy. ShorePass will provide appropriate affiliate disclosure where required.

10. Moderation evidence, legal holds, and access to private communications

ShorePass is designed so that ordinary administrators cannot freely browse private messages.

There are narrow exceptions:

1. User reports. If a user reports a specific message or conversation, ShorePass may create a server-side evidence snapshot containing the reported material and limited surrounding context. This is available only through restricted moderation functions to authorized roles and access is auditable.
2. Specific preservation/legal holds. A highly restricted authorized process may preserve evidence tied to a specific message or conversation where there is a legitimate legal, safety, dispute, or compliance need. ShorePass does not currently implement broad subject-wide preservation of all of a person's communications.
3. Lawful demands. We may retrieve and disclose information still held by ShorePass in response to valid legal process as described in Section 8.3.

Preserved evidence is not used for ordinary product analytics or advertising.

11. Retention and account deletion

We keep personal data only for as long as reasonably necessary for the purpose for which it is processed, taking account of the nature of the data, user expectations, security and abuse-prevention needs, contractual needs, applicable legal obligations, disputes, and limitation periods. Where a fixed retention period has not been formally established, we use purpose-based retention criteria rather than inventing a universal period.

11.1 While your account is active

Core account, profile, social, work, message, and feature data is generally retained while needed to provide the feature, subject to your ability to edit/delete particular information and our safety/legal obligations.

11.2 When you delete your ShorePass account

ShorePass provides in-app account deletion and an external deletion resource at https://shorepass.app/account-deletion.

Under the current deletion architecture, account deletion is designed to remove the real authentication identity and ordinary user-associated data, including, as applicable:

• profile and private-profile information;
• contracts, supported document metadata, and certifications;
• planner data;
• friendships, blocks, and social state;
• ordinary direct conversations and messages;
• user notifications and push-device associations;
• saved/visited-port data and votes;
• user-created tips, including approved tips under the current policy;
• avatar files and ordinary user-owned storage covered by the deletion process.

Deleting your account does not merely “freeze” it.

11.3 Narrow information that may survive deletion

Some information may remain where deletion is not legally required or where retention is reasonably necessary and lawful, including:

• report/moderation evidence already captured to investigate abuse, safety issues, or disputes;
• specific message/conversation preservation evidence already captured under a valid scoped legal/safety hold;
• minimal deletion audit records designed to document that a deletion occurred without retaining ordinary profile content;
• records required by law, court order, regulatory obligation, fraud prevention, security, or the establishment, exercise, or defence of legal claims.

Where identifiers can be removed or de-linked consistently with the retention purpose, ShorePass uses that approach. Retained evidence remains access-restricted and is not restored as a new account if you later re-register.

A deleted user who later registers again receives a new account identity. ShorePass does not automatically reconnect the new account to the deleted profile, messages, friendships, or other deleted data.

11.4 Service-provider residual copies

Deletion from ShorePass's active systems may not instantly erase every residual copy that a service provider must temporarily maintain in restricted backup, security, anti-abuse, or legal systems. Such residual data is not used as an active ShorePass account and remains subject to the provider's applicable deletion/retention controls and our contractual/legal requirements.

12. International data transfers

ShorePass is operated from the United Arab Emirates and uses international technology providers. Your personal data may therefore be processed in the UAE, European Economic Area, United States, or other countries in which our providers operate.

Where the GDPR or another law requires safeguards for an international transfer, we use an applicable lawful transfer mechanism available for the relevant processing, which may include an adequacy decision or contractual safeguards such as Standard Contractual Clauses, together with supplementary safeguards where required. Where UAE law requires conditions or safeguards for cross-border processing, we take steps designed to satisfy the applicable UAE requirements.

You may contact privacy@shorepass.app for information about the safeguards applicable to a particular category of transfer.

13. Security

We use technical and organizational measures designed to protect personal data against unauthorized access, loss, misuse, alteration, and disclosure. Depending on the system, measures include authenticated access, role-based authorization, row-level database controls, server-side handling of privileged credentials, encryption in transit, access logging for sensitive moderation functions, data minimization, input validation, rate limiting, and controlled account-deletion processes.

No online service can guarantee absolute security. You are responsible for keeping your credentials secure, maintaining control of your email/provider accounts, using device security features, and notifying us promptly if you believe your ShorePass account has been compromised.

Where a personal-data breach triggers notification obligations under applicable law, we will notify the appropriate authority and/or affected users as required.

14. Your privacy rights and choices

Subject to applicable law and lawful exceptions, you may have rights to:

• obtain information about and access personal data we process about you;
• correct inaccurate or incomplete data;
• request deletion;
• request restriction of processing;
• object to certain processing, including direct marketing;
• obtain portable data where the right to portability applies;
• withdraw consent for future processing where processing relies on consent;
• complain to a competent data-protection or supervisory authority;
• receive information about relevant international-transfer safeguards;
• request review of qualifying solely automated decisions, if ShorePass ever makes such a decision about you.

Many profile and privacy choices can be managed directly in the Service. For other requests, contact privacy@shorepass.app. We may need to verify your identity before acting on a request so that we do not disclose or delete another person's data.

Where the GDPR applies, we aim to respond within the periods required by Articles 12–22 GDPR, subject to lawful extensions and exceptions. Rights are not absolute; for example, we may lawfully retain specific evidence required for legal claims, safety, fraud prevention, or legal obligations.

If you are in the UAE, the rights and safeguards available under Federal Decree-Law No. 45 of 2021 Concerning the Protection of Personal Data apply according to its scope and exceptions, including applicable rights relating to access/information, correction, deletion, restriction, objection, and data security.

If you are in the EEA or another jurisdiction with a data-protection authority, you may also lodge a complaint with the authority competent for your location or the relevant processing. We encourage you to contact us first so that we can try to resolve the issue.

Where applicable law requires JP Aureon LLC to appoint a local privacy representative, data protection officer, or similar contact, we will publish the required contact details in this Policy.

15. Automated processing, recommendations, and AI

ShorePass may use automated logic to provide functionality such as people-you-may-know suggestions, content ranking, notification delivery, moderation safeguards, and AI-generated shore-leave plans.

These features are intended to assist you and operate the Service. ShorePass does not currently use automated processing to make decisions that produce legal effects or similarly significant effects about a user's employment, immigration status, credit, insurance, medical treatment, or legal rights.

The AI Planner output is generated by an AI model and is not a decision by ShorePass about your rights or eligibility for anything.

16. Children

ShorePass is intended for adults and requires users to be at least 18 years old. We do not knowingly permit children under 18 to create ShorePass accounts. If we learn that an under-18 account has been created, we may suspend and delete it, subject to any legal obligation to preserve specific information.

If you believe a minor has provided personal data to ShorePass, contact privacy@shorepass.app.

17. Third-party sites and services

ShorePass may link to or integrate with third-party services. A third party's own collection and use of data is governed by its terms and privacy policy when it acts independently from ShorePass. We are not responsible for a third party's independent privacy practices, but we remain responsible for selecting and configuring ShorePass processors as required by applicable law and platform rules.

Before providing sensitive information on an external service, review that service's privacy terms.

18. Changes to this Privacy Policy

We may update this Privacy Policy when the Service, law, or our processing changes. The current version will be published at https://shorepass.app/privacy with its effective date and version.

Material changes will be communicated in a manner appropriate to the change and applicable law. Where a change requires new consent, we will seek that consent before beginning the relevant processing. An update to explanatory privacy wording does not by itself mean we will treat you as having consented to a new optional purpose.

Historical versions may be maintained so that the version applicable at an earlier date can be identified.

19. Contact us

Data controller:
JP Aureon LLC
Shams Business Center
Sharjah, United Arab Emirates

Privacy: privacy@shorepass.app
General support: hello@shorepass.app

For account deletion, you may use the in-app deletion feature or visit:
https://shorepass.app/account-deletion