PrivacyPrivacy policy
How Veebiagentuur OÜ handles personal data in and around Claveo.
Last updated: 8 July 2026
1. Who we are
Claveo is operated by Veebiagentuur OÜ. In this policy, "Claveo", "we", "us" and "our" refer to Veebiagentuur OÜ when we operate the Claveo website, app, billing, support and service infrastructure.
For account, billing, support and website data, Veebiagentuur OÜ usually acts as data controller. For guest registration data entered into a customer workspace, the host or property manager usually acts as data controller and Veebiagentuur OÜ acts as processor providing the Claveo service.
Veebiagentuur OÜ, registry code 12050902, Pääsukese 6, Kopli küla, Rae vald, Estonia, 75321.
2. Data we process
We may process account details such as name, email address, workspace, role, login and security events, billing state, plan, support messages and product usage logs.
Customer workspaces may contain property, booking, contract, export, audit and guest registration data. Guest data can include contact details, address, document details, date of birth, nationality, signatures, consent choices, OCR extraction results and regulatory reporting history.
We also process technical data such as IP address, device/browser information, session cookies, diagnostics, error logs and security metadata needed to run and protect the service.
3. Why we use data
We use data to provide the Claveo service, authenticate users, maintain workspaces, generate guest links, process guest forms, support SES.Hospedajes/XML/export workflows, create contracts, provide support, manage billing, prevent abuse, keep audit logs and improve reliability.
Depending on the context, the legal bases may include contract performance, legal obligations, legitimate interests, consent and, for customer-controlled guest records, the lawful basis chosen by the host or property manager.
4. Sharing and processors
We share personal data only where needed to run the service, comply with law, protect rights, process payments, provide hosting, deliver email or messaging, support integrations, or communicate with authorities when a customer has configured that workflow.
Third-party providers may include hosting, database, logging, email, payment, analytics, OCR, messaging and authority-integration providers. We expect processors to use appropriate confidentiality and security measures.
5. Retention
We keep data only for as long as needed for the purposes described above, including service operation, legal compliance, auditability, dispute handling and security. Workspace owners can configure retention controls where the plan supports them.
Guest registration records may need to be retained by the host or property manager for legal reasons. Customers are responsible for choosing retention settings that match their own legal obligations.
6. Security
We use technical and organisational safeguards such as authenticated access, role-based permissions, tenant separation, encryption where appropriate, audit logging, backups, monitoring and restricted administrative access.
No online service can guarantee absolute security. Customers should use strong passwords, limit team access, keep credentials confidential and notify us promptly if they suspect unauthorised access.
7. Your rights
Depending on your location and the processing context, you may have rights to access, correct, delete, restrict, object to or receive a copy of your personal data. You may also withdraw consent where processing is based on consent.
If your data was submitted through a host or property manager workspace, we may direct your request to that customer because they control the guest record. You may also contact your local data protection authority.
8. Contact and changes
You can contact Veebiagentuur OÜ about privacy through the contact or support channels available on the Claveo website or inside the app.
General contact: info@claveohost.es. Privacy contact person: Marmo Luik, marmo@veebiagentuur.ee.
We may update this policy when the service, law or our processing practices change. The latest version will be published on this page.