Data Processing Addendum
This Data Processing Addendum ("DPA") forms part of the agreement between OryxBara LLC, a Wyoming (USA) limited liability company that operates Auramaris ("Auramaris", "we", "us"), and the customer that accepts the Auramaris Terms of Service ("Customer", "you") (together, the "Agreement"). It applies where Auramaris processes personal data on behalf of Customer.
1. Definitions
1.1 In this DPA:
- "Applicable Data Protection Law" means Regulation (EU) 2016/679 ("GDPR"), the UK GDPR and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection ("FADP"), and any other data protection law that applies to Customer Personal Data.
- "Customer Content" means the documents, records and other data that Customer or its users upload to or create in the Services.
- "Customer Personal Data" means personal data contained in Customer Content that Auramaris processes on behalf of Customer.
- "Services" means the Auramaris platform and related services.
- "Sub-processor" means a third party engaged by Auramaris to process Customer Personal Data.
- "SCCs" means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914.
- "UK Addendum" means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner (version B1.0, in force 21 March 2022).
- "Personal Data Breach" has the meaning in the GDPR.
1.2 "Controller", "processor", "data subject", "personal data", "processing" and "supervisory authority" have the meanings given in the GDPR.
2. Roles and scope
2.1 Customer is the controller of Customer Personal Data, or a processor acting on behalf of the controller. If Customer is a processor, Customer confirms that it is authorised to give the instructions in this DPA and to engage Auramaris as a sub-processor.
2.2 Auramaris is the processor of Customer Personal Data (or Customer's sub-processor).
2.3 Auramaris acts as an independent controller for account, billing, security and website-usage data. That processing is governed by the Auramaris Privacy Policy and not by this DPA.
2.4 Customer is responsible for having a lawful basis for the processing, for giving the required notices to the people whose data is in Customer Content (for example, crew members and vessel personnel), and for the accuracy and legality of Customer Content.
2.5 The subject matter, nature, purpose and duration of the processing, the types of personal data and the categories of data subjects are described in Annex I.
2.6 Special categories. Customer must not upload special categories of personal data (Article 9 GDPR) or data relating to criminal convictions (Article 10 GDPR) to the Services unless the parties have agreed in writing, and Annex I has been updated, before the upload.
3. Instructions
3.1 Auramaris will process Customer Personal Data only on Customer's documented instructions, which are: (a) the Agreement and this DPA; (b) Customer's use and configuration of the Services; and (c) further written instructions that are consistent with the Agreement.
3.2 Auramaris may process Customer Personal Data where required by Union or Member State law, UK law or other law to which Auramaris is subject. In that case it will inform Customer before the processing, unless the law prohibits this.
3.3 Auramaris will inform Customer without undue delay if, in its opinion, an instruction infringes Applicable Data Protection Law.
3.4 Auramaris will not sell Customer Personal Data, will not process it for its own purposes, and will not combine it with personal data from other sources, except as needed to provide the Services.
3.5 AI features. Auramaris will not use Customer Personal Data to train, fine-tune or improve artificial intelligence models of Auramaris or of any third party. Where Auramaris uses a third-party AI service to process Customer Content, it does so only to produce the output that Customer requested, under terms that prohibit use of the data for model training.
4. Confidentiality
4.1 Auramaris will ensure that the people it authorises to process Customer Personal Data are bound by a duty of confidentiality, and will limit access to those who need it to provide the Services.
5. Security
5.1 Auramaris will implement appropriate technical and organisational measures to protect Customer Personal Data in line with Article 32 GDPR, including the measures in Annex II.
5.2 Customer is responsible for the security of its own accounts, credentials and devices, and for configuring user access within the Services.
6. Sub-processors
6.1 Customer gives Auramaris general authorisation to engage Sub-processors. The current list is in Annex III and is published at auramaris.app/legal/subprocessors.
6.2 Auramaris will give Customer at least 30 days' notice before adding or replacing a Sub-processor, by email to the account administrator or through the notification channel on the page above.
6.3 Customer may object on reasonable data protection grounds within that period. The parties will discuss the objection in good faith. If it cannot be resolved, Customer may terminate the affected Services without penalty and receive a pro-rata refund of prepaid fees for the remaining term.
6.4 Auramaris will bind each Sub-processor by a written contract that imposes data protection obligations no less protective than those in this DPA, and remains liable to Customer for the Sub-processor's performance.
7. Data subject rights
7.1 Taking into account the nature of the processing, Auramaris will assist Customer, by appropriate technical and organisational measures, to respond to requests from data subjects to exercise their rights under Applicable Data Protection Law.
7.2 If Auramaris receives a request directly from a data subject about Customer Personal Data, it will forward it to Customer within 5 business days and will not respond other than to tell the data subject to contact Customer, unless Customer instructs otherwise.
7.3 Reasonable assistance is included in the fees. Auramaris may charge reasonable fees for assistance that requires disproportionate effort, after telling Customer in advance.
8. Personal Data Breach
8.1 Auramaris will notify Customer without undue delay and in any event within 48 hours after becoming aware of a Personal Data Breach affecting Customer Personal Data.
8.2 The notice will describe, as far as known: the nature of the breach, the categories and approximate number of data subjects and records, the likely consequences, and the measures taken or proposed. Auramaris will provide further information as it becomes available and will cooperate with Customer's investigation and mitigation.
8.3 Customer decides whether to notify authorities and data subjects. Auramaris will not make public statements naming Customer without Customer's consent, unless the law requires it.
9. Further assistance
9.1 Taking into account the nature of the processing and the information available to it, Auramaris will assist Customer with its obligations under Articles 32 to 36 GDPR, including data protection impact assessments and prior consultation with supervisory authorities.
10. Return and deletion
10.1 When the Services end, Auramaris will make Customer Content available for export for 30 days.
10.2 After the 30-day export period ends, Auramaris will delete Customer Personal Data from active systems within a further 30 days, unless Union or Member State law (or other applicable law) requires retention. Data retained for that reason remains protected under this DPA. 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.
10.3 On request, Auramaris will confirm the deletion in writing.
11. Information and audits
11.1 Auramaris will make available to Customer the information necessary to demonstrate compliance with Article 28 GDPR, such as security documentation, any third-party reports or certifications it holds, and answers to reasonable security questionnaires.
11.2 If that information is not enough, Customer (or an independent auditor bound by confidentiality) may audit Auramaris, once in any 12-month period (more often after a Personal Data Breach or if a supervisory authority requires it), on at least 30 days' written notice, during business hours, with minimum disruption, and only as to systems that process Customer Personal Data. Customer bears the audit costs. Auramaris will not be required to give access to other customers' data.
12. International transfers
12.1 Customer acknowledges that Auramaris is established in the United States and that Customer Personal Data may be processed in the United States and in the countries where Sub-processors operate (Annex III).
12.2 EU SCCs. To the extent that Customer Personal Data subject to the GDPR is transferred to Auramaris in a country that does not ensure an adequate level of protection, and no other lawful transfer mechanism applies, the parties agree to the SCCs, Module Two (controller to processor), which are incorporated by reference. Customer is the "data exporter" and Auramaris the "data importer". If Customer is itself a processor, Module Three applies. The parties select:
- Clause 7 (docking clause): included.
- Clause 9(a): Option 2 (general written authorisation), with a notice period of 30 days as in clause 6.2 of this DPA.
- Clause 11(a): the optional independent dispute-resolution wording is not included.
- Clause 13: the competent supervisory authority is identified in Annex I.C.
- Clause 17: Option 1; the law of Ireland.
- Clause 18(b): the courts of Ireland.
- Annexes I, II and III of the SCCs are Annexes I, II and III of this DPA.
12.3 UK. For transfers subject to the UK GDPR, the UK Addendum is incorporated by reference. Table 1: the parties and details in Annex I. Table 2: the EU SCCs as selected in clause 12.2. Table 3: Annexes I, II and III of this DPA. Table 4: neither party may end the Addendum when the Approved Addendum changes.
12.4 Switzerland. For transfers subject to the FADP, the SCCs apply with these changes: references to the GDPR mean the FADP; the competent authority is the Federal Data Protection and Information Commissioner; and "Member State" includes Switzerland, so that data subjects in Switzerland may enforce their rights in Switzerland.
12.5 Data Privacy Frameworks. If and for as long as Auramaris is certified to the EU-US Data Privacy Framework (and its UK and Swiss extensions) and the relevant adequacy decision is in force, transfers to Auramaris may also rely on that certification. The SCCs in this clause remain in place as a fallback.
12.6 Onward transfers. Auramaris will transfer Customer Personal Data to a Sub-processor outside the EEA, UK or Switzerland only under an adequacy decision, a valid framework certification, or SCCs (Module Three) or the UK equivalent.
12.7 Government access. Auramaris will notify Customer of any legally binding request from a public authority for Customer Personal Data, unless prohibited, and will challenge requests that it reasonably considers unlawful, as set out in Clause 15 of the SCCs.
13. Liability
13.1 Each party's liability under this DPA is subject to the limitations in the Agreement, except that nothing limits liability that cannot be limited by law, including a party's liability to data subjects under Article 82 GDPR and under the SCCs.
14. Term
14.1 This DPA applies from the date Customer accepts the Agreement and continues for as long as Auramaris processes Customer Personal Data. Clauses 10 (return and deletion), 11 (audits, for the period of retention) and 13 survive.
15. General
15.1 Order of precedence. For the processing of Customer Personal Data: the SCCs (and the UK Addendum) prevail over this DPA, and this DPA prevails over the rest of the Agreement.
15.2 Changes. Auramaris may update this DPA to reflect changes in law or in the Services, with at least 30 days' notice. Changes that reduce Customer's protections need Customer's agreement.
15.3 Governing law. Except where the SCCs or the UK Addendum require otherwise, this DPA is governed by the law that governs the Agreement.
15.4 EU and UK representative. Auramaris has appointed Data Protection Representative Limited, trading as DataRep, as its representative under Article 27 GDPR and the equivalent UK law, and as its legal representative under Article 13 of the Digital Services Act. Data protection contact details are in the Auramaris Privacy Policy. Digital Services Act contact details are on the Digital Services Act page.
15.5 Contact. Questions about this DPA: compliance@oryxbara.com.
Annex I: Description of the processing
A. List of parties
| Data exporter (Customer) | Data importer (Auramaris) | |
|---|---|---|
| Name | The customer identified in the Auramaris account or order | OryxBara LLC (Auramaris) |
| Address | As in the account or order | 30 N Gould St #66811, Sheridan, WY 82801, USA |
| Contact | The account administrator | Rogerio Aguirres Correa, Managing Member, compliance@oryxbara.com |
| Role | Controller (or processor, for Module Three) | Processor (or sub-processor) |
| Signature and date | By accepting the Agreement | By publishing this DPA |
B. Description of processing and of the transfer
| Item | Description |
|---|---|
| Subject matter | Provision of the Auramaris regulatory-compliance platform |
| Nature of processing | Hosting and storage; document upload; parsing and extraction; AI-assisted analysis against regulatory requirements; display to Customer's users; deletion |
| Purpose | To provide the Services that Customer has requested |
| Categories of data subjects | Customer's personnel and contractors; crew members; vessel officers, skippers and owners; other individuals named in the documents that Customer uploads |
| Categories of personal data | Identification data of crew and people on board (name, role, nationality, date and place of birth, gender, identity document type, number, issuing country and expiry); photos of identity documents (roster photos are read by an AI service for extraction, and deletion of the temporary copies right after reading has not been verified; this feature is under review and real identity documents must not be submitted; manifest photos are kept for a limited retention window); contact details and tax IDs of vessel owners; insurance broker contacts; names of skippers or commanders; professional qualifications, licences and certificates; vessel-related records linked to a person |
| Special categories | None intended. Not permitted unless agreed under clause 2.6 |
| Frequency of transfer | Continuous, while Customer uses the Services |
| Retention | Until the Services end, plus the periods in clause 10 |
| Sub-processor processing | Same subject matter, nature and duration, as listed in Annex III |
C. Competent supervisory authority
The supervisory authority of the EU Member State in which Customer is established; if Customer is not established in the EU but has appointed a representative, the authority of the Member State where the representative is established. For UK transfers, the Information Commissioner's Office. For Swiss transfers, the Federal Data Protection and Information Commissioner.
Annex II: Technical and organisational measures
| Area | Measure |
|---|---|
| Access control | Role-based access; least privilege; access limited to Customer's own account users and to authorised Auramaris staff who need it for support |
| Customer separation | Logical separation of each customer's data (for example, row-level security in the database) |
| Authentication | Unique user accounts; strong password policy; multi-factor authentication available for users and enforced for Auramaris administrators |
| Encryption | Encryption in transit (TLS 1.2 or higher) and at rest for stored data and backups |
| Logging and monitoring | Logs of access and administrative actions; alerts for unusual activity |
| Vulnerability management | Regular updates and patching of systems and dependencies; periodic security review |
| Secure development | Code review and separation of development and production environments; no Customer Content in test environments |
| Backup and continuity | Regular encrypted backups and recovery procedures |
| Incident response | Documented procedure for detecting, assessing, escalating and notifying Personal Data Breaches |
| Personnel | Confidentiality undertakings; security and data protection awareness |
| Data minimisation and retention | Only the data needed for the Services; deletion under clause 10 |
| Sub-processor management | Due diligence and written data protection terms with each Sub-processor |
| Identity photos and data | Photos taken to fill in a crew form are read by an AI service for extraction; deletion of the temporary copies right after reading has not been verified, and this feature is under review, so real identity documents must not be submitted; identity data and photos in voyage manifests are kept until the manifest's retention date (5 years by default, set per vessel) and can be erased by a workspace owner or administrator |
| Document storage | Private storage with time-limited signed links; no public document URLs |
| AI gateway logging | For Auramaris requests the gateway keeps technical metadata (time, model, token counts, cost) and, for new Auramaris requests, 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 excerpts recorded during earlier testing have not yet been removed and will be removed. Copies held in the hosting platform's backups may not be removed at the same moment |
| AI safeguards | No training on Customer Personal Data; use of AI services only to produce the requested output |
| Physical security | Provided by the hosting Sub-processors' certified data centres |
Annex III: Authorised Sub-processors
| Sub-processor | Purpose | Location of processing |
|---|---|---|
| Supabase | Database, sign-in and file storage | European Union (Paris, AWS eu-west-3) |
| Lovable Labs Sweden AB, with its infrastructure providers including Cloudflare | Platform that runs the Auramaris application and the AI gateway | United States and Sweden; edge network in many countries |
| Feetech Online (Rogerio A Correa Desenvolvimento de Programas de Computador LTDA), operator of the LogoriOn AI gateway | Routing of AI requests (Marin@ assistant, identity document reading, content translation) | Brazil; gateway database in Ireland (EU) |
| Google (Gemini API, paid services) | AI model for the Marin@ assistant and for reading identity document photos | United States and other countries where Google processes |
| Resend | Notification emails and Pre-Arrival Package emails | United States |
Stripe handles billing data that Auramaris controls. OpenFreeMap (map images) and Google (sign-in, fonts) receive technical data such as the IP address, but not Customer Content. None of them is a Sub-processor of Customer Personal Data. The current list is also published at auramaris.app/legal/subprocessors.