Privacy Policy
Last updated: November 19, 2026
This policy explains how Ubelus Ltd (“Ubelus”, “we”, “us”) handles personal data when you visit our website, contact us, apply for a role, create an account, buy our software or use Overlaya, our work platform for Windows and the web. It applies under the UK GDPR and, for people in the European Economic Area, the EU GDPR. It is the privacy policy for Overlaya, including the Overlaya Windows app and its Microsoft Store listing.
1. Who is responsible
Ubelus Ltd, Flat 921, Churchill Place, Churchill Way, Basingstoke, Hampshire, RG21 7ES, United Kingdom, is the controller of your personal data. Contact us about privacy at privacy@ubelus.com.
For the content that you and your team store in an Overlaya workspace, the workspace owner decides what is stored. Where a business uses Overlaya for its own staff or customers, Ubelus acts as that business's processor for that content. If you need a data processing agreement, email privacy@ubelus.com.
2. Data we collect
- Contact form: name, email, company, project type, budget, timeline and your message.
- Recruitment: the selected role, name, email and CV; optional LinkedIn, phone, location, GitHub, portfolio and cover letter; submission type, notice version and acknowledgement, processing-basis assessment reference, status and internal review notes. Historical submissions retain their original consent record rather than being relabelled. Please do not include sensitive information or identity documents.
- Account: email, username, password (stored only as a one-way hash by our backend) and, if you use Google sign-in, your Google profile identifier and email. One Ubelus account is used on ubelus.com and in Overlaya.
- Orders and licenses: products purchased, order, payment-status and license records. Card and PayPal details for purchases on ubelus.com are handled by PayPal. Card details for Overlaya Pro are handled by Revolut. We do not store card details.
- Overlaya: the data described in section 3.
- Technical data: IP address and request logs processed by our hosting and security providers.
- Support access records: the administrator, account, stated support reason, authorization record and confirmation, session times, and connection details when a support session is used.
- Browser storage: sign-in tokens and preferences kept in your browser (see our Cookie Policy).
3. Overlaya
Overlaya is a work platform with projects, tasks, documents, whiteboards, timers and desktop overlays. It is available at overlaya.ubelus.com and as a Windows desktop app. This section says exactly what it collects and where it goes.
At a glance (Microsoft Store disclosures)
| Personal information collected | Account details (email, username, display name), your sign-in session, workspace membership and roles, the content you create, your preferences and, for paying workspace owners, billing references. Optional onboarding answers about how you will use Overlaya. |
|---|---|
| Shared with third parties? | Only with providers that run the service for us: hosting, email delivery, session storage, DNS and security, Google sign-in (if you choose it) and Revolut (Pro payments). We do not sell personal data and we do not share it for advertising. See section 5. |
| Analytics providers? | None. Overlaya contains no analytics, advertising or tracking software, and no third-party crash-reporting service. |
| Authentication providers? | Ubelus signs you in with your Ubelus username and password. You can instead use Google sign-in, which is optional. |
| Cloud storage providers? | Overlaya workspace data (projects, tasks, documents, files, whiteboards) is stored on our own database server hosted with Oracle Cloud Infrastructure in the UK (London). Ubelus account records (account, orders, licenses, subscriptions) are stored with Neon, a managed PostgreSQL provider, in the EU (Frankfurt). Sign-in session tokens are stored on our own server in the UK. |
| Your controls | Download a copy of your data, correct it, and permanently delete your account yourself, in Overlaya under Settings → Your data and privacy, or on this website. See sections 8 and 9. |
User accounts
You use Overlaya with a Ubelus account: email address, username, a verified-email flag and a password hash, or a Google profile identifier if you sign in with Google. Inside Overlaya we also keep an optional display name, the workspaces you own or belong to, your role in each, and invitations sent to your email address.
Authentication
Ubelus checks your credentials and issues short-lived access tokens and a longer-lived refresh token. In the browser these are kept in secure, HttpOnly cookies for up to 7 days between visits. The desktop app signs you in through your browser, so your password is never typed into the app. Refresh tokens are stored on our own server so they can be revoked. If you choose Google sign-in, Google receives your sign-in request and we receive your Google profile identifier and email address; we never receive your Google password.
Personal information collected
- Identity: email, username, display name and account identifier.
- Onboarding answers (optional): what you plan to use Overlaya for, how you heard about it, tools you use and features you are interested in. We use them to set up your first workspace and to decide what to build.
- Invitations: the email addresses you invite to a workspace, used to send the invitation and to match it when accepted.
- Billing (workspace owners only): workspace identifier, plan and billing period, payer email, and Revolut subscription and payment references. Only the owner pays; editors and viewers are never billed or asked for payment details. Payments are made on our website, never inside the desktop app.
- Preferences: settings, overlay layouts and the applications you choose to bind an overlay to, so they follow you between devices.
Usage analytics
We do not run product analytics, behavioural tracking, session recording or advertising in Overlaya. Features such as focus sessions, time tracking and dashboards show you your own activity and are stored as your content; they are not sent to an analytics provider. Our servers keep ordinary operational logs (IP address, time, request method and path, response status and size) for security and troubleshooting, normally for about 10 days.
Crash reporting
Overlaya does not send automatic crash reports or diagnostics to us or to any third-party service. If you contact support, we only see what you choose to send us. If you install Overlaya from the Microsoft Store, Microsoft may collect diagnostic data under its own privacy statement and your Windows settings, and may give us aggregated reports that do not identify you.
Device information
- To position overlays, the desktop app reads your monitors' names, sizes and positions on your device.
- For application-aware overlays, it reads the file name of the program in the foreground (for example Unity.exe) on your device to show or hide overlays. It does not read window contents, keystrokes, screenshots, clipboard or documents. This detection stays on your device and is not sent to us. If you bind an overlay to a program, that program's file name is saved with the overlay setting.
- The desktop app checks overlaya.ubelus.com for updates, which reveals your IP address and app version to our host, as any web request does.
- Run-in-background and start-with-Windows choices are stored on your device.
User-generated content
Projects, tasks, comments, documents (including images and attachments up to 5 MB each), whiteboards, timers and overlay layouts are stored on our servers so you and the people you share a workspace with can reach them. Access follows the roles set by the workspace owner. We do not read your content, except when you authorize a support session, to keep the service secure, or when the law requires it. We do not use your content to train AI models. If you embed a YouTube video in a document, YouTube thumbnails are loaded from Google and the video only plays after you click it.
AI interactions
Overlaya does not currently include AI features, so no content is sent to any AI provider. If we add them, we will update this policy first, tell you which provider receives what, and ask you before you first use them.
Cloud synchronisation
Overlaya is cloud-based. Your data is saved to our servers and shared live between the web and desktop apps and between collaborators. The apps do not keep a separate offline copy of your workspace on your device, other than files you choose to export.
Service emails
We email you only about the service: address verification, password reset, workspace invitations, deletion confirmation codes and account notices. They are sent from noreply@ubelus.com through Oracle Cloud Infrastructure Email Delivery (UK). We do not send marketing email about Overlaya without your consent.
4. Why we use it
- To answer your enquiries and provide quotes (legitimate interests / pre-contract steps).
- For new submissions under recruitment notice version 2026-11-18-recruitment-v2, our intended basis is legitimate interests: assessing skills and recruiting for current vacancies, or planning possible recruitment for the selected talent pool as client demand and project workload increase. New intake remains paused until the relevant assessment has been approved. A talent pool is not a current vacancy and guarantees no opening, interview or offer. Required fields are marked; optional profiles and contact details are not needed to submit.
- We use talent pool CVs to assess relevant skills ahead of potential recruitment, not for marketing, unrelated talent pools or sharing with other employers. A privacy-notice acknowledgement records that the notice was presented; it is not consent or a waiver of your rights. Historical consent-based records are flagged for review: we do not retrospectively switch their lawful basis, expand their purpose or contact their holders merely because this notice changes.
- To create and secure your account and deliver purchased software and Overlaya (contract).
- To process payments and prevent fraud (contract, legal obligation, legitimate interests).
- To send service emails such as verification, invitations and password reset (contract).
- To tailor your first Overlaya workspace from optional onboarding answers and to decide what to build (legitimate interests).
- To provide support only after customer authorization has been recorded, using a short-lived, auditable session without viewing or using the customer's password (legitimate interests and, where applicable, consent).
- To keep the service secure and fix problems (legitimate interests).
- To keep records the law requires, such as tax records (legal obligation).
5. Who we share it with
We only share data with providers that help us run the service, under appropriate agreements. We do not sell your personal data and we do not share it for advertising.
- Hosting and Overlaya data: Oracle Cloud Infrastructure, UK (London), which also delivers our service email.
- Account database: Neon (managed PostgreSQL, hosted on AWS in Frankfurt) holds Ubelus account, order, license and subscription records.
- Website hosting: GitHub Pages, which serves ubelus.com and overlaya.ubelus.com and sees visitors' IP addresses and requests.
- DNS, security and proxying: Cloudflare, which also passes traffic to our API and so sees those requests.
- Sign-in: Google, only if you choose Google sign-in or play a YouTube embed.
- Payments: PayPal for purchases on ubelus.com; Revolut for Overlaya Pro. These providers decide how they use payment data under their own privacy policies.
- Microsoft: if you install from the Microsoft Store, Microsoft handles the download and licensing under its own privacy statement.
Applicant records and CVs are available through administrator-only recruitment tools. Application details are stored in our backend, not published on the website. Email providers deliver application acknowledgements; new administrator notifications do not include candidate details or CVs.
We may disclose data where the law requires it or to protect rights and safety. If Ubelus is reorganised or sold, we will tell you before your data becomes subject to a different policy.
6. International transfers
Overlaya workspace data is stored in the UK. Ubelus account records are stored in the EU (Frankfurt), and personal data can move freely between the UK and the EEA under UK adequacy regulations. Some providers (for example Neon, GitHub, Cloudflare, Google and Revolut) are or may be part of groups that process limited data outside the UK and EEA, including in the United States. Where required, we rely on safeguards such as UK adequacy regulations (including the UK–US data bridge for certified providers), the UK International Data Transfer Agreement or Addendum, or standard contractual clauses.
7. Retention
- Enquiries: as long as needed to respond and for a reasonable period afterwards.
- Account and Overlaya data: while your account is active. When you close your account it is deleted as described in section 8.
- Order, payment and invoice records: six years, because UK tax law requires it.
- Server logs: about 10 days.
- Backups: we only keep short-lived database snapshots taken before software upgrades, and we delete them within 30 days. Our managed database provider also keeps a rolling recovery history that is overwritten within 30 days.
- Support access records: kept only as long as needed for security and audit purposes, and reviewed at least once a year.
- Cookie consent records: kept as proof of your choice.
Job applications and talent pool registrations, including CVs and review notes, expire no later than 12 months after submission. The cap reflects our anticipated business-planning cycle and aims to avoid repeated submissions, but is not a legal minimum or a reason to keep data we no longer need. We must review continued necessity and delete earlier where appropriate. Expired records are inaccessible through recruitment tools and removed from the live database by an hourly cleanup, including after restart. We do not automatically extend the deadline.
Live-database deletion does not itself erase separately downloaded files, emails or backups. We must also handle these copies when carrying out an erasure request. Backup copies must be protected, removed under the 30-day schedule above, and not restored into active use after deletion; if a backup is ever restored, we re-apply every erasure made since it was taken.
8. Account deletion and data erasure
How to delete your account
- In Overlaya: open Settings, find Your data and privacy and choose Delete account.
- On this website: sign in and go to Office → Account → Delete (sign in required).
- By email: write to privacy@ubelus.com or support@ubelus.com from your account email address. We will confirm your identity and respond within one month.
Self-service deletion shows you what will be deleted, then emails a 6-digit code to your account address that expires after 15 minutes. You confirm by entering the code and typing your email address. Deletion is permanent and cannot be undone. Because one Ubelus account is used on ubelus.com and in Overlaya, closing it closes both.
What is deleted
- Your Ubelus account: username, email, password hash, Google link, sign-in sessions, licenses, Software Library access, carts and unfinished sign-up records.
- Every Overlaya workspace you own, with all its projects, tasks, documents, attachments, comments, timers, settings, member lists and invitations. Other members of those workspaces lose access.
- Whiteboards you own, and your membership of workspaces and whiteboards owned by others.
- Your preferences, onboarding answers, task assignments, personal priorities, favourites and collaborator listings.
- Invitations sent to your email address.
- Your Overlaya Pro subscription, which is cancelled so you are not charged again.
What is anonymised rather than deleted
Comments and activity entries you wrote in workspaces owned by other people stay, so that their conversations make sense, but your name and identifier are replaced with “Deleted user”. If a comment itself contains personal data about you, email privacy@ubelus.com and we will remove it.
What may be kept, and why
- Order, payment and invoice records for six years, because tax law requires it. They are no longer linked to an identifiable account; Overlaya payment records keep the amount, period and provider reference but not your email.
- Records at payment providers. Revolut, PayPal and similar providers keep their own records for their legal obligations. We cannot erase those.
- Support access records showing that a support session took place and when, with its connection details and reason removed, to keep an accurate security audit trail.
- An erasure record containing only your former account number and the date, so that an erasure can be re-applied if a backup is ever restored. It contains no personal data.
- Operational logs and backups until they expire under section 7, and data we must keep to establish, exercise or defend legal claims.
How long it takes
Self-service deletion takes effect immediately in our live systems, normally within a minute, and we email you a confirmation. Short-lived backups are gone within 30 days, so erasure is complete within 30 days. Requests made by email are answered within one month.
When we cannot close an account automatically
If you own an Ubelus commerce shop, are an Ubelus commerce customer with contracts and invoices, or hold an administrator account, we will tell you and ask you to contact support@ubelus.com so we can close it safely. If your Overlaya subscription cannot be cancelled, or Overlaya cannot be reached, nothing is deleted and you can try again.
9. Your rights
Depending on where you live, you have the right to access, correct, delete or export your data, to object to or restrict processing, and to withdraw consent. For Overlaya users:
- A copy of your data: in Overlaya choose Download my data in Settings, or use Office → Account → Download your data (sign in required). You receive one JSON file with your account details, orders, the workspaces you own, your contributions to workspaces you belong to and your whiteboards. Passwords are only stored as one-way hashes and cannot be exported.
- Correction: change your username or email on your Ubelus profile, or email privacy@ubelus.com to correct anything else.
- Deletion and closing your account: see section 8.
- Objection, restriction, withdrawing consent: email privacy@ubelus.com.
You can also complain to the UK Information Commissioner's Office (ico.org.uk) or your local data protection authority. Contact us first and we will do our best to put things right.
You can object to recruitment processing based on legitimate interests, request restriction or deletion, or ask for access or correction. Where a historical submission relied on consent, you can withdraw it without affecting the lawfulness of earlier processing. Contact us using the email above so we can verify your request without collecting unnecessary identity information. We do not use automated decision-making to accept or reject recruitment submissions, or to make decisions with legal effect about Overlaya users.
10. Security
We use HTTPS (TLS 1.2 or later), hashed passwords, short-lived access tokens, HttpOnly cookies, role-based access controls and rate limiting, and our hosting provider encrypts stored data. Account deletion requires a code sent to your own email address. No system is perfectly secure, so please use a strong, unique password. If a breach puts your rights at risk, we will tell you and the regulator as the law requires.
11. Children
Our services, including Overlaya, are for businesses and professionals and are not directed to children under 16. We do not knowingly collect their data; if you think a child has an account, email privacy@ubelus.com and we will delete it.
12. Changes
We may update this policy as Overlaya changes. We will change the date above, and tell Overlaya users in the app or by email before any material change that affects what we collect or share, including adding analytics, crash reporting or AI features.