Privacy policy
Who is responsible
Organisation: Genlabs Group SL
Registration identifier: B21641469
Address: Gran Via 1, 48001 Bilbao, Biscay, Spain
Contact: legal@medicaldevicewatchdog.com
Brand: Medical Device Watchdog
Scope of this notice
Medical-device concern intake, evidence and status tracking.
Domains: https://medicaldevicewatchdog.com, https://app.medicaldevicewatchdog.com
Surfaces: website, application
This notice covers the currently operating scope described above.
Collect and track device concerns and evidence, record external identity-sharing preference, and support authorised review and AI-assisted working drafts.
Our role in this activity: controller
Role and responsibilities: We determine how the requested product functions process the profile, submissions and results described here.
Personal data: Reporter account identity, device/manufacturer/model/serial information, device concern narrative, non-patient evidence and metadata, external contact-sharing preference and status. Identifiable patient information and medical records must not be submitted.
People concerned: Adult reporters and other people lawfully identified in device-related evidence. Identifiable patient information and medical records are prohibited.
Source of the data: Authenticated reporter submissions and attachments; administrator status updates; automated draft suggestions.
Consequences of not providing the data: Using these functions is optional. The information needed for a selected profile, document, analysis or submission must be supplied to produce that requested result.
Lawful basis: Legitimate interests (Article 6.1.f GDPR).
Legitimate interests: Our legitimate interest is to receive, review and track voluntarily submitted device concerns and prepare authorised working materials, while respecting the reporter’s external identity-sharing choice.
Provision of data: Optional
Recipients for this activity: Google Cloud / Firebase
Authenticate users, maintain account/session and send access links; optional Google sign-in when configured.
Our role in this activity: controller
Role and responsibilities: We manage access, authentication and administration of this service account.
Personal data: Account name/email and identifier, verification token, session data and optional OAuth account identifiers.
People concerned: Account users.
Source of the data: User entry, email sign-in and optional configured OAuth provider;
Consequences of not providing the data: The minimum sign-in and verification information is required for authenticated account access. Without it, you cannot sign in to the account; public pages remain available.
Lawful basis: Contract or requested precontractual steps (Article 6.1.b GDPR).
Provision of data: Required for this purpose
Recipients for this activity: Google Cloud / Firebase, Transactional email delivery and mailbox provider
Understand how the website and service are used by measuring visits and selected interactions.
Our role in this activity: controller
Role and responsibilities: We decide which website visits and bounded interactions to measure to understand and improve this website.
Personal data: Page URL, referral and campaign information, event name and any configured event properties; IP address and browser information are processed in the request path. Configured conversion paths can store a signup marker or checkout-session identifier locally to reduce repeat counts. The shared conversion wrapper does not send these deduplication identifiers to the analytics providers.
People concerned: Website visitors.
Source of the data: Your browser sends page and event information through our analytics relay. The relay processes technical request information, including IP address and browser information, and forwards the permitted event fields to our self-hosted analytics service.
Consequences of not providing the data: Analytics information is not a prerequisite for opening the public website.
Lawful basis: Legitimate interests (Article 6.1.f GDPR).
Legitimate interests: Our legitimate interest is to understand use of our informational website and improve its pages using limited visit and interaction information. This is not permission for terminal storage that separately requires consent.
Provision of data: Optional
Recipients for this activity: Google Cloud / Firebase
Answer the support questions you submit using an automated assistant and, if you request it, make the conversation available to a human support reviewer.
Our role in this activity: controller
Role and responsibilities: We determine how to answer enquiries and provide the requested support or follow-up.
Personal data: Your submitted messages, automated replies, product and language, conversation reference/status and technical timestamps. An email address is collected when you request human follow-up. Do not send passwords, payment details, health information or confidential documents.
People concerned: Visitors and users who choose to ask for product support.
Source of the data: Information you enter into the support chat and responses generated by the assistant. The conversation is stored before the assistant replies; a refusal to repeat sensitive information does not prevent its storage.
Consequences of not providing the data: Using chat is optional. A question is needed to answer it, and an email is needed only if you request human follow-up.
Lawful basis: Legitimate interests (Article 6.1.f GDPR).
Legitimate interests: Our legitimate interest is to answer the enquiry you choose to submit and organise the support or commercial follow-up you request. This does not authorise unrelated promotional messages.
Provision of data: Optional
Recipients for this activity: Google Cloud
Retention and deletion
Retention period or criteria: We retain saved concerns and active evidence until deletion is requested. Access links expire after seven days; that does not delete their files. After an evidence object is deleted, the provider retains a recovery copy for seven days.
Applies to: Collect and track device concerns and evidence, record external identity-sharing preference, and support authorised review and AI-assisted working drafts.
Retention period or criteria: We keep your account information until you request deletion. Email sign-in links expire after 24 hours.
Applies to: Authenticate users, maintain account/session and send access links; optional Google sign-in when configured.
Retention period or criteria: Our policy is to retain website-measurement records until deletion is requested. These records do not have an automatic expiry. We assess requests using information we can reasonably link to the requester.
Applies to: Understand how the website and service are used by measuring visits and selected interactions.
Retention period or criteria: Conversations are scheduled to expire 30 days after the last conversation message or status change, and internal notification records 30 days after creation. Automatic deletion is asynchronous. Provider or separate email copies are not covered by this timer.
Applies to: Answer the support questions you submit using an automated assistant and, if you request it, make the conversation available to a human support reviewer.
Deletion: Account deletion blocks further account writes while cleanup is pending, removes active evidence files in the exact account UID namespace including orphaned uploads, and removes saved account, concern, nested and sign-in records and explicitly UID-linked local payment projections. Unresolved uploads, storage failures or ambiguous payment ownership keep deletion pending for retry or reconciliation. A minimal deleted-UID marker prevents stale sessions or callbacks from recreating account data. This does not erase downloaded copies, separate external filings, provider payment history or provider recovery copies. Deleting an individual concern does not establish ownership or deletion of its legacy attachment URLs.
Applies to: Collect and track device concerns and evidence, record external identity-sharing preference, and support authorised review and AI-assisted working drafts.
Deletion: You may request erasure through the privacy contact. Closing the chat or marking a question resolved does not itself delete the stored conversation.
Applies to: Answer the support questions you submit using an automated assistant and, if you request it, make the conversation available to a human support reviewer.
Who receives the data
- Google Cloud / Firebase (processor; europe-west4 (Firestore / Storage); global): Host authenticated concern records and supplied evidence files, and provide AI-assisted working drafts from submitted device facts and narrative. Evidence uses a private configured bucket and time-limited signed access. Account erasure deletes live UID-owned files with retry and race protection; it does not anonymise supplied files or erase separate provider recovery copies. Google may process service data globally under its applicable published data-processing and transfer terms: https://cloud.google.com/terms/data-processing-addendum .
- Google Cloud (processor; Google Cloud (global)): Host the requested support conversation, store messages and responses, and generate automated help through Vertex AI. Google may process service data globally under its applicable published data-processing and transfer terms: https://cloud.google.com/terms/data-processing-addendum .
- Transactional email delivery and mailbox provider (processor; DE / US): Deliver requested sign-in links using recipient addresses, email content and delivery information.
International transfers
Transactional email delivery and mailbox provider (US): No transfer safeguard identified; transfer legality remains unresolved. Email delivery may involve processing in the United States. We have not identified an applicable adequacy decision or other GDPR transfer safeguard covering this email service.
No identified transfer-safeguard copy is available for this email service. Contact legal@medicaldevicewatchdog.com for current information.
Automated decisions
We do not make solely automated decisions that produce legal or similarly significant effects in this scope.
Your data protection rights
Depending on the applicable conditions, you can request access, rectification, erasure, restriction and portability, and object to processing (Articles 15–21 GDPR).
Request deletion through Account or the privacy contact. If cleanup cannot finish, you can retry the pending request or contact us. A matching local draft is removed from the browser where deletion was requested when browser storage is available; copies in other browsers should be cleared separately.
Rights contact: legal@medicaldevicewatchdog.com
You can lodge a complaint with a competent supervisory authority, including in the Member State of your habitual residence, workplace or the alleged infringement (Article 77 GDPR).