Privacy

What we collect, and why.

This policy covers the Orvedis app, the service behind it, and this website. Last updated 23 October 2026.

Who we are

Orvedis is operated by ORVEDİS TEKNOLOJİ ANONİM ŞİRKETİ (Orvedis Teknoloji A.Ş.), Cevizli Mah. Enderun Sk. Nursanlar Sitesi A Blok No: 10AA, Kartal, İstanbul, Türkiye. MERSİS no. 0648188319300001. In this policy “Orvedis”, “we” and “us” mean Orvedis Teknoloji A.Ş.

We make the Orvedis mobile app for iOS and Android, and a web sign-in for the company side (fleet managers and DPAs). Ship crews and fleet operators use it to ask an AI assistant about the navigation and communication equipment on board, to read the answer against the device’s own manual, and to turn a fault that cannot be settled on board into a service report.

Orvedis is a business to business product. Accounts are created by Orvedis for a customer organisation, normally a fleet operator. There is no self-service sign-up. The people who use the app are crew members, DPAs and technical managers, and organisation admins.

For anything on this page, write to privacy@orvedis.com.

Who is the controller

Data inside the app. The customer organisation that provisioned the account is the controller. Orvedis is the processor and acts on that organisation’s documented instructions under a data processing agreement. If you are a crew member, a DPA, a technical manager or an admin, the organisation that gave you your account decides what is put into the app and how long it is kept, within the limits set out here.

Data on this website and in direct correspondence. Orvedis Teknoloji A.Ş. is the controller. That covers the demo request form on this site and email sent to our addresses.

If you send us a request we can only answer as a processor, we pass it to the controller without delay and help them answer it.

What we collect, and why

We get this data from what you type and say in the app, from the device records and manuals your organisation uploads or designates, from the account details your organisation gives us when it opens the account, from technical records the app and the server generate automatically, and from the form on this website.

Name and work email address. To create the account, identify the user, and send account and security email.
Password, stored only as a bcrypt hash. To let the user sign in. We never hold the password itself.
Role, organisation and vessel membership. To show the right vessels and devices, and to keep each organisation’s data separate from every other organisation.
Two-factor codes. For admin accounts, and for fleet manager accounts that turn it on, to protect the accounts that can change fleet data.
Device records: brand, model, serial number, position on board. So the assistant knows which device the question is about.
Manuals uploaded or designated by the customer, and the text chunks and embeddings derived from them. So the assistant answers from the device’s own documentation and can cite the page it read.
Fault conversations in text. To carry the conversation, build the service report, and let the crew read what was already tried.
Voice call audio and the transcript. To hear the question and answer out loud. Audio is not stored after the call ends; the transcript is kept with the conversation.
Photos attached to a ticket. To show the fault to whoever reads the report. EXIF metadata, including GPS coordinates, is removed on upload.
Tickets and PDF service reports. To record the incident and hand a structured account of it to the service company the customer already works with.
Reminders. To tell the crew that a check is due.
Push notification token. To deliver notifications to the device.
Crash and diagnostic data. To find and fix faults in the app.
IP address and request metadata in server security logs, kept 90 days. For rate limiting and abuse prevention.
Assistant inputs and outputs, with personal identifiers removed. To measure answer quality and the safety gate that stops the assistant from instructing hazardous work.
The demo request form on this site. Name, work email, company, country, and if you fill them in, fleet size, role and message; plus the time of the request, a salted one-way hash of your IP address and your browser’s user-agent string. To read your request and reply to it, and to stop the form from being flooded.

We do not collect position data from the device, we use no advertising identifiers, and we do not track users across other apps or websites. There are no payments in the app, so we never process card or bank details.

Legal bases

Inside the app the customer organisation determines the purpose and the legal basis. For the processing we are responsible for, the bases are these.

Running the app for a user whose organisation has a contract with us. Performance of a contract. GDPR Art. 6(1)(b); KVKK m. 5/2-c.
Keeping the service secure: authentication, rate limiting, abuse and misuse detection. Legitimate interests. Art. 6(1)(f); m. 5/2-f.
Crash and diagnostic data, and quality measurement on logs with identifiers removed. Legitimate interests. Art. 6(1)(f); m. 5/2-f.
Answering a demo request or an email you send us. Performance of a contract and legitimate interests. Art. 6(1)(b) and Art. 6(1)(f); m. 5/2-c and m. 5/2-f.
Keeping records the law requires us to keep, and answering lawful requests from authorities. Legal obligation. Art. 6(1)(c); m. 5/2-ç.

The microphone is used only while a voice call is running, and only after the operating system permission has been granted. That permission can be withdrawn at any time in the device settings, and the rest of the app keeps working without it.

Who processes data for us

Each of them is bound by a written contract with data protection obligations no weaker than those we give you here, and processes data only on our instructions.

We list our providers here in full, as the law requires. The assistant’s brain is Orvedis; a provider can change, and we announce it 30 days ahead.

Anthropic, United States. Runs the model that generates the assistant’s answers from the user’s message and the relevant manual pages and excerpts sent with it. We have applied for a zero data retention arrangement with Anthropic; it is not yet in place and we will say so here when it is.
OpenAI, United States. Turns the user’s question, and the text of the manuals the customer supplies or designates, into search vectors (embeddings) so the assistant can find the relevant manual pages; and turns a recorded voice question into text (speech to text). Under OpenAI’s API terms, data sent through the API is not used to train its models, and it may be kept for up to 30 days for abuse monitoring.
ElevenLabs, United States. Speech to text and text to speech during a voice call.
Supabase, United States. PostgreSQL database and file storage, encrypted at rest. The database region is set for our deployment.
Cloudflare, United States. R2 object storage for photos, manuals and backup copies. The bucket region is set for our deployment.
Hostinger, European Union. Hosting for the API and for this website.
Sentry, United States. Crash and error reporting from the app and the API.
Resend, United States. Delivery of transactional email.
Expo, United States. Delivery of push notifications to the device.

Where a provider offers a choice of hosting region, the region in use is stated on request to privacy@orvedis.com. We announce a change at least 30 days before the new provider starts processing, and a customer organisation may object to it under its data processing agreement.

International transfers

We are in Türkiye and several of our providers are in the United States or the European Union, so personal data may be processed outside the country you are in. For transfers out of the European Economic Area we rely on the European Commission’s standard contractual clauses, which form part of the data processing agreements we hold with those providers, together with the security measures below. For transfers abroad under Turkish law we rely on the grounds permitted by Article 9 of Law No. 6698, including standard contracts notified to the Personal Data Protection Board where that is the applicable route.

How long we keep it

Account data. Until the user or the organisation deletes it.
Device records, manuals and the text derived from them. For as long as the organisation’s subscription runs, or until the organisation deletes them.
Conversations, including voice transcripts. For as long as the organisation’s subscription runs.
Voice call audio. Not stored after the call ends.
Tickets, service reports and their photos. For as long as the organisation’s subscription runs.
Reminders. For as long as the organisation’s subscription runs.
Push notification token. While the account is active.
Crash and diagnostic data. 90 days.
IP address and request metadata in server security logs. 90 days.
Assistant evaluation logs, with personal identifiers removed. 12 months.
A demo request from this site. Until the request has been handled and the correspondence about it has ended.
Backups. Point in time recovery covers the last 7 days. Encrypted backup copies are deleted after 60 days.

In-app or written deletion requests are completed within 30 days. When a customer contract ends, the organisation has 30 days to export its data, after which live data is deleted within a further 30 days; backup copies expire within 60 days. Data already written to a backup copy is removed when that copy expires, and it is not restored into the live service in the meantime.

Security

TLS for everything in transit. Encryption at rest for the database and for stored files.
Passwords are hashed with bcrypt. We cannot read them.
Short-lived access tokens with rotating refresh tokens that can be revoked, held in the Keychain on iOS and the Keystore on Android.
Two-factor authentication is required for admin accounts and available to fleet manager accounts.
Every request to every endpoint is scoped to the organisation on the signed-in account, and so is every retrieval the assistant makes. That boundary has its own tests, and they run on every release.
Rate limiting on authentication and on the API as a whole.
EXIF and GPS metadata stripped from user photos on upload.
No payment data is processed anywhere in the app.

No system is perfect. If a personal data breach occurs we notify the affected customer organisation without undue delay and within 72 hours of becoming aware of it, and we notify the authorities and the people affected where the law requires it.

Your rights, and how to use them

Under the GDPR and under Article 11 of Law No. 6698 you can ask for access to your personal data, for it to be corrected, for it to be erased, for processing to be restricted, for a copy in a portable form, and you can object to processing based on legitimate interests. You can also ask whether your data has been processed at all, and ask to be told to whom it has been transferred.

There are three ways to act. The app has an in-app export that produces a copy of your data. The app has in-app account deletion. Or write to privacy@orvedis.com and we will answer within 30 days. We may ask you to confirm who you are before we act, and we ask no more than is needed for that.

Where Orvedis is the processor and not the controller, we forward your request to your organisation and support them in answering it.

If you are not satisfied, you can complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurumu) in Türkiye, or to the supervisory authority of the country you live or work in if you are in the European Union.

The assistant, and what is sent where

When a user asks the assistant something, we send the message, the relevant pages and excerpts of the device’s own manual, the device record and the recent turns of that conversation to our AI provider, which generates the answer. While a voice call is running, the audio is sent to our voice provider to be turned into text, and the text of the answer is sent back to our voice provider to be spoken. To find the relevant manual pages, the text of the question is sent to a second AI provider that turns it into a search vector, and a voice question recorded in the app is sent to the same provider to be turned into text.

Nothing you or your crew send is used to train AI models. Under the API terms of the providers we use, inputs and outputs sent through the API are not used for model training. Retention on the provider side is governed by each provider’s API terms.
Voice audio is not stored by Orvedis after the call ends. The transcript is kept with the conversation so the crew can read what was said.
Every retrieval the assistant performs is restricted to the organisation of the signed-in account. It cannot read another organisation’s vessels, devices, manuals or conversations.
Fault conversations are part of the vessel’s technical record: the fleet manager in your own organisation can read them. Your lessons and your lesson progress are not shared.
The assistant’s inputs and outputs are logged with personal identifiers removed, so we can measure answer quality and the safety gate that stops it from instructing hazardous work.

The assistant answers questions about equipment. It makes no automated decision that produces a legal or similarly significant effect on a person, and it is not used to evaluate crew performance.

Children

Orvedis is a workplace tool for professional seafarers and fleet staff. It is not directed at anyone under 18, and we do not knowingly process the personal data of a child. Accounts are created by the customer organisation for its own personnel.

This website

orvedis.com is a static site. It sets no cookies, uses no analytics and carries no advertising or tracking tags. The demo request form is protected by a bot check that confirms the sender is a person rather than a script. The form stores a salted one-way hash of the sender’s IP address so that submissions can be rate limited by the hour, and it delivers the message to hello@orvedis.com.

Changes to this policy

When we change this policy we change the date at the top and describe what moved. A change that materially affects how personal data is processed is announced to customer organisations before it takes effect.

Contact

Privacy and data protection requests: privacy@orvedis.com. Security reports: security@orvedis.com. Support: support@orvedis.com. Everything else: hello@orvedis.com. Post: ORVEDİS TEKNOLOJİ ANONİM ŞİRKETİ (Orvedis Teknoloji A.Ş.), Cevizli Mah. Enderun Sk. Nursanlar Sitesi A Blok No: 10AA, Kartal, İstanbul, Türkiye. MERSİS no. 0648188319300001.

This policy was prepared by Orvedis and is subject to review by external counsel; any revision will be dated here. Last updated 23 October 2026.