uDock.me

Privacy at uDock.me

Updated 18 November 2026 · Applies to the live uDock.me service.

uDock.me helps boaters explore marinas and private docks, submit berth requests and ask to verify their relationship with a marina. Contact support@udock.me for account help or privacy requests.

Privacy notice version 2026-11-18 · Private Docks update

Information used by the service

Private Docks contact and arrival access

You can sign in to message a host before booking. Messages use plain text. Keep personal contact details, exact addresses, access codes, identity documents and outside links out of messages and public listing fields. Automated checks catch common disclosures. Report concerns to support@udock.me.

For new stays, the host must approve the request and uDock support must separately verify the booking for arrival access. Support uses a booking-specific account and request check and records the reviewer, outcome and time. This flow does not collect identity documents. The requesting boater can open the saved exact address, pin and arrival instructions through the booking through the departure date in the dock’s local time. Previously accepted stays keep their original access while accepted unless revoked. Cancellation, revocation or an inactive participating account stops future access. Information already viewed or copied cannot be recalled.

For a new verified stay, either participant can choose to share their current account email with the other participant for that stay. Sharing starts off and can be withdrawn. We record a protected match for the selected address to avoid sharing a changed address automatically. The optional account phone remains private. Hosts receive generic alerts when email delivery is available and can turn them off in each conversation. Boaters can opt in. For those alerts, Resend receives the recipient account address and generic notice. The alert contains no message, address, access instructions or other participant’s contact details.

AI Marina Concierge

Where enabled, authorized booking staff can use the AI Marina Concierge to review a berth request and draft a reply.

Preparing a draft sends the requested dates and vessel dimensions to OpenAI.

If excerpt sharing is enabled for the marina, staff can review and choose to include a short excerpt from the booking owner’s latest message in that conversation. uDock.me masks common contact details and known names before showing the preview. Staff check for any remaining sensitive details before sharing the excerpt.

The booking fields sent to OpenAI exclude account identifiers, structured contact details, vessel names, staff notes, attachments and information from other bookings. Staff review the draft and send any reply through the booking conversation.

uDock.me disables saved response history for these requests.

OpenAI may retain input and output in abuse-monitoring logs for up to 30 days by default. Legal or safety exceptions may extend retention.

OpenAI may also temporarily cache request data.

OpenAI API data controls

Cookies, saved preferences and visitor statistics

Essential cookies keep you signed in and protect requests. A short-lived cookie supports social sign-in callbacks. They are required for account security and cannot be turned off from the service. Your browser may also save functional choices such as your cruising area, display preferences and language. To recover safely from an interrupted private dock booking request, we temporarily retain its command identifier, vessel identifier, dates and displayed quote in this tab’s session storage. This essential recovery record is separate from optional analytics and is removed when the request result is confirmed or the browser session ends.

When you first visit, you can accept or reject optional analytics cookies. If you reject them, uDock.me does not create anonymous visitor or session identifiers and does not send visitor analytics events. We save your choice in browser storage so that we can remember it; you can change it at any time through Cookie choices in the site footer. If you accept, uDock.me hashes those anonymous identifiers on the server and uses them to produce aggregate counts for visitors, sessions, page views, viewed marina profiles, site sections, device class, operating-system family, browser family, website or app source, reported app version, workspace audience (Boater, Marina or Platform Admin), language, referring website domain and approximate geography. Geographic totals use country supplied by the hosting platform when available, otherwise a validated combination of browser time zone and regional locale. Visitor analytics indicate whether a view came from a signed-in account, but do not store the account identity, full user-agent string, raw IP address, precise coordinates or street-level location. These aggregate records are kept for up to 400 days. The directory does not need your device’s precise location to work.

The visible map area is sent to uDock.me to load marina results. Your location is not saved to your profile.

External maps and sign-in providers

Standard map images and marine features are requested from OpenStreetMap and OpenSeaMap services. Optional satellite and hybrid imagery comes from MapTiler. While a host types a dock address, the address search sends that text to MapTiler to suggest matching addresses and coordinates. Map providers receive normal web-request information, including your IP address and requested map area. MapTiler requests send the website origin, without the private page path, account identifiers or booking details. Address search is part of dock setup and is separate from optional visitor analytics; you can enter an address and coordinates manually. Selecting a suggestion or adjusting the pin changes the draft form; the listing changes only when you save it. Public dock maps continue to use approximate coordinates. If you choose social sign-in, your browser visits the selected provider and its own privacy terms apply.

OpenStreetMap privacy policy · MapTiler privacy policy · Google · Apple · Meta

Service emails

When email notifications are enabled, uDock.me sends account, berth-request and marina-claim updates through Resend. The delivery service receives the recipient address and message content, including relevant account, trip or claim details. Administrators can view delivery status; failed addresses may be suppressed to avoid repeated sending. Email queue and delivery records are stored privately. These operational messages do not subscribe you to marketing. Replies go to support@udock.me. Resend privacy policy.

Access and use

Account, request and claim information is used to operate the service, review berth requests, verify marina representatives and protect accounts. Account details and private requests are accessible to the account holder and authorized administrators. Public marina information is displayed in the directory. Submitting a request is not a confirmed reservation; an administrator reviews it. This version does not collect payment-card information.

Your choices

You can browse the directory without an account and can sign out at any time. Email support@udock.me to request access, correction or deletion of your account information. We need to verify that a request comes from the account holder. See account-deletion instructions for the process and how to disconnect a sign-in provider.

Retention and questions

Account, booking and marina-claim records remain until removed through the support process. Private Docks conversations, booking snapshots, support decisions and security records may need a separate retention review. Request account closure or data removal through support, which will explain the records it can remove and any obligations affecting active stays or disputes. Some records may need to be retained for security, unresolved requests or applicable legal obligations; support can explain what applies to your request. Backups may retain earlier copies until they are replaced. Do not include passwords, identity documents or other sensitive information in booking notes or marina-claim explanations.