Privacy Policy

ORL-HNS measures aggregate visits, public page paths and referring sites so we can decide what to improve and publish. Measurement is first-party and stored with the platform. We do not use Google Analytics, third-party usage trackers, advertising trackers, cross-site identifiers or fingerprinting, and the event store does not retain IP addresses or raw browser identifiers. For anonymous public page views, the hosting edge may provide a coarse city; Analytics shows it only as an aggregate when at least three browser sessions share that city, never beside a named person.

Once you sign in, usage events may be linked to your account so we can provide study history, understand feature use and support the service. We do not sell this information or use it for advertising or automated decisions. You can object in this browser below.

We process the email address and account identifier used to sign in, and a display name if you add one.

You may create notes, highlights, answers, drawings, captures, images, audio recordings, support messages, training-portfolio entries, evidence attachments and other study material. Questions and answers submitted through Ask ORL-HNS are retained with your account so the owner can audit safety, identify weak answers and improve the service, even though they are not shown as saved chat history. Do not include patient identifiers or confidential clinical information.

Portfolio evidence is private to your account. If you choose the portfolio assistant, your typed or dictated text is sent to the configured AI provider only when you ask it to structure a draft. You must review the result before saving.

If you explicitly connect ISCP, an isolated Browserbase browser displays the official ISCP service inside ORL-HNS. You enter your login and any multi-factor code directly into that official page; ORL-HNS does not receive or store your password. ORL-HNS retains an encrypted, revocable remote-browser context so an approved draft or structured read can continue while the connection is active. It never fills assessor feedback or performs final submission. You can disconnect at any time to destroy the retained remote context.

We store information needed to provide the service, such as question attempts, review schedules, reading progress, bookmarks, settings and saved links. Some reading data, downloaded books, Pencil drawings and unfinished drafts remain only on your device unless the app says they are being synced or uploaded.

The in-app research browser lets you navigate the open web. ORL-HNS does not receive or store your external browsing history by default. The websites you visit, including search and video providers, receive requests directly from your device and apply their own privacy policies. If you choose “Save link to Inbox”, that URL becomes part of your ORL-HNS content.

We use information to authenticate you, sync your work, personalise study queues, show progress, provide support, secure and operate the service, and improve reliability. We do not sell personal information and do not use it to track you across other companies’ apps or websites.

ORL-HNS relies on service providers including Supabase for authentication and database services, Sanity for managed content and media, Vercel for hosting, OpenRouter and its selected model provider for Ask ORL-HNS generation, Browserbase for an isolated browser when you explicitly connect an official portfolio service, and Apple for app distribution. Google is involved when you choose Google sign-in or use Google in the research browser. Each provider handles data under its own terms and safeguards.

We keep account and study data while your account is active and as reasonably needed to provide, secure or comply with legal obligations for the service. We use access controls and encrypted network connections, but no online service can promise absolute security.

You can sign out at any time and remove downloaded books from device settings. You can request a copy, correction or deletion of your account and associated personal data through the in-app account controls or the contact form.