Privacy Policy
Notice at collection (California and other US states). We collect the categories of personal information listed in Section 2 and Section 17.6 for the purposes in Section 3. We keep each category for the periods in Section 13. Section 10 explains the information we collect from public sources for the Collective.
We do not sell personal information for money. Our website uses Google and Meta advertising measurement tags, and some state laws treat that as "selling" or "sharing" personal information for cross-context behavioral (targeted) advertising. You can opt out at the "Your Privacy Choices" link in the footer of our Websites or by sending a Global Privacy Control signal (Section 6).
We do not use sensitive personal information to infer characteristics about you (Section 7).
1. Who We Are and What This Policy Covers
1.1 Who we are. CelesteOS LLC ("Company", "we", "us", "our") is a Florida limited liability company located at 7901 4th St N, #36609, St Petersburg, FL 33702, USA. We provide CelesteOS, a hosted software platform that yacht operators and management companies use to manage maintenance, safety and compliance records for their vessels (the "Service").
1.2 Defined terms in this Policy.
- "Customer" means an organization (such as a yacht operator or management company) that subscribes to the Service.
- "Authorized User" means a person a Customer allows to use the Service, such as a crew member or shore-based manager.
- "Customer Data" means the records, documents and other content that a Customer and its Authorized Users put into the Service.
- "Websites" means celeste7.ai and our other marketing web pages that link to this Policy.
- "Verifier" means our public record-checking tool at verifier.celeste7.ai.
- "Collective" means our engineering-knowledge service for equipment faults and fixes. It displays Public-Source Content to signed-in users and includes an optional, opt-in program through which participating fleets share de-identified engineering insights (Section 9).
- "Collective Site" means our Collective website at collective.celeste7.ai, including its public pages and the pages available after sign-in.
- "Public-Source Content" means posts, reports and other content that we collect from publicly available third-party sources for the Collective, and the information we derive from it (Section 10).
1.3 What this Policy covers. This Policy explains how we handle personal information when:
(a) you visit our Websites, the Collective Site or the Verifier;
(b) you contact us, book a demonstration or otherwise deal with us as a prospective customer, partner or supplier;
(c) you use the Service or sign in to the Collective Site as an Authorized User. For this item, it covers only the account, security and relationship information we use for our own purposes (see Section 1.4); and
(d) content you or others published on a public website (such as a forum post or a question-and-answer post) is collected as Public-Source Content (Section 10).
1.4 What this Policy does not cover: Customer Data. The crew records, certificates, operational records, documents and other Customer Data in the Service belong to the Customer that subscribed to the Service. For Customer Data, the Customer is the controller (or "business"), and we act only as its processor or service provider under a written data processing agreement. If you are a crew member or other person whose information appears in a Customer's records, the Customer's own privacy notice applies. Please send requests about those records to the Customer, usually your employer or the vessel's management company. If you contact us instead, we will pass your request to the relevant Customer (Section 17.3).
1.5 Related notices. Please also read our Cookie Notice (https://celeste7.ai/cookies) and our public Sub-processor List (https://celeste7.ai/subprocessors).
2. Personal Information We Collect
2.1 Information you give us.
- Contact and professional details: name, email address, telephone number, company, job title, vessel or fleet details, and the content of your messages, for example when you complete a contact form, book a demonstration or email us.
- Account details (Authorized Users): name, work email address, role or rank, assigned vessel, and password (we store passwords only in hashed form).
- Support communications: the content of support requests and our replies.
- Billing contacts: name, email and billing address of the person responsible for a Customer's account. We do not use a payment processor and do not collect payment card details: invoices are paid by bank transfer, and bank details are handled by our bank.
2.2 Information we receive from your organization. A Customer may create your Authorized User account and give us your name, work email, role and vessel assignment.
2.3 Information we receive from Microsoft. If you choose "Sign in with Microsoft", Microsoft confirms your identity to us and sends us your name, work email address, a directory identifier and your organization's tenant identifier. We never receive your Microsoft password. We also use Microsoft's services to verify sign-ins and to send the service emails described in Section 3(a) from an email account we control. We do not read or access your own email.
2.4 Information collected automatically.
- Website: IP address, approximate location derived from it (city or region level), browser and device type, pages viewed, referring page, time spent, clicks and similar interactions, and identifiers stored in cookies or similar technologies. Some of this is collected by Google and our session-analytics provider, as explained in Section 5 and our Cookie Notice.
- Service (security and operations): IP address, browser and device information, sign-in times, failed sign-in counts, session identifiers and error logs. We use this to keep accounts and the Service secure and working. The Service does not use advertising or analytics cookies.
- Collective Site: when you sign in, we process your email address, password (checked against the hashed version we hold), sign-in times and session identifiers, using the same account system as the Service, and your browser keeps a session token in local storage (Section 9.5). The Collective Site uses no cookies, analytics or advertising tools, and all of its scripts and fonts are served from its own domain, so your browser does not contact third-party content networks when you use it.
- Hosting logs: when your browser loads the Collective Site or the Verifier, our hosting provider receives standard technical information, such as your IP address, browser type, the page requested and the time, and keeps it in its logs. We use this only to deliver and secure the pages.
2.5 Information from public and professional sources. We may collect business contact details of prospective customers from publicly available professional sources, such as company websites and industry directories. For the Collective, we also collect content from public websites, which may include user names and other personal information (Section 10).
3. How We Use Personal Information
We use personal information to:
(a) provide and administer accounts: create and manage Authorized User accounts, authenticate users and send service messages (such as password-reset emails, sign-in verification codes and account notices);
(b) secure the Service: detect and prevent unauthorized access, fraud and abuse, including through sign-in lockouts and session revocation;
(c) support you: respond to questions and support requests;
(d) run our customer relationships: manage subscriptions, invoicing and renewals;
(e) communicate with prospects: respond to enquiries, arrange demonstrations and send business-to-business information about the Service. You can opt out at any time (Section 17.1);
(f) understand and improve our Websites: measure traffic and how visitors use our pages, using analytics tools where you allow them (Section 5);
(g) measure our advertising: learn whether our online ads lead to visits or enquiries, where you allow this (Section 5);
(h) comply with law and protect rights: meet legal, tax and accounting obligations, respond to lawful requests, and establish or defend legal claims;
(i) handle business transfers: as part of a merger, financing, acquisition or similar transaction (Section 4.1(f));
(j) create de-identified or aggregated information that no longer identifies anyone, for purposes such as improving the Service. We do not attempt to re-identify de-identified information, except to test whether our de-identification methods meet legal requirements; and
(k) operate the Collective's public-source knowledge base: collect, organize and display Public-Source Content so that vessel engineers can find reported equipment faults and fixes (Section 10).
4. How We Disclose Personal Information
4.1 Recipients. We disclose personal information to the following categories of recipients:
(a) Service providers that help us run our business and the Service. These include cloud hosting and storage, edge network and security services, a session-security cache, identity and transactional email services, error monitoring, push-notification delivery and customer support tools. They may use personal information only to provide services to us.
(b) Third-party AI model providers, which process content when you use AI features of the Service (Section 8).
(c) Analytics and advertising partners: Google, Meta, and our session-analytics provider, on our Websites only, subject to your choices (Sections 5 and 6).
(d) Our bank, which handles the bank details in payments made to us under its own privacy terms.
(e) Your organization. If you are an Authorized User, the Customer that gave you access can see your account details and activity in the Service.
(f) Professional advisers, acquirers and investors, under confidentiality obligations, including in connection with a merger, acquisition, financing, sale of assets or similar transaction.
(g) Authorities and others, where we believe in good faith that the law requires disclosure, or that disclosure is needed to protect rights, safety or property.
(h) Others at your direction, for example where you ask us to share information.
(i) Signed-in users of the Collective Site, who can see Public-Source Content, including user names or display names as they appeared in the original source (Section 10).
4.2 Customer Data. We disclose Customer Data only on the Customer's instructions and to the sub-processors listed in our Sub-processor List.
7. Sensitive Personal Information
7.1 What we collect. The only sensitive personal information we collect as a controller is account log-in credentials (your user name together with your password, which we store only in hashed form). We use them only to authenticate you and secure your account. We do not use or disclose sensitive personal information to infer characteristics about you, or for any purpose that would give rise to a right to limit its use under California law.
7.2 Sensitive information in Customer Data. A Customer may choose to store crew documents in the Service that contain sensitive information, such as medical fitness certificates or passport details. We process those only as the Customer's processor (Section 1.4).
8. Artificial Intelligence Features
8.1 What the AI features do. The Service includes features powered by third-party AI model providers, which provide:
- search and answers with source citations;
- document classification and data extraction;
- reading text from scanned documents;
- drafting handover notes from user notes;
- suggesting related documents; and
- finding warranty information.
8.2 What is sent. When these features run, the text of the relevant records or documents, or page images, is sent to the AI model provider. We send only what each feature reasonably needs. We do not remove names or vessel names before sending. The only exception is that we mask email addresses and telephone numbers in text used to build search indexes.
8.3 No training. Our contracts with, or the published terms of, our AI model providers do not permit them to use content sent through the Service to train their models.
8.4 Retention by providers. Some providers keep inputs for a limited period for abuse monitoring, which for at least one provider is up to 30 days, before deleting them.
8.5 Outputs can be wrong. AI outputs can be inaccurate or incomplete. The Service does not use AI to make decisions about individuals that have legal or similarly significant effects. Decisions remain with the vessel's Master, crew and the Customer.
9. The Collective
9.1 What it is. The Collective is an engineering-knowledge service about equipment failures and fixes. The Collective Site displays Public-Source Content (Section 10). Once fleet-contributed insights are published, participating Customers will also see de-identified insights built from the contributions of participating fleets there. Participating Customers contribute engineering information from their own records so that the whole fleet can learn which problems recur and what solved them. Sections 9.2 to 9.4 describe how that works. A Customer's data is never used for the Collective unless that Customer has opted in.
9.2 Opt-in by Customers only. A Customer's data is used for the Collective only if that Customer opts in through its contract with us. Individual crew members do not opt in or out themselves. Questions about whether your organization participates should go to your organization.
9.3 What is shared. If a Customer opts in, before anything is shared:
- the Customer's identity is replaced with a pseudonym;
- identifiers are removed by rule, including names, email addresses, vessel names, vessel identification numbers, call signs and equipment serial numbers;
- free-text notes are excluded by default; and
- nothing is published unless at least five independent fleets have reported the same failure and fix.
What participants will see are de-identified engineering patterns, not crew information and not any one vessel's records.
9.4 Pseudonymized is not anonymous. The pseudonymized contributions are not anonymous, and we protect them as personal information where they relate to an identifiable person. Insights published to participants are de-identified.
9.5 Signing in to the Collective Site. You sign in to the Collective Site with your CelesteOS account. We use the same account system as the Service and process your sign-in information as described in Section 2.4. While you are signed in, your browser keeps a session token in local storage so that you stay signed in; it is removed when you sign out. We do not use analytics or advertising tools on the Collective Site, and we do not record your searches for any purpose other than delivering results and keeping the site secure.
10. Information We Collect from Public Sources (Collective)
10.1 What we collect and from where. For the Collective, we collect posts, reports and other content that has been published on publicly accessible websites. Our sources include public accident-investigation and incident reports, industry safety notices, maritime and yachting news sites, public boating and engineering forums and discussion boards, public question-and-answer sites, public video and code-hosting platforms, and published equipment manuals. From these sources we may collect:
- the user name, display name or author name under which the content was published;
- the title, text and date of the post or report, and a link to it where available; and
- any personal information that the author or others included in the content, such as a person's name or a description of an incident. Such content may occasionally include information about health or injuries, for example in accident reports.
10.2 Why we collect it. We use this information to build a searchable knowledge base of reported equipment faults, the remedies people tried, and the reported outcomes, so that vessel engineers can find relevant experience quickly (Section 3(k)). We do not use it to contact, profile or market to the people who wrote it, and we do not combine it with other information to identify them.
10.3 How we process it. Our automated tools collect the content and then use AI models to extract technical fields (such as equipment, manufacturer, model and root cause) and to label reported outcomes. At present, these AI models run on our own equipment, and we do not send Public-Source Content to third-party AI model providers. If that changes, we will update this Policy first.
10.4 Who can see it. Public-Source Content is shown to signed-in users of the Collective Site, with a link to the original source where we have one. It may include the user name or display name under which the content was originally published.
10.5 How we limit personal information. We remove email addresses and telephone numbers from the text of collected content. We use automated tools to detect and remove other people's names from the text where they can, but these tools do not catch every name. User names and titles are currently displayed as they appeared in the original source. We are updating our collection process so that author names and handles are no longer stored, and are working to remove them from existing records. We will remove or reduce any item on request (Section 10.8).
10.6 Legal basis and this notice (EEA, UK and Switzerland). We rely on our legitimate interests, and the interests of the vessel engineers who use the Collective, in making publicly reported technical experience about equipment faults easier to find, which supports safe and reliable vessel maintenance. We have balanced these interests against the interests of the people concerned, taking into account that the content was published publicly in a technical context, the measures in Section 10.5, and your right to object. You can ask us for details of this assessment. This Section 10 is our notice to the people whose information we collect from public sources, as required by Article 14 of the GDPR and UK GDPR. We generally do not hold contact details for the authors of public posts, so contacting each of them individually would be impossible or would involve disproportionate effort, and would require us to collect more personal information about them. We therefore make this information publicly available here instead.
10.7 Retention and location. We keep Public-Source Content for as long as the item remains useful to the knowledge base, and we remove it promptly on a valid objection or takedown request (Section 10.8). It is stored with our primary hosting provider in Germany. Collection and processing also take place on our own equipment in the United States.
10.8 Your choices and rights. If you believe your information appears in Public-Source Content, you can ask us to remove it, correct it, give you a copy, or stop processing it, by emailing contact@celeste7.ai with the user name or a link to the item or the original post. In the EEA, UK and Switzerland, you have the right to object to our processing based on legitimate interests (Section 18.3). We will stop displaying an item promptly while we review a request, and we will remove your information unless we have compelling legitimate grounds to keep it or the law requires otherwise. If you have deleted or edited the original post, please tell us, and we will update or remove our copy. These rights apply in addition to the rights in Sections 17 and 18.
10.9 US state privacy laws. Some US state privacy laws, including California's, exclude "publicly available information" from the personal information they regulate. Under California law, that exclusion covers only information that is lawfully made available from government records, or that a business has a reasonable basis to believe is lawfully made available to the general public by the person concerned or by widely distributed media. Not all Public-Source Content may meet that test. Whether or not an exclusion applies, we will honor requests about Public-Source Content as described in Section 10.8. We do not sell or share Public-Source Content.
10.10 Copyright and other requests. Requests from authors or rights holders about the content itself, rather than personal information, can be made under our Terms of Use.
11. The Verifier
11.1 Your file is never uploaded. The Verifier lets anyone check whether the content of a sealed record export matches the integrity digests recorded in it. It runs entirely in your web browser. The file you check is never uploaded to us, and the Verifier makes no network requests during the check and uses no cookies, browser storage or analytics.
11.2 Page hosting. When your browser loads the Verifier page, our hosting provider receives standard technical information, such as your IP address and browser type, as for any web page. That information is used only to deliver and secure the page. The Verifier's fonts are served from our own site, and the Verifier loads no files from third parties.
11.3 What the check covers. The Verifier checks the file's internal content integrity. It does not currently validate the digital signature.
12. The App on Your Device: Browser Storage and Offline Access
12.1 What is stored on your device. To keep you signed in and to let you work on board with poor connectivity, the Service stores the following in your browser:
(a) your session token, user identifier, email address, role and vessel name, in your browser's local storage; and
(b) copies of records you have viewed, for up to 7 days, in an offline cache. The cache is kept separately for each user and each vessel, is deleted when you sign out, and never includes crew certificates.
12.2 Not encrypted by the app. This stored information is not encrypted by the Service on your device. Anyone with access to your unlocked device or browser profile could read it. Please use device encryption and a screen lock, and sign out on shared devices. Your organization may have its own device rules.
12.3 Push notifications. If you enable push notifications, your browser registers with its push service (operated by your browser or device maker), and notification titles and text pass through that service.
13. Retention
We keep personal information only as long as needed for the purposes in Section 3, then delete or de-identify it.
| Information | Retention |
|---|---|
| Website analytics data (Google Analytics) | 14 months |
| Advertising measurement and session-analytics data | As set by those tools; see the Cookie Notice |
| Consent choices | 12 months, after which we ask again |
| Prospect enquiries and contact details | 24 months after our last contact with you, unless you become a customer or ask us to delete them sooner |
| Authorized User account details | For the life of the account, then deleted within 90 days after the account is closed, unless the Customer's agreement with us requires otherwise, subject to backup expiry |
| Security logs and sign-in records | 12 months |
| Support communications | 24 months after the request is closed |
| Billing and contract records | 7 years, to meet tax and accounting obligations |
| Encrypted backups | Overwritten on a rolling cycle of no more than 90 days |
| Content sent to AI model providers | Up to 30 days at the provider for abuse monitoring, then deleted (no zero-retention arrangement with that provider) |
| Customer Data | As set by the Customer and our agreement with it (Section 1.4) |
| Public-Source Content (Collective) | For as long as the item remains useful to the knowledge base; removed promptly on a valid objection or takedown request (Section 10) |
| Hosting logs for the Collective Site and the Verifier | As set by our hosting provider, currently 30 days |
14. Security
We use administrative, technical and organizational measures designed to protect personal information, including:
- encryption in transit;
- encrypted backups;
- access controls that separate each Customer's and vessel's data; and
- monitoring for misuse.
No method of transmission or storage is completely secure, and we cannot guarantee the security of personal information.
Security breaches. If a breach of security affects personal information that we control, we will notify affected individuals and regulators as the law requires. For example, for residents of Florida, we will notify affected individuals no later than 30 days after we determine that a breach occurred or have reason to believe one occurred (unless law enforcement asks us to delay or the law allows a short extension), and we will notify the Florida Department of Legal Affairs where 500 or more Florida residents are affected. If a breach affects Customer Data, we notify the affected Customer without undue delay, with a target of 48 hours after we confirm the breach, so that the Customer can meet its own notification duties.
Please tell us promptly at contact@celeste7.ai (subject line "Security") if you believe your account has been compromised.
15. International Transfers
15.1 Where information is processed. We are based in the United States. Our primary hosting for the Service is in Germany. Personal information is also processed in the United States and in other countries where our service providers operate, including by our edge network, session-security cache, AI model providers and Google. Public-Source Content is stored in Germany and is also collected and processed on our own equipment in the United States (Section 10.7).
15.2 Safeguards for EEA, UK and Swiss data. Where we transfer personal information from the European Economic Area, the United Kingdom or Switzerland to a country without an adequacy decision, we use appropriate safeguards. These include the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, and recipients' certifications under the EU-US Data Privacy Framework (including its UK Extension and the Swiss-US framework). You can ask for a copy of the relevant safeguards at contact@celeste7.ai.
16. Children
The Websites and the Service are intended for businesses and are not directed to children under 16. We do not knowingly collect personal information from children under 16 as a controller. If you believe we have done so, contact contact@celeste7.ai and we will delete it.
17. Your Privacy Rights
17.1 Everyone. Wherever you live, you can:
- unsubscribe from our marketing emails using the link in each email, or by emailing contact@celeste7.ai;
- update your account details through the Service or by asking your Customer administrator; and
- ask us questions about this Policy.
17.2 US state privacy rights. Depending on your state of residence, you may have some or all of the following rights. These may include California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon and other states with comprehensive privacy laws.
- Know and access: to know what personal information we have collected about you, including the categories, sources, purposes and recipients, and to get a copy in a portable format.
- Correct: to correct inaccurate personal information.
- Delete: to delete personal information we collected from or about you, subject to legal exceptions.
- Opt out: of the sale or sharing of personal information, and of targeted advertising (Section 6). We do not engage in profiling that produces legal or similarly significant effects.
- Non-discrimination: to exercise these rights without discriminatory treatment.
Note that several states' laws do not apply to information about people acting in a business or employment capacity. California's law does apply to that information.
17.3 How to submit a request. Email contact@celeste7.ai with the subject "Privacy request". We conduct business online, so we accept requests by email.
- Verification. We will verify your identity by matching information you give us with information we hold, usually by confirming control of the email address associated with your account or enquiry. For requests for specific pieces of information, we may ask for more.
- Requests about Customer Data. If your request concerns Customer Data, we will forward it to the relevant Customer and tell you we have done so.
- Response times. We will respond within the time the law requires: generally 45 days, extendable once by a further 45 days where necessary, with notice to you.
17.4 Authorized agents. You may use an authorized agent to submit a request. We may require written, signed permission from you, may verify the agent's identity, and, unless the agent holds a valid power of attorney, may ask you to confirm your identity directly with us.
17.5 Appeals. If we decline your request, you may appeal by emailing contact@celeste7.ai with the subject "Privacy Appeal" within a reasonable time after our decision. We will respond in writing within the time your state's law requires (generally 45 or 60 days), explaining our reasons. If we deny your appeal, you may contact your state Attorney General.
17.6 California disclosures for the past 12 months.
| Category (Cal. Civ. Code § 1798.140) | Examples | Sources | Business purposes (Section 3) | Disclosed for a business purpose to | Sold or shared? |
|---|---|---|---|---|---|
| Identifiers | Name, email, phone, IP address, account ID, cookie IDs | You; your organization; Microsoft (sign-in); automatically | (a)–(j) | Service providers; AI model providers; our bank (payments); professional advisers | Shared (cookie IDs and IP, Websites only, with our advertising partners) |
| Customer records (§ 1798.80(e)) | Name, address, phone, employer, job title | You; your organization | (a), (c)–(e), (h) | Service providers; our bank (payments); professional advisers | No |
| Commercial information | Subscription and billing history | You; your organization | (d), (h) | Service providers; our bank (payments); professional advisers | No |
| Internet or network activity | Website browsing and interactions; Service and Collective Site sign-in and security logs; hosting logs | Automatically | (b), (f), (g) | Service providers; analytics and advertising partners | Shared (Website activity only) |
| Approximate geolocation | City or region inferred from IP | Automatically | (b), (f), (g) | Service providers; analytics and advertising partners | Shared (Websites only) |
| Professional or employment information | Employer, role or rank, vessel assignment | You; your organization | (a)–(e) | Service providers | No |
| Identifiers and other content in public posts (Collective) | User names, display names or author names, and any personal information in a public post or report | Publicly available websites (Section 10.1) | (k) | Service providers (hosting); signed-in users of the Collective Site | No |
| Sensitive personal information | Account log-in and password (hashed) | You | (a), (b) | Service providers (hosting) | No |
We do not collect biometric information, precise geolocation, or protected classification characteristics as a controller, except where such information happens to appear in Public-Source Content (Section 10.1). Some Public-Source Content may be "publicly available information" outside the scope of California law; we list it here anyway (Section 10.9). We do not draw inferences to create profiles about you. Retention periods are in Section 13.
17.7 Shine the Light (California). We do not disclose personal information to third parties for their own direct marketing purposes.
17.8 Nevada. We do not sell covered information as defined by Nevada law. Nevada residents may still send an opt-out request to contact@celeste7.ai.
18. Additional Information for the EEA, UK and Switzerland
18.1 Controller. CelesteOS LLC is the controller of the personal information described in this Policy. For Customer Data, the Customer is the controller and we are its processor (Section 1.4).
18.2 Legal bases.
| Purpose (Section 3) | Legal basis |
|---|---|
| (a) Account administration and service messages | Legitimate interests (operating the Service the Customer has contracted for) |
| (b) Security of the Service | Legitimate interests (keeping the Service and accounts secure); legal obligation where security law applies |
| (c) Support | Legitimate interests (responding to you) |
| (d) Customer relationship, billing | Legitimate interests; legal obligation for tax and accounting records |
| (e) Prospect communications | Legitimate interests (responding to enquiries and business-to-business marketing); steps at your request before a contract; consent where local law requires it for electronic marketing |
| (f) Website analytics and session analytics | Consent (withdrawable at any time) |
| (g) Advertising measurement | Consent (withdrawable at any time) |
| (h) Legal compliance and claims | Legal obligation; legitimate interests (establishing or defending claims) |
| (i) Business transfers | Legitimate interests |
| (j) De-identification | Legitimate interests (improving the Service without identifying anyone) |
| (k) Collective public-source knowledge base | Legitimate interests (making publicly reported technical experience about equipment faults easier to find, supporting safe and reliable vessel maintenance); you may object at any time (Section 10.8) |
| Strictly necessary browser storage | Legitimate interests; exempt from consent as strictly necessary |
Where we rely on legitimate interests, you can ask us for details of our balancing assessment.
18.3 Your rights. You have the right to:
- access your personal information;
- correct it;
- delete it;
- restrict its processing;
- receive it in a portable format;
- object to processing based on legitimate interests or for direct marketing; and
- withdraw consent at any time, without affecting earlier processing.
We will respond within one month, extendable by two further months for complex requests, in which case we will tell you why. We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects.
18.4 Erasure of records in the Service. Where your information is part of Customer Data, the Customer decides on erasure. Service records are kept in an append-only, tamper-evident form so that they remain reliable evidence for maritime safety and compliance purposes. Where erasure is required, it may therefore be carried out by removing or anonymizing your identifying details instead of deleting the underlying operational entry. Copies of sealed records that the Customer has already downloaded remain under the Customer's control.
18.5 Complaints. You may complain to the data protection authority where you live or work, or where an alleged infringement occurred:
- EEA: see the list of authorities at edpb.europa.eu.
- UK: the Information Commissioner's Office (ico.org.uk; 0303 123 1113).
- Switzerland: the FDPIC (edoeb.admin.ch).
We would appreciate the chance to address your concerns first.
19. Changes to This Policy
We may update this Policy from time to time. We will post the updated version with a new effective date. If changes are material, we will give additional notice, such as a notice on our Websites or an email to account holders.
20. Contact Us
- Email: contact@celeste7.ai
- Mail: CelesteOS LLC, 7901 4th St N, #36609, St Petersburg, FL 33702, USA
Version 1.1 — effective October 31, 2026. Version 1.1 adds the Meta Pixel and server-side advertising conversions (Sections 5 and 6).