Privacy Policy
1. Who we are
Auramaris is operated by OryxBara LLC, a limited liability company registered in Wyoming, USA (30 N Gould St #66811, Sheridan, WY 82801, USA). In this policy, "we", "us" and "Auramaris" mean OryxBara LLC. You can reach us at compliance@oryxbara.com.
We have not appointed a data protection officer under the GDPR or the UK GDPR. For the Brazilian LGPD (Article 41), our person in charge of personal data (encarregado) is Marcos Eduardo Oliveira Alves, at compliance@oryxbara.com, the same address as above. DataRep is our representative in the EU, EEA and UK; it is not our data protection officer.
Auramaris is currently in a private beta for invited testers. This policy applies to the beta in the same way. Please use test data, and do not upload real identity documents or other real personal data about other people during the beta.
2. Our representative in the EU, EEA and UK
OryxBara LLC has no establishment of its own in the European Union, European Economic Area or United Kingdom. We have appointed Data Protection Representative Limited, trading as DataRep, as our Data Protection Representative under Article 27 of the GDPR and the equivalent UK law.
If you are in the EU, EEA or UK, you may contact DataRep directly to exercise your rights:
- Email: datarequest@datarep.com (please write "Auramaris" in the subject line)
- Online form: www.datarep.com/data-request
- Post: addresses are available on request by email. Always address post to "DataRep", not to OryxBara or Auramaris.
DataRep forwards your request to us and we reply to you directly. You may also contact us directly at compliance@oryxbara.com. DataRep is registered in Ireland (company number 616588), 77 Camden Street Lower, Dublin, D02 XE80, Ireland. Its privacy notice is at www.datarep.com/privacy-policy.
3. Two roles: when we decide, and when we follow your instructions
- We are the controller of your account data, your subscription and billing data, and the technical data about how you use Auramaris. This policy explains that processing.
- We are a processor (we act on your instructions) for the information you upload about vessels and about other people, such as crew members and people on board: documents, crew rosters, voyage manifests and photos of identity documents. For that information, you (or your organisation) are the controller, and our Data Processing Addendum at auramaris.app/legal/dpa applies.
If you are a crew member or a person named in a vessel's records: the vessel owner or operator who added you decides how your information is used. Please contact them first. If you write to us, we will pass your request to them.
4. What information we handle
| Category | What it includes | Where it comes from |
|---|---|---|
| Account | Name, email address, preferred language, sign-in method (password or Google), workspace and role | You |
| Vessel and compliance records | Vessel details, documents you upload, owner and contact details (name, email, phone, tax ID), insurance policies and broker contacts, maintenance records, planned routes and names of skippers, deadlines, trip briefs and free-text notes | You |
| Crew and people on board | Full name, role, nationality, date and place of birth, gender, identity document type, number, issuing country and expiry date | You (about other people) |
| Photos of identity documents | A photo you take or upload to fill in a form. See section 7 | You |
| AI assistant (Marin@) | Your questions, the answers, and the vessel and regulatory context needed to answer | You |
| Community posts | Questions and answers you publish in the community, shown with your account name. They are visible to other signed-in Auramaris users | You |
| Subscription and billing | Plan, billing interval, status, renewal date. Card details are handled by Stripe and never reach our servers | You and Stripe |
| Technical | IP address, browser and device information, error and security logs | Your device |
| Email notifications | Your email address and the content of expiry and deadline alerts | We generate them |
We do not knowingly collect special categories of personal data (such as health data). Please do not upload them.
5. Why we use it, and our legal basis
| Purpose | Legal basis (GDPR / UK GDPR) |
|---|---|
| To create your account, provide Auramaris and support you | Performing our contract with you (Art. 6(1)(b)) |
| To process payments and keep billing records | Contract (Art. 6(1)(b)) and legal obligations such as tax and accounting (Art. 6(1)(c)) |
| To send deadline and expiry alerts you asked for, and service messages | Contract (Art. 6(1)(b)) |
| To answer your questions with the AI assistant and to read documents you submit | Contract (Art. 6(1)(b)) |
| To let you take part in the community, and to moderate it | Contract (Art. 6(1)(b)) and our legitimate interests in a safe community (Art. 6(1)(f)) |
| To keep Auramaris secure, prevent fraud and misuse, and fix errors | Our legitimate interests in a secure service (Art. 6(1)(f)) |
| To meet legal duties and answer lawful requests from authorities | Legal obligation (Art. 6(1)(c)) |
We do not use your information for advertising, and we do not sell it. In Brazil, we rely on the equivalent bases in Article 7 of the LGPD.
6. How the AI features work
Auramaris uses artificial intelligence in two places: the assistant Marin@, and the reading of identity document photos. Requests go from our servers to our AI gateway, LogoriOn, and from there to an AI model provider that produces the answer. Both the assistant and the reading of identity document photos use Google's Gemini model, reached through LogoriOn. The assistant receives your question, your recent messages, and context from your vessel records, such as deadlines, documents and the names of people who marked checklist items.
- AI answers can be wrong. They are information, not legal advice, and they do not make decisions that have legal or similarly significant effects on you.
- We do not use the information you upload to train AI models of ours or of third parties. Our AI providers work under paid commercial terms that do not let them use it to improve their products; they may keep requests for a limited period only to detect abuse. Our AI gateway records technical data about each request, such as time, model and size. For new Auramaris requests it does not keep the content of requests or answers in its operational logs. When idempotency is used to prevent duplicate processing, the gateway temporarily stores the response; under normal operation, these records are removed within approximately one day. Some answer excerpts recorded during earlier testing have not yet been removed; we will remove them. Copies held in the hosting platform's backups may not be removed at the same moment.
- You can always fill in a form by hand.
7. Photos of identity documents
When you add a crew member, you may photograph an identity document so that the form fills itself in. The photo is read by an AI service. We have not yet verified that the temporary copy is deleted right after reading, and this feature is under review, so please do not upload real identity documents. In a voyage manifest, a photo may be kept, only for the retention period in section 10.
8. Who receives your information
| Recipient | Why | Location |
|---|---|---|
| Supabase | Hosting of our database, sign-in and file storage | European Union (Paris, France) |
| Stripe | Payments and subscription management. Stripe is an independent controller for some of its own uses, such as fraud prevention and legal compliance | EU and US |
| LogoriOn AI gateway, operated by Feetech Online (Rogerio A Correa Desenvolvimento de Programas de Computador LTDA) | Routing requests to AI models | Brazil (operator); gateway database in Ireland (EU) |
| Lovable Labs Sweden AB and its infrastructure providers, including Cloudflare | Platform that runs our application and the AI gateway | United States and Sweden; the application is served from an edge network in many countries |
| Google (Gemini model) | AI model for the assistant and for reading identity document photos | United States and other countries where Google processes |
| Resend | Sending notification emails and Pre-Arrival Package emails, which may carry a PDF with crew and passenger lists | United States |
| OpenFreeMap | Map images. It sees your IP address and the area of the map you view | |
| If you choose "Continue with Google": your Google account email and name. Fonts, until we host them ourselves | United States and elsewhere | |
| Authorities and advisers | When the law requires, or to protect our rights, and to our professional advisers under confidentiality | Where needed |
We do not give any other third party access to your information. If we merge with or are acquired by another company, your information may transfer to it, and we will tell you.
9. Transfers outside your country
We are in the United States, and our providers process information in the United States and in other countries. When we transfer personal data from the EU, EEA, UK or Switzerland, we use the EU Standard Contractual Clauses (with the UK Addendum for the UK), or a framework certification such as the EU-US Data Privacy Framework where a provider has one. Our hosting platform's edge network may handle requests in countries outside the EU; we rely on the safeguards provided by the platform and its infrastructure providers. Our AI gateway is operated from Brazil, which benefits from an EU adequacy decision (26 January 2026) for transfers from the EU; for the UK we use the UK Addendum to the standard contractual clauses with that operator. You can ask us for a copy of the safeguards at compliance@oryxbara.com.
10. How long we keep it
| Information | Period |
|---|---|
| Account data | While your account is open, then up to 30 days |
| Vessel records and documents | Until you delete them or your account closes. After closure, content can be exported for 30 days, and we then delete it from active systems within a further 30 days, unless applicable law requires retention. This account-closure schedule does not override applicable data protection rights or valid instructions requiring earlier deletion. Residual copies may remain in hosting-platform backups until overwritten under the platform's backup cycle; the applicable backup retention period is being confirmed. |
| Crew roster entries | Removing a crew member from the roster hides them but keeps their details until your account is deleted or you ask us to erase them |
| Identity documents and details in voyage manifests | Until the manifest's retention date, which is 5 years from the voyage by default and can be set by the vessel owner (0 to 50 years). A workspace owner or administrator can erase them earlier, and we erase them on request. They are not erased automatically when the period ends unless an owner or administrator does so |
| Community posts | Until removed. When an account is deleted, we remove the person's name from their posts |
| Audit log of changes to compliance records | It shows which user made each change, and is kept while the workspace exists and as long as we need it to show that we comply with the rules. |
| Records of emails we sent you | Until your account is deleted |
| Billing records | For the period that tax and accounting law require |
| Security and error logs, and platform backups | Our hosting platform keeps technical logs and daily database backups, in the same region as the database, and does not let us set or shorten how long it keeps them. Logs we keep ourselves: up to 90 days |
11. Your rights
You may ask us to access, correct, delete, restrict or port your personal data, to object to our use of it, and to withdraw consent where we rely on it. Write to compliance@oryxbara.com, or to DataRep as in section 2. We reply within one month (15 days for a full declaration under the LGPD), free of charge, and we may need to check your identity first.
You can complain to your data protection authority: in the EU, the authority of your country of residence; in the UK, the Information Commissioner's Office; in Brazil, the ANPD.
12. Cookies and similar technologies
We do not use advertising or analytics cookies or trackers. Auramaris stores in your browser only what it needs to work: your sign-in session, and your language and display preferences. These are strictly necessary or chosen by you, so we do not show a consent banner.
13. Security
We protect information with access controls, encryption in transit, private storage for documents with time-limited links, and separation between customers. No system is perfectly secure. If a breach affects you, we notify you and the authorities as the law requires.
14. Children
Auramaris is not for people under 18, and we do not knowingly collect their information.
15. Changes to this policy
When we make material changes, we update the date above and tell you, by email or in the app, before they take effect.
16. Contact
OryxBara LLC, 30 N Gould St #66811, Sheridan, WY 82801, USA. compliance@oryxbara.com.