LugexaThis policy explains the present position for the public website and the controlled development of Lugexa – Luggage Management. It does not describe the browser service, paid plans, Wallet passes or native apps as publicly launched.
1. Who operates Lugexa
Lugexa is the trading name used for this software project. The full legal operator name, legal status and suitable service address still need to be confirmed before public service launch. Privacy questions can be sent to support@lugexa.com.
2. Public website
The public marketing website does not currently contain an account area, contact form, analytics, advertising pixels, embedded media or non-essential cookies. Hosting and security providers may process technical request information such as IP address, requested page, browser or device details, timestamps and security events to deliver and protect the site.
See the Cookie Policy for the website storage and tracking audit.
3. Development web application
The authenticated application at lugexa.app is being developed for authorised hotel users. The controlled development environment may process account details, property membership and role data, session information, luggage tags, bag details, location, colour, approximate size, operational notes, timestamps, audit events and optional luggage photos.
Core development workflows use cloud-backed records. This replaces earlier local-only product positioning. The service is not publicly open, and the current development environment must not be treated as production-ready for hotel or guest data.
4. Photos and retention
Photos are optional. Where a photo is used in the development service, it is intended to be available only to authorised property users through private access controls. The planned Free policy retains photos for up to 24 hours while the related luggage record and History may remain. Final production retention, deletion, storage and backup behaviour must be verified before launch.
If a photo allowance is reached, new uploads may pause, but ordinary luggage records should remain usable without photos.
5. Hotel responsibilities
A hotel using Lugexa will decide what operational information to record and will have its own data-protection responsibilities. Hotels should minimise personal information, avoid unnecessary guest details in notes, provide any required notices, manage authorised staff access and apply appropriate collection checks. Lugexa does not prove that a person owns luggage.
6. Support and early-access enquiries
If you email Lugexa, the information received may include your name, work email, hotel or company, device details, message and any attachments you choose to send. It is used to answer the enquiry, consider early-access suitability, maintain an appropriate support record and protect the service from misuse. Do not send real guest photos, live luggage records, passwords or access codes.
7. Purposes and legal bases
- Enquiries and requested steps: legitimate interests in responding, or steps at your request before a contract where applicable.
- Development access: providing and securing authorised testing, subject to the applicable test arrangement.
- Website and service security: legitimate interests in operating, diagnosing and protecting the services.
- Legal obligations: processing needed to comply with applicable law or lawful requests.
No support or early-access enquiry is automatically enrolled in unrelated marketing.
8. Providers and international processing
The public site currently uses OpenAI Sites for hosting, GoDaddy for domain services and Microsoft 365 for support email. The development architecture uses Cloudflare and Supabase for application and data services. Provider roles, regions, contracts, subprocessors and international-transfer safeguards must be confirmed as part of production legal readiness. Information may also be disclosed where required by law or to protect legal rights.
9. Retention
Support correspondence is kept only as long as reasonably needed to answer enquiries, maintain suitable records, resolve disputes or meet legal obligations. A documented support-email schedule remains an owner decision. Development data must be synthetic unless specifically authorised and governed. Production account, luggage, audit and backup retention schedules require final owner decisions and legal review.
10. Security
The development architecture includes protected sessions, property-level access rules, private photo handling and audit controls. No online service can be guaranteed completely secure. Email delivery, recovery, backup restoration, monitoring and remaining security checks must be completed before public hotel use. This policy does not claim certification or absolute security.
11. Your rights
Depending on the circumstances, UK data-protection law may provide rights to be informed, access personal information, correct it, request erasure, restrict or object to processing, receive portable data and complain. Conditions and exemptions may apply.
Email support@lugexa.com to make a request. You may also use the ICO data-protection complaints service. Visitors elsewhere may have the right to contact a local supervisory authority.
12. Future services
Native apps, paid plans, additional cloud options, reusable QR tags and guest Wallet features remain in development or planned. Their notices, terms and processor information will be updated before or when they launch.
13. Contact and updates
This policy may change as Lugexa, its providers or legal requirements change. Questions and privacy requests can be sent to support@lugexa.com.
Owner information and legal review required: legal operator name and status, suitable service address, controller and processor allocations, production provider agreements, transfer safeguards, retention schedules, incident procedures and service-specific notices must be completed before public launch.