1. Who operates the project
NexaCloudHub is independently operated under the public name Vlad D., based in Romania. Contact: contact@nexacloudhub.com.
This policy covers nexacloudhub.com, its project presentation pages, the hosted Repos workspace, browser Calendar and the Webmail destination at mail.nexacloudhub.com. Separate application notices are linked below. This notice distinguishes information processed locally by the application from information received by NexaCloudHub through a hosted service or support request.
2. Website visits and contact
Ordinary requests to serve a page include an IP address, requested URL, time, browser information and potentially a referring page. Infrastructure may record these details in access, error or security logs to deliver pages, diagnose faults and prevent abuse. Page content is hosted as part of NexaCloudHub; following an external link sends a request to that destination.
The presentation pages do not include advertising trackers or an analytics script. Contact links open an email client; the information you put into a message is processed to answer it. No newsletter signup or payment collection is provided by these presentation pages.
3. Repos: a shared workspace
Repos stores collection titles, categories, names, optional email addresses, passwords and comments submitted by people with workspace access. It also handles session and request-security data. Account-record fields are encrypted in the server database; collection titles and category names are metadata. The server uses the key to retrieve account details for authorized sessions.
Repos uses one shared access password. Everyone who has that password can access the shared workspace and may view, edit or delete its records. There are no individual roles or private account partitions in this version. Only store information you are authorized to share with all workspace participants. The workspace password is stored as a password hash.
4. Calendar and ORA accounts
Creating an ORA account involves a username, password hash, sessions and security metadata. Synchronizing adds your event or task details, categories, dates, locations, notes, completion state and synchronization identifiers to the hosted database. Passwords are hashed; calendar item content is encrypted at rest with a key held by the server.
Browser Calendar keeps an account-specific cache and pending edits in browser local storage. Logging out revokes the session and clears that account’s browser cache. Synchronization can retain deletion markers, revisions and operation history needed to reconcile devices; deleting a visible event is not the same as erasing the entire account. See the ORA Privacy Policy for desktop and Android processing.
5. Webmail
The Webmail destination is an online mailbox service, not just a static project page. Using it involves authentication and the mail account’s addresses, messages, attachments, contacts or preferences you save, and delivery, connection and security metadata. Sending mail discloses it to addressed recipients and the mail systems involved in delivery.
Mail already hosted by NexaCloudHub is processed by the mail infrastructure independently of whether you read it through Webmail or Flluet. Connecting a third-party mailbox in a local email app does not, by itself, upload that entire mailbox to the NexaCloudHub website. For mailbox access, retention, account closure or the current mail infrastructure, contact contact@nexacloudhub.com.
6. Necessary cookies and browser storage
Repos uses a first-party authentication cookie scoped to /repos, with a session lifetime of up to 12 hours. Browser Calendar uses one scoped to /calendar, with a lifetime of up to 30 days. Logout, revocation or a security change can end access earlier. Session tokens and request-security mechanisms enable authenticated actions; these are not advertising identifiers.
Calendar local storage holds its account cache and synchronization queue. Webmail also needs its own session state to maintain a login. Blocking or clearing necessary cookies or storage can sign you out or remove unsent local changes. These descriptions cover functional storage and do not authorize unrelated tracking.
7. Why data is processed
Data is used to provide the functions you request, maintain access and synchronization, respond to support messages and protect services against misuse. Where GDPR applies, the relevant grounds are performance of the requested service or steps you ask for before using it; legitimate interests in security, maintenance and handling correspondence; consent where an optional processing activity requires it; and compliance with applicable legal obligations. An operating-system permission or an OAuth authorization is a technical permission and is not, by itself, the legal basis for every processing activity.
9. Retention and deletion
Hosted workspace and calendar records remain while the workspace or account is used, until records are removed, account closure is handled, or there is another applicable reason to retain limited data. Session expiry limits authentication; it does not automatically erase stored workspace, mailbox or calendar content. Account deletion is handled by contacting contact@nexacloudhub.com; there is no promise of a self-service account-deletion button in this version.
Operational and security records are retained only for the period needed to run and protect the service, investigate the relevant issue or meet a legal requirement. Support correspondence is kept while needed to resolve and document the request. Backup copies, if made, are separate from the live service and can retain older records until replaced or removed; no automatic fixed backup-deletion schedule is represented here. Contact us for the current retention arrangements of a particular hosted service.
10. Your rights and requests
Where GDPR applies, you may request access, correction, erasure, restriction or portability of your personal data, subject to the conditions of those rights. You may object to processing based on legitimate interests and withdraw consent for consent-based processing without affecting earlier lawful processing. Contact contact@nexacloudhub.com and identify the service and account concerned. We may ask for proportionate information to verify the request; do not send passwords, access tokens or your entire mailbox.
Requests are handled within the applicable legal time limits, normally within one month; an extension may apply to complex or multiple requests, with an explanation. You may complain to a competent supervisory authority, including Romania’s ANSPDCP. These projects do not make solely automated decisions intended to produce legal or similarly significant effects about you.
11. Contact and changes
NexaCloudHub is independently operated under the public name Vlad D., based in Romania. Contact: contact@nexacloudhub.com.
For privacy questions, rights requests or security concerns, use the contact address above and name the relevant project. This notice may change when features or processing change. The revision date identifies the version; a material new use of data will be explained before it begins, with a new choice where required.