Account Data
Email address, authentication identifiers, profile fields, settings, billing state, and organization membership data.
A compact view of what Revelar processes, why it is needed, how long it is kept, and how to exercise your rights.
Last updated: 2026-11-05Revelar is a trading name of Lucas Van Houtven, Bautersemstraat 3 bus 201, 2550 Kontich, Belgium, enterprise and VAT number BE 1024.931.197. Revelar is the controller for account and product data it controls. For patient data entered during clinical use under a customer data processing agreement (DPA), the customer organisation is the controller and Revelar acts as processor on its instructions. Conditions for processing health data under Article 9 GDPR are the customer-controller's and are exercised through the Article 28 DPA. For privacy inquiries, contact privacy@revelarmedical.com. For support, contact support@revelarmedical.com.
Email address, authentication identifiers, profile fields, settings, billing state, and organization membership data.
Report text can be processed during active AI and dictation workflows, but Revelar does not keep it as a server-side report archive. Saved reports, where switched on, are kept end-to-end encrypted for at most 7 days; Revelar cannot read them.
Product, billing, credit, and safety metadata needed to run the service.
Session, device, diagnostic, and security metadata needed for authentication, abuse prevention, debugging, and reliability.
When you dictate, voice audio is sent to Soniox in its EU region to produce the transcript that appears in your report. Revelar does not keep the audio.
Contact details you send from the public site, such as your email address, an optional name, the call times you picked, and the page the request came from. They are used to schedule and answer that request.
Processing needed to provide the reporting workspace, AI assistance, dictation, and organization features you have signed up for.
Processing needed for account access, authentication email, billing, settings, support, and statutory accounting duties.
Security monitoring, abuse prevention, and short-retention diagnostics. The interest is keeping the service reliable and safe to use, balanced against a bounded retention period.
Marketing communications are consent-based and can be withdrawn at any time.
To exercise these rights, email privacy@revelarmedical.com or use the account data export page.
AI requests process the current report text only when you use an AI function. Dictation sends voice audio to Soniox in its EU region. Short terms you approve can be reused as recognition vocabulary for other users, but only when the model judges the term reusable and free of patient data, and never when you use Revelar as a member of an organisation such as a hospital. No report text, transcript or patient context is shared with it. You can have a shared term retired by emailing privacy@revelarmedical.com.
Authentication, database, account data, organization data, and RLS-backed storage.
HTTPS delivery for revelarmedical.com. Requests arrive at the Cloudflare location nearest to you and are forwarded to Google Cloud Run in Belgium.
Application hosting for revelarmedical.com and eu.revelarmedical.com on Google Cloud Run in Belgium (europe-west1), secrets in Secret Manager, and Google OAuth sign-in when you choose it.
Authentication email through Supabase SMTP and support email from support@revelarmedical.com. Email must not contain clinical report content.
Converts dictated voice audio into editable text during dictation, in Soniox's EU region. The connection is pinned to the EU endpoints and refuses a non-EU endpoint. Revelar keeps no audio.
Process current report text to produce the wording, formatting, and structure proposals you request. Every model is reached through Opper in Sweden. The writing model (Claude Haiku 5.5) runs on Amazon Bedrock on an EU route, and decision questions go to Berget in Sweden and Sference in the EEA. The routes are the same on revelarmedical.com and on the hospital address eu.revelarmedical.com. Opper's own service providers may process outside the EU.
Payments for credit top-ups. It receives billing and account identifiers, never report content.
Hosting (Google Cloud, Belgium), the database (Supabase, EU) and dictation (Soniox, EU region) are in the EU. AI models are reached through Opper in Sweden; the writing model runs on Amazon Bedrock on an EU route and the decision models at Berget (Sweden) and Sference (EEA). Several providers belong to United States groups, and server logs, email metadata (Resend) and payments (Stripe) can be processed outside the EU. Those transfers rely on an adequacy decision, the EU-US Data Privacy Framework or Standard Contractual Clauses, as listed in the data processing agreement. This is not a claim that all processing stays in the EU.
For privacy inquiries, data subject requests, DPA questions, or complaints, contact our privacy mailbox.
privacy@revelarmedical.comThis privacy notice may be updated as the product, processor list, DPA, and clinical deployment posture mature.