Contact and requests
Operator particulars, support, billing and data-protection requests.
- Service operator
- Operator details pending
- Test registration — replace before launch
- Registration pending
- Country
- Country pending
- Test address — replace before launch
- Registered address pending
- Support
- [email protected] · example only
- Data protection requests
- [email protected] · example only
On this page
01Operator and contact channels
The operator particulars and contact addresses appear above. Example addresses are not monitored channels and must be replaced before launch. The support address handles service issues, billing questions and misuse or vulnerability reports. The privacy address handles personal-data requests. Do not treat an in-app AI answer as an official response to a contractual or privacy request.
02Getting support
Describe what you tried, what you expected and what happened. Include the approximate time and time zone, application section, browser or device, and a relevant item identifier if available. Use a redacted screenshot when it helps. Do not provide passwords, login cookies, recovery codes, API tokens, full payment-card details or unrelated private documents. We may request a smaller example or an appropriate secure channel.
03Personal-data requests
State whether you seek access, correction, erasure, restriction, portability, withdrawal of consent or an objection to processing, and describe the relevant account and information. Using your account email can help verification, but tell us if you no longer control it. We may request proportionate additional information when identity is uncertain. Do not send identity documents unless specifically needed and requested through an appropriate channel.
04Timeframes and verification
Under the GDPR, requests are normally answered within one month of receipt. A permitted extension for complexity or volume requires an explanation within the first month. We will explain if a right does not apply or a request cannot be fulfilled, including relevant complaint options. Requests are generally free; an applicable exception for manifestly unfounded or excessive requests must be justified. Verification must protect your data without collecting unnecessary information.
05Organisational workspaces
For material controlled by your employer or another organisation, identify the workspace and contact its administrator or privacy contact. Lunume may need to refer or assist the request under its agreement with that organisation. Your rights and another participant’s privacy must both be considered. A request for your personal information does not automatically entitle you to every document in a shared workspace.
06Deletion and account closure
Save needed material and arrange transfer of team ownership first. Specify whether you want to remove a particular item, leave a workspace, close an account or exercise a data-protection right. Moving an item to trash does not close an account, and closing an account does not by itself cancel a separately billed subscription. We will explain the applicable scope, consequences and any lawful retention before completing a request that requires review.
07Billing, cancellation and refunds
Identify the workspace or account, order or receipt identifier, date, amount and currency. Never send a complete card number. Cancellation, renewal, withdrawal and refund rights depend on the order presented before payment and mandatory law. If the normal cancellation method fails, report it through support. There is no obligation to provide a particular form where the law permits an unambiguous withdrawal statement.
08Complaints and other remedies
Explain the concern, the outcome you seek and any prior request reference so it can be reviewed. You do not have to waive legal rights to contact us. For personal-data concerns, you may complain to the Cyprus Commissioner for Personal Data Protection or another competent supervisory authority and seek a judicial remedy. This contact process does not replace emergency services.