Privacy Policy

Account information includes the name and email address you provide, password-based sign-in and session records, and the account type you select. A phone number is optional. Signup also records the privacy-policy version and label shown to you, the account type, and the time you accepted it. Terms acceptance is recorded separately.

Vessel owners can add vessel and equipment details, service dates, engine hours, notes, receipts, photos, documents, maintenance reminders, service requests, and conversations. Marine service providers can add business and service-area details, categories, listings, work photos, and service records. Keelstory also stores booking, service-history, and payment-status records created through these features.

Visitors who send a private Help or website message provide a name, email address, and message. Keelstory stores the message thread and provides visitor access through a link that expires after 30 days.

For account-security alerts, the app records a device marker and browser user-agent when available. The site also stores a generated visitor identifier in browser local storage and sends that identifier with Keelstory’s site identifier to Polsia’s page-view beacon.

Keelstory uses submitted information to create and maintain accounts, provide vessel and provider features, keep service histories, handle service requests and conversations, display listings you publish, send account and requested service notifications, operate membership and payment flows, and protect account access.

When you use an AI chat feature, the chat content is sent to Polsia’s AI service for processing. When you use a payment flow, Keelstory sends checkout information through its Polsia billing integration and stores the resulting checkout reference and payment status.

Vessel records are available to the account that manages them unless that account uses a sharing or service workflow. An owner can create a link for one service entry or selected service-history entries. Anyone with an active link can view those selected entries without signing in. The shared view can include the entry title, service type, date, engine hours, notes, source, and provider name when available. The owner can revoke a link in Keelstory.

When you send a service request, booking request, or message to a marine service provider, that provider and authorized members of its provider account can see the information and files you submit for that interaction. Providers can submit service records for an owner to review; approved records become part of the vessel’s service history.

Provider profiles, provider listings, work photos, and vessel-sale listings are visible publicly while published. Public listing pages show the details entered for the listing, such as business or vessel information, service area or sale location, description, price, and photos.

Keelstory uses Polsia-connected services to deliver account and service emails, route website-message submissions to the owner, store files uploaded through the app, process AI chat requests, and collect page-view counts. The relevant email address and message, uploaded file, chat content, or visitor identifier is sent when you use the corresponding feature.

Payment checkout is hosted by Stripe through Keelstory’s Polsia billing integration. Keelstory receives and stores checkout references and payment outcomes; payment details are entered in the hosted payment flow.

The product materials available for this policy do not identify every hosting, database, storage, analytics, email, or payment subprocessor, their processing locations, or their retention periods. No additional vendor or data-transfer claim is made here.

You can request permanent account deletion from account settings. The deletion flow ends sign-in and removes account-only data handled by that flow, including private vessel documents and reminders, account links, and provider profile and listing content associated with the account. Public profile and listing content owned by the deleted account is removed.

The app preserves records that are shared with or still needed by other accounts, including service history, booking and service records, and related payment records. The signup record keeps the accepted Privacy Policy version, acceptance time, and account type, while a separate Terms record keeps Terms acceptance. Account deletion clears the signup record’s phone number and email/text update choices but leaves the acceptance records.

The product materials do not specify fixed retention periods for remaining shared records, account-acceptance records, uploaded files, analytics, payment records, backups, or service-provider copies. Keelstory has not published a time-based retention schedule in the materials reviewed for this policy.

Keelstory uses Better Auth for account sign-in and session handling. Protected account, vessel, and provider operations check the signed-in account and its applicable ownership or provider permissions. Service-history links use randomly generated tokens stored as hashes and expose only the entries selected for that link; an active link does not require sign-in and can be revoked by its owner.

The available product materials do not establish encryption, backup, monitoring, incident-response, or security-certification details. This policy makes no claim about those practices.

Email and text update choices are optional at signup, and a phone number is requested only if you select text updates. A separate optional signup choice covers Keelstory email announcements. You can choose an additional channel for booking-reply alerts in account settings. The app does not currently expose a self-service control for changing the signup email/text choices or disabling its page-view beacon.

You control whether to publish provider or vessel-sale listings and which service entries to put in a share link. You can revoke an active service-history link or request account deletion in Keelstory. For a privacy question or request, email keelstory@polsia.app.

The product materials reviewed do not identify the legal entity operating Keelstory, its mailing address, or the jurisdictions in which it offers the service. They also do not establish retention periods for each data category and vendor, a complete processor and subprocessor list with data locations, analytics opt-out and retention behavior, whether AI requests are retained or used to train models, or details about encryption, backups, access monitoring, legal requests, and incident response. Keelstory must supply those facts before this policy can make claims about them.