Seacove Intellectual Property Policy
Last updated: 11 August 2026.
This policy explains who owns what in Seacove: the app and its branding, the content you post, and the cruise line and ship names the app displays. It also explains what to do if you think something on Seacove infringes your rights.
1. Who runs Seacove
Seacove is operated by a company currently being incorporated in the EU. There is no registered company yet. See section 1 of the Terms of Service and section 1 of the Privacy page for what that means and when it changes.
2. Seacove’s own brand: name, logo, and trademark status
The Seacove name, the Seacove logo, the app’s colour system, and its overall look and feel belong to the company operating Seacove.
Honest status, stated plainly: as of this document’s date, “Seacove” is not a registered trademark. A trademark clearance search and an EUIPO filing across the appropriate classes is planned work, ahead of public launch. Using the Seacove name and logo today rests on ordinary unregistered rights (use in commerce, and, in some EU jurisdictions, protection for an established trade name), not on a registered mark. This document will be updated with the registration details once a filing is made and, later, once it grants.
Until then: don’t use the Seacove name, logo, wordmark, colour system, or any part of the app’s visual identity, for any purpose, without written permission from the company operating Seacove. This includes using them to imply an official partnership, sponsorship or endorsement that does not exist.
Font and stock asset licences. The website’s wordmark typeface and any stock photography used on the site or in marketing are used under licences that permit this specific commercial use, including embedding in an app binary where relevant. Nothing on the site or in the app uses an asset without a licence that covers it.
3. Cruise line and ship names
Seacove lists real cruise lines and real ships by name, because that is how the app functions: crew identify their own employer and vessel. Using a company’s own name and its ships’ own names to identify them, in this factual and functional way, is standard practice and does not require that company’s permission. This is sometimes called nominative use.
Logos are a different matter, and the rule is absolute: Seacove does not use, and will not use, any cruise line’s logo, house colours, ship livery, or any other trademarked visual identity, anywhere in the app or on the website. Cruise line and ship names appear as plain text only, everywhere in the product. This rule is stated once here and is binding on every screen and every page. It is not a suggestion.
4. Your content
Anything you post to Seacove, your photos, your bio, your free-text department and position fields, and anything else you write, stays yours. You own it.
By posting it, you give Seacove a licence to:
- Store it.
- Display it to other users, as the app’s features are designed to show it (your profile to people who can see it, your messages to the person you’re messaging).
- Process it as needed to run the service, including running photos through automated content moderation (see section 8 of the Privacy page).
This licence ends when you delete the specific content or delete your account, at which point it is removed from active use, subject to the retention rules in section 11 of the Privacy page (for example, a short window where deleted content might still exist in a backup before it rotates out, or where it is kept as part of an open safety investigation).
Seacove does not sell your content, license it to a third party for their own use, or use it to train a model that is shared or sold outside the product. The on-device face-matching used for verification is covered separately in section 6 of the Privacy page; it does not treat your profile photos as training material in that sense either.
You confirm, by posting, that:
- The content is yours to post, or you have the right to post it.
- It doesn’t infringe someone else’s copyright, trademark, or other right.
- Where a photo shows another identifiable person, that person consented to appear in it.
This mirrors, and does not replace, section 4 of the Terms of Service, which sets out what you cannot post.
5. Reporting infringement or a rights problem
If you believe something on Seacove infringes your copyright, trademark, or other intellectual property right, or that your image or likeness has been posted without your consent, tell us and we will act.
How to report:
- From inside the app, use the report function on the specific profile, photo, or message. This routes into the same 24-hour moderation commitment described in section 5 of the Terms of Service.
- Or write directly to support@seacoveapp.com with: what the content is, where it appears (a link or a clear description), why you believe it infringes your right, and your contact details.
What happens next. Every report is reviewed. Content confirmed to infringe a right is removed. The account responsible for it is warned, and repeated or serious infringement is grounds for suspension or termination under section 7 of the Terms of Service. If we act on a report, the affected user is told what was decided and, at a basic level, why, matching the notice-and-action approach described for content moderation generally.
A note on formal process. Seacove is a small EU-based operation without US presence, so a US-style DMCA counter-notice process is not the primary mechanism here; the process above, review and act within the same 24-hour commitment that covers every other report, is. If you are in the US and prefer to invoke DMCA procedure specifically, say so in your report and it will be handled under that framework as well, to the extent it applies.
6. If you think we got it wrong
If your content was removed and you believe that was a mistake, write to support@seacoveapp.com and say so. We will look at it again and tell you the outcome.
7. Changes to this policy
This policy changes if the facts in it change, most importantly once a trademark filing exists, or once the operating company is formally named. A new dated version replaces this one when that happens, and the old version is kept in the project’s own records rather than deleted.