1. Who is responsible #
The data controller for the Vessly apps and this website is the publisher named below. Questions, access requests and deletion requests go to the e-mail address listed here. If you are in the EU/EEA, the UK or Türkiye (KVKK), the same address is your point of contact for your rights under those laws.
- Publisher: GenX Development
- Postal address: KARAR-BEKLİYOR
- E-mail: support@vesslyapp.com
2. The short version #
- Used on your own, Vessly needs no account. Boats, engines, records, photos and tasks live in a database on your phone, and the app works fully offline.
- Vessly Fleet is optional. If you create a Fleet account, the boats you share with your crew are stored on our servers (Cloudflare) so every member sees the same data.
- AI Mechanic is optional and you start every conversation. Your question and a short summary of the boat are sent through our server to Anthropic, the AI provider. We do not keep the conversation.
- The app sends anonymous crash reports and usage statistics (Firebase). They never contain what you type, and they are tied to a random installation ID, not to you.
- No ads, no advertising identifiers, no tracking across apps, and we never sell or rent your data.
3. Using Vessly on your own #
Without a Fleet account, everything you enter is stored in a local database on your device (SQLite). That includes your boat profile (name, type, make and model, year, hull number), engines and their hours, maintenance records with amounts and notes, tasks and reminders, expenses and receipts, documents, checklists, logbook entries, inventory, contacts, and the photos you attach.
None of this is uploaded anywhere by default. We have no copy of it and cannot see it. The only data that leaves your phone in this mode is the anonymous diagnostics described in section 8.
Photos. When you attach a photo or scan a receipt, the app removes GPS location metadata from the image before saving it and keeps only the date and orientation. Photos stay in the app's private storage and are included only in the exports, backups or fleet syncs you choose to make.
Permissions the app may ask for
- Notifications — for maintenance reminders. Reminders are generated on your phone; if you decline, they still appear inside the app.
- Camera — only when you choose to take a photo of a receipt, a part or a boat. The photo picker is used for existing photos. On iOS the camera is offered only where the system permission text is available.
- Network — needed for Fleet, AI Mechanic, cloud backup and anonymous diagnostics. Everything else works offline.
Vessly does not request your location, your contacts list, your microphone or your calendar.
4. Backups #
You can create a backup file at any time and keep it wherever you like. It is a ZIP archive containing a manifest, a copy of the app database and your photos and documents. You can also export your full history as PDF and CSV, free of charge.
With Vessly Pro you can turn on automatic cloud backup to your own Google Drive. The app asks Google for the narrowest permission available (`drive.appdata`): a hidden, app-only folder in your Drive that no other app, and no person, can browse. The backup goes from your phone to your Google account. We do not have access to it, and it never passes through our servers. Google stores it under Google's own privacy terms.
You can disconnect Drive at any time in Settings. Uninstalling the app or revoking its Drive access may delete the backup, so keep a recent backup file if you are about to change phones.
5. Vessly Fleet account #
Fleet lets several people work on the same boats. It is the only part of Vessly that needs an account, and the only part that stores your boat data on our servers.
Signing in. You sign in with Google or with a one-time code sent to your e-mail address. We do not store your Google ID or your e-mail address as such: the server keeps a one-way SHA-256 hash of the identity, plus the display name you choose. The one-time code is kept for ten minutes and then discarded. Sign-in e-mails are sent through Resend.
Where. Fleet data is processed and stored on Cloudflare's network (D1 database, Durable Objects and object storage). Data is encrypted in transit with TLS. Each fleet (organisation) is isolated in its own storage object; data from one fleet is never loaded next to another's.
What the server stores for a Fleet account
- A hashed identity, your display name, and, if you were invited by e-mail, the invited e-mail address shown to the other members of that fleet.
- The fleets you own or belong to, your role in each, and the invitations you have created or accepted, including the version of the crew consent you agreed to when joining.
- The shared boat data of those fleets: boats, engines, maintenance records, tasks, checklists, expenses, documents, logbook entries, inventory, contacts and the photos attached to them. Amounts can be hidden from crew by the owner; hidden amounts are not sent to those members at all.
- A push notification token for each signed-in device (see section 9).
- Your subscription state for Fleet (plan tier, boat limit, active or not) and the RevenueCat customer ID it is linked to. No card or bank details.
- Technical logs on the server (request time, status, error messages) kept briefly for operations. They do not contain your boat data.
How long it is kept
- Fleet data stays as long as the fleet exists. If a Fleet subscription lapses, the data is not deleted: the fleet becomes read-only after the grace period and the owner can export everything at any time.
- When you leave a fleet, the entries you added stay with the fleet and your name is shown as "Former member". That is what you agree to when you join.
- When you delete your account (Settings → Fleet → Account → Delete account), your hashed identity and display name are erased, your device tokens and billing record are removed, fleets you own are dissolved together with their data and photos, and your RevenueCat customer record is deleted. Memberships in fleets owned by others are closed and your name is cleared from them.
- Operational backups of the fleet database are kept for a limited time for disaster recovery and are then deleted.
6. AI Mechanic #
AI Mechanic answers a fault description with a first diagnosis based on your own boat. You start every conversation; nothing is sent until you type a message.
What is sent. Your message, the response language, and a short context block built from your log: boat type, model and year; up to four engines with their hours; up to five recent maintenance records (date, category, title, engine hours); and up to eight items of installed equipment (name, category, model or serial). Boat names, amounts, notes, photos and documents are not included.
Where it goes. The request goes to our server (Cloudflare Worker), which forwards it to the Anthropic API (model: Claude Haiku) and streams the answer back to you. Our server does not store your messages or the answers. It keeps only a monthly message counter per hashed identity so that the allowance (15 messages a month on Free, 30 on Pro) can be enforced, and a running cost budget.
At Anthropic. Anthropic processes the request as our service provider under its commercial API terms. Its retention and use of API data are governed by those terms and by its privacy policy; we do not grant Anthropic any other rights to your data.
AI Mechanic is advice, not a diagnosis. See the Terms of Use for what that means. Anthropic processes requests under its commercial API terms, which do not allow using customer data to train its models.
7. Purchases and subscriptions #
Vessly Pro and Vessly Fleet are sold as subscriptions through the App Store (iOS) and Google Play (Android). Apple or Google processes the payment; we never receive or store card or bank details.
To know which features to unlock, the app uses RevenueCat. RevenueCat receives the store receipt and an app user ID. Without a Fleet account that ID is a random, anonymous identifier created on your device. When you sign in to Fleet, the ID is linked to your Fleet user ID so that a Fleet subscription can be recognised on every device you sign in on. RevenueCat stores your purchase history for that ID; the store itself always remains the source of truth for billing, renewals and refunds.
If you delete your Fleet account, we also delete the RevenueCat customer record (section 5). Your store subscription is between you and Apple or Google: manage or cancel it in your App Store or Google Play subscription settings.
8. Crash reports and usage statistics #
To find crashes and to see which parts of the app are actually used, Vessly uses three Google Firebase services: Crashlytics (crash reports), Analytics (usage events) and Performance Monitoring (how fast screens and operations run). Firebase App Check is also used so that only genuine copies of the app can talk to our server.
- A crash report contains the stack trace, device model, operating system version and app version. It never contains your boats, records, photos or anything you typed.
- Usage events carry technical values only: screen and component names, counts, durations, the app version and language, device model and OS version. The list of allowed event names and parameters is fixed in code and tested; free text, names, e-mail addresses, boat names, amounts, serial numbers, locations and identifiers can structurally not be sent.
- You are identified only by a random installation ID generated on your device. It is not linked to your Fleet account, e-mail or Google account, and it is reset when you use "Delete all data" or reinstall the app.
- The app contains no advertising SDK. On Android the advertising-ID permission is explicitly removed from the app; on iOS the app does not ask for tracking permission.
- Crash reporting and analytics are switched off in development builds.
Google processes this data as our processor under the Firebase terms. None of it is used for advertising.
9. Notifications #
Maintenance reminders are created and shown by your phone. No server is involved.
Fleet notifications (for example a task assigned to you) are push messages. When you sign in to Fleet, the app registers a push token for your device with our server, which stores it together with your Fleet user ID and platform. Messages are sent through Firebase Cloud Messaging (Android, and iOS via Apple Push Notification service). They are data-only: the server sends a message key and identifiers, and your phone composes the text in your language. Tokens are deleted when you sign out of a device or delete your account.
10. Support requests #
If you send a support request from Settings → Help in the app, your message reaches our mailbox by e-mail (sent through Resend) together with the app version, your device model and your app language. Your e-mail address is included only if you choose to give one, and it is used only to reply to you. No boat data, photos or amounts are sent. Requests are rate-limited per identity to prevent abuse. We keep no support database: the request lives in our mailbox until the matter is closed.
The contact form on this website is not yet connected; the Contact page currently points you to e-mail. Nothing you type on this site is sent anywhere until you send it yourself.
11. What we do not do #
- We do not sell, rent or trade your data, and we do not share the content you enter with anyone other than the service providers listed in section 16, who act on our instructions.
- We do not show ads, and the app contains no advertising identifiers or tracking SDKs.
- We do not build profiles of you for marketing.
- We do not collect your location.
- We do not read your backups in Google Drive and cannot.
- We do not use your AI Mechanic conversations or your boat data for anything other than answering you.
12. Keeping and deleting your data #
On your phone. Your data stays until you delete it. Settings → Delete all data permanently erases every local record and photo, resets the random installation ID used for diagnostics and, if cloud backup is connected, deletes the backup in your Google Drive. You can export everything first (PDF, CSV and backup file).
Fleet account. Settings → Fleet → Account → Delete account removes your account from our servers as described in section 5, immediately. If you only want to leave a fleet, the owner can remove you or you can leave; your past entries stay with that fleet under "Former member".
Fleet data without a subscription. A lapsed Fleet subscription never deletes data; the fleet becomes read-only and the owner can export it at any time.
Your rights. Depending on where you live (GDPR, UK GDPR, KVKK and similar laws), you may have the right to access, correct, export, restrict or delete your personal data and to object to processing. For data on your phone you can do all of this yourself in the app. For Fleet data, write to the address in section 1; we answer within 30 days. You also have the right to complain to your local data protection authority.
13. Children #
Vessly is not directed to children under 13 and we do not knowingly collect personal data from them. The app stores are configured with a 4+ rating because the app contains no objectionable content, but a Fleet account may only be created by someone aged 13 or over (16 where local law requires). If you believe a child has created a Fleet account, contact us and we will delete it.
14. Changes and contact #
When this policy changes, the date at the top changes with it and meaningful changes are announced in the app. Earlier versions are available on request. Questions about privacy, requests under data protection law, and anything else about this policy:
E-mail: support@vesslyapp.com · Contact page
15. This website #
This website is a set of static pages. It does not use cookies and runs no analytics or tracking scripts. The only things it stores in your browser are your preferences — light or dark theme, your language, and whether you closed the announcement bar — in your browser's local storage, which never leaves your device. The site loads fonts and images from the same server; nothing is fetched from third-party servers. If we ever add privacy-friendly analytics, this section will say so first.
Hosting provider: KARAR-BEKLİYOR
16. Service providers #
These are the companies that process data on our behalf, and only for the purposes shown. The same list is used on the Security page.
| Provider | What for | What it receives |
|---|---|---|
| Apple (App Store) | Selling and billing subscriptions on iOS; push delivery (APNs) | Payment details (never seen by us); push token |
| Google Play | Selling and billing subscriptions on Android | Payment details (never seen by us) |
| RevenueCat | Recognising active subscriptions across devices | Store receipt, app user ID (random, or linked to your Fleet ID), purchase history |
| Google Firebase | Crash reports, anonymous usage statistics, performance, App Check, push messaging | Random installation ID, device model, OS and app version, technical events; push token |
| Cloudflare | Running our server; storing Fleet data; relaying AI Mechanic requests | Fleet boat data and photos, hashed identities, display names, device tokens, subscription state |
| Anthropic | Answering AI Mechanic questions | Your message and the boat context block (no names, amounts, notes or photos) |
| Resend | Sending sign-in codes and support e-mails | Your e-mail address, the one-time code or your support message |
| Google Drive (your account) | Optional Pro cloud backup, in your own Google account | Your backup, in a hidden app-only folder we cannot access |
How each of these is used, and what never leaves your phone, is described step by step on the Security page.