MIAMI · LAUNCH PREVIEW
Privacy & beta support.
Last updated November 2, 2026. This notice describes the current RideFloaty preview for iPhone and the web.
Accounts
If you choose to sign in, Apple or Google authenticates you. RideFloaty receives an account identifier, email address (which may be an Apple private relay address), and available profile details such as your name. We store your rider or captain role, the name you save, and, for captains, your boat name and registration review status. These records support account access and captain registration.
Account information is stored using Supabase. The app is hosted on Google Cloud. These providers process data to operate the service. Your chosen sign-in provider also handles its part of authentication under its own privacy policy. RideFloaty does not ask for your Apple or Google password. Sign-in sessions use protected cookies.
Demo rides and transfers
When signed in, preview trips are stored in Supabase and include your route, guest count, departure time, illustrative price, vessel, and request status. A transfer request is shared with the verified captain of the destination or pickup vessel. That captain can approve or decline it before the rider confirms. Authorized staff can review account and trip records, manage captain verification, and keep private support notes and a history of administrative decisions. No boat is dispatched and no payment is collected. Guest demo trips and simulated decisions remain on your device; removing the app or clearing its website data removes that local history. Please use fictional details while testing.
Verified floatee bookings
When passenger services are enabled, every floatee must sign in and complete a government ID and matching-selfie check with Stripe Identity before requesting or joining a booking. Stripe handles ID and selfie collection. RideFloaty stores the provider session reference and verification status, not the ID or selfie images. See Stripe’s privacy information. These services remain unavailable until provider activation is complete.
Verified bookings store the route, departure, individual crew membership, assigned captain and boat, approved fare and payment shares in Supabase. Stripe Checkout handles card entry. RideFloaty stores payment and refund references, amounts and statuses, not card numbers. Crew members and the assigned captain can see names, verification status, payment-share status and boarding status for their booking. Authorized operations staff can manage bookings and refunds.
Invitations are single-use links. Anyone receiving a forwarded, unclaimed link can claim that seat after verification. Invitation secrets, scanner secrets and live optical patterns are stored only as cryptographic digests. Boarding uses an online captain challenge and a temporary public app key; the private key stays in app memory. We store the public key, challenge metadata and verification progress for the boarding session, and record who boarded and when. The captain’s camera is used only after permission to decode the circle on-device. Camera frames are not uploaded or stored. Contact support below for account, verification-data or booking-data deletion requests; provider records and transaction retention may require separate processing.
Boat and driver onboarding
Boat owners can submit vessel registration details, hull or official numbers, registration certificates, and maintenance records. Maintenance submissions include the service date, service provider, work performed and next service date. These files and details are stored privately in Supabase for boat approval and ongoing review. The submitting boat owner and authorized operations staff can download the files. Assigned drivers do not receive access to these documents. Staff can review submission metadata; uploads, reviews and downloads are logged. Updated documents require another boat review.
We also store driver applications, boat assignments and acceptance, engagement type, verification outcomes, evidence references and expiration dates. Do not upload Social Security cards, personal identity documents, banking details or background reports through the boat-record upload form. To request deletion of onboarding records and submitted files, use the support email below.
Service information
Hosting and authentication services may process technical request and security information, including IP addresses, request times, and error information, to operate and protect the service. This app does not include advertising or analytics SDKs. Optional nearby-dock setup requests location access; boarding scanning requests camera access. The app does not request access to contacts or the microphone.
Your choices and support
You can explore the demo without signing in, edit your account profile in the app, or sign out. To request deletion of your RideFloaty account, stored profile, and shared preview trips, or to ask a privacy question, email oscar@verdesx.com from your account email. Do not send your password or identity documents. Deleting an account does not remove device-local demo history or technical records retained by the hosting providers.
Send beta feedback through TestFlight or email oscar@verdesx.com. TestFlight may share crash information and feedback with the developer according to Apple's TestFlight privacy information.
About this beta
RideFloaty is a product preview. Routes, prices, boats, and travel times are illustrative. Preview trips do not book a ride, dispatch a boat or collect payment. The separate verified booking flow requires provider activation and operational setup before use; check the displayed provider mode before paying. Google sign-in currently supports only the developer's approved test accounts; other testers can use Apple sign-in or explore without an account.