UETR.io
Robert Jacobsens Vej 78a, 2300 Copenhagen SDenmark
[email protected]
Information handled by the service
A lookup uses a UETR, message date, timezone and email address. Registered records include amounts, currencies, banks and events. Private records can also contain participant names, addresses, account identifiers and contact details supplied with the transaction.
Account registration collects a name, email and password. The service stores password hashes, email-verification state and session information. Hosting, email and security infrastructure may process connection information such as IP addresses and delivery logs.
Why information is used
- Match a reference to a registered transaction and display its record.
- Confirm alert requests and send recorded-event notifications.
- Authenticate accounts and decide access to participant details.
- Handle support enquiries, investigate errors and protect the service from abuse.
Where data-protection law requires a lawful basis, the relevant basis depends on the purpose: providing the requested service, permission for optional alerts, legitimate interests in security and support, or an applicable legal obligation. Sending a reference does not authorize unrelated marketing.
Who can receive information
A valid signed transaction link can display the public timeline and summary to its holder. Private details require additional account and participant checks. Authorized service administrators may access records to manage the service.
Infrastructure providers process data needed for hosting, network operation and email delivery. The service uses Resend for transactional email; Cloudflare services may handle domain, network or email-routing traffic. Their roles and processing locations depend on the deployed service arrangements. Data may also need to be disclosed in response to a valid legal requirement.
Retention and requests to remove information
Different records have different purposes. Transaction records may be needed for service history, support, dispute resolution or applicable obligations; security and email providers maintain their own operational records. This page does not promise one universal automatic deletion period.
Unsubscribing removes the corresponding alert subscription from the application. It does not remove the underlying transaction, account or provider delivery logs. For a broader deletion or retention enquiry, contact us so the relevant record and any necessary verification can be identified.
Your choices and applicable rights
You can stop an alert subscription through an update email and ask about access, correction, deletion or restrictions by emailing [email protected]. Rights and exceptions depend on the law that applies to you and the processing involved. Where available, you may also raise a concern with the relevant supervisory authority.
Do not send a password, one-time code or full identity document with an initial request. We will use proportionate checks before disclosing personal information.
Controller and European data-protection enquiries
UETR.io, at the Copenhagen address above, is the service contact and controller for the service’s own lookup, account and alert processing. Where another organization supplies transaction information, it may have separate responsibilities for that original information.
Where the GDPR applies, you can ask for access, correction, erasure, restriction or portability where the relevant conditions are met, object to processing based on legitimate interests, and withdraw consent for optional alerts. Withdrawal does not undo processing already carried out. You can complain to the Danish Data Protection Agency or another competent supervisory authority.
Our infrastructure and email providers may process information outside Denmark or the EEA. You can contact [email protected] to ask which providers handle your information, where that processing takes place and which safeguards apply to a relevant transfer. Please do not include payment documents in your initial enquiry.