Privacy Policy

1. Who is responsible

RAMJOHN CAPITAL GROUP LLC is the platform operator and a Massachusetts limited liability company. Contact ramjohncapital@gmail.com for privacy questions or requests. Operators are independent businesses responsible for their own service and guest-data practices.

Yamira acts as a controller for platform accounts, billing, security, support, and purposes it determines. When processing an operator’s guest or team information on its instructions, Yamira acts as its service provider or processor under the Data Processing Addendum. Roles depend on the actual processing, not simply on an account label.

2. Information we handle

Account and contact information includes names, email addresses, telephone numbers, account identifiers, organization membership, preferences, and authentication records. Booking and operational information includes dates, guest counts, passenger names, manifests, packages, assignments, customer notes, invoices, refunds, and support records.

Users may upload business, vessel, identity, or booking documents. Provide only what is necessary; avoid uploading unnecessary sensitive information. Authorized location sharing can include latitude, longitude, accuracy, heading, speed, driver and assignment identifiers, and update times.

Payment providers handle payment credentials. Yamira receives transaction identifiers, status, amounts, currency, connected merchant information, and relevant dispute or settlement records. Do not submit full card numbers or passwords through Yamira support or documents.

Connected Google Calendar accounts provide the authorized calendar event data and OAuth credentials needed for synchronization. Technical information may include IP addresses, device/browser information, cookies, logs, error reports, and service activity.

3. Purposes and legal bases

We use information to establish accounts, deliver bookings and operations, provide authorized synchronization and tracking, process billing, communicate service changes, resolve complaints, prevent abuse, maintain security, and meet legal obligations. Operational analytics and benchmarking are described in the AI and Analytics Notice.

Where a law requires a legal basis, processing may rely on performing a contract, legal obligations, legitimate interests balanced against individual rights, or consent where required. Marketing, optional tracking, and sensitive-data uses must have an appropriate independent basis; accepting platform terms does not provide blanket consent for every use.

4. Who receives information

The operator delivering a booking and its authorized personnel receive relevant guest and operational information. Access is limited by roles and legitimate responsibilities. Authorized Yamira personnel may access records for support, security, payment administration, compliance, and operational oversight.

Service providers may include Supabase for database, authentication and storage; Vercel for hosting; Resend for transactional email; Stripe and PayPal for payments; and Google for elected Calendar synchronization or Maps functionality. Each receives information relevant to its function. Applicable provider terms and privacy practices also govern its independent processing.

We may disclose information where lawfully required by authorities, to protect legal rights or safety, or in a business transfer subject to appropriate confidentiality and lawful safeguards. We do not sell guest contact information. Operators must not use received guest data for unrelated unsolicited marketing.

5. Google user data

Google Calendar access is used to deliver synchronization requested by the connected user or organization. We request the calendar.events permission for event synchronization; users can disconnect in Yamira or revoke access in their Google account.

Use and transfer of information received from Google APIs must adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not used for advertising, sold, or used to train general-purpose AI models. Human access is limited to allowed support, security, legal, or user-authorized purposes.

6. Transfers, security, and retention

Yamira and its service providers may process information in the United States and other countries where their services operate. Where required, we use appropriate contractual or other lawful transfer safeguards. A vendor’s presence in this notice does not itself establish a transfer mechanism.

We use access controls, authenticated workspaces, and other appropriate technical and organizational safeguards. No service can guarantee absolute security. Retention depends on purpose, legal obligations, disputes, and the schedule in the Data Retention and Requests Policy. Backups and legally retained records may remain after an operational deletion.

7. Choices and requests

Depending on applicable law, individuals may request access, correction, export, deletion, restriction, or objection, and may withdraw consent for processing based on consent. You can submit a request through https://yamiraos.com/legal/requests or email ramjohncapital@gmail.com. We verify identity proportionately and apply the relevant legal response deadline.

Guest requests about an operator’s records may be coordinated with that operator. Deletion may be limited by legal obligations, active bookings, financial records, disputes, or security needs. We explain applicable restrictions; closing an account is not a promise to erase all records immediately.

You can stop location sharing, disconnect Calendar, and manage supported browser storage. Essential service messages may still be sent. Complaints may also be raised with a competent privacy regulator.

8. Children and changes

Platform accounts and payment authorization are intended for adults with legal capacity. Operators must obtain appropriate guardian permissions where children participate in an experience and minimize collection of their information. We do not knowingly offer account registration to children.

Material changes will be announced through the platform or appropriate account contact where reasonably practicable. The version and effective date appear on this page.