EUDAMate← Back to site

Legal

Privacy Policy

Last updated: November 2026

1. Who we are

EUDAMate is operated by Ege Can Gecer, trading as EUDAMate (“we”, “us”, “our”). We are the data controller for personal data processed through eudamate.eu.

Contact: hello@eudamate.eu

2. What data we collect

We collect only what is necessary to provide the service:

  • Email address: provided when you request a Readiness Check or create an account. Used to send your results and product communications you opt into.
  • Uploaded files: spreadsheets you upload for EUDAMED data preparation. These contain device data, not personal data about individuals. Files are processed immediately and permanently deleted from our servers after analysis. You can also upload PDF and Word documents, such as certificates, declarations of conformity and labels, for us to read. These can name people, for example the person who signed them. We keep the file name and a SHA-256 fingerprint of each file in the project's audit trail so the Registration Decision Record can show which file was used.
  • Account data: name, email, and password hash if you register. Stored in Supabase.
  • Name and role for the Registration Decision Record: your name and job title, if you enter them in Settings or on the export screen. The Registration Decision Record names you with them as the person who approved an export. You can change them in Settings. A change applies to later exports only.
  • Payment data: handled entirely by Stripe. We do not store card numbers or full payment details. We receive a transaction reference and billing email.
  • Server logs: IP address, browser type, pages visited, timestamps. Retained for up to 30 days for security and debugging purposes.
  • Verification checks: anyone can check a fingerprint printed in a Registration Decision Record or listed in its checksums.sha256 at www.eudamate.eu/verify, or register a fingerprint there. Our server uses the IP address of the person checking or registering to limit the number of requests per minute. Apart from the server logs above, it is held for that minute only. The check answers whether the fingerprint is in an audit trail we hold, belongs to a file an export made or was registered with us. It returns no project, device, account or name.
  • The register of fingerprints at www.eudamate.eu/verify stores only the fingerprint and the time it arrived, nothing about who sent it. The file it was made from never reaches us.

3. How we use your data

  • To run the readiness analysis and return your report
  • To manage your account and project history
  • To process payments and issue invoices
  • To send transactional emails (report delivery, account confirmation)
  • To print your name and role in the Registration Decision Record of an export you approve
  • To improve the service and fix errors

We do not sell your data, share it with third parties for marketing, or use it for automated profiling.

We send a project's audit trail file to someone else only when you ask us in writing, for example for an audit.

4. Legal basis (GDPR Article 6)

  • Contract performance: processing necessary to deliver the Readiness Check and paid data preparation service you requested, including the name and role printed in your Registration Decision Record.
  • Legitimate interests: server logs, security monitoring and limiting checks and registrations on the verification page.
  • Consent: marketing emails, if you opt in.

5. Data processors

We use the following sub-processors.

  • Supabase: database and authentication (EU region)
  • Railway: backend API hosting
  • Vercel: frontend hosting and CDN
  • Stripe: payment processing
  • Anthropic: AI processing for column mapping, EMDN classification and reading the documents you upload, such as certificates and labels. Uploaded file content may be sent to Anthropic's API for this purpose. For EMDN classification we also send the manufacturer's name as registered in EUDAMED, which we look up from the SRN in your file. Anthropic does not use API inputs to train models. Anthropic deletes API inputs after a period set by its own retention terms, currently at most 30 days.
  • Resend: transactional email delivery
  • GitHub hosts our code and runs our automated jobs. Once a week a job on GitHub's servers reads the EMDN decisions made in reviews to retune the weights that rank EMDN suggestions. Each decision holds the device name, model, trade name and description. It also holds the EMDN code chosen, the user ID of the account and the manufacturer SRN. Only the resulting weights are kept.

Supabase, Railway, Vercel, Stripe, Anthropic and Resend are each bound by a data processing agreement with us.

We also send device texts to openFDA, the public device database API of the US Food and Drug Administration at api.fda.gov. To suggest an EMDN code we can look up a device's name, model, trade name and description there. We send at most six words from each of these texts, with sizes and pack counts removed. We send no account details. Device texts do not normally hold personal data.

6. International data transfers

Our database is hosted in the European Union. Some of the providers listed in section 5 are based in the United States, so personal data and the content of files you upload can be processed outside the European Economic Area. For Supabase, Railway, Vercel, Stripe, Anthropic and Resend these transfers are covered by the EU-US Data Privacy Framework or by the EU Standard Contractual Clauses in each provider's data processing agreement. This does not apply to openFDA, a public US government service that receives only the device texts described in section 5. You can request a copy of the relevant safeguards at hello@eudamate.eu.

7. Data retention

  • Uploaded files: spreadsheets are deleted as soon as they are analysed. PDF and Word documents you ask us to read are held in server memory, never written to our storage, until the reading ends or for at most one hour if you do not start it. They are then deleted. We keep each file's name, page count and fingerprint. Content sent to Anthropic follows Anthropic's retention terms (section 5).
  • Account data: retained while your account is active. Deleted within 30 days of account deletion request.
  • Projects in a subscription account (Registry Care or Consultant plan) are kept for the life of the subscription. Once the subscription ends they follow the one-off rules below, with the deletion period counted from the end of the subscription or from your export, whichever is later. Your export means your first export from 1 December 2026 and your last export until then.
  • From 1 December 2026 one-off projects are deleted 90 days after your first export. Exporting again does not extend the 90 days, but the project keeps any later date the earlier rule would have given. A project you never export is deleted 90 days after you created it. No scheduled deletion comes earlier than 30 days after you last recorded a EUDAMED result for the project. No project gets an earlier deletion date than it had under the earlier rule. Until 1 December 2026 one-off projects are deleted 60 days after your last export and each new export restarts the 60 days. Until then a project you never export is deleted 60 days after your last activity on it. A project you mark as finished is deleted within one day. We email you 7 days and 2 days before the deletion date.
  • Your name and role are stored with each export, apart from the project's audit trail. The audit trail, which cannot be edited, holds only a fingerprint of them that identifies no one once they are deleted. They are deleted with the project under the rules above, or earlier if you ask (section 8).
  • A short record that the project existed remains after deletion. It holds the project's name, its dates, its device count and a fingerprint of its audit trail. It holds no device data. A later record of the same device can name the earlier project and say that its data was deleted. That fingerprint can still be checked at www.eudamate.eu/verify. We also keep the name, model, trade name and description of each device you reviewed with the EMDN code you chose. We use them to improve EMDN code suggestions. Other customers never see these names or descriptions. We look up each device's UDI-DI in the public EUDAMED database when we delete the project. We keep whether the device is registered there and under which EMDN code so that suggestions can rely more on codes confirmed by a registration.
  • Projects in an account we provide free of charge are exempt from these deletion rules. They are kept until you delete them or ask us to delete them.
  • We keep the fingerprints of your files and records so anyone you show them to can still check them. A fingerprint cannot be turned back into your data. The fingerprints stay when a project's data is deleted.
  • When you record a EUDAMED result for a file, we keep only the fingerprint of the reply EUDAMED gave you, never the reply itself.
  • Payment records: retained for 7 years per EU accounting requirements.
  • AI results: what the AI returned for your device texts and documents, such as translations, EMDN suggestions and certificate readings, is kept for up to 30 days after it was last saved. It is not linked to a project, so it is deleted on this schedule rather than with the project. It lets the same text be answered again without a new AI request.
  • Server logs: 30 days.

8. Your rights

Under GDPR, you have the right to:

  • Access the personal data we hold about you
  • Correct inaccurate data
  • Request deletion (“right to be forgotten”)
  • Restrict or object to processing
  • Data portability
  • Withdraw consent at any time (where processing is based on consent)
  • Lodge a complaint with your national data protection authority

You can ask us to delete your name and role from every export you approved. We delete them together with the key that links them to the fingerprint in the audit trail, so the fingerprint no longer identifies you and the audit trail still checks. A record made after that says your name was deleted on request. A record already made and handed out keeps the name it printed. A change in Settings applies to later exports. This covers your name and role. The email address a record shows for the account that generated it is account data and follows the rules for account data above.

To exercise any of these rights, email hello@eudamate.eu. We respond within 30 days.

9. Cookies

We use only essential session cookies required to keep you logged in. We do not use advertising or tracking cookies.

For aggregate page statistics we use Vercel Web Analytics, a cookieless service that does not store cookies on your device, does not collect or retain personal identifiers, and does not track you across sites or sessions. Visits are counted using an anonymized hash that is discarded within 24 hours.

10. Changes to this policy

We will notify registered users by email of material changes to this policy at least 14 days before they take effect. The “Last updated” date at the top of this page reflects the most recent revision.