Legal
Privacy Notice
Introduction
This Privacy Notice explains how VEYLO X processes personal data in connection with its platform and services.
We are committed to processing data in accordance with the UK GDPR and Data Protection Act 2018.
Role of VEYLO X
VEYLO X is the data controller for the personal data processed through the platform. We decide what is collected, why, how long it is kept and who it is shared with.
A landlord or agent is a separate, independent controller for what they do with information once they have received it, for their own purposes and under their own responsibility. We are not joint controllers with them, and neither of us decides the other's purposes.
We are not responsible for what a landlord or agent does with information after they have received it, and they are not responsible for how we run the platform. If you have a question about their use of your information, you can raise it with them directly, and you can also raise it with us.
Nature of Data Processing
We process personal data necessary to:
- operate and maintain the platform
- enable account functionality
- support property and tenancy workflows
- generate system outputs (e.g. alerts, summaries)
We may also process technical and usage data for system performance and security.
Network addresses, account limits, and when we refuse requests
Every time your device asks our systems for something, it tells us the network address it is asking from. Data protection law treats that address as information about you, even though it does not carry your name.
Why we keep it. We keep a record of a network address so that we can notice when our service is being attacked or abused, and stop it. The record holds the address, the time of the request, what was asked for, and whether it worked. Where we refuse an address, we also record who decided, why, and when the refusal ends. We do not use the network-address record to build a picture of you, and we do not try to work out who you are from that record.
Our lawful basis is our legitimate interests, under Article 6(1)(f) of the UK GDPR. The interest is keeping the service running and safe for the people using it. We have written down our assessment of that, and you can ask us to explain it.
We may refuse requests coming from a particular network address where we believe that address is being used to attack or abuse our service. That particular refusal is based on the network address rather than the identity of the account. Separately, some of our security controls limit how often an account can make particular requests, and those controls may refuse a request when those limits are reached. For a network-address refusal we normally set an end date. Where we need to keep one in place without an end date, a named person has to decide that and write down why.
We also keep a count of refusals against the account they came from. We keep how many times an account was refused on a day, when the last one was, and which feature refused it. We keep it so we can tell the difference between our own checks wrongly shutting out genuine use and one account repeatedly hitting our abuse controls. It is used only for security monitoring and investigation, troubleshooting, and handling rights requests, complaints and regulatory enquiries. We do not use this count to make or support decisions about tenancy, listings, pricing or eligibility. Where a security investigation leads us to restrict an account, that decision is made by two of our people on the evidence of what happened, and a count on its own is never a reason to restrict anybody. Unlike the record of a network address above, this count is kept against your account, so it does identify you. We look up whose account it is only where we need to for a rights request, a complaint, a security investigation or a question from a regulator, and that access is restricted and logged.
What a network-address refusal does not do. It only affects requests that reach our own servers, and that is a smaller thing than it sounds. It does not stop you opening our website, which our hosting provider answers before any rule of ours runs. It does not stop you signing in. It does not stop you reading or updating your records in the app, because your device fetches those from our platform provider directly. It is not a block on the internet, and it does not stop your device reaching anything else.
What a network-address refusal can stop. Some parts of the service are answered by our own servers rather than by our providers, and a refusal does reach those. The clearest example is downloading a document we hold for you, such as a compliance certificate, a photograph, or a tenancy pack. If a network-address refusal is stopping you getting a document you need, tell us and we will look at it.
One address is often shared by many people. Everyone in an office, in a hall of residence or in a hotel can be using one address, and so can everyone on the same mobile network at the same time. That means refusing one address can affect people who have done nothing at all. Where that is happening we will lift the refusal promptly.
If we have refused your address, tell us and we will look at it again. Write to support@veylox.uk, which is the same address the refusal message itself gives you. Email always reaches us, whatever we have refused, because a refusal only applies to requests your device makes to our servers. We will not ask you to prove which device was yours. We will look at whether the refusal is still needed, and lift it if it is not. That is how we handle a request to lift a refusal, and it does not change any checks we may need to make before we answer your other privacy requests.
How long we keep the network-address record. Six months, counted from the last time the record changed. Where we have refused an address, the six months start on the day the refusal ended rather than the day it began. We keep each day’s record of refusals against an account for 30 days after the most recent refusal included in it. The retention table below sets out both periods.
Your right to object. You can object to us using your information in this way, both the network-address record and the count kept against your account. Write to privacy@veylox.uk, and see Your Rights below. Neither a network-address refusal nor an account limit stops you writing to either address.
The early-access list on veylox.uk
Our website at veylox.uk has a form for joining the early-access list. This section covers that form only. It is the sole personal information the marketing website collects, and it is separate from anything described elsewhere in this notice.
When you join the list we store:
- your email address, so we can write to you
- whether the page you signed up from was written for renters or for landlords, so that what we send is relevant
- the path of the page you were on, so we know which of our guides people find useful. The path only, never the query string
- the website you arrived from, if any, recorded as the site name alone. Any search terms in the link are discarded before it is stored
- the date you joined, and your browser's user agent string, for record keeping and to tell real sign-ups from automated ones
We do not ask for your name, your address, your telephone number or anything about your tenancy, and the marketing website has no other form.
Our lawful basis is consent, under Article 6(1)(a) of the UK GDPR, for everything in that list. The page you signed up from and the site you arrived from are held as part of the same single record, not separately and not for any other purpose, so one consent covers the whole entry. Giving us your email address is entirely optional; nothing on the website requires it, and the only consequence of not giving it is that we cannot write to you.
What we send. A short plain-English guide to what the Renters' Rights Act 2025 changed, sent as soon as you join. After that, we use the contact details you provide to send you occasional emails with new plain-English guides and updates about VEYLO X. Every message carries a one-click way to stop receiving them, and we do not sell, rent or pass your address to anyone else for their own marketing.
Withdrawing consent. Email us and we will remove you. Withdrawal is as easy as joining, it does not affect anything done before you withdrew, and we delete the entire entry rather than keeping the rest of it.
How long we keep it. Until the earlier of two years from the day you joined, or the day you ask us to remove you. If you joined the list before 21 October 2026 and did not go on to create an account, we delete your entry by 21 April 2027.
Where it is held. In the same infrastructure as the rest of the platform, described under Who handles your data and International transfers below. The marketing website itself sets no cookies of its own; page views are counted by Cloudflare Web Analytics, which is the only third party the website loads anything from.
Tenant and Applicant Data
Where tenant or applicant data is processed:
- where a landlord or agent gives us information about an applicant or tenant, we are the controller for what we then do with it on the platform, and we decide how long it is kept and who it goes to
- the landlord or agent remains separately responsible for what they do with that information for their own purposes, and for having been entitled to give it to us
- a named tenant's own legal name, which the tenant gives us directly, is covered under Your legal name when you join a tenancy below
- a person applying for a tenancy can also give us the name and email address of somebody they invite to apply with them or to act as their guarantor, and we are the controller for what we then do with those details
Credas verifies identity documents on our behalf. We also carry out the manual comparisons described below.
Documents you send us to finish an identity check. If the photo check cannot match you, you can send us your identity document in the app, under More, Account, Send us a document. A colleague at VEYLO X opens it, compares its photograph with the one you took, and records whether they match. Only colleagues whose role allows it can open a document, and each opening is recorded with a reason. We delete the files 7 days after you send them, whether or not anyone has looked at them. We currently retain the check record, including file names and any note, without an automatic deletion process. We aim to retain it for no more than six years, subject to lawful extensions, and are implementing deletion controls. We do this in our legitimate interests (UK GDPR Article 6(1)(f)) in completing the check you started and being able to show how it was decided. You can object: write to privacy@veylox.uk. Please use Send us a document rather than email. If you email us an identity document, contact privacy@veylox.uk so that we can arrange secure handling and consider its deletion.
Documents you send us for an ownership check. If the ownership check for a property has not passed, we may ask you to send us an official record of who owns it, such as an HM Land Registry title register, through the app. The app tells you which documents we accept, what they must show and what you may cover. We may ask you to confirm a notice first, and we record that you did. A colleague at VEYLO X whose role allows it compares details on the record, such as the owner's name and the property's address, with the details we hold for your account and the property, and may compare it with a copy we obtain from the registry that keeps it. The colleague records whether the record names you as an owner of that property. If it does, the ownership check for that property is recorded as passed, subject to the other checks required before you can invite a tenant to pay through VEYLO X. If it does not, the check stays not passed. We do not show your tenant the result of this comparison. It is a comparison only. It does not establish that you own the property, and we do not use it to check any mortgage, any other person's interest or your right to let, or use anything on the record that the comparison does not need. Access to the files is restricted and recorded. How long we keep the files, any copy we obtain and our record of the check is set out under Data Retention. We do this in our legitimate interests (UK GDPR Article 6(1)(f)) in making sure that a person who invites a tenant to pay for a property through VEYLO X is named as an owner of it, and in being able to show how that was decided. You can object: write to privacy@veylox.uk.
If you are named on an ownership record. If you are named on an ownership record that a landlord sends us, or on a copy we obtain to compare with it, we may hold your name, your address or other contact details, and any entry about you on it, such as a mortgage or other interest, a restriction or the price paid, for the periods set out under Data Retention. We do not use those details in the check or copy them into the record of the check, although a file name or note the landlord adds may contain them. A record can also include an entry that relates to criminal proceedings, or special category data, such as information about a person's health. We do not use the entry or copy it into the check record. We hold it for the Data Retention periods only where the statutory conditions and safeguards for preventing or detecting unlawful acts are met: UK GDPR Article 9(2)(g) and Data Protection Act 2018 Schedule 1 paragraph 10 for special category data; Article 10 and paragraph 36 for criminal offence data. If we hold contact details for you because the landlord has named you to us as another owner of the property who is named on the title, we tell you about this when they name you. For anyone else named on such a record, including other owners we hold no contact details for, lenders and others with a charge, former owners and people named in a restriction or notice, we have assessed and recorded that telling each person individually would involve disproportionate effort, so we give you this information here instead (UK GDPR Article 14(5)(e)). We hold the files in our legitimate interests (UK GDPR Article 6(1)(f)) described above; storage is described under Who handles your data and Data Retention. You have the rights described under Your Rights, including the right to object, and you can complain to the Information Commission.
Users remain responsible for:
- Right to Rent compliance
- identity verification
- lawful processing of personal data
Where you provide Right to Rent information through VEYLO X, we use it to keep a tenancy record and, where a follow-up check is legally required, to show your landlord a limited reminder that a Right to Rent re-check is due. We do not show your passport image, share code, document number, nationality, immigration route or visa/BRP class in the landlord dashboard.
If the date is wrong, contact us so it can be checked and corrected.
Your search preferences
When you use Find a place to rent, we ask what you are looking for so we can show you places that fit. Where you are looking, your budget, bedrooms, property type, move-in date, household size and lifestyle choices are used to produce those matches, and we need them to carry out the search you asked us for.
The same questionnaire also asks, optionally, about your income source, your income and your savings. We store your income source so that your preferences stay complete and you do not have to retype it. Where you give us an income or savings figure, we use that figure to show a rough comparison against the advertised rent, and to help order your matches. Leave them blank and we skip that comparison. We do not verify these figures and we make no approval decision.
Our lawful basis for your search preferences is UK GDPR Article 6(1)(b): processing necessary to take steps at your request before entering into a contract. That covers the optional income and savings figures only where you choose to give them as part of this matching feature.
We do not ask for your Right to Rent or immigration status when you search. We explain that a landlord has to carry out a Right to Rent check before a tenancy starts in England, so that you know what to expect, but we do not record an answer, and it plays no part in which properties you are shown.
Your answers are stored against your own account. A landlord or agent does not see them. Information reaches a landlord only when you choose to send it as part of an application. You can change or delete your answers at any time in More › AI Property Preferences.
Showing your name to your tenant
When you accept a prospective tenant's application, we show that person the name you have confirmed on your profile, so they know who their landlord is. If you let through a limited company, we show the company's registered name as it appears at Companies House, rather than a personal name.
We do not show your name earlier in the process. It is not shown while your property is listed, and it is not shown to people who only enquire about your property or attend a viewing.
If you are the lead owner of a property on VEYLO X, then while it is publicly listed, people viewing the listing can see the dates on which your identity check and the property ownership name match for it were completed. When holding deposits open on it, we may also email those dates once to applicants whose applications for it are still open. We show and send the dates only, never the result detail, the report or any document. We keep a copy of that email for six years after it was sent, and then delete it. We do this in our legitimate interests, and those of prospective tenants, in knowing which checks were completed and when, and you can object; see Your Rights below.
You manage your own name in your profile. If you update it, we update the name shown on your accepted applications so it stays current. We store it on those applications and on the resulting tenancy record. We keep it for the life of the tenancy and for six years afterwards; where an application is accepted but does not go on to a tenancy, we keep it for six years from the application.
We do this to perform our agreement with you. A landlord also has their own legal duties to give their name to a tenant on a written request, and on any written rent demand (Landlord and Tenant Act 1985, section 1, and Landlord and Tenant Act 1987, section 47). Those duties apply to you directly. VEYLO X records and displays the information you provide; it does not act on your behalf, and does not give legal advice.
Holding deposits where no tenancy agreement is recorded. If an applicant paid you a holding deposit and, once the deadline for agreement shown in our records has passed, we hold no record of a tenancy agreement being signed or of what happened to the deposit, we may email that applicant. The email gives your name, or if you let through a limited company the company's registered name, and the repayment date calculated from the deadline for agreement shown in our records. The actual repayment deadline under the Tenant Fees Act 2019 may be earlier or different depending on what happened to the proposed tenancy, and in some cases the Act allows the deposit to be kept. We may also email the applicant an email address for you that we have verified, so that they can contact you about the deposit. If you let through a limited company, it is the email address of the person who acts for the company on VEYLO X. We do this only where our records show that you received the deposit yourself. Before we first give your email address in this way, we tell you, so that you have time to object. We send your email address only to that applicant, and we tell you when we have sent it. Apart from your name, your email address and the address of the property the applicant applied for, our emails to the applicant about the deposit give no other contact details for you and no details of anyone else who owns the property. We include your name, and may give your email address, in our legitimate interests, and those of the applicant, in their knowing which landlord received the deposit and being able to contact that landlord about it when they may no longer be able to message you through VEYLO X. We do not hold the deposit, and we do not check whether you read email sent to that address. We keep a copy of each of these emails for six years after it was sent, and then delete it. If an email gave your email address, the copy we keep does not include it.
Your right to object to our giving your email address to an applicant who paid you a holding deposit. You can object at any time to our giving your email address to an applicant who paid you a holding deposit, as described above. You do not need to give a reason. You can object by emailing privacy@veylox.uk. Writing from the email address on your account, or including it in your message, helps us identify your account. We also accept an objection made to us in any other way. Once we have your objection and can identify your account, we stop giving your email address to applicants in this way, for all your properties, unless you withdraw your objection. An objection cannot recall an email address we have already sent.
You will see the landlord's name once the landlord accepts your application. If the landlord lets through a limited company, we show the company's registered name as it appears at Companies House.
When holding deposits open on a property you have applied for, we may email you the dates on which the lead owner's identity check and the property ownership name match for it were completed, and we keep a copy of that email for six years after it was sent.
If you paid a holding deposit and, once the deadline for agreement shown in our records has passed, we hold no record of a tenancy agreement being signed or of what happened to the deposit, we may email you with the landlord's name and the repayment date calculated from the deadline for agreement shown in our records. The actual repayment deadline under the Tenant Fees Act 2019 may be earlier or different depending on what happened to the proposed tenancy, and in some cases the Act allows the deposit to be kept. We may also email you an email address for the landlord that we have verified or, if the landlord lets through a limited company, for the person who acts for the company on VEYLO X. We give it to you only so that you can contact the landlord about the deposit. We do not hold the deposit, and we cannot tell whether the landlord reads email sent to that address. We send these emails in our legitimate interests, and yours, in your knowing that date and being able to contact the landlord, and you can object; see Your Rights below. We keep a copy of each of these emails for six years after it was sent, and then delete it. If an email gave you the landlord's email address, the copy we keep does not include it.
Taking over from your agent
If you are taking over the management of a property from a letting agent, we can prepare two letters for you: one to the agent, and one to your tenant. You sign them and you send them. We do not send them, and we do not contact your agent.
To prepare them we ask you for your full legal name, an address in England or Wales at which notices may be served on you, its postcode, the date you are taking over, and a telephone number your tenant can ring to check the letter is genuine. We ask you to type your name rather than take it from your account, because the name on an account may be an email address, and these letters may be read by a court. We ask for the address because a landlord must give the tenant an address in England or Wales at which notices may be served on the landlord (Landlord and Tenant Act 1987, section 48). That duty is yours and not ours. We record what you give us. We do not check it, and we do not give legal advice.
We also ask where your tenant pays their rent at the moment, and you answer that question about them. The answer decides which of two rent paragraphs the tenant letter carries, and we do not use it for anything else. Your tenant can ask us what we hold about them, and we will tell them.
We keep this information so that the pack can be produced again later while the information needed for it remains available. Our lawful basis for what you tell us about yourself is that the processing is necessary to perform our agreement with you, under Article 6(1)(b) of the UK GDPR. Our lawful basis for the answer about your tenant is our legitimate interests, under Article 6(1)(f): our interest is in not putting something about their rent into a letter that is not true. You or your tenant can object, and Your Rights below says how. How long we keep each of these is set out under Data Retention below.
Who can see it. This sits with the rest of the owner-only record of that property. You can see it, and so can anybody you have added to that property as a co-owner with the management role, because those are the people who already act on the property. It is not on the part of the property record that the public or a prospective tenant can read, and we do not give your agent access to this record through the platform.
Your legal name when you join a tenancy
If you join a tenancy as a named tenant, for example as a joint tenant with other people, we ask you for your full legal name. We ask for it because it goes on the tenancy agreement, alongside the other named tenants, and on the deposit protection record if a deposit is protected, so a deposit can be protected and registered as the law requires (Housing Act 2004). An account display name or nickname is not suitable for those formal records. You give us this name yourself, so for this information VEYLO X is the data controller.
We process your legal name to perform our agreement with you and to provide the tenancy platform. Where your landlord registers a deposit through us, we send your legal name to the deposit protection scheme in our legitimate interests, and those of your landlord, in having your deposit protected in your name, as the Housing Act 2004 requires your landlord to do (UK GDPR Article 6(1)(f)).
You have the right to object at any time, on grounds relating to your particular situation, to our sending your legal name to the scheme. To object, email privacy@veylox.uk or write to VEYLO X Limited, 66 Paul Street, London, EC2A 4NA. If you object, we must stop this processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed to establish, exercise or defend legal claims. We will tell you the outcome of your objection. Until we confirm that the relevant disclosure has been stopped, a deposit registration through VEYLO X may still include your name.
We ask for your name as a single entry, rather than separate first and last name boxes, so that names in any script, single-word names, and names that include punctuation are all accepted, and your spelling and capitalisation are kept. Please enter it as it appears on your identity documents, including any middle names. VEYLO X records the name you provide. Entering your name here does not verify your identity. Where we check it against your identity report, as described below, the name we hold can end up different from the name you gave us.
When you add your name, you confirm that it is your full legal name, and we keep a dated record of that confirmation. You can choose to do this later if you are not ready, and we will ask again next time you sign in. If you do not provide it, we cannot add you as a named tenant on the tenancy agreement or on the deposit protection record. Until you provide it, we show your landlord and the other tenants the name on your account, the name or email address the person who invited you gave us (some earlier invitations only), or your place in the household. Where the name or email address we show came from the person who invited you, we show it so that your landlord and the other tenants can tell the people on the tenancy apart until you give us your legal name. The person who invited you typed it, you have not confirmed it, and it may be incorrect. You can object: write to privacy@veylox.uk.
Your name also appears on a transcript of your messages if you or the other party download one. That document can be given to a deposit adjudicator, the Property Ombudsman or a court.
Your legal name is used on your tenancy record and, where a deposit is protected, is sent to the deposit protection scheme so the deposit can be registered in your name. This is the statutory deposit protection described under Who handles your data below, where the scheme acts as an independent organisation responsible for the data in its own right. Where your name is also used for a referencing or identity check, Let Alliance acts under its own privacy notice and Credas acts on our instructions, as explained under Who handles your data.
Your contact details on these records. Your landlord and the deposit protection scheme also receive contact details for you. A tenancy agreement sent through VEYLO X can give an email address for each named tenant. The prescribed information an owner produces through VEYLO X for a protected deposit can give an email address and a telephone number for each named tenant, because the Housing (Tenancy Deposits) (Prescribed Information) Order 2007 requires the information a landlord gives about a deposit to include the name, address, telephone number and any email address of the tenant (Article 2(1)(g)(iv)). Your landlord can see these details, and so can the other parties to the tenancy agreement and anyone the prescribed information is given to. When your landlord registers a deposit through VEYLO X, we send the scheme your legal name and an email address or a telephone number for you. These details enable the scheme to contact you about the protection of your deposit and its return. If you applied for the tenancy and the tenancy record holds both an email address and a telephone number for you, we send the scheme both.
These details come from you or your account. For the tenant who applied for the tenancy, they can also come from the tenancy record, which can include details your landlord entered, so they can differ from those on your account.
We rely on UK GDPR Article 6(1)(f) to give your landlord the contact details described above on these documents and to send one contact detail for each named tenant to the deposit protection scheme. Our legitimate interests, and those of your landlord, are in providing tenancy agreements and prescribed information with tenant contact details, having deposits protected, and enabling the scheme to contact named tenants about them. This applies to every named tenant, including the tenant who applied for the tenancy. Your landlord is responsible for what they do with these details for their own purposes, as explained under Role of VEYLO X above, and the scheme is responsible for them in its own right once it receives them, as described under Who handles your data below.
You have the right to object at any time, on grounds relating to your particular situation, to our giving your contact details to your landlord on these documents or sending them to the scheme. To object, email privacy@veylox.uk or write to VEYLO X Limited, 66 Paul Street, London, EC2A 4NA. If you object, we must stop this processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed to establish, exercise or defend legal claims. We will tell you the outcome of your objection. Until we confirm that we have stopped the relevant disclosure, a document your landlord produces through VEYLO X, or a deposit registration your landlord makes through VEYLO X, may still include your details, including after we have accepted your objection. This does not change details your landlord or the scheme already holds.
If you change your email address or mobile number with us after the deposit is registered, we do not pass the change to the scheme unless you ask us to. If the details we sent are wrong or out of date, you can contact the scheme, or ask us at privacy@veylox.uk to correct them. When we correct details we sent to the scheme, we will tell the scheme, unless that proves impossible or involves disproportionate effort. You can also ask us which organisations we have sent your details to.
When your name is locked
Once your tenancy agreement is signed, or your deposit is registered with the scheme, your legal name is fixed on those records. From that point you can no longer edit it yourself in the app, because it now sits on a signed agreement and, where relevant, on a statutory deposit record that VEYLO X does not change.
If a locked name is spelt wrong, or your legal name later changes, speak to your landlord. Your landlord holds your identity information and is responsible for the tenancy agreement and for the deposit registration, so a correction is made through them. Where your landlord confirms a correction, we update the name we hold to match, and we keep a record of the previous name, because your signed agreement and deposit record still carry it. We will tell you when the name we hold for you has been updated. Where the name we hold is the name we recorded from an identity report, your landlord cannot make that correction, and it is made through us instead.
You can also ask us directly to correct your name at any time, whether or not your landlord has acted. Contact us at privacy@veylox.uk and we will handle your request as set out under Your Rights below. We will not change a tenancy agreement or a deposit registration ourselves, and we cannot give you legal advice, but we can correct the name we hold, and where we have already shared it with an organisation such as the deposit protection scheme, we will tell them, unless that proves impossible or involves disproportionate effort, so their record can be updated too.
We keep your legal name on your tenancy record for the life of the tenancy and for six years afterwards, as set out in the named-tenant legal name row in the retention table below. As a field on your account profile, your legal name is kept for the life of your account and for 12 months afterwards, in line with the account record row in the same table. We keep the dated record of your confirmation, and of any later correction, for seven years, as set out in the compliance attestations row.
When we check your name against your identity report
Where an identity report is available, an authorised colleague may compare the name you provided with the name shown on the report and record the result. A comparison does not automatically change the name held for you. Any proposed change must be approved by a second colleague before it is recorded as the name held on the platform. A new use of information we already hold has to be set out before it starts, whether you gave that information to us or it reached us from somebody else (UK GDPR Articles 13(3) and 14(4)), which is why it is set out here.
The report we receive carries the name taken from the identity document you used. The comparison is ours. It is not a conclusion a provider reached for us, and it is not a pass or a not pass on a check.
Where the two names do not match, the colleague types the name as it is printed on the report, so that what they read can be checked afterwards. That typed name is kept with the report as a record of what the report said.
Nothing on the platform uses that record as the name we hold for you, before or after any decision about the name we hold. That includes the party names on a tenancy agreement, the registration of a deposit with a tenancy deposit scheme, and payment details.
The same name can become the name we hold for you, but only if two colleagues take the steps set out below, never by the record alone. Until they do, the name we already hold for you stays as it is.
If a change is approved, the name we hold for you is updated to the approved name. That name may then be used in tenancy agreements, deposit registrations and payment details. You may challenge an inaccurate name and ask us to correct it.
Neither that record nor those steps decide what your legal name is. The name printed on your document may already be your correct legal name, and the name we hold may be the wrong one, whichever way our review goes. What the steps below decide is the name we use, and nothing more.
A colleague cannot do this alone. One colleague puts forward the name from the report, and a second colleague has to approve it. The same person cannot do both. The name put forward has to be the one a colleague recorded off the report, and a colleague has to have recorded that the two names do not match before it can be put forward at all. Until it is approved, the name we hold for you does not change. Where the second colleague does not approve it, we clear the name that was put forward and the name we held before it, and keep only the fact that a proposal was made and not approved, who made it, who did not approve it, when, and why. That clearing applies from the day we start clearing refused names. Proposals refused before then, under the earlier route we have used since August 2026, still hold both the name that was put forward and the name we held, and nothing deletes them. If the second colleague approves the change, we keep a record of that decision. It is a separate record from the comparison record kept with the identity report, and the 12 month limit set out below does not cover it.
We keep the decision record with your tenancy record and dispose of it when we dispose of that record, six years after the tenancy ends, which is the period set out for your legal name above. A tenancy record is only disposed of once it is recorded as ended, terminated or cancelled and that end date is more than six years old. Where we hold no end date, or the tenancy has not ended, those six years never start, and the decision record stays with the tenancy record for as long as we hold it.
A legal hold can keep the record for longer than that. We place a hold only where we can state the reason for it, we limit the hold to the records that reason covers, and we record what has to happen for it to be lifted, which is the end of the claim, investigation or other matter the hold was placed for. When that happens we lift the hold and the record is disposed of as set out above. Once it is approved, you cannot change it in the app, and neither can your landlord. We keep the name we held before, on your record, with the date it was replaced, because your signed agreement and your deposit registration still carry it. We create the notification at the same time as the change, so either both happen or neither does. Delivery may take longer and is not guaranteed to be immediate. We do not write to you when we make the comparison. The message tells you that we have changed the full legal name we hold, that the name came from the identity report about you, that you cannot change it in the app and neither can your landlord, how to tell us it is wrong, and that we will answer you in writing within one month. We send you that message even if you have turned off your other notifications. To change it, contact us at privacy@veylox.uk. This is the one case where your landlord cannot make the change, so please come to us and not to them. You can also send us a document in the app, under More, Account, The name we hold is wrong, and tell us there what you say your name is.
If you tell us in the app that the name we hold is wrong, we record that you say so, the name we hold, and any name you give us that we can record. This changes neither name. While that is open, we do not use the name we hold to register a new deposit. A colleague then reads what you sent and either keeps the name we hold or proposes changing it to the name you gave. A proposed change takes effect only if a second colleague approves it. Either way, that decides the name we use, not what your legal name is. Handling what you tell us does not give your landlord the files you sent, or the name you gave us unless we change the name we hold to it. If they try to register a new deposit through us before we answer, we refuse it and tell them that one of the tenants has said the name we hold for them is wrong. We write to you with our answer within one month. If you tell us again before we have answered, we answer the newer message instead, within one month of it. If the older one had already led us to change your name, we still write to tell you that. We delete our record of what you tell us in the app about your name, our answer, any change it led to, the copies we keep of the emails we send you about it, and the note of it on your account, after six years from the day you told us. We keep them longer while a hold we have placed on the record, or on a tenancy you are a tenant on, is in place, or while a request you have made in the app to erase your account is waiting; for three months after you make any other request to us about your data through our in-app assistant, whether or not we have answered it by then; while we still owe you an answer or an email about it; while an answer or change is still being sent or approved; while an inconsistency in the record or its linked records prevents us from confirming that deletion would be safe; or if we cannot read the date on the record. Our team also receives an email about the dispute containing its case number, but not your name or account number. Our automatic dispute-record deletion does not delete that email from the company mailbox; once the dispute record is deleted, its case number no longer finds your account through our back-office case-number search. After that, we keep internal records of the steps our staff took. We remove your account identifier from those records, but retain internal reference IDs. We also keep a separate deletion marker containing your account identifier and the dispute ID, so that we can remove email copies that arrive late. That marker is scheduled for removal after 30 days. Until it is removed, the retained records may still be linked to you through their reference IDs. We keep the dated record of any correction for seven years, as set out above. If we changed your name, your former name stays in your account's name history, as after any correction, because signed agreements and deposit registrations carry it. You can ask us to delete any of these at privacy@veylox.uk.
Your landlord does not see the comparison itself. They see the name we hold once it is recorded.
A document you send us is deleted 7 days after you send it, whether or not anyone has looked at it. We keep what the colleague recorded off the report for no longer than 12 months from the day we filed the report. That outside limit runs from the day we filed the report and not from the day of the comparison, so a comparison made late in that period is kept only for what is left of it. Where a hold keeps the report, it keeps this with it. Once the report has gone there is nothing left to check the record against, and we do not make a new one. This is a period we have chosen and not one the law requires of us. You can also ask us to delete it at privacy@veylox.uk.
We do this in our legitimate interests in having the right name on a tenancy agreement and on a statutory deposit record, and in being able to show how that name was settled (UK GDPR Article 6(1)(f)). You can object: write to privacy@veylox.uk. If you object, we will stop unless we can show compelling legitimate grounds that override your interests, rights and freedoms, or we need the record to establish, exercise or defend legal claims.
VEYLO X records and displays the legal name currently held in your platform record. This is normally the name you provide, but it may be changed following the identity-report comparison and two-colleague approval process described above. Entering or recording a name does not, by itself, verify a person's identity. Any separate identity checks are described in the relevant section of this notice. We do not act for you or your landlord, and we do not provide legal advice.
Your name when you own a property with somebody else. If you have confirmed your own details as one of the owners of a property, and an owner sends a tenancy agreement for that property through VEYLO X, we put the full legal name you confirmed in your own account on the agreement, in the part that names the landlord, and ask you to sign it. The tenants and the other owners can see your name on it. When you sign, we record the details described under Signing a document electronically, and the other parties to the agreement can see them as described there. We also tell you when it is your turn to sign. We use your name in this way to perform our agreement with you, because you asked us to hold the details you confirmed as an owner of the property and to let you sign documents for it (UK GDPR Article 6(1)(b)), and in our legitimate interests and those of the other parties in a tenancy agreement that names every legal owner of the property correctly (Article 6(1)(f)). You can object to our relying on those legitimate interests: write to privacy@veylox.uk.
The prescribed information your tenant is given. Where a deposit is protected for the tenancy, we produce the prescribed information for an owner to give to the tenant. It names every landlord, so where you own the property with somebody else it carries your name, the address recorded for you, your telephone number and your email address, alongside the other owners'. Article 2(1)(g)(iii) of the Housing (Tenancy Deposits) (Prescribed Information) Order 2007 requires the name, address, telephone number and any email address of the landlord, and where a property is let by more than one landlord it requires those details for each of them. The document also gives a correspondence address for the service of notices. That address is not held for each of you separately: where your tenancy agreement names more than one landlord, the address the agreement gives for notices is printed as the correspondence address for every landlord it names, because the agreement states that one such address serves all of them and each person it names signs it. Where the agreement gives no such address, the document says that a correspondence address is not recorded. VEYLO X does not serve the prescribed information on your tenant and does not send it to them. The owner does that, and the duty is theirs and not ours. Where the document an owner has served is held on the Platform, your tenant can open a copy of it in the app.
Council tax when you move in
When you move into a rented home, your local council needs to know who now lives there so that council tax can be billed to the right people. Your landlord can use VEYLO X to notify the council of the change of tenancy. Where they do, the notification includes your name and the date your tenancy starts. Your landlord types your name into the notification and sends it themselves, from their own council account, online form or email. VEYLO X provides the template and prepares the wording, but it does not fill your name in from your record, and it does not send anything to the council for your landlord or for you. VEYLO X is a software platform for renting and letting in England. It does not act for your landlord or for you, and it does not give legal advice.
We do not ask for your consent to this, and it does not depend on your consent. Council tax, and keeping a council informed of who is liable to pay it, are set by law under the Local Government Finance Act 1992. Your landlord makes the notification to meet their responsibilities under that system, in their legitimate interests as the person letting the property to you, so that the council can bill the right people. We hold your name and your tenancy dates so that we can provide the tenancy platform to you under our agreement. Because the law provides for this, you are not asked to agree to it or to opt in.
The name used is the one your landlord types in. That is a separate thing from the legal name you give us directly when you join a tenancy, which is described under Your legal name when you join a tenancy above, and for which VEYLO X is the data controller. Once your landlord has notified the council, your landlord is separately responsible for what they have sent and for dealing with the council, as explained under Role of VEYLO X above.
The notification is about the move from the previous tenancy to yours. It shows your name and your tenancy start date, and, where your landlord provides them, the name and end date of the tenant who is moving out. Your landlord may also choose to add the number of adults living in the home and their own telephone number. Those extra details are optional and are the landlord's choice. VEYLO X does not add them, and it does not take them from your account.
If your name or your tenancy dates are shown incorrectly, the quickest way to put it right is usually through your landlord, who prepares and sends the notification and can send the council a correction. You can also contact us at privacy@veylox.uk, and we will deal with your request as set out under Your Rights below. We can correct the name and details we hold, but we cannot change what your landlord has already sent to the council, and we cannot give you legal advice. You can also contact your local council yourself to register for council tax, and VEYLO X can provide wording you can use for that. Either way, VEYLO X records and provides the wording only. It does not deal with the council for you and does not verify anything with the council.
Signing a document electronically
When you sign a tenancy agreement or a deed of guarantee on the Platform, we record what happened so that each party can later show that the document was signed. We record the time you signed, the email address on your VEYLO X account, the IP address your device was using at the time, the fingerprint of the terms you agreed, the wording you confirmed before signing, and the fact that you confirmed who you are again immediately before signing. We record the same facts for the other parties.
The other parties can see this. Each party to the document can download a Certificate of Completion and can see the signing record on screen. Your name, your email address, the time you signed and the IP address you signed from appear on it, and you can see the same details for the other parties. Where more than one tenant signs the same agreement, a tenant does not see another tenant's email address or IP address on the Certificate of Completion or the signing record. Where more than one owner signs, every party can see each owner's name, email address and IP address.
We do this in our legitimate interests, and in the legitimate interests of the parties, in being able to evidence that an agreement was signed if it is ever questioned (UK GDPR Article 6(1)(f)). We record that the email address on the account was confirmed and that you signed in again immediately before signing. That is evidence of control of the account and the mailbox. It is not an identity check, and VEYLO X does not tell anyone that it has established who you are.
The Certificate of Completion is only ever downloaded by a party to the document, after signing in. We do not send it by email. How long we keep the signing record is set out under Data Retention below.
When somebody complains about you, and what we write down
Somebody may complain to us about you. If they do, we open a case and write down what was said. Our Terms explain what happens next, in the section titled Temporarily pausing part of your account. That section tells you the two things we may pause while we look into it, the long list of things we will never pause, how long a pause can last, and how to reply. This section is about the information side of the same thing: what we write down, where it came from, why we are allowed to hold it, how long we keep it, and what you can ask us for.
A case is not a finding about you. Opening one is not a decision that you did anything, and we do not keep score. How many complaints have been made about you is never a reason to pause part of your account, and it is not something we count, work out, or hold as a total anywhere. We also never pause your account because the other party to a tenancy says you behaved badly as a landlord or as a tenant. That is not ours to decide.
What we write down. Who the complaint is about, which is you. What was alleged, in words, written as an allegation and not as a fact. Which of the reasons listed in our Terms we are relying on. What harm we think may carry on if we pause nothing. Where in our own records we can see something that bears the allegation out. Whether we considered if the decision would treat you unfairly because of who you are, and what we concluded. Which of the two things in our Terms we paused, if we paused anything. Which of our people proposed it, which of them agreed to it, and when. When we wrote to you, and what we told you. When it ended, and why. Where one of our people later lifts a pause, we write down who did it and how they saw the risk at that point.
Where it comes from. Most of this does not come from you. What was alleged comes from the person who complained, and what bears it out comes from records we already hold. We also keep a way of finding the complaint we are acting on, and that reference may carry information about the person who made it. We hold it because a decision to pause part of somebody's account has to be traceable back to what prompted it. A decision nobody can trace back is a decision nobody can review, including you.
Sensitive information can end up in what we write. Some of the reasons in our Terms concern an allegation that something unlawful was done, so what we write down can concern an alleged offence. Separately, where we have written down whether a decision would treat you unfairly because of who you are, that reasoning can touch something the law treats as especially sensitive, such as your health, your beliefs, your race, or your sex life. We do not ask you for any of it, we do not go looking for it, and we never use it to decide anything about you. Where it appears, it is there because it was needed in order to answer whether we were being fair to you, and it is among the first things we delete.
Our lawful basis is our legitimate interests, under Article 6(1)(f) of the UK GDPR. The interest is protecting people from harm being carried on through our platform, and being able to show that a decision to pause part of an account was properly made, properly recorded and open to review. Where we are required to pause an account by law, or by a body entitled to require it, our basis is our legal obligation, under Article 6(1)(c). For the especially sensitive information described above, our condition is Article 9(2)(f) of the UK GDPR, which permits it where it is necessary for the establishment, exercise or defence of legal claims. Where what we write concerns an alleged offence, Article 10 of the UK GDPR applies, and our condition is the one for legal claims at paragraph 33 of Schedule 1 to the Data Protection Act 2018. Both come to the same thing in practice. We hold it so that a decision we made can be answered for, to you, to the Information Commission or to a court, and for nothing else.
No pause is ever decided by a computer. Two of our people have to agree before a pause takes effect, and whoever proposes it cannot be the one who agrees to it. In an emergency one of our people may act alone, and that pause ends by itself within twenty-four hours unless a second person has agreed to it by then.
What we tell you, and when. A pause has no effect until we have written to you. We tell you what is paused and from when, exactly what you can still do, the reason in words, the date it lifts by itself, how to reply and to whom, how to complain, and that your rights in law are not affected. We may hold the reason back for a time, where telling you would tip somebody off, destroy evidence, or create a risk to somebody's safety. We will never hold back the fact that something is paused, we write down why we held the reason back, and we tell you the reason once it is safe to do so.
We do not tell you who complained. You can ask us for a copy of the information we hold about you, and this record is part of it. What we will not give you is anything that would tell you who complained, or anything that is information about another person. Where we hold something back for that reason, we will tell you that we have done so and why, so you know the copy you have is not the whole of the record. The right that gives you a copy of your own information does not give you somebody else's, and we would answer a request from them about you in exactly the same way.
How long we keep it. We keep what was alleged for 12 months, and the record of what we decided for 6 years. Both are counted from the day the case ended, and where a case never went anywhere at all, from the day we opened it. At 12 months we delete what was alleged, where in our own records we could see something that bore it out, what harm we thought might carry on, and what we concluded about whether the decision would treat you unfairly. What is left is the record of the decision itself: that there was a case, which of the reasons in our Terms we relied on, what we paused if we paused anything, which of our people proposed it and which agreed to it, when we wrote to you, and how it ended. At 6 years we delete that as well, and what stays after that is our own internal note that a member of our staff took each step, with you taken out of it. Six years is the period in which a claim about something we did can still be brought, under the Limitation Act 1980, and it is the period we already use for other records for the same reason. Twelve months is shorter on purpose, because a pause can last twenty-eight days at the very most, and holding an unproven allegation about you for six years to account for twenty-eight days is longer than we can justify. This happens by itself, once a day, rather than waiting for one of our people to remember. The one thing that stops it is a dispute that is still live. Where you are challenging a pause, or a complaint, a request about your own information or a claim is still running, we keep the whole record until that is finished, and then delete it as soon as the periods above have run out.
Your rights, and how to use them. You can ask us for a copy of this record, ask us to correct it, ask us to limit how we use it while you dispute what it says, ask us to erase it, and object to us holding it at all. Write to privacy@veylox.uk. Your Rights below sets out each of those rights in full, together with the route for complaining to us about how we have handled information about you and the times we work to. Replying to a pause, exercising your rights over your own data, and getting in touch with us are all among the things a pause never stops.
The card your plans renew on
When you buy a monthly or annual plan, you enter your card details into a field provided by our payment provider, Stripe, and they go straight to Stripe. VEYLO X never receives, sees or stores your full card number or its security code.
What we keep. So that your plan can renew, we ask Stripe to keep your card for later payments, and we keep: the reference Stripe gives your customer account and your card; the card brand; the last four digits; the expiry month and year; and whether you have switched off auto-renewal. To create your Stripe customer profile, we provide your email address and our internal account reference. Stripe also receives information needed to process the payment, including its amount and transaction reference, and collects information directly through its payment services. For each payment, we record your billing country and the country that issued your payment card to assess applicable taxes and maintain supporting tax records. We use this information where necessary for our legal obligations (Article 6(1)(c)) or our legitimate interests in determining the correct tax treatment (Article 6(1)(f)). We do not create a renewal customer profile or save a renewal card through our one-off purchase flow.
What we use it for. We use these details to charge your card for each renewal of your plans until you switch off auto-renewal, and to show you on your Subscriptions page which card that is.
Why we may use it. We use saved-card details as necessary to administer your subscription and collect renewals you have authorised under Article 6(1)(b) of the UK GDPR. This data-protection basis does not itself authorise a card charge or justify keeping details that are no longer needed. We remove saved-card details we no longer need, as described under How long we keep these details. Any limited record retained for another purpose requires a separate, identified lawful basis.
We also keep limited records of cancellation or withdrawal instructions to prevent further unauthorised charges. We retain the minimum operational restriction while it is needed to prevent reuse of the stopped authority. We assess any separate evidence retained for a dispute under its own lawful basis and retention criteria. Deleting saved-card details does not reactivate a withdrawn authority.
Where your bank, through Stripe, tells us that payment authority has been withdrawn or a stop-payment instruction applies, we record the affected card reference, the reason code and when the instruction was recorded. We use this information to prevent further attempts to charge that card under the withdrawn authority.
We keep the record that you switched off auto-renewal or cancelled a plan to carry out your instruction under our contract with you (Article 6(1)(b) of the UK GDPR). We keep the record of a withdrawn payment authority because we have a legitimate interest, which we share with you, in never charging a card whose authority has been withdrawn (Article 6(1)(f)). We keep that record while the card remains saved with Stripe for your account. Our daily process normally deletes it 31 days after Stripe confirms the card has been removed, the period in which Stripe can still resend a delayed message about it. Deletion is delayed while removal cannot be verified, records cannot be read, a card change or another record could restore the card, a legal hold applies, or the stop still protects a renewal card. You have the right to object to this use. If you do, we will stop unless we have compelling legitimate grounds that override your interests, rights and freedoms, such as preventing an unauthorised charge to your card.
Stripe. Stripe holds your card and takes payments for us, on our instructions. Stripe also processes payment information for purposes it determines itself, including fraud prevention, security, legal compliance and operating and improving its services, as explained in its privacy policy. See Who handles your data below.
How long we keep these details. A daily process checks the cards saved for renewals. We normally request removal of a replaced card seven days after replacement, or seven days after our process first finds it if no replacement record exists, and we stop charging it straight away. When no plan remains renewable, we remove operational card details and request card removal about 30 days after the latest paid-period end or lapse. With no recurring-plan record, this runs from first detection. The customer reference and separately described cancellation, restriction and evidence records remain. We keep the record of the authority you gave to save a card (the wording you agreed, when, and the card it covers) while it is in force and for six years after the money for the last payment under it was taken. If no payment was ever taken under it, we delete it about 31 days after it ends, or when an erasure of your data completes if sooner. A card change that was started but not completed is deleted about 7 days after it is resolved, once any unused card from it is removed. Unresolved payments, unreadable records and legal holds can delay deletion. Removal failures are retried, and repeated failures and anything held back for more than 14 days are flagged for review by our team. A card change that did not complete but carried a payment instruction, including one refused after payment was taken, is normally deleted six years after final resolution. Applied changes follow the authority-evidence retention period above. Legal holds, unreadable records and unresolved charging activity can delay deletion. You can ask us at any time to remove your saved card or to erase these details.
Payment and refund records. We keep records of subscription payments, one-off purchases, checks, cancellations, refunds and payment disputes. These may include transaction references, dates, amounts, VAT, payment status, the plan or service purchased, property and application references, applicant slot and check-provider references, commissioning details, renewal reminders, payment failure and dispute reasons, cancellation dates and methods, reasons you provide for cancellation, refund calculations and decisions, reasons recorded by staff for refunds, staff action records, and your recorded choices concerning services started during the 14-day cancellation period.
We use information necessary to administer purchases, subscriptions, cancellations and refunds under Article 6(1)(b) of the UK GDPR. We retain information necessary to comply with applicable tax and accounting obligations under Article 6(1)(c). Article 6(1)(c) also covers the records we need to meet our duties when you cancel within the 14-day cancellation period under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013. Where information is separately retained to establish, exercise or defend legal claims under Article 6(1)(f), we explain that purpose, the applicable retention criteria and your right to object. Different retention criteria apply to different categories. These records are separate from saved-card details.
After a plan or purchase ends, we keep the records of what you bought, what you paid, any cancellation or refund, the reminders we sent and your cooling-off choice, and, after a payment dispute, the records needed for it, to establish, exercise or defend legal claims about it (Article 6(1)(f)), for the periods in the retention table. You have the right to object to this use. If you do, we will stop unless we need the records to establish, exercise or defend legal claims or have compelling legitimate grounds that override your interests, rights and freedoms.
When you start a purchase, we keep a short record of the plan and properties concerned so that a repeated click cannot charge you twice. It is normally deleted when the purchase completes. If the purchase is interrupted, the record is deleted automatically about 30 days after it was started.
Removing your card or erasing your data. Contact privacy@veylox.uk to request removal of your saved card or erasure of your data. One of our colleagues handles each request, removes your saved cards at Stripe and, where you ask for erasure, your Stripe customer record, and records anything kept and why. We will tell you what we have removed, anything we have kept and why, and anything we have not yet been able to complete. Removing a card does not by itself settle or cancel a separate contractual liability.
Free offers
We email free offers only to people who have agreed to receive emails from us about free offers and promotions (Article 6(1)(a) of the UK GDPR and regulation 22 of the Privacy and Electronic Communications Regulations); you can unsubscribe at any time from any offer email. We keep a record of your marketing consent and any withdrawal so that we can demonstrate your choice and honour it. We retain the minimum information needed for this purpose and review it periodically. You can withdraw consent at any time. The link carries a single-use code. We record your email address and the name we wrote to, which offer it was, who sent it, when the link expires and, if you use it, your account and the property you chose. Once you switch an offer on, we use these details to provide it to you (Article 6(1)(b)). We keep a record of which offer your account took and when it ends, because that record is what stops an account taking a second free offer (our legitimate interest in applying the one-offer rule, Article 6(1)(f)). When you open an offer link while signed in, we count how many times your account has checked an offer link that day, to protect offers from misuse (Article 6(1)(f)). You have the right to object to our uses based on legitimate interests. If you do, we will stop unless we have compelling legitimate grounds that override your interests, rights and freedoms.
Lawful Basis
Processing is carried out on the basis of:
- contractual necessity
- legal obligations
- legitimate interests
We rely on consent for biometric identity checks, as explained under Biometric identity checks below, and for affiliate tracking when you open a paid partner ad, as explained under Affiliate referrals and tracking below.
For non-biometric Credas checks, we rely on our legitimate interests and those of landlords in verifying identity, address, property ownership and company details, preventing fraud, and screening for sanctions and politically exposed persons (UK GDPR Article 6(1)(f)). You can object at privacy@veylox.uk. Our use of saved cards and provider reports is explained under The card your plans renew on and Reports our providers send us.
Data Sharing
We may share data with:
- infrastructure providers
- third-party integrations (e.g. referencing, payment, tenancy services)
We do not sell personal data.
Who handles your data
We work with four different kinds of organisation, and the law treats them differently. We set them out separately so it is clear what each one does and who is responsible.
These providers process personal data only on our instructions, under a written data-processing contract. We remain responsible for your data.
Processors acting on our behalf (UK GDPR Article 28)
| Provider | Purpose | Region | Transfer safeguard |
|---|---|---|---|
| Google Cloud / Firebase | PurposeHosting, authentication, Firestore database, file storage, App Check, Cloud Functions | RegionDatabase, hosting and the files you upload, such as documents and photographs: United Kingdom (London). Sign-in data for Firebase Authentication is processed in the United States by Google. | Transfer safeguardStandard Contractual Clauses with the UK Addendum, plus Google LLC's EU-US Data Privacy Framework (UK Extension) |
| Google (Gemini API) | PurposeReading the content you send to our assistant, so that it can answer you. Reading compliance certificates and other property documents you upload, so that we can pick out the dates and reference numbers and save you typing them in. Writing a draft listing description from the property details a landlord has entered, including the address. Reading a listing description as it is written, so that wording which conflicts with letting rules can be pointed out before the listing is published. Suggesting how time-sensitive a repair appears, and drafting a message to the landlord's own contractor, from what the landlord types into the repair assistant. We do not use this to make any decision about you. Google does not use your content to improve its products, or to train any AI models other than those it uses to enforce its policies. | RegionWhat we send to Google, and what it sends back, may be held in any country in which Google or its agents maintain facilities. Google keeps it for 55 days to detect abuse and for safety, security and legal reasons, and authorised Google staff may review it. | Transfer safeguardOur contract is with Google Cloud EMEA Limited in Ireland, which the United Kingdom recognises as providing an adequate level of protection. For onward transfers, Google relies on its certification under the EU-US Data Privacy Framework, UK Extension, and on standard contractual clauses with the United Kingdom International Data Transfer Addendum. |
| Cloudflare (Turnstile) | PurposeProtecting the sign-up flow, and certain secure areas of the service, against automated abuse. The check loads only once you start creating an account, or when you open one of those secure areas. It does not load when you are simply browsing the site or when you sign in to an existing account. It runs in the background, normally completes without you noticing, and only shows you a challenge if something about the visit looks unusual. It receives your IP address and basic technical information about your browser. It does not receive your name, your email address, your password, or anything else you type into the form. Cloudflare also uses what it learns from these checks for its own purposes, which we explain separately below. | RegionYour connection is normally handled at Cloudflare’s UK data centre. Cloudflare, Inc. is based in the United States and may access the data from there. | Transfer safeguardStandard Contractual Clauses with the UK Addendum, under Cloudflare’s published data processing agreement. |
| Private Email (Namecheap) | PurposeSending service emails (verification, receipts, notices) | RegionUS | Transfer safeguardUK IDTA |
| Daily (Daily.co) | PurposeRunning live video viewings. When you join a viewing, Daily carries the live picture and sound between you and the other party, along with anything you choose to share on screen, anything typed into the chat during the call, the display name you enter before joining, and your IP address and basic device information. VEYLO X never joins the call. Recording is switched off for every room and for every person joining, and the room setting is checked again before anyone is issued a pass to join. Daily has confirmed to us in writing that a room setting overrides the settings on our account, so recording cannot be turned back on by a setting elsewhere in our Daily account. Because we do not record the call, there is no picture or sound from the call for Daily to keep. Daily does keep technical records about the call itself, such as when it ran and how well the connection performed. Its published policy is not consistent about how long: the same document says data is stored indefinitely, and also says usage data is kept for one year and performance data is deleted after one month. Daily has not told us which of those applies to the records it keeps about a video call, so we are asking, and we will update this notice once we know. We do not receive or keep any picture, sound, screen share or chat from the call. We keep only a record that the viewing took place, which people took part, and when the room expired. | RegionWe set every viewing room to run on Daily servers in London. That is not the same as saying nothing leaves the United Kingdom, and we are not telling you that it is. Daily is a United States company and uses other United States companies to run its service. Two of those provide relay servers. When the two devices cannot reach each other directly, the picture and sound are carried through one of those relay servers instead, so part of a call can travel through the United States. Our contract is with Daily, Co., of San Francisco, California. We have not yet confirmed where Daily holds its own technical records about the call. We are establishing that with the provider and will update this notice as soon as we have. | Transfer safeguardStandard Contractual Clauses with the UK Addendum, under our signed data processing agreement with Daily, Co. |
| Mapbox | PurposeMap tiles for property listings, and the walking-distance overlay that shows what is within a few minutes’ walk (location data, which can be personal data when linked to your session) | RegionUK / US | Transfer safeguardUK IDTA |
| PostHog | PurposeAnonymous product analytics. We use it to see which steps people reach and where problems happen, so we can fix bugs and improve the service. Events are anonymous and are never linked to your name or email. | RegionEU (European Union servers) | Transfer safeguardStandard Contractual Clauses with the UK Addendum, where any provider support takes place outside the UK or EU |
| Stripe (Stripe Payments Europe, Limited and, for applicable UK regulated payment services, Stripe Payments UK Ltd) | PurposeTaking payment for plans and product fees, keeping the card you save when you buy a monthly or annual plan, and charging it for renewals until you switch off auto-renewal. We give Stripe your email address and our own reference for your account. We never receive or store your full card number or security code; Stripe holds them. The saved-card details we keep are Stripe's customer and card references, the card brand, last four digits and expiry date. Separate payment records are described elsewhere in this notice. | RegionUnited Kingdom and European Economic Area, with transfers to Stripe, LLC in the United States and to Stripe affiliates and sub-processors in other jurisdictions. Under the Stripe Data Processing Agreement, Stripe may transfer personal data on a global basis as necessary to provide its services. | Transfer safeguardEU-US Data Privacy Framework; the European Commission's standard contractual clauses; and the United Kingdom International Data Transfer Addendum, under the Stripe Data Processing Agreement. |
| Credas Technologies Ltd | PurposeIdentity verification, including document, address, liveness and biometric face matching checks; sanctions and PEP screening; proof of property ownership; and company verification (KYB). Credas acts on our instructions and VEYLO X is the controller. We receive results and some reports, as explained under Reports our providers send us. We never give the sanctions and PEP report or PEP status to the landlord. | RegionUnited Kingdom | Transfer safeguardNo restricted transfer |
Our database and hosting are in the United Kingdom (London). Files you upload are stored in the United Kingdom. Some providers may also need to access data from outside the United Kingdom for support, monitoring, or through their own sub-processors. Where that happens we rely on the transfer safeguards recorded against each provider in the table above, and on the safeguards described under International transfers below.
These organisations decide for themselves how they use your data and are responsible for it in their own right. What is listed here is their own use of your data, not work they carry out for us as our processor. Where we share your data for a credit or referencing check, we ask your permission first, and you should also read their own privacy notice. Those that carry out credit, referencing or identity checks run them under their own regulatory permissions.
Independent organisations we share your data with, or introduce you to
| Organisation | Purpose | Role |
|---|---|---|
| Let Alliance (a trading name of Barbon Insurance Group Limited, FCA 308724) | PurposeFull tenant reference and affordability assessment, including income and affordability checks, identity authentication and fraud screening, and Open Banking where requested as part of the Let Alliance reference. You authorise Let Alliance to carry out the check under its own privacy notice and permissions. This may involve credit reference agencies. It may include a quotation (soft) credit search, which can leave a soft-search record on your credit file but does not affect your credit score. Let Alliance returns the referencing result and a reference report, which we keep as explained under Reports our providers send us. | RoleIndependent controller |
| Fena (Fena Labs Ltd) | PurposeOpen Banking payment initiation through Fena, the FCA-authorised Payment Initiation Service Provider, for rent and deposit payments. You authorise each payment in your own bank app. VEYLO X does not receive, hold or transfer your money. | RoleIndependent controller |
| Stripe (Stripe Payments Europe, Limited and, for applicable UK regulated payment services, Stripe Payments UK Ltd) | PurposeStripe also processes payment information for purposes it determines itself, including fraud prevention, security, legal compliance and operating and improving its services, as explained in its privacy policy. This is separate from the payment processing Stripe carries out for us, listed above. | RoleIndependent controller |
| TDS (Tenancy Deposit Scheme) | PurposeStatutory deposit protection. When a landlord registers a deposit through us, we send the scheme the tenancy and deposit details, the legal name of each named tenant, and an email address or a telephone number for each named tenant, and both for the tenant who applied where the tenancy record holds both; we never hold the deposit money itself. | RoleIndependent controller |
| Tuxa (Marks Out Of Tenancy Ltd) | PurposeTelling us whether a property needs a licence from its council. We send the property's address and postcode. We do this in our legitimate interests under Article 6(1)(f) of the UK GDPR, in helping a landlord see what a property needs; you can object, and Your Rights below says how. We hold an account with Tuxa and pay for each lookup. | RoleIndependent controller |
| PolicyBee, Hiscox, ARAG | PurposeInsurance and legal-advice helpline, engaged only when a claim is notified | RoleIndependent controller. This row says "controller to controller" elsewhere in our records; the two mean the same thing, that they decide for themselves what they do with your data rather than acting on our instructions. |
| Cloudflare, Inc. (Turnstile) | PurposeImproving Cloudflare’s own systems for telling people apart from automated traffic. Cloudflare uses what it learns from the checks described above across the many websites it protects, so this is its own use of that information rather than something we ask it to do. It is the same check you have already passed, not an extra one, and it involves no further information about you beyond what that check already sees. Cloudflare is responsible for this use in its own right, and you should read Cloudflare’s own privacy notice for it. | RoleIndependent controller |
| Awin Ltd | PurposeAffiliate network. If you agree on the confirm screen when you open a paid partner ad on our Services page, Awin records the referral and reports qualifying sales, bookings or enquiries, so that VEYLO X may be paid a commission. See Affiliate referrals and tracking below. | RoleJoint controller with VEYLO X for collecting and transmitting information through Awin tracking when you follow a tracked affiliate link from our Services page. Controller in its own right for its further processing. |
| Advertisers shown as paid partner ads on our Services page | PurposeIf you continue to an advertiser, you visit its website and it collects information under its own privacy notice, including a referral reference from Awin. The confirm screen names the advertiser. VEYLO X does not send advertisers your personal data. | RoleIndependent controller |
VEYLO X commissions and administers checks carried out by Credas as our processor and receives referencing checks from Let Alliance as an independent controller. Our colleagues may record an internal administrative outcome and apply platform access rules. For sanctions screening, that outcome records the conclusion Credas reported or an external solicitor reached; our colleagues do not decide whether a possible match is you. VEYLO X does not independently certify identity, ownership, eligibility or the accuracy of a provider's findings. If we record a landlord's own check as not passed, the landlord cannot invite a tenant to pay through VEYLO X. The landlord can ask us to review that outcome.
If you do not take the steps in a check invitation in time. When a landlord buys a check on you, we send you an invitation that tells you which steps to take. You have until 7 days after the landlord paid to complete those steps. The invitation states the exact deadline, including the time and time zone. The deadline runs from the landlord's payment, so you have fewer than 7 days after receiving the invitation. If you complete them in time, the invitation does not lapse while provider processing or other people's replies remain outstanding. Otherwise, including where our or the provider's delay stopped you, the invitation lapses. We ask the provider to close it, tell the landlord that it lapsed and when, and refund the landlord. No fee is charged to anyone. Closure may not be immediate. If you complete your steps after the invitation lapses because it could not be closed in time, we tell the landlord and make the permitted result available under the sharing rules in this notice. If the result arrives before the landlord is refunded, the check counts as completed and is not refunded. If the landlord has already been refunded, no further charge is made. We may explain administrative delays or errors to the landlord where necessary, but we do not infer or report a personal reason for your not completing the steps. A lapse is not a check result.
The same payment-based deadline, closure process and late-result and refund rules apply when you buy a check on yourself as a landlord. Our record of it is described in the row for our record of a check outcome.
A referral partner is an organisation we can introduce you to with our own link, for a service you may want and are never required to take. Nothing on the Platform makes your application depend on it. The paid partner ads on our Services page are not this: those links go through our affiliate network, which receives your IP address and technical information about your device, and they are described under Affiliate referrals and tracking below. You apply to the partner directly, under their own terms and their own privacy notice. We do not send them your personal data: not your application, not your documents, not your contact details. The link carries a code identifying VEYLO X, not you. A partner may pay us a referral fee if you take up their service. The partner charges you for the service and takes your payment: you pay the partner directly, never VEYLO X.
Referral partners
This describes the referral partners we introduce you to with our own links, whether or not they are named here. It does not describe the paid partner ads on our Services page, which go through our affiliate network and are described under Affiliate referrals and tracking below. The partners we work with change from time to time, and any partner named below is given to show how the arrangement works rather than as a complete list. Nothing about how we handle your personal data changes when a partner is added or removed. The partners we work with at present include RentGuarantor, an optional rent guarantor service, and My Landlord Certificate, which supplies property certificates to a landlord.
What we record. Where you open a referral partner from the Platform, we record that the link was opened, which partner and which service it related to, and, where it related to one of your records, which record, and when. We make this record only where the partner's link is set up for it, and where it is not, no such record exists. That record holds your account identifier and the references to your own records described above. It does not hold your name, your email address, your contact details, your documents or the address of a property, and we do not send any of those to the partner.
What a partner tells us. A partner may tell us whether you have taken up or cancelled their service, and a member of our staff records what they tell us. That information therefore reaches us from the partner rather than from you, and Article 14 of the UK GDPR is the reason it is written out here. Where it concerns an application you have made to a landlord, we record it and show it to that landlord, so that the landlord knows the position on your application. A partner tells us nothing else about you. We do not receive your application to them, their assessment of it, or any information about your finances.
Why we process it, and on what basis. We process these records to receive and check the referral fee a partner pays us, and to keep the accounting records the law requires us to keep. We do this in our legitimate interests, under Article 6(1)(f) of the UK GDPR, in being paid correctly and in meeting our own record-keeping obligations. Where we show a partner's status to the landlord you applied to, we do that in order to take the steps you have asked us to take on your application.
How long we keep it. We delete the record that you opened a partner's link 24 months after it was opened. We delete what a partner tells us about your take-up of their service six years after it was last updated, and we keep the accounting records behind a fee for six years. Where a member of our staff typed a note about what a partner told us, or about where that information came from, we clear those notes twelve months after they were last written, and the rest of that record stays for the six years just given.
Objecting, and erasure. You can object to processing carried out in our legitimate interests, and you can ask us to erase these records; Your Rights below says how. Where you object to the record that you opened a partner's link, or ask us to erase it, we delete it, and we do not weigh that against our own interest in checking a fee. For what a partner told us about your take-up, and for the accounting records behind a fee, Your Rights below explains the limits that can apply.
This last group works the other way round from the three above. We are not sending your information to an organisation so that it can do something for you. We are looking something up about a property, in a public register or in open data, and recording the answer on that property's record.
To look something up we have to send the property's postcode, and for some of them its full address. We do not send your name, your email address, your account details, your documents or anything about your finances. What comes back is information about the property, or about the area around it, rather than about you. Where it is recorded against a property we can link to you, for example because you are the landlord who listed it, we treat it as your personal data and the rights set out below apply to it in the ordinary way.
Article 14 of the UK GDPR is about personal data a company obtains from somewhere other than the person it is about, and it is the reason this group is written out here. Every source in the table is a public register or a publicly accessible open data service. We use these lookups in our legitimate interests, under Article 6(1)(f) of the UK GDPR, in describing a property accurately and in helping a landlord see what a property needs. You can object; see Your Rights below. What comes back is kept on the property record, under the retention rules for that record in the table above. Nine of the eleven sources in the table are United Kingdom public bodies and are provided from the United Kingdom. The other two are private services: postcodes.io and OpenStreetMap. The map data lookup is made to overpass-api.de, which is operated outside the United Kingdom, so when that lookup runs the property's coordinates are transferred out of the United Kingdom. We have not established which country that service is provided from, and we have not established where postcodes.io is provided from either. We do not rely on adequacy regulations under Article 45A of the UK GDPR for any of these lookups, and there is no data-processing contract or other safeguard under Article 46 or Article 47 behind them, so there is no copy of a safeguard for us to give you. We would rather say that than name a protection we have not checked. What we send is the property's postcode, coordinates or address, and not your name or your contact details. These transfers are set out again under International transfers below. Where the table says your own device makes the lookup, the service you are looking up can see your device's network address.
Some of these your own device contacts directly, rather than our servers doing it for you. Where that happens the service receives your device's network address, because that is how a connection is made, and the table says which ones. We send them nothing else about you.
Public registers and open data we look up about a property
| Source | What we send | What comes back | Who makes the connection |
|---|---|---|---|
| postcodes.io | What we sendThe property's postcode | What comes backThe map coordinates for that postcode, and the local authority area it sits in | Who makes the connectionOur servers, and your own device |
| Energy certificate register | What we sendThe property's address and postcode | What comes backThe energy performance certificate held on the public register for that property, including its rating and when it was lodged | Who makes the connectionOur servers |
| Environment Agency flood map | What we sendThe property's coordinates | What comes backWhether the property sits in an area recorded as being at risk of flooding | Who makes the connectionOur servers |
| Environment Agency flood warnings | What we sendThe property's coordinates | What comes backThe flood warnings in force near the property at that moment | Who makes the connectionYour own device |
| Mining Remediation Authority | What we sendThe property's coordinates | What comes backWhether the property sits over recorded former coal workings | Who makes the connectionOur servers |
| Historic England | What we sendThe property's coordinates | What comes backWhether the building is listed | Who makes the connectionOur servers |
| Planning data | What we sendThe property's coordinates | What comes backWhether the property sits inside a conservation area | Who makes the connectionOur servers |
| Police open data | What we sendThe property's coordinates | What comes backThe recorded street level crime figures for the streets around it | Who makes the connectionOur servers |
| NHS organisation directory | What we sendThe property's coordinates | What comes backThe doctors' surgeries near the property | Who makes the connectionOur servers |
| OpenStreetMap | What we sendThe property's coordinates | What comes backThe shops and other amenities near the property | Who makes the connectionOur servers, and your own device |
| Transport for London | What we sendThe property's coordinates | What comes backThe stations and bus stops near the property | Who makes the connectionYour own device |
Companies House. If you let through a limited company, we look that company up on the public register at Companies House. We do it to confirm that the company exists and that you are recorded as one of its officers, because that is what lets us show your tenant a company name in place of a personal name. What comes back is the company's registered details together with the names and roles of its officers, which can include people other than you. This is personal data we have obtained from a public register rather than from you, and Article 14 of the UK GDPR is why it is set out here. We do it to perform our agreement with you, and in our legitimate interests in recording accurately who a landlord is. What comes back is kept on the account and property record, under the retention rules in the table above.
HM Land Registry. If a landlord sends us an ownership record for an ownership check, we may obtain a copy of the same record from the registry that keeps it, which for a property in England is HM Land Registry's public register. We give the registry the reference it needs to find the record, such as the title number, and nothing else about the landlord. What comes back can name the registered owners and other people. This is personal data we have obtained from a public register rather than from the person it is about, and Article 14 of the UK GDPR is why it is set out here. What we use it for, our lawful basis and how long we keep it are set out under Documents you send us for an ownership check, above.
E-signature of tenancy documents is handled on VEYLO X's own infrastructure, so it is not a third party.
We checked the Stripe, Credas and Let Alliance entries on 17 October 2026, the Google (Gemini API) entry on 20 October 2026, and the Awin entry on 13 November 2026. The other provider entries were last checked on 4 September 2026. A new organisation can be in use before it appears here, and we would rather you knew that was possible than be told it never is. If you want to know whether a particular organisation handles your data, ask us at privacy@veylox.uk and we will tell you.
International transfers
We intend to transfer personal data to countries outside the United Kingdom. Where we do, we make sure the transfer is protected in one of the ways the law allows.
Our database and hosting are in the United Kingdom (London). Personal data is transferred outside the United Kingdom in the following circumstances.
Files you upload. Documents, certificates and photographs you upload to the Platform are stored in the United Kingdom by our infrastructure provider, Google. Copies of files uploaded before 18 July 2026 that we deleted from our former United States storage on 17 October 2026 can still be recovered by our storage provider until approximately 24 October 2026. Parts of Google's group may access that information from outside the United Kingdom, for example to provide technical support; that access is covered by the safeguard recorded against Google in the complete list of service providers above.
Signing in to your account. When you create an account, sign in, or confirm who you are again immediately before you sign a document electronically, that sign-in data is processed in the United States by our authentication provider, Google. That transfer is covered by the Standard Contractual Clauses with the UK Addendum, plus Google LLC's EU-US Data Privacy Framework (UK Extension).
Security checks when you create an account. Our security check provider, Cloudflare, normally handles your connection at its UK data centre, but Cloudflare, Inc. is based in the United States and may access the information from there. That transfer is covered by the Standard Contractual Clauses with the UK Addendum, under Cloudflare's data processing addendum.
Live video viewings. When you take part in a live video viewing, the picture and sound travel from your device to our video provider, Daily, and usually straight between the two devices on the call. We set every viewing room to run on Daily servers in London. That is not the same as saying nothing leaves the United Kingdom, and we are not telling you that it is. Daily is a United States company and uses other United States companies to run its service. Two of those provide relay servers. When the two devices cannot reach each other directly, the picture and sound are carried through one of those relay servers instead, so part of a call can travel through the United States. Our contract is with Daily, Co., of San Francisco, California. That transfer is covered by the Standard Contractual Clauses with the UK Addendum, under our signed data processing agreement with them. We have not yet confirmed where Daily holds its own technical records about the call. We are establishing that with the provider and will update this notice as soon as we have. We do not receive or keep any picture, sound or chat from the call.
Looking a property up in a public register or in open data. When we look a property up in one of the sources listed under Who handles your data above, we send the property's postcode, coordinates or address. The map data lookup is made to overpass-api.de, which is operated outside the United Kingdom, so those coordinates leave the United Kingdom. We have not established which country that service is provided from, and we have not established where postcodes.io is provided from either. We do not rely on adequacy regulations under Article 45A of the UK GDPR for these lookups, and there is no safeguard under Article 46 or Article 47 behind them, so there is no copy of a safeguard for us to provide. We do not send your name or your contact details with a lookup. Where your own device makes the lookup rather than our servers, the service can see your device's network address.
Transfers to the European Economic Area. Some of our providers process personal data on servers in the European Economic Area. The United Kingdom government has decided that the European Economic Area provides an adequate level of protection for personal data, so no further safeguard is required for those transfers.
Transfers to the United States and elsewhere. Some of our providers, and some of their own sub-processors, process personal data in the United States or in other countries. The United Kingdom has not made an adequacy decision covering those transfers generally. We therefore rely on the safeguards permitted by Article 46 of the UK GDPR. Depending on the provider, the safeguard is one or more of the following:
- the United Kingdom International Data Transfer Agreement;
- the European Commission's standard contractual clauses, together with the United Kingdom International Data Transfer Addendum;
- the provider's certification under the EU-US Data Privacy Framework, UK Extension.
The safeguard that applies to each provider is recorded against that provider in the complete list of service providers above.
You can ask us for a copy of the safeguard that applies to any transfer of your personal data. Contact us at privacy@veylox.uk and we will provide it, or tell you where it is published, within one month. Where a document contains commercially confidential terms, we will provide a copy with those terms removed.
Data Retention
We retain personal data only for as long as necessary to operate the service, meet legal obligations, and protect ourselves and our users from regulatory or contractual claims. The table below sets out our standard retention periods. Where a record is legally required for longer (e.g. tax, court evidence), the longer period applies.
| Data type | Retention | Why |
|---|---|---|
| Account record (name, email) | Account life + 12 months | Service operation, support follow-up |
| Card on file for renewals (Stripe's references for your customer account and card, card brand, last four digits, expiry month and year, whether auto-renewal is switched off) | We normally request removal of a replaced card seven days after replacement, or seven days after our process first finds it if no replacement record exists. When no plan remains renewable, we remove operational card details and request card removal about 30 days after the latest paid-period end or lapse; with no recurring-plan record, this runs from first detection. The customer reference and separately described cancellation, restriction and evidence records remain. Unresolved payments, unreadable records and legal holds can delay removal. You can ask for removal at any time. | Needed to charge renewals you have authorised and to show you which card they go on (Article 6(1)(b)) |
| Authority to charge a saved card (the authorisation wording you agreed, its version, when you gave it, and the card it covers) | While the authority is in force, and six years after the money for the last payment under it was taken. If no payment was ever taken under the authority, the record is deleted about 31 days after the authority ends, or when an erasure of your data completes if sooner. Where a date cannot be established, the record is held for review rather than given an assumed date. A card change that was started but not completed: about 7 days after it is resolved, once any unused card from it is removed. Unresolved payments, unreadable records and legal holds can delay deletion. | Our legitimate interest in showing what you authorised and establishing, exercising or defending claims about charges (Article 6(1)(f)). You may object. We will stop unless we demonstrate compelling overriding legitimate grounds or need the records for legal claims. |
| Payment and refund records (transaction references, dates, amounts, VAT and status; the plan, check or purchase concerned and its property, application, applicant slot and check-provider references; commissioning details; renewal reminders; payment failure and dispute reasons; cancellation dates, methods and any reason you give; refund calculations and decisions, including staff-recorded reasons; staff action records; your cooling-off choice) | Information necessary for company tax and accounting records is retained for six years from the end of the relevant company financial year, or longer where an applicable legal requirement applies. VAT records follow applicable VAT retention requirements. Other records of a plan or purchase, its cancellation or refund, the reminders we sent and your cooling-off choice are kept while it is active and for six years after it ends, the period in which a claim about it can normally be brought. Where a payment dispute arises, we keep only the records needed for the dispute and any related legal claim, for no longer than six years after the dispute is resolved, and remove them earlier when they are no longer needed. A reason you type when cancelling is to be kept for no more than 12 months after the cancellation. We have not yet started deleting these records when these periods end, so some may currently be kept for longer. We have not yet implemented a scheduled review or automatic deletion of these records. | Administering purchases, subscriptions, cancellations and refunds (Article 6(1)(b)); tax, accounting, VAT and statutory cancellation obligations (Article 6(1)(c)); establishing, exercising or defending legal claims after a plan or purchase ends and for disputes (Article 6(1)(f)) |
| Free offer links (your email address, the name we wrote to, the offer, who sent it, when the link expires and, if used, your account and property) | If you do not use the link, a daily deletion run removes your email address, the name we wrote to and other recipient-identifying details when the link expires, 30 days after it was issued. We keep limited information about the offer, its status, who issued it and the relevant dates. The remaining record is deleted 30 days after expiry, normally around 60 days after issue. If you use the link, we keep the record to prevent the offer being used again and to record which account accepted it. The daily run removes the original recipient email address and name, but the retained account information may still identify you. If we cannot establish the expiry date, the record is referred for manual review rather than deleted automatically. Where a retention hold applies, automatic deletion is suspended until an authorised colleague releases that hold. | Sending an offer you agreed to receive (Article 6(1)(a)); providing an offer you switched on (Article 6(1)(b)); applying the one-offer rule (Article 6(1)(f)) |
| The free offer your account took (the offer, the property, when it started and ends, reminders we sent) | We currently retain this record without an automatic deletion date. We will review whether it is still needed, including when an account closes. | Applying the one-offer rule (Article 6(1)(f)) |
| Account limit records (one record for each account for each of our limits, holding your account identifier, when we last accepted a request from you and that day's count) | We keep each account limit record for 30 days after the last request that the relevant limit accepted from your account. A refused request does not restart this period. These records support limits on opening free offer links, changing account email addresses, requesting a review by a colleague, accepting our terms and using two separate AI features. Our database provider automatically removes expired records using an expiry date stored with each record. Removal may take place shortly after that date rather than at the exact moment it is reached. | Protecting the service from misuse and keeping our limits working (Article 6(1)(f)). You can object, and the account limits section above tells you how. |
| Terms acceptance records (the version of our terms you accepted, the account that accepted them and when) | We keep these records while your account remains open and for six years after the account closes. No automatic deletion is in place for them yet, and nothing removes them on a schedule. Where a complaint, dispute, investigation or legal claim requires a record to be kept for longer, we keep it for as long as is reasonably necessary and review that need periodically. | UK GDPR Article 6(1)(f), legitimate interests: keeping reliable evidence of which terms applied to your account, answering disputes, and establishing, exercising or defending legal claims |
| Withdrawn payment authority (the card reference, the bank's reason code and when it was recorded) | While the card remains saved with Stripe for your account, and after the card is removed from Stripe only while restoring, replaying or recreating our records could make that authority usable again. Our daily process normally deletes the record 31 days after Stripe confirms the card has been removed. Deletion is delayed while removal cannot be verified, records cannot be read, a card change or another record could restore the card, a legal hold applies, or the stop still protects a renewal card. | Preventing a charge to a card whose authority has been withdrawn (Article 6(1)(f)) |
| Search preferences (where and what you are looking for, and any income or savings figures you chose to give) | Until you delete them; otherwise for as long as your account is open | They are only useful while you are looking for a home, so you hold them and you can erase them yourself at any time in More › AI Property Preferences. Deleting them does not close your account |
| Messages between you and your landlord or tenant, and anything attached to them (the Conversations screen) | Tenancy chat messages and attachments: kept for six years from the end of the tenancy, then permanently deleted. We use this as our standard retention period because it reflects the usual six-year limitation period for many tenancy-related civil claims, including simple contract claims under the Limitation Act 1980, section 5. We email both parties 30 days before deletion, and again 7 days before deletion, so either of you can download a copy first. Deletion is permanent and we do not keep a copy afterwards | The thread is the record of what the two of you agreed, and either of you can download it if there is a dispute. A download takes full copies of the messages, and of anything attached to them, out of VEYLO X. Once that file is saved we cannot recall it or delete it, including the copy the other person takes, which is why whoever downloads it is asked whether to include the photographs. Where both names are on file, the document names both of you, as landlord and as tenant, using the names recorded on this tenancy. Where either name is missing it names neither. The document is designed to be given to a deposit adjudicator, the Property Ombudsman or a court. Your contact details are not included. Once sent, a message cannot be deleted through the chat by either side. Authorised VEYLO X staff can read these messages for support, safety, security, compliance and dispute-record purposes |
| Compliance attestations & declarations | 7 years from creation | We keep every compliance attestation for seven years from the date it was created, whether or not it forms part of our tax records. Where it does, this meets HMRC's rule of six years from the end of the accounting period. Where it does not, we keep it for the same period under our legitimate interests, so that we can show what was confirmed, by whom and when, if a claim or complaint is raised. We intend to remove identifying details after seven years and retain an anonymised entry, but this is not yet automatic. Until the process is implemented, an identifiable entry may remain longer; we review erasure and objection requests individually. The record of a guarantor's signed deed is kept for twelve years after the tenancy ends, as set out in its own row. |
| Property certificates (EPC, EICR, gas safety record) | Lifetime of the certificate + 2 years. If a certificate was in force during one or more tenancies recorded on VEYLO X, we keep the tenancy copy until 6 years after the last recorded tenancy it covered has ended, if that is later. If a certificate was never in force during a recorded tenancy, only the certificate-period rule applies. | Statutory inspection records and evidence of compliance. A certificate that covered a tenancy forms part of that tenancy record because it may evidence what the landlord gave the tenant and what was in force during the tenancy. The landlord and the tenant for that tenancy can download the tenancy copy while that tenancy record is kept, including after the tenancy has ended. Removing a certificate from the property record does not delete a tenancy copy that is still within its retention period. |
| Tenancy records (parties, rent, deposit) | Tenancy end + 6 years | Limitation Act 1980: recoverable claim window |
| Named-tenant legal name (on a tenancy) | Tenancy end + 6 years | On the tenancy agreement party list and, where a deposit is protected, the statutory deposit-protection record (Limitation Act 1980; Housing Act 2004) |
| Deposit protection checks we stopped (our internal record of when we stopped checking with a deposit protection scheme whether a deposit had been registered or was being held, and why we stopped; it identifies the tenancy, the landlord, the property and its address, and the scheme's deposit account number. They do not contain names, but the property address and other identifiers may identify individuals.) | We normally keep records of deposit protection checks that we have stopped for six years, calculated from the applicable statutory deposit protection deadline. For deposits subject to the standard 30-day requirement under section 213 of the Housing Act 2004, this deadline is calculated from the date the deposit was received. Where a later deposit registration establishes a new applicable retention date, we use that later date. A daily deletion run automatically deletes records once their retention period has expired, unless a retention hold applies. If we cannot reliably calculate the relevant date, or cannot identify the tenancy associated with the record, we refer the record for manual review rather than deleting it automatically. Records subject to an applicable complaint, dispute, legal claim or data rights hold are retained until the hold is reviewed and released. | UK GDPR Article 6(1)(f), legitimate interests: maintaining proportionate evidence to establish, exercise or defend legal claims. The retention period is informed by the Housing Act 2004 and the Limitation Act 1980. If you ask us to erase these records, we consider your request individually and may refuse where a record is needed for a legal claim (Article 17(3)(e) of the UK GDPR); we will tell you our decision and why. You may object; we will stop unless we need the records for legal claims or have compelling legitimate grounds. |
| Electronic signature record (the Certificate of Completion, the times each party signed and confirmed who they are, the email address on each signer's account, and the IP address each signature came from) | Tenancy end + 6 years | Limitation Act 1980: the period during which a claim arising from the tenancy may be brought, and during which a party may need to show that the document was signed and by whom. It runs on the same clock as the tenancy records above, because the signing record is part of that tenancy's record. It is not the seven-years-from-creation period used for compliance attestations |
| References we seek about a tenant from a named referee (a previous landlord or employer): the referee's name, their reply, answers and comments | Tenancy end + 6 years; where no tenancy results, 6 years from the application | Limitation Act 1980: the period during which a claim arising from the tenancy or the application may be brought, and during which VEYLO X may need to evidence how it handled the application. This row covers replies VEYLO X seeks directly from a referee. The outcomes of checks run through our providers (identity, referencing and credit, right to rent, and Open Banking) are covered by the next row |
| VEYLO X record of a check outcome. This covers checks run through our providers on people applying for a tenancy and on guarantors (identity, right to rent, sanctions screening, tenant referencing and credit, affordability, and Open Banking) and checks a landlord has run about themselves or their property, or has paid for on another owner of that property (identity and proof of ownership). The record holds which provider, the type of check, the result or status, the date and a reference id. It can also hold whether one of our colleagues recorded the check as passed or not passed and, if not passed, a reason chosen from a fixed list. | For checks on people applying for a tenancy and on guarantors: our record of the outcome, 6 years from when it was first made; our colleague's assessment, 6 years from the colleague's most recent decision. Either is kept for longer while it is held, as explained in the next column. The status of each check shown on the application, and records of checks a landlord has run about themselves: no deletion period is yet in place. Records of checks a landlord has paid for on another owner of their property: no more than 6 years from the check, and the automatic deletion for these is still being built. | A limited record of the check outcome and our colleague's recorded assessment, kept in VEYLO X's legitimate interests under UK GDPR Article 6(1)(f), so that we can respond to a complaint or legal claim about how a check was handled and show that we handled applications and landlord accounts consistently and without discrimination (Equality Act 2010). The record itself is limited to the details listed in this row. For checks on people applying for a tenancy and on guarantors, our record of the outcome is deleted automatically six years after it was first made, and our colleague's assessment six years after the colleague's most recent decision. We keep both for longer while they are held, either because the outcome record itself is needed for a complaint, a request about your data, a dispute or legal claim, or a concern about fraud, discrimination or safeguarding, or because a report on the same application is held (see Reports our providers send us). The status of each check shown on the application, including the sanctions screening outcome, is kept with the application and is not yet deleted automatically. Records of checks a landlord has run about themselves are not yet deleted automatically. Records of checks a landlord has paid for on another owner of their property are kept for no more than six years after the check, and their automatic deletion is still being built. Separately, we keep copies of some reports our providers send us: see Reports our providers send us, below this table. If we record a landlord's own check as not passed, the landlord cannot invite a tenant to pay through VEYLO X. The landlord can ask us to review that outcome. Credas keeps the underlying check data for 12 months, then deletes it on our instructions. An invitation Credas sends expires 7 days after it is sent if it is not used. That expiry does not extend the deadline, measured from the landlord's payment, described under Who handles your data. Earlier deletion following withdrawal of biometric consent is explained under Biometric identity checks. Let Alliance keeps its underlying check data under its own privacy notice. Your landlord remains responsible in law for carrying out and keeping any Right to Rent check that is required. |
| Identity documents you send us for a manual check | 7 days from upload, then deleted | Needed only for the comparison (Article 6(1)(f)) |
| Documents a landlord sends us for an ownership check, and any copy we obtain from the registry to compare with them | Files the landlord sends: deleted automatically once 7 days have passed since upload, or sooner if we record that a file cannot be used. Any copy we obtain: we require downloaded copies to be deleted once the comparison is complete. HM Land Registry keeps copies bought through its search service available in our account for 90 days after purchase, then removes them from the service. We do not reopen them without first recording why. | Used only for the comparison (Article 6(1)(f)) |
| Record of a manual identity or ownership check (reference, date, file names, any notes, any notice you confirmed, the conclusion and who recorded it) | We currently retain the check record, including file names and any note, without an automatic deletion process. We aim to retain it for no more than six years, subject to lawful extensions, and are implementing deletion controls. | Showing how the check was decided (Article 6(1)(f)) |
| Referral partner: record that you opened the link | 24 months from when you opened the link | Checking the referral fee we are paid, and guarding against misuse of the referral link |
| Referral partner: guarantee status | 6 years from the last update | The limitation period for a claim arising from the guarantee you took out (Limitation Act 1980) |
| Referral fee accounting records | 6 years | Our own tax and accounting records, and the limitation period for a contractual claim (Limitation Act 1980) |
| Notifications & system messages | 24 months | Audit trail, dispute support |
| Analytics events (if consented) | 12 months | Aggregated product improvement |
| Affiliate tracking choices (a random identifier held on your device, whether you agreed or withdrew, which advertiser it was for, the wording shown and when) | 24 months from each entry | Demonstrating how your consent was obtained and withdrawn (UK GDPR Articles 6(1)(c) and 7(1)), and administering and evidencing our affiliate arrangement with Awin (Article 6(1)(f)). 24 months covers the 12 months a choice is remembered plus the longest Awin cookie (one year) set by a link followed under it |
| Support correspondence (messages to our support address that are not complaints) | 36 months | Quality, training, dispute support. A message that is, or later becomes, a complaint about our service or about how we have handled your personal information is a complaint record and the row below applies to it instead, from the day we close the complaint. A complaint usually reaches us by email, so the two look alike in your inbox; what decides which period applies is whether we treated it as a complaint, not which address you sent it to |
| Complaint records (a complaint you make to us about our service or about how we have handled your personal information, anything you send with it, our investigation, and our response) | 6 years from the day we close the complaint | This is a period we have chosen. Neither the law nor the Property Redress Scheme requires us to keep a complaint file for six years, and we are not telling you that they do. We keep it in our legitimate interests (UK GDPR Article 6(1)(f)) so that we can establish, exercise or defend a legal claim arising from the complaint while one can still be brought, which for a contract claim is six years (Limitation Act 1980, section 5), and so that we can produce the file if the Property Redress Scheme, a court or an enforcement authority asks us for it. If you ask us to erase a complaint file we may refuse for that reason, which is the exemption in Article 17(3)(e) of the UK GDPR, and we will tell you that is the ground we are relying on |
| Backup copies | 30 days rolling | Disaster recovery; auto-purged thereafter |
| Record of a network address (the address a request came from, the time, what was asked for and whether it worked; and, where we have refused an address, the decision, who made it, and why) | 6 months from the last time the record changed. Where an address was refused, the 6 months start when the refusal ended | So we can recognise a pattern of abuse, and so we can answer a complaint or a question from the regulator about a refusal we made. A refusal that is still running is not deleted, because deleting it would quietly let the address back in |
| Record of an account we refused (which account was refused, how many times, when the last refusal was, and which feature refused it) | 30 days after the most recent refusal included in that day’s record | So we can see short-term patterns showing whether our security checks are wrongly blocking genuine use, or one account is repeatedly hitting our abuse controls. Separately, we keep overall totals for each day, and those totals name no account |
| Record of a case opened after somebody complained about you (what was alleged, the reason we relied on, our view of the harm, where our own records bore it out, the fairness check, what was paused, which of our people decided and when, what we told you and when, and how it ended) | 12 months for what was alleged, our view of the harm, where our own records bore it out, and the fairness check. 6 years for the record of the decision. Both counted from the day the case ended, or from the day we opened the case where it never led to a decision. Where a dispute about the pause is still running, nothing is deleted until it is finished | So we can answer you if you challenge a pause, answer a complaint or a question from the regulator about a decision we made, and show that a decision to pause part of somebody's account was properly made and properly reviewed. 6 years is the period in which a claim can still be brought (Limitation Act 1980). 12 months is shorter for what was alleged because a pause lasts 28 days at the most, and holding an unproven allegation about a named person for 6 years to account for that is longer than can be justified |
Biometric identity checks
Credas checks that you are a live person and compares your face with your identity document photograph. This uses biometric data to identify you. VEYLO X is the controller and Credas acts on our instructions. Credas obtains each person’s explicit consent on our behalf before scanning. We rely on consent under UK GDPR Article 6(1)(a) and explicit consent under Article 9(2)(a). If you do not want a face scan, you can ask for an identity check without one, which Credas also carries out. You can withdraw consent at any time by contacting privacy@veylox.uk. We will stop biometric processing and instruct Credas to delete your biometric data. Withdrawal does not affect processing lawfully carried out before you withdrew consent. Check results and reports are kept separately as explained below.
Reports our providers send us
We keep copies of some reports our providers send us about a check on a person applying for a tenancy or on a guarantor. These are the Credas identity results report, the Credas address and mortality report, the Credas sanctions and PEP report, and the Let Alliance reference report and guarantor reference report we receive. Depending on the report, they can include your full name, date of birth, address, email address and mobile number, the results of identity and facial match checks, the results of electoral register, credit reference agency and deceased register matching, screening results, and a score based on your credit file. The Credas identity results report contains no photograph of you or image of your identity document. The Credas sanctions and PEP report can contain a photograph of you.
After a colleague has checked a report, we may make it available to the landlord for the application where it has been approved for release. The Credas sanctions and PEP report is the exception: we never give it to the landlord. Paying for a check does not by itself entitle anyone to a report. The receiving landlord is a separate controller for their use of the report. VEYLO X remains responsible for its own storage, use and disclosure of the report. Access to filed reports is restricted to authorised colleagues for defined purposes.
Sanctions screening. If the landlord asks for sanctions screening, Credas checks you on our behalf against sanctions lists and lists of politically exposed persons (people who hold or have held a prominent public position, and their close family and associates). We email each person being screened a sanctions screening notice when the landlord pays. We tell the landlord the sanctions outcome only: either that no match was found on the sanctions lists we screen against, with the date that was recorded, or that a possible match needs checking. We never tell the landlord whether you are a politically exposed person, and we do not share anything else from the report with them. We tell the landlord the sanctions outcome in our legitimate interests and the landlord's in knowing whether the screening the landlord asked for is clear (UK GDPR Article 6(1)(f)). Our colleagues do not decide whether a possible match is you. They record the conclusion Credas reports or, where needed, the conclusion of an external solicitor we instruct, and we may share the report with that solicitor for that purpose. If Credas reports a possible sanctions match, we will contact you so that you can send us information that may resolve it. We pass what you send to Credas or to that solicitor, and they weigh it, not our colleagues. If you think a result recorded about you is wrong, tell us at privacy@veylox.uk.
How we use and keep the Credas sanctions and PEP report. The report can contain a photograph of you and, where there is a possible match, information that reveals political opinions or that relates to alleged criminal offences. We use it for two separate purposes.
Resolving a possible match. Where Credas reports a possible sanctions match, we use the report, and share it with the external solicitor where needed, to resolve the match as described under Sanctions screening above. Our lawful basis is our legitimate interests and the landlord's in knowing whether the screening is clear (UK GDPR Article 6(1)(f)). Where a possible match requires information that reveals political opinions or concerns criminal offences, we will use that information only where a separate condition under the UK GDPR and Data Protection Act 2018 applies, and only to the extent necessary. We will not use Schedule 1 paragraph 10 unless its statutory tests and required safeguards are met.
Keeping it afterwards as our evidence. Credas deletes the check data it holds for us after 12 months. We separately keep our report as evidence of the screening and its outcome where necessary to establish, exercise or defend a legal claim, for the period explained below. Our lawful basis is our legitimate interests in doing so (UK GDPR Article 6(1)(f)). Where the report contains information that reveals political opinions or relates to alleged offences, we rely on Article 9(2)(f) of the UK GDPR and on paragraph 33 of Schedule 1 to the Data Protection Act 2018, both of which permit processing that is necessary to establish, exercise or defend legal claims. You have the right to object to us keeping it. If you do, we will stop unless we need it to establish, exercise or defend legal claims.
Reports about checks a landlord runs about themselves. We can also keep copies of the Credas identity report, proof of ownership report and company report about a check a landlord has run about themselves or their property. We do not keep these for landlords at present. When we do, they are kept and deleted in the same way as the reports above.
Downloading a copy of your own reports. If we keep a Credas identity report or proof of ownership report about a check you ran about yourself or your property as a landlord, you can download a watermarked copy under Checks on yourself on the Referencing page where that report is available for download. Company reports are not available through this download. Before each download, we check that you signed in or re-authenticated within the last five minutes. If we cannot confirm this, we ask you to authenticate again to help protect access to your report. Every page of the copy is marked "DATA SUBJECT COPY. NOT A CERTIFICATE. NOT RIGHT TO RENT EVIDENCE." together with your account email address (or phone number or account reference), the date and time the copy is prepared and a download reference, to identify it as your copy and discourage its misuse as a certificate or as Right to Rent evidence. Before preparing the copy, we record the download request, including your account reference, the report requested, the date and time and a download reference. This record may remain even if the download fails. We keep it for our legitimate interests in protecting personal data, investigating possible misuse and tracing requests for report copies (UK GDPR Article 6(1)(f)). We keep each download-request record for 12 months from the request and then delete it automatically, unless that record is needed for an ongoing security investigation or to establish, exercise or defend legal claims, in which case we keep it until it is no longer needed for that purpose. You can object to us keeping or using these records on grounds relating to your particular situation. We will stop unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed to establish, exercise or defend legal claims. We generate the watermarked copy when you request it and do not retain that generated copy on our servers. Downloading a copy does not change how long we keep the report.
How long we keep them. Each report becomes due for automatic deletion 12 months after we filed it and is deleted by a daily deletion run, unless a hold or the exception described below applies. A deleted file can be recovered from our storage provider for 7 days after deletion, and is then gone. A report whose filing date cannot be read is not deleted automatically; it is listed for one of our colleagues to deal with. If a report is needed for a complaint, a dispute, a legal claim that has been made or threatened, a court order, a request from a regulator, a request to preserve it, or a request you have made about your data, one of our colleagues places a hold on it, and we keep it until a colleague ends the hold. We do not yet set a date for reviewing each hold. When a hold ends, a report already more than 12 months old is deleted at the next daily run. While a report on an application is held, we also keep our record of the outcome of the checks on that application. Deleting a report removes the copy held in our systems. It does not reach a copy a landlord has already downloaded, which the landlord holds as a separate controller. You can ask us at privacy@veylox.uk what we hold about you and ask us to delete it.
Documents you upload to help complete a check. If you upload a document to VEYLO X to help complete a check, we store it temporarily. Files become due for deletion seven days after upload and are deleted by the next daily deletion run. Deleting the file does not delete the upload record. We currently retain the original file name and file size in that record.
We receive the reports and screening results described here from Credas and Let Alliance. Depending on the check, these providers may obtain information from identity and address verification sources, electoral registers, credit reference agencies, deceased-person records, sanctions lists and politically exposed person lists. We explain the recipients, purposes, lawful bases and retention periods in this notice.
For this table, the lifetime of a certificate means the period for which that certificate or report is treated by VEYLO X as current for the relevant property record, based on the certificate type, the inspection date and any stated next-inspection date.
Live video viewings. We keep a technical record of each live video viewing: who joined, when, and the room's settings. We delete that record automatically 90 days after the viewing. We do not record the call, so there is no picture or sound to delete.
Nine retention explanations set out in words. The nine explanations that follow are set out here in words, and not in the table above. They give retention periods, as the table does.
Handover pack record. This is the name you sign the handover letters with, the address in England or Wales at which notices may be served on you, its postcode, the date you take over, and the telephone number printed on the letter. We keep it for 6 years from the date you recorded as the day you take over. Where you did not get as far as recording that date, we keep it for 6 years from the day the record was last changed. The six-year period takes account of the ordinary limitation period for claims founded on simple contract under the Limitation Act 1980. It does not determine the deadline for every claim concerning a handover or service address. This is a period we have chosen and not one the law requires of us. The answer about where your tenant pays their rent is kept for the shorter period set out in the next paragraph.
Where a tenant pays their rent at the time their landlord takes over from an agent. This is the landlord's answer about their tenant. We keep it for 12 months from the most recent time the handover record containing the answer was saved. Saving that record again restarts this period, even if the answer is unchanged. It decides which rent paragraph the handover letter carries, and it has no further use once the letters have been produced and the landlord has had time to produce them again. We keep it in our legitimate interests (UK GDPR Article 6(1)(f)), and not because the law requires it.
Right to Rent share code and date of birth. If you give us a GOV.UK share code and your date of birth so that a landlord can check your right to rent, we delete them from your application when the landlord records that they have done the check. Our daily deletion run also deletes any share code and accompanying date of birth that remain on your application or your tenant profile once 90 days have passed since you gave them to us. If our records do not show when you gave them, the 90 days run from the day our daily deletion run first finds them. We keep a note that a code was given, which shows no more than its first three characters. We use them in our legitimate interests and the landlord's, so that the landlord can carry out the check the law requires of them (UK GDPR Article 6(1)(f)).
Contact details a landlord gives us for their tenant. If a landlord records their tenant's contact details, or invites their tenant, we keep those details encrypted. Once the tenancy has ended and 12 months have passed since the most recent contact details for the property were recorded, we destroy the key that unlocks them, so they can no longer be read. We treat a tenancy as ended when the landlord archives or removes the property, or records that the tenant moved out on or after the day those details were recorded and no other tenancy at the property is still open. In any case, we destroy the key once 6 years have passed since the most recent contact details for the property were recorded and, if the property has had a tenancy, since the last one ended. We hold them in our legitimate interests, and the landlord's, in running the tenancy record the landlord keeps with us and, after the tenancy, in being able to deal with a legal claim about it (UK GDPR Article 6(1)(f)).
An invitation to a co-owner, and checks on a co-owner. If an owner invites somebody to manage a property with them, we use the name and email address the owner gives for that person to create the invitation, which the owner sends them, and to check that the person who accepts it is the one invited. Where the owner says the person is named on the title, we also use the address and telephone number the owner gives, so that the person can review the details given about them. If the owner pays for an identity check or a proof of ownership check on that person, one of our colleagues reads the name, email address and telephone number the owner gave and uses them to ask Credas, which acts on our instructions, to carry out the check. For an identity check, Credas sends the person an invitation to take part. We start a check on the person only once they have joined and authorised that owner to handle the letting. A check already started when they withdraw can still be completed and recorded. The colleague is shown that the details came from the owner and not from the person, and each time a colleague reads them, our systems record who read them, which details were shown and why, before they are shown. The invitation lasts 14 days. If it is not accepted, our daily deletion run removes these details once 44 days have passed since the invitation was created. If it is accepted, we keep the details the owner gave for no more than six years after the invitation was created, and we are still building the automatic deletion for them. You can ask us to delete them sooner at privacy@veylox.uk. We hold them in our legitimate interests in letting owners manage a property together and, where the owner pays for checks, in having the identity and ownership of a property's owners checked and in preventing fraud (UK GDPR Article 6(1)(f)). The owner who invited the person can see whether that person has joined, whether their checks are complete, and whether they have authorised that owner to handle the letting of the property or withdrawn that authorisation, but never that person's documents or anything the checks contain. A check is shown as complete only once it has been passed, so a check that has failed is shown as not complete. While checks that the owner paid for are open, we may email the owner to remind them that the invitation is theirs to send or that the checks on the property are not complete. We do both in our legitimate interests, and the owner's, in the owner knowing how far the checks on the property have got, because the owner cannot invite anyone to pay a holding deposit on the property until they are complete, and in having checks that have been paid for finished before they close (UK GDPR Article 6(1)(f)). The person can object; see Your Rights below. Where the owner tells us that the person they are inviting is named on the title of the property, we write to the email address they give us for that person at the time we are given their details, to tell them what we hold, who gave it to us and what it is for. That message carries no invitation and no link, because the invitation itself is the owner's to send. If that message cannot be sent we try again the next time the owner uses the invitation, so a message that fails is not abandoned. Where the person is being recorded only as somebody helping with the property, we do not write to them at that point: the only details we keep for them are the email address and the name the owner typed, and we keep no postal address or telephone number.
When another owner authorises the lead owner, or withdraws. When another owner of a property authorises the lead owner to handle the letting, or withdraws that authorisation, we record their choice, the words they were shown and when they made it. We use this record to apply their choice on VEYLO X: while they have not authorised the lead owner, or after they withdraw, we start no new check on them and some steps in letting the property through VEYLO X are not available. Steps already under way may continue. We also keep the record as evidence of what was authorised and when. We share their choice, and any withdrawal, with the lead owner, and we tell the lead owner when it changes. We do this in our legitimate interests, and those of the owners, in letting a jointly owned property according to each owner's choice and in keeping evidence of it (UK GDPR Article 6(1)(f)). We keep the record of each choice, and its history, while that choice applies to the property. After it is withdrawn or stops applying, we aim to keep it for no more than six years, as evidence of what was authorised and when, unless we need it for longer to establish, exercise or defend a legal claim. There is no automatic deletion for this record yet, and we are building it.
An invitation to a joint applicant or a guarantor. If a person applying for a tenancy invites somebody to apply with them, or to act as their guarantor, we use the name and email address they give us for that person to create the invitation and to check that the person who accepts it is the one invited. Where the invitation is to act as a guarantor, we also use the relationship between the two of them, which the person applying chooses from a list. We keep the email address encrypted. The invitation lasts 7 days. The 7 days end the invitation link. They do not end our record of the invitation. Where an invitation is to act as a guarantor, we show the landlord the name entered by the applicant before the invited person accepts, and that a guarantor has been asked for and has not yet signed. The invited person has not confirmed that name, so it may be incorrect, and they may not have agreed to be named. Where an invitation is to apply jointly, we do not show the landlord the invited person's details unless the invitation is accepted. The landlord cannot open the underlying invitation record, but in the case of a guarantor invitation, they can see the name taken from it. Once an invitation is accepted, the invited person becomes one of the people named on the application, and the landlord can see them there. We hold these details in our legitimate interests in letting people apply for a tenancy together and in letting a person applying offer a guarantor (UK GDPR Article 6(1)(f)).
How long we keep an invitation of this kind. We have not set a period for keeping this record, and nothing deletes it automatically, whether or not the invitation was accepted. You can ask us to delete it at privacy@veylox.uk. We keep each record under the invitation's own reference, and the email address in it is encrypted, so we may need the invitation link, or the name and email address that were given, or the details of the person who sent the invitation, before we can find the record that concerns you. The invited person's name, and for a guarantor their relationship to the person applying, are also part of the confirmation the person applying signed when they sent the invitation, which we keep as set out for compliance attestations and declarations in the table above.
What the invited person hears from us. Where a person applying for a tenancy invites a joint applicant or a guarantor, we do not write to the invited person at the time of the invitation, and this notice is not a substitute for telling them. If the landlord then buys checks on the people named on the application, we send a notice about those checks to the email address given for the invited person, even if they have not accepted the invitation. Where we cannot tell which person a particular check covers, that notice says that it may include them.
Your right to object. The invited person can object to our holding and using these details, because we rely on our legitimate interests. Write to privacy@veylox.uk. If they object, we will stop unless we can show compelling legitimate grounds that override their interests, rights and freedoms, or we need the details to establish, exercise or defend legal claims.
Usage counters for video calls and AI features. To stop the video viewing and AI features being overused, we count how often each account uses them, per minute and per day. Each count holds your account identifier, the period it covers and, for rejoining a video viewing, which viewing it was. A daily deletion run deletes each count once it has expired, so we normally keep none for more than three days. We do this in our legitimate interests in protecting the service from misuse (UK GDPR Article 6(1)(f)).
Conversations with the assistant. If you use the assistant in your message inbox, we keep each question and its answer in your chat history, and a daily deletion run normally deletes each one by the time it is 30 days old. When the assistant needs Google to answer a question, we send it, and the information sent with it, to Google, which runs the assistant for us. Google keeps these and the answer for 55 days to detect abuse and for safety, security and legal reasons, and authorised Google staff may review them. Google does not use them to improve its products, or to train any AI models other than those it uses to enforce its policies. We use them to provide the assistant you have chosen to use (UK GDPR Article 6(1)(b)). Where what you type is about somebody else, we rely on our legitimate interests in providing the assistant (Article 6(1)(f)). If you use the assistant to make a request about your own information, we keep what you wrote as a record of that request, as set out in the next paragraph.
Requests about your own information. If you use the assistant to ask us to see, correct or delete your information, or to make another request about it, we keep what you wrote for 12 months after we have dealt with the request, and our record of how we dealt with it for 6 years, so that we can show how we handled it. If we have not recorded the day we dealt with it, we count both retention periods from three months after we received it. We record and deal with your request because the law requires us to (UK GDPR Article 6(1)(c)), and we keep these records afterwards in our legitimate interests in being able to show how we handled it (Article 6(1)(f)).
You may request deletion at any time (see Your Rights). Some of the periods in this table are required of us by law. Others are periods we have chosen, so that we can answer a claim while one can still be brought. Where we keep something after you have asked us to erase it, we keep only what the ground we are relying on actually needs, we limit what else we do with it, and we tell you the ground.
Cookies & similar technologies
We use a small number of cookies and similar technologies that are necessary to deliver the service you have asked for, and which do not require your consent. These keep you signed in, remember the cookie choice you make, remember your display theme once you have chosen one, and confirm that requests come from a genuine browser rather than an automated script. That last check is Firebase App Check, which uses Google reCAPTCHA Enterprise: it stores a value on your device and Google receives your IP address and technical information about your device and browser. We also keep a local copy of property listings on your device so that pages load faster.
Where you have opted in through the cookie banner, we also use anonymous analytics, which is processed on our behalf by PostHog on European Union servers. The analytics records which steps you reach and any errors, so we can improve the service. It is never linked to your name or email. We do not sell your data and we do not use session recording. We do not use advertising cookies or track you across other websites for marketing purposes, except Awin affiliate tracking when you agree to it on the confirm screen of a paid partner ad, explained under Affiliate referrals and tracking below. You can change your choices any time under More, then Cookie preferences.
The Cloudflare security check that protects our sign-up flow and certain secure areas of the service does not store anything on your device.
Affiliate referrals and tracking
VEYLO X participates in Awin's affiliate network. Advertisers may be shown as paid partner ads on our Services page. We decide which paid partner ads appear. Awin operates the tracking and reports commissions to us.
Your choice. Before a paid partner ad link opens, a confirm screen names the advertiser and explains Awin's tracking. If you continue, the link goes through Awin, and VEYLO X may be paid a commission if the advertiser confirms a qualifying sale, booking or enquiry. If you cancel, nothing opens and nothing is sent to Awin or the advertiser. We rely on your consent (UK GDPR Article 6(1)(a) and regulation 6 of the Privacy and Electronic Communications Regulations). We remember your choice for each advertiser on that device for up to 12 months. After that, if you withdraw your consent, or if we change what the confirm screen says, we ask you again the next time you open that advertiser's paid partner ad.
Who is responsible. VEYLO X and Awin act as joint controllers for the collection and transmission of personal data through Awin tracking when you follow a tracked affiliate link from our Services page. Each party's responsibilities for this processing are described below. Awin also carries out further processing for purposes it determines, as explained in its privacy policy. Advertisers process information they receive for their own purposes, under their own privacy notices. VEYLO X is responsible for asking for your consent, telling you about it and keeping a record of it. Awin is responsible for its tracking technology, for telling you about its own processing in its privacy policy, and for what it does with the information afterwards as a controller in its own right. You may exercise your data protection rights against either VEYLO X or Awin in relation to their joint processing. Under our arrangement, the organisation receiving your request first will normally coordinate the response, with assistance from the other organisation. This does not limit your rights against either controller.
What Awin and the advertiser receive. When you continue, your browser connects to Awin, which learns that the visit came from VEYLO X and which advertiser it is for, and receives your IP address and technical information about your device. Awin sets cookies on its own website, awin1.com: a programme cookie named "aw" followed by the advertiser's programme number, lasting for that advertiser's cookie period, which the confirm screen states, and one named "bId", lasting one year. Awin says the main technologies it uses for tracking are tracking domain cookies, journey tags and device fingerprinting, and that it may link a referral on one device to one completed on another. Awin then sends you to the advertiser with a referral reference. We do not send Awin or the advertiser your name, email address or account details.
Our record of your consent. When you first continue to an advertiser, or later withdraw, we record what you chose, which advertiser it was for, the wording you were shown and when, against a random identifier stored on your device. The record does not include your name, email address, account or IP address. We keep a limited record of your affiliate tracking choices so that we can demonstrate how consent was obtained and withdrawn, and manage our compliance with data protection requirements. We rely on Article 6(1)(c) where keeping the record is necessary to comply with our legal obligations, and Article 6(1)(f) where necessary for our legitimate interests in administering and evidencing our affiliate arrangements. We delete each entry 24 months after it is made.
Your right to object to this record. You may object to processing based on legitimate interests, including our keeping of this record. To object, email privacy@veylox.uk.
Awin's retention and transfers. Awin's privacy policy, as we read it on 11 November 2026, says that "In general, tracking data collected through the Awin technology is retained for up to three (3) years, after which it is deleted or anonymised", and that "In limited circumstances, Awin may retain certain tracking data in pseudonymised form for up to five (5) years" where this is necessary for its internal analysis. It also says that, for transfers to countries "which have not been deemed to have an adequate level of protection", Awin uses specific contracts containing the EU Commission's "standard contractual clauses". For the full position, including who Awin shares data with, see Awin's privacy policy.
Withdrawing. Go to More, then Cookie preferences, then Affiliate partner tracking, and withdraw your consent for any advertiser, or withdraw all. Withdrawing stops VEYLO X using your existing consent for future tracked links: the next time you open that advertiser's paid partner ad, the confirm screen asks you again. It does not automatically remove cookies already placed by Awin or advertisers, or undo processing already carried out. You can delete cookies in your browser settings, or ask Awin.
You can contact VEYLO X at privacy@veylox.uk and Awin at global-privacy@awin.com about the processing for which each is responsible. Awin's privacy policy is at https://www.awin.com/gb/privacy.
Artificial intelligence and automated processing
We use an artificial intelligence service provided by Google for the purposes set out below.
The assistant. Where you use the assistant in your message inbox, what you type is sent to Google so that a reply can be generated. Do not send the assistant anything you would not want processed in this way. The assistant provides general information about using the Platform. It does not give legal advice, it does not make any decision about you, your application or your tenancy, and nothing it says binds VEYLO X or your landlord.
Reading documents. Where you upload a compliance certificate or a similar property document, the document is sent to Google so that the dates, reference numbers and other details can be read out of it and filled in for you. You can always enter those details yourself instead, and you can correct anything that is read incorrectly. We do not treat what is read as verified, and it is recorded as your entry, not as a check we have carried out.
Writing a listing description. Where you ask us to draft a description for a property you are listing, the details you entered in the listing steps, including the address, are sent to Google so that a draft can be written for you. The draft is yours to edit or replace, and nothing goes on the listing until you publish it. You can always write the description yourself instead.
Checking listing wording. Where a listing description is being written, the text is sent to Google so that wording which conflicts with letting rules can be pointed out before the listing is published. What comes back is a prompt to the person writing the listing. It is not a decision about anyone, we do not treat it as a check we have carried out, and the landlord remains responsible for what they publish.
The repair assistant. Where a landlord uses the repair assistant, what they type about the repair is sent to Google so that it can suggest how time-sensitive the issue appears and draft a message to their own contractor. If the landlord types a name or an address, that is sent too. The repair record is made from the landlord's own answers, which they check before it is saved, and the message is only shown to them to copy. Nothing the assistant writes is saved to the repair record.
Google processes this content as our service provider under a written contract. Google does not use your content to improve its products, or to train any AI models other than those it uses to enforce its policies.
None of this processing produces a decision that has a legal effect on you, or that similarly significantly affects you, within the meaning of Articles 22A to 22D of the UK GDPR. If you would rather not use the assistant, do not use it; nothing on the Platform depends on it. If you would rather not have a document read automatically, enter the details yourself. If you would rather write your listing description yourself, do not ask us to draft one. If you would rather not use the repair assistant, record the repair yourself. The check on listing wording is not optional, because it runs on the description whenever one is being written.
Security
We take appropriate technical and organisational measures to protect personal data against unauthorised access, loss, alteration and disclosure. Our platform's measures include the following.
Encryption. Personal data is encrypted while it is travelling between your device and the Platform, and while it is stored, by our infrastructure provider. In addition, we apply our own encryption to certain contact details before they are stored, so that they cannot be read from the underlying database.
Access control. Access to personal data is restricted by rule, at the level of each individual record. Our default position is that access is denied unless a rule expressly permits it, and we test those rules automatically. Certain sensitive operations additionally require the request to be verified as coming from our own application.
Audit records. Where a landlord, an agent or a member of our staff views a tenant's personal information through the Platform, we aim to record that access. Where a member of our staff looks up your contact details, our systems record who looked and why before the details are shown to them. On some screens the colleague must write the reason. On screens that are used for only one purpose, such as starting a check, our systems record that purpose as the reason, and the colleague does not have to write one. You can ask us for a copy of the record of who has accessed your information; see Your Rights below.
Two-factor authentication. You can turn on two-factor authentication for your account using an authenticator app. We do not currently require it.
Deletion. Where, at your request, we delete data we have encrypted ourselves, we also delete its key. Backup copies, including of the key, are removed when those backups expire, as set out under Data Retention.
Personal data breaches. If a personal data breach occurs, we will assess it. Where the law requires it, we will report it to the Information Commission within 72 hours of becoming aware of it, and where a breach is likely to result in a high risk to your rights and freedoms we will tell you without undue delay.
No system can be made completely secure, and we do not represent that ours is.
Insurance Alignment (Data Protection Context)
VEYLO X maintains cyber and data protection insurance.
This insurance:
- supports incident response
- does not guarantee prevention of breaches
- does not extend to user-controlled data risks
Users remain responsible for secure handling of their own data.
Data protection contact
We have a single point of contact for privacy queries and for requests about your rights. Contact us at:
Data protection contact
privacy@veylox.uk
VEYLO X Limited, 66 Paul Street, London, EC2A 4NA
We aim to acknowledge data protection enquiries, rights requests and complaints sent to this address within 3 working days. Where you are exercising a right over your own data, we will respond substantively within the statutory period of one month, which may be extended by up to two further months where the request is complex or where we have received a number of requests from you. If we extend, we will tell you within one month and explain why.
VEYLO X has not designated a Data Protection Officer under Article 37 of the UK GDPR. We have assessed that we are not required to designate one. The contact above handles the same enquiries.
Your Rights
Under UK GDPR you have the following rights in respect of your personal data:
- Access: a copy of the personal data we hold about you (subject access request).
- Rectification: correction of inaccurate or incomplete data. You can usually correct your details yourself in your profile. Some information that sits on a formal record cannot be edited in the app once it is fixed there, for example your legal name once your tenancy is signed or your deposit is registered. You can still ask us to correct it, and we will action a valid request within one month, whether or not anyone else has acted. Where we have already shared the corrected information with an organisation such as the deposit protection scheme, we will tell them, unless that proves impossible or involves disproportionate effort, so their record can be updated too, and you can ask us who we have shared your name with.
- Erasure: deletion of your data. We may refuse to erase a record where one of the exemptions in Article 17(3) of the UK GDPR applies. Two of them come up here. The first is where we have to keep something to comply with a legal obligation, for example the accounting records HMRC requires us to keep. The second is where we need the record to establish, exercise or defend a legal claim, and that is the ground for the records we keep for the period in which a claim can still be brought, including your tenancy records, our record of a check outcome, our record of a complaint, and our record of a case opened after somebody complained about you. Those are periods we have chosen, not obligations imposed on us. Where the ground covers only part of a record we erase the rest, and we tell you which ground we have relied on.
- Restriction: you can ask us to limit how we use your information, for example while we check something you say is wrong. Email privacy@veylox.uk. A member of our team handles each request. We will tell you what we have limited, and we will tell you before we lift the restriction.
- Portability: receipt of your data in a structured, machine-readable format.
- Objection: to processing carried out under legitimate interests or for direct marketing.
- Rights related to automated decision-making and profiling: under Articles 22A-22D of the UK GDPR (inserted by the Data (Use and Access) Act 2025). We use a deterministic, preference-based fit indicator that compares the search preferences you set against a landlord's declared listing fields, to show how well a property lines up with them. This does not make a decision about you, is not shared with landlords to screen you, and does not produce a legal or similarly significant effect on you. It runs under our legitimate interests; you can object at any time (see Objection above) or clear your saved preferences to switch it off.
- Withdraw consent: where processing is based on your consent, you may withdraw it at any time without affecting prior lawfulness.
To exercise any right, contact us at privacy@veylox.uk.
You have the right to complain to us if you consider that there has been a breach of data protection law in connection with your personal data. This right is in section 164A of the Data Protection Act 2018. To complain, email privacy@veylox.uk or write to us at the address at the end of this notice. You do not need to use any particular wording.
We aim to acknowledge your complaint within 3 working days. The law requires us to acknowledge it within 30 days, so our own promise is the shorter one. We aim to look into your complaint and tell you the outcome within 15 working days. The law requires us to respond without undue delay rather than by a fixed date, so this is our own promise too. If we need longer than 15 working days, we will tell you why and when to expect our answer.
If your complaint is about what a landlord or agent did with your information after they received it, they are a separate controller for that and may need to answer that part. We will answer for our own part.
You also have the right to lodge a complaint with the UK supervisory authority, the Information Commission (ICO), at ico.org.uk/make-a-complaint or on 0303 123 1113. You can contact the ICO at any time. You do not have to complain to us first, and complaining to us does not affect your right to go to the ICO.
Changes
This Notice may be updated from time to time.
We keep the earlier versions of this notice, with the dates each one was in force. If you want to read the version that applied to you on a particular date, ask us at info@veylox.uk and we will send it to you.
17 November 2026: privacy-v1.33-2026-11-17. Said for the first time how long we keep a copy of the email that gives applicants the dates of the lead owner's checks when holding deposits open on a property: six years after it was sent. Said the same to applicants, in the part of this notice written for them, together with the fact that we may send them that email. Said that we may email those dates to applicants, rather than that we always do. Corrected what we said about the email we may send an applicant once the deadline for agreement for a holding deposit has passed and we hold no record of a tenancy agreement being signed or of what happened to the deposit. The previous version, privacy-v1.32-2026-11-16, said that if that email gives the landlord's contact details, it gives the email address and telephone number on the landlord's account, and that we might continue after a landlord objected if we had compelling legitimate grounds or needed to for legal claims. As at 17 November 2026, we have not given either detail to any applicant in this way. Said that we may email the applicant the landlord's email address and no other contact details for them beyond the address of the property, only where our records show that the landlord received the deposit themselves, and that we tell the landlord before we first give it. Said that a landlord can object without giving a reason and in any way, and that once we have a landlord's objection and can identify their account we stop, with no exception for compelling grounds or legal claims. Described the repayment date as calculated from the deadline for agreement shown in our records, said that the actual deadline may be earlier or different and that in some cases the Tenant Fees Act 2019 allows the deposit to be kept, and said that we may send that email rather than that we always send it once. Said the legal basis for including the landlord's name in that email. Made the matching changes in the part of this notice written for applicants, and said there for the first time how long we keep a copy of that email. Said that a file a landlord sends for the ownership check may be deleted before seven days have passed where we record that it cannot be used. Said that the security measures we describe are those of our own platform, and that where we delete data we have encrypted ourselves we also delete its key, with backup copies removed when those backups expire. Removed the description of the feature for translating text on screen, and its mention among the purposes for which we use Google, because that feature stopped on 3 September 2026, before the platform opened on 21 October 2026. The entry for 15 November 2026, privacy-v1.31-2026-11-15, has moved behind the control marked Summary of changes, where every entry already behind it is still there and can be read by opening the control or by printing this page.
16 November 2026: privacy-v1.32-2026-11-16. Said for the first time that, while a property is publicly listed, people viewing the listing can see the dates on which the identity check of its lead owner and the property ownership name match for it were completed, which the listing already showed, and that when holding deposits open on the property we email those dates once to applicants whose applications for it are still open. Said for the first time that once the deadline for agreement for a holding deposit has passed and we hold no record of a tenancy agreement being signed or of what happened to the deposit, we email the applicant who paid it once with the landlord's name and the last day of the seven days that the Tenant Fees Act 2019 allows for repaying it where the Act requires it to be repaid. Said that where that email also gives the landlord's email address and telephone number, we give them only to that applicant, why and on what basis, that we tell the landlord, that the landlord can object, and how long we keep a copy of the email. Said for the first time that copies bought through HM Land Registry's search service remain available in our account for 90 days after purchase, then are removed, and that we record why before reopening them. Referred to Data Retention for other people's details, clarified the conditions for holding sensitive entries and the comparison purpose, and corrected the storage description and Article 14 reference. Named the UK supervisory authority as the Information Commission, which took over from the Information Commissioner on 30 September 2026. Its website, telephone number and our registration reference are unchanged. The entry for 14 November 2026, privacy-v1.30-2026-11-14, has moved behind the control marked Summary of changes, where every entry already behind it is still there and can be read by opening the control or by printing this page.
Summary of changes
15 November 2026: privacy-v1.31-2026-11-15. Said for the first time that where the ownership check for a property has not passed, we may ask the landlord for an official record of who owns it, such as an HM Land Registry title register, and that a colleague compares details on it with the details we hold and may compare it with a copy we obtain from the registry. Said what that comparison decides and what it does not, that we do not show the tenant the result, our lawful basis, and how long we keep the files, any copy we obtain and the record of the check. Said for the first time what happens to the details of other people named on such a record, including entries that relate to criminal proceedings or are special category data and the basis on which we hold them, that we tell another owner the landlord has named to us when they are named, and that for everyone else named on such a record this notice is how we tell them. Added HM Land Registry to the sources we obtain information from. Added a row to the retention table, and widened the row for the record of a manual check to cover ownership checks. Said for the first time that the owner who invited another owner can see whether that owner has authorised them to handle the letting or withdrawn, and is told when it changes; that we start a check on another owner only once they have joined and authorised the lead owner, and that a check already started can be completed after a withdrawal; what we record about that choice, why, on what basis and for how long; and, in a paragraph of its own, how to object. Until today this notice said that a check on another owner could start before they accepted the invitation, and that the owner who invited them could see only whether they had joined and whether their checks were complete. The entry for 13 November 2026, privacy-v1.29-2026-11-13, has moved behind the control marked Summary of changes, where every entry already behind it is still there and can be read by opening the control or by printing this page.
14 November 2026: privacy-v1.30-2026-11-14. Rewrote the section on referral partners so that it describes the arrangement itself rather than each partner: what we record when you open a partner's link, what we never record and never send, why we keep it and on what legal basis, how long we keep it, and what happens when you object or ask us to erase it. The same text now covers every referral partner we work with, so adding or removing one does not change this notice. We also removed the rate of the referral fee a partner pays us, while leaving the fee itself disclosed, together with the fact that a partner charges you and takes your payment and that you pay the partner directly, never VEYLO X. Said for the first time that where a member of our staff typed a note about what a partner told us, or about where that information came from, we clear those notes twelve months after they were last written, while the rest of that record stays for six years. Said for the first time, in plain view, that the paid partner ads on our Services page are not referral partners of this kind and are covered by their own section. Said what happens when you object to the record that you opened a partner's link, or ask us to erase it: we delete that record. We did not change what we collect, who we share it with, or what rights you have. The entry for 10 November 2026, privacy-v1.28-2026-11-10, has moved behind the control marked Summary of changes, where every entry already behind it is still there and can be read by opening the control or by printing this page.
13 November 2026: privacy-v1.29-2026-11-13. Said for the first time that your landlord receives contact details for you: an email address on a tenancy agreement sent through us, and an email address, where held, and a telephone number on the prescribed information, as required by the law. Said for the first time that when your landlord registers a deposit through us, we send the scheme your legal name and an email address or a telephone number for you, that for the tenant who applied we send both where the tenancy record holds both, and where these details come from. Said that we rely on our legitimate interests for the landlord disclosures and for sending one contact detail per named tenant to the deposit protection scheme, and explained how to object. This notice did not say either of these before. We were already giving these details to landlords, and sending them to the scheme for the tenant who applied for a tenancy, before it did. Corrected our explanation of the lawful basis for sending your legal name to the scheme: we rely on legitimate interests rather than performance of our agreement with you, and explained how to object. Corrected what we said about telling an organisation when we correct information we have shared with it: we tell it ourselves, unless that proves impossible or involves disproportionate effort, and no longer say that we or your landlord will. Said that we do not pass a later change of your contact details to the scheme unless you ask us to, and how to have details we sent corrected. Corrected the address for an unsolicited job application. It is careers@veylox.uk, the address our careers page gives. This notice previously gave career@veylox.uk, which is not that address. Said how long we keep a job application: 12 months from receipt, unless you ask us to delete it sooner, and that we may keep it for longer, or after you have asked us to delete it, only where a legal obligation or a legal claim requires it. The previous wording said only that we keep it for as long as reasonably necessary, which did not tell you the period. Our careers page already said 12 months, and the two pages did not agree. Corrected the address to write to about deleting an application on our careers page to privacy@veylox.uk, which is the address this notice gives. Said for the first time that if you have confirmed your own details as one of the owners of a property, and an owner sends a tenancy agreement for that property through VEYLO X, the full legal name you confirmed in your own account goes on the agreement, in the part that names the landlord, and we ask you to sign it, and that the tenants and the other owners can see your name on it. Said for the first time that where more than one owner signs a tenancy agreement, every party can see each owner's name, email address and IP address. That was already so and this notice did not say it. Corrected "the other party can see this" to "the other parties can see this" in the section on signing a document electronically, because a document can have more than two parties. Said for the first time what we show a landlord and the other tenants for a joint tenant who has not provided their legal name, including, for some earlier invitations, the name or email address the person who invited them gave us. Limited the statement about another tenant's email address and IP address to the Certificate of Completion and the signing record. Said why we show that name or email address, that the person who invited you typed it and you have not confirmed it, so it may be incorrect, and that you can object. Added a new section, Affiliate referrals and tracking, describing the paid partner ads on our Services page, the confirm screen we show before a tracked link opens, that we rely on your consent, that VEYLO X and Awin are joint controllers for the collection and transmission of personal data through Awin tracking when you follow one of those links, what Awin and the advertiser receive, the record we keep of what you chose and our deletion of each entry after 24 months, what Awin's own privacy policy says about its retention and transfers, and how to withdraw. Added Awin and the advertisers shown as paid partner ads to the list of independent organisations we share data with, added affiliate tracking choices to the retention table, and added affiliate tracking to the list of things we rely on consent for. Changed the sentence that said we do not use advertising cookies and do not track you across other websites for marketing purposes, because it is no longer true once a tracked link is live: it now states that exception and nothing wider. Said for the first time that where a deposit is protected, the prescribed information we produce for an owner to give to the tenant names every landlord, so it carries each owner's name, address, telephone number and email address, and that the correspondence address it gives for the service of notices is the one address the tenancy agreement gives for every landlord it names, or a statement that none is recorded. That was already so and this notice did not say it. Said for the first time that where the document an owner has served is held on the Platform, the tenant can open a copy of it in the app. Said for the first time that when an owner gives us another owner's details we write to that person at the time, to tell them that we hold them, who gave them to us and what they are for. Limited the statement that we do not write to an invited person at the time of the invitation to an invitation from a person applying for a tenancy, which is the only kind of invitation it was ever true of. This notice did not say so before. Corrected a sentence that said that, while you have told us the name we hold is wrong, we do not use it to draw up a new tenancy agreement. No such block exists, and what we do not do is use it to register a new deposit. This notice should not have promised the first. Narrowed a sentence that said we do not replace the name we hold with the name you say is yours. Recording what you tell us changes neither name, but we may later change the name we hold to the one you gave us. Corrected a sentence that said we give your landlord what you have told us about your name. Handling what you tell us does not give them the files you sent, or the name you gave us unless we change the name we hold to it. Said for the first time that if your landlord tries to register a new deposit through us before we answer, we refuse it and tell them that one of the tenants has said the name we hold for them is wrong. This notice did not say so before. Said for the first time how we answer you when you tell us in the app that the name we hold is wrong: a colleague either keeps the name we hold or proposes changing it to the name you gave, a proposed change takes effect only if a second colleague approves it, and that decides the name we use, not what your legal name is. This replaces the sentence that said we do not decide which name is right, which is no longer so. Said for the first time that if you tell us again before we have answered, we answer the newer message instead, within one month of it, and still tell you of any change the older one led to. Corrected the place in the app where you tell us that the name we hold is wrong, which is More, Account, The name we hold is wrong, and not Send us a document. Narrowed what we said we record when you tell us that in the app: we record any name you give us only where we can record it. Made clear that the 12 month limit covers what a colleague recorded off the identity report, and not what you tell us about your name. Clarified the six-year deletion rule for in-app name disputes, linked name changes, tagged email copies and account notes, including the applicable holds, outstanding actions and conditions preventing safe deletion. Distinguished pending account-erasure requests made through the app from data-rights requests made through the in-app assistant, which create a three-month hold from receipt. Clarified that the internal office email contains a case number rather than a name or account number, and that the back-office case-number lookup stops resolving the account after the dispute record is deleted. Explained that staff-step records retain internal reference IDs and that a separate deletion marker temporarily allows those records to be linked to the person, with removal scheduled after 30 days. Confirmed the separate rules for correction attestations and former-name history. This notice did not say how long we keep any of these before. Corrected the route for changing your cookie choices, and for withdrawing consent to affiliate tracking: it is More, then Cookie preferences. This app has no screen called Settings. Said for the first time that the owner who invited the person can see whether that person has joined and whether their checks are complete, which they are shown to be only once passed, though never that person's documents or anything the checks contain, and that while checks an owner paid for are open we may email that owner to remind them that the invitation is theirs to send or that the checks on the property are not complete. That visibility was already so and this notice did not say it. Removed the registered trade mark symbol from the opening sentence. The mark and its number are stated in the legal notice at the foot of this page, which is where they belong. Nothing about this notice's meaning changes. The entry for 6 November 2026, privacy-v1.27-2026-11-06, has moved behind the control marked Summary of changes, where every entry already behind it is still there and can be read by opening the control or by printing this page.
10 November 2026: privacy-v1.28-2026-11-10. Said for the first time that when an owner pays for an identity check or a proof of ownership check on another owner they have named, one of our colleagues reads the name, email address and telephone number the owner gave for that person and uses them to ask Credas to carry out the check, even if the person has not accepted the owner's invitation. Said for the first time how long we keep the details an owner gives for a co-owner once the invitation is accepted, and how long we keep our record of a check paid for on another owner: no more than six years in each case. Corrected a sentence that said our staff must write a reason before looking up your contact details. On screens used for only one purpose, the reason we record is that purpose and the colleague does not write one, and that was already so before this version. Our record of a check outcome now also covers checks a landlord pays for on another owner of their property. The entry for 3 November 2026, privacy-v1.26-2026-11-03, has moved behind the control marked Summary of changes, where every entry already behind it is still there and can be read by opening the control or by printing this page.
6 November 2026: privacy-v1.27-2026-11-06. Removed the sixteen oldest entries from this section, running from 11 August 2026 to the entry for 20 October 2026, privacy-v1.20-2026-10-20. The oldest entry still here is the other entry for 20 October 2026, privacy-v1.21-2026-10-20. We keep the earlier versions we hold, with the dates each one was in force; ask us at info@veylox.uk and we will send it to you. The entries that stay keep the wording they were published with: where one of them describes entries behind the control marked Summary of changes, the entries it describes are among the sixteen, and opening the control no longer shows them.
3 November 2026: privacy-v1.26-2026-11-03. Changed one word in a sentence that said the name you provide may be changed following the identity-report comparison and two-colleague approval process described below. That process is described above that sentence and not below it, so the sentence now says above, and nothing about the process itself has changed. Added one sentence to the end of the part that tells you to speak to your landlord if a locked name is spelt wrong or your legal name later changes, because that part did not say that the case added by the version published earlier today is different: where the name we hold is the name we recorded from an identity report, your landlord cannot make that correction and it is made through us instead. Not one word of that part has been altered, and this version changes nothing about how a correction to the name we hold is made. Corrected this section, where the entry for 3 November 2026, privacy-v1.25-2026-11-03, describes two of the things that version said using words this notice does not use. It says that nothing on the platform reads that record as your legal name, where this notice says that nothing on the platform uses that record as the name we hold for you. It says that a colleague compares the full legal name you gave us with the name printed on the report, where this notice says that an authorised colleague may compare the name you provided with the name shown on the report. Where that entry and the body of this notice differ, the body applies, and this version does not change either of those two sentences in the body. That entry also says which entries were in plain view when it was published, which was correct then and does not describe the arrangement now shown, because this entry is now in plain view above it. We have left the wording of that entry as it was published, and we have added a note after it recording this correction. Not one word of any existing entry in this section has been altered, no entry has been removed and nothing has been shortened. This version asks you for nothing new. It changes nothing about how we handle your personal data and takes nothing away from any right you have.
3 November 2026: privacy-v1.25-2026-11-03. Said for the first time that when a person applying for a tenancy invites somebody to apply with them or to act as their guarantor, we keep the name and email address they give us for that person, that we keep the email address encrypted, and that the 7 days end the invitation link and not our record of it. Said that the landlord cannot read that record, that where the invitation is to act as a guarantor we show the landlord the name given for that person, and that where it is to apply jointly we show the landlord nothing about the invited person unless they accept, and that the name we show the landlord is the one the person applying typed, which we do not ask the invited person to confirm first. Said that we have not set a period for keeping the record and that nothing deletes it automatically, whether or not the invitation was accepted, and what we may need before we can find the record that concerns you. Said that we do not write to the invited person at the time of the invitation, and that where the landlord buys checks we send a notice about them to the email address given for that person even if they have not accepted. Set out their right to object. Added to Tenant and Applicant Data that a person applying for a tenancy can give us another person's details in this way. Said for the first time that where your landlord has bought an identity check on you, a colleague compares the full legal name you gave us with the name printed on the report, and that the comparison is ours and is not a pass or a not pass on a check. Said that where the two names do not match the colleague types the name as it is printed on the report, that this is evidence of what the report said and that nothing on the platform reads that record as your legal name, that the same name becomes the name we hold only if two colleagues take the steps set out, that where the second colleague does not approve it we clear both names from the proposal but that proposals refused before this starts, under the route we have used since August 2026, still hold both names and nothing deletes them, that the change to the name we hold and the message telling you about it are written in the same step, that from the point we record it neither you nor your landlord can change it in the app, and that the route to change it is us and not your landlord. Said that a document you send us is deleted 7 days after you send it, that what the colleague recorded is kept with the report for no longer than 12 months from the day we filed it, that a hold on the report keeps it too, that the record of a decision about your name is a different record which that 12 month limit does not cover and which we keep with your tenancy record and dispose of with it six years after the tenancy ends, or keep until we hold an end date where we do not, and set out your right to object. Replaced two sentences about recording the name you provide, in the section about your legal name, because this version adds the check against an identity report: the first no longer says we do not check the name against a document, and both now say that the name we hold can be the name on that report instead of the name you gave us. Changed the count in the sentence that introduces the retention explanations set out in words from eight to nine, because this version adds one of them. This version asks you for nothing new. It explains how we may compare the name provided by a tenant with the name shown on an identity report already obtained for that tenant, and that the process may create additional records, including the comparison result and, where a change is proposed, records of the proposal and decision.
A correction to this entry. Two sentences above describe this version using words this notice does not use, and one sentence above describes which entries were in plain view when this entry was published. The entry for 3 November 2026, privacy-v1.26-2026-11-03, above, sets out what this notice says instead and what has changed since. We have left the wording of this entry as it was published, so what you read here is what we published on 3 November 2026. Where this entry and the body of this notice differ, the body applies: it says that nothing on the platform uses that record as the name we hold for you, and that an authorised colleague may compare the name you provided with the name shown on the report.
Which entry moved. One entry has moved behind the control marked Summary of changes: the entry for 31 October 2026, privacy-v1.23-2026-10-31. The entry for 31 October 2026, privacy-v1.24-2026-10-31, which remains in plain view, refers to that entry, and it is now behind the control and can be read by opening it. The entries in plain view are now this entry and the entry for 31 October 2026, privacy-v1.24-2026-10-31, so the control again holds every entry except the two most recent. Not one word of any existing entry has been altered, no entry has been removed and nothing has been shortened. This section is still one list with the most recent entry at the top, and where two entries share a date the one published later is above the one published earlier. The control still holds the oldest entries only, and every entry inside it was published before every entry outside it. Every entry behind the control can be read by opening it, and all of them print in full when you print this page. Every earlier version of this notice is unchanged, and the version we send you if you ask for a particular date is the version that was in force on that date.
31 October 2026: privacy-v1.24-2026-10-31. Moved fourteen entries in this section behind the control marked Summary of changes, so that it now holds every entry except the two most recent. Not one word of any existing entry has been altered, no entry has been removed, and these changes to the Changes section do not change how we handle your personal data or any right you have.
Which entries moved. The four oldest, for 4 September 2026, 29 August 2026, 20 August 2026 and 11 August 2026, were already behind the control. The other fourteen entries now behind it were in plain view until today, and they run from the entry for 31 October 2026, privacy-v1.22-2026-10-31, down to the entry for 4 September 2026 that begins "Stopped publishing earlier versions of this notice as pages on this site". Nothing has been removed and nothing has been shortened. Every entry behind the control can be read by opening it, and all of them print in full when you print this page.
This section is still one list with the most recent entry at the top, and where two entries share a date the one published later is above the one published earlier. The control still holds the oldest entries only, and every entry inside it was published before every entry outside it. The entry for 31 October 2026, privacy-v1.23-2026-10-31, says the control holds four entries, which it did when that entry was published. It does not describe the arrangement now shown, and we have left its wording as it was published. Every earlier version of this notice is unchanged, and the version we send you if you ask for a particular date is the version that was in force on that date.
31 October 2026: privacy-v1.23-2026-10-31. Reordered this section and changed which entries sit behind the control marked Summary of changes. Not one word of any existing entry has been altered, no entry has been removed, and these changes to the Changes section do not change how we handle your personal data or any right you have.
Until today this section held its entries in two different orders, which met at 4 September 2026. From 18 October 2026 the entries for 6 October 2026 and 26 September 2026 sat behind the control although they were more recent than entries left in plain view, so a reader who did not open the control saw the older change and not the newer one. The 18 October entry also directed readers to the 6 October entry below without saying that they needed to open the control to read it. Both entries are now in plain view. The entries for 4 September 2026, 9 September 2026 and 7 September 2026 that sat below the control are now above it.
From today this section is one list with the most recent entry at the top, and where two entries share a date the one published later is above the one published earlier. The control holds the oldest entries only, and every entry inside it was published before every entry outside it. It now holds the four entries for 4 September 2026, 29 August 2026, 20 August 2026 and 11 August 2026. The entry for 4 September 2026 that describes the control records the arrangement announced in that version. It does not describe the arrangement now shown, and we have left its wording as it was published. Every earlier version of this notice is unchanged, and the version we send you if you ask for a particular date is the version that was in force on that date.
31 October 2026: privacy-v1.22-2026-10-31. Updated our retention information to reflect automatic deletion of unused free offer link records, account limit records and discontinued deposit protection check records. Clarified the information retained when an offer link has been used, the 30-day expiry period for six account limit records, and the applicable six-year retention period for discontinued deposit protection checks. Explained the circumstances in which records require manual review or are preserved under a retention hold. Updated our early-access communications description, gave the date by which we delete the entries of people who joined the list before 21 October 2026 and did not go on to create an account, replaced the sentence describing what VEYLO X is, and stated for the first time how long we keep a record of the terms you accepted.
20 October 2026: privacy-v1.21-2026-10-20. Corrected the Council tax section. It said your landlord may also choose to add a forwarding address for the tenant who is moving out. That field was taken off the platform on 24 August 2026 and cannot be entered, so we do not collect that address and this notice should not have gone on describing it. Nothing else in the Council tax section changes, and no new collection, use or retention is added by this version.
If you send us a job application
We are not currently advertising vacancies. If you send us an unsolicited job application (please use careers@veylox.uk), we use it to consider and respond to your enquiry, in our legitimate interests in dealing with correspondence sent to us (Article 6(1)(f) of the UK GDPR). Contact privacy@veylox.uk to ask about deletion. We will retain application correspondence for 12 months from receipt, unless you ask us to delete it sooner. We may keep it for longer than 12 months, or keep it after you have asked us to delete it, only where a legal obligation or a legal claim requires it.
Contact
VEYLO X Limited
66 Paul Street, London, EC2A 4NA
info@veylox.uk
Company number: 17203848 · ICO registration: ZC156986
Need a hand?
We reply to every email. Usually within one working day. Monday-Friday, 09:00-18:00 UK.
support@veylox.uk