Agency Feed Agreement

You are a brokerage registered on the Dubai Land Department's offices file, identified by the office number (ORN) you give in the signature block, and holding the trade licence you name there. Keyva checks that office number against the Department's published offices file. While it does not match an entry there, your feed is not activated and no advert from it is shown. An admin may still run a test read of a feed that has not been activated, to see whether it parses; nothing from such a read reaches a reader.

Neither of us pays the other anything under this Agreement. You pay nothing to have your adverts read or shown, and Keyva pays nothing for them.

It is not exclusive, in either direction. You may send the same feed to any portal or site you like, and Keyva may take feeds from any number of other agencies.

It creates no agency, partnership, joint venture or employment between us, and it does not appoint Keyva as your broker, your sub-agent or your representative. Keyva is not a registered real estate broker under Bylaw No. 85 of 2006 and does not carry on real estate brokerage.

For every property in your feed, Keyva is not the seller, not the landlord, not the agent, and not a party to any transaction that follows. Keyva takes no commission and no other payment on anything you sell or let.

You give Keyva one feed URL that your CRM publishes, in one of two formats: the Bayut/dubizzle combined XML, or the Property Finder legacy XML. Tell us which one your CRM actually produces, and write it on the signed copy — Keyva does not guess, and a feed whose format does not match what you told us is refused rather than read loosely.

The URL must be served over https. Keyva stores it encrypted, because CRM feed URLs often carry a token in them, and the admin screens show only its host.

You keep the URL working and current, and you tell us before it changes. If the feed stops answering, the adverts Keyva has already read stay as they are for seven days. An advert Keyva has not read in your feed for seven days stops being shown, so a feed that has been down for a week does not leave adverts up under a date that has stopped moving. They are not deleted: when the feed answers again and still carries them, they are shown again.

There are two ways your feed gets read: a scheduled read, once a day, and an admin pressing a button to read it. The scheduled read is switched off today, and Keyva may switch it on without a new version of this Agreement, so for now nothing reads your feed except an admin pressing that button.

The once-a-day figure is the schedule's own cadence, not a cap, and Keyva does not promise you one: an admin can press the button as often as they choose. What does limit Keyva, in its own design, is this. Only one read of your feed that may add or replace an advert runs at a time, held for up to ten minutes — two admin test reads can overlap, because neither adds or replaces an advert, though each of them does write the run report section 4 describes. Keyva stops reading at 10 MB of feed. And it gives up if your host takes more than 10 seconds to accept the connection, more than 20 seconds to send the first byte, or more than 60 seconds in all. Those are limits on Keyva, not on you.

Under this Agreement Keyva requests nothing but the feed URL: it never follows a link found inside the feed, does not fetch your photographs, videos or floor plans in this version, and requests no page of your website or of any portal to read your adverts.

That is a statement about what reading your feed involves, and it is deliberately not a statement about everything Keyva's software does elsewhere on the public web. Keyva runs other programmes that request pages — it builds a directory of brokerage contact details and writes to the published office addresses it finds, and it reads developers' own websites for their published asking prices — and this Agreement neither covers them nor promises you they do not exist. What it promises is that reading your feed under it is one request to the URL you gave us.

You give each of the warranties below for every advert in the feed, on every day it is in the feed. They are continuing warranties, not statements made once when you sign.

(a) The property is genuinely available for sale or for rent through you, and you are instructed by its owner to advertise it.

(b) Every advert carries a Trakheesi advertising permit that is validly issued to you, for that property and for that advertisement, that has not expired and has not been withdrawn — and the permit number in the feed is that permit's number, filed correctly.

(c) The asking price in the feed is the price you actually advertise for that property. It is not a placeholder, not an indication, and not a figure set away from what you advertise elsewhere in order to draw enquiries.

(d) You hold every real estate licence and registration that UAE and Dubai law require for the activity you carry on through this feed — including registration on the Real Estate Brokers Register under Bylaw No. 85 of 2006 — you keep them current, and you tell us within seven days if any of them lapses.

(e) Nothing in the feed infringes anyone's rights, including copyright in any text or image and any third party's trade marks.

(f) You remove an advert from the feed once the property is withdrawn, let or sold, or once the permit for it stops being live.

The Land Department has announced that an advertisement carries the Madmoun QR code issued with its permit as well as the permit number. The permit and that QR code are issued to you and are yours to hold. Your feed does not send the QR code to Keyva, and Keyva does not create, store or show one: a card on Keyva carries the permit number only, as you filed it. Whether an advert republished on Keyva must also carry the QR code is a question for your own advisers; the duty under (b) is yours either way.

The Land Department publishes fines of AED 50,000 per advertising violation, rising with repetition to cancellation of the advertising company's licence, for advertising with no permit, misusing a permit number, or using an expired one. That exposure is yours, not Keyva's, which is why (b) and (f) are continuing.

Read this first, because it is the one thing signing gets you and it is not switched on. Whether an advert from any agency may appear on a public page at all is a single switch in Keyva's own settings, and that switch is off today. While it is off, no advert from your feed — and none from any other agency's feed — is shown to a reader on any page of this site. Everything else in this section describes what a card carries when the switch is on.

What remains before Keyva turns it on is what its own settings page says: a signed agency whose feed is active, that has passed its dry run, and whose unmatched queue is empty. Keyva may turn it on at any time, and it does not need a new version of this Agreement or a fresh signature from you to do it. Everything below is what your adverts carry from the moment it does.

An advert appears only on the building page or the project page it matches. An advert Keyva cannot resolve to one building or one project is held on the admin desk and is not published at all. There is no area fallback, no listings index, no search over adverts and no price filter.

Where an advert is shown, its card carries these things from your feed, and nothing else from it: the bedrooms, the property type, whether the home is ready or off-plan, and whether it is for sale or to rent, as you filed them; the size as you filed it, in the unit you filed it in; your asking price, with its period where it is a rent; every asking price Keyva has read for that advert, oldest first, each one dated; and the advertising permit number as you filed it.

The same card carries these things, which are Keyva's own rather than yours: your name and office number as they stand in the Land Department's offices file, with the date on that file; the day Keyva first read the advert in your feed and the day it last read it; the registered sale figures the next paragraph describes, or the reason there are none; the registered rent figures the next paragraph describes, or the reason there are none; one action, which while Keyva offers no introduction is a link to Keyva's own /check page; and Keyva's own footnote — that this is your advertising, received from your feed under a written agreement, that Keyva is not the seller or an agent and earns nothing from the sale, and that adverts enter no median, trend or yield.

Ready or off-plan is printed only where your feed says which; where it says neither, the card says neither.

And where the size you filed is outside the range Keyva expects for that many bedrooms, the card says so beside it and does not use it: the registered figures below the advert then drop their size band and compare on bedrooms alone. That is Keyva's own judgement of the figure, not a correction of it — your size is still printed as you filed it.

Where your feed files no asking price, or files it as price on application, the card says that the agency has not published an asking price. It does not guess one and it does not leave the line blank.

Those office lines come from the Department's public file, not from your feed. They also carry the licence end date that file records, and the licence number where the Department files one number against more than one office, saying that it is shared. Where the Department files no name against your office number, the card says that instead of a name. And where that licence end date has passed, or your office is not in the Department's newest offices file, no advert of yours is shown at all — the card does not appear saying your licence has lapsed, it does not appear.

The two read dates are Keyva's own record of its own reading. Your feed does not send them and cannot set them.

The /check page that action links to explains how a reader checks a permit with the Land Department, free. Where an advert is shown, beside that link the card says that Keyva cannot introduce a reader to the advert's agent.

Your own reference for the advert is on neither list, and is shown to nobody. Keyva stores it, and an admin sees it on the admin desk and in the report of every read, but no page a reader can load carries it and no query that builds a public page can even read it: the reference is yours to choose, and a field you choose must not be able to order or label anything a reader sees.

Beside your advert, on the same card, Keyva shows registered Land Department figures for the same building or project — medians of what was actually paid or contracted, with the number of records behind them and the window they cover. That comparison is the reason adverts are accepted here. It is not removable and it is not negotiable for an individual advert.

A permit number is shown exactly as you filed it and is not checked by Keyva. Checking one advert's permit needs the Land Department's Trakheesi API, which Keyva has not bought, so no permit number on Keyva has been checked against the Department's records. The card says so beside the number, in these words: "Keyva cannot check a permit number against DLD advert by advert."

Keyva does not show your titles, your descriptions, your photographs, your videos or your floor plans in this version. Your photographs, videos and floor plans are never fetched at all. Your titles and descriptions are stored, for the two reasons section 5 gives, and are shown to nobody but an admin. If that is ever to change, it changes by a new version of this Agreement that you sign — never by Keyva beginning to show them.

Keyva never shows an agent's name, phone number or email address: not on the card, not in the page's source, and nowhere a reader or a search engine can reach.

Keyva decides where an advert appears and whether it appears at all. Keyva may hide any advert, or stop showing your whole feed, at any time and without giving a reason.

Four rules keep an advert of yours off a page, and you should know all four before you sign. The first three take down adverts with nothing wrong with the property itself; the fourth is a filing Keyva cannot read, and it happens before anything is stored.

First, only homes are shown: apartments, penthouses, duplexes, villas and townhouses. Everything else in your feed is read and kept and never published, and this is the whole list of it: commercial property, hotel apartments, land, any property type Keyva's own list of types does not recognise, a rent quoted by the day or by the week, and an advert that carries a holiday-home (DTCM) permit number. A holiday-let or short-stay agency's feed would load and publish nothing at all, so read that list before you send us one.

Second, where another agency's feed files the same advertising permit number as one of your adverts, Keyva shows neither advert — it cannot tell which filing is right, so a filing mistake at another brokerage can take one of yours down.

Third, an advert Keyva cannot check is held for an admin to look at, and is not shown while it is held. That is any of: a size filed in a unit Keyva does not recognise, a sale price below the floor Keyva treats as credible, a sale price per square foot outside the range Keyva expects, a sale price Keyva cannot check at all because the size is missing or itself implausible, a rent outside the range Keyva expects for its period and its bedroom count, the same advertising permit number filed twice inside your own feed, and the same permit number already filed by another feed of your own office.

Fourth, an advert Keyva cannot read is rejected as the feed is read and is never stored at all, so it reaches none of the rules above. Nothing of it is kept: its reference, its place in the file and why it was rejected go into the read's report, for the first 200 rejections of that read, and the advert itself is not written. That is any of: no reference of your own, or one carrying a space, or one longer than 64 characters; the same reference on two adverts in the one feed, which drops both; no advertising permit number at all; a permit number that is not shaped like one — under four digits in it, or under four or over thirty-two characters long; a city that is not Dubai; a purpose Keyva cannot read as either sale or rent; a labour camp, staff accommodation or bulk unit, which Keyva never stores; a property type that is not in Keyva's vocabulary for the format you named — each feed is read against its own format's list only, never against the other's; a bedroom count Keyva cannot read, or none filed at all on a home; a rent whose period Keyva cannot read as yearly, monthly, weekly or daily — on a Bayut/dubizzle feed the period is a word, and Keyva reads yearly, year or annually, monthly or month, weekly or week, and daily or day; on a Property Finder feed it is one of the four price tags yearly, monthly, weekly and daily; anything else is treated as no period — and such a rent is rejected on a Property Finder feed unless price on application is declared with the word yes, and on a Bayut/dubizzle feed always, because Keyva's reader of that format takes no price-on-application field; a price that is not a number, or is zero or below; a price past what the column holds (100 billion dirhams); a size that is not a number; and a size past what the column holds (100 million).

How you find out about all four: every read writes a report on Keyva's admin desk, which keeps a sample of up to 200 of your own references that were rejected and why, so an admin can tell you what to fix. The report is a disclosure, not a fifth rule — it takes nothing down.

Keyva does not rank adverts or agencies, does not sort by price, and never tells a reader whether an advert is priced well or badly. Adverts are ordered by purpose, then bedrooms, then the date Keyva first read them — never by price, never by the gap to a registered figure, and never by agency.

Asking prices from your feed never enter any median, trend, yield, index or other computed figure on Keyva, and never reach its assistant. The registered side and the advertised side are kept apart, and each is labelled for what it is.

You give Keyva a non-exclusive, revocable, royalty-free licence to do the three things below with what your feed carries, and nothing else. It is a licence to use, never a transfer: your adverts, your copy and your images stay yours.

(a) To store your feed as Keyva received it. Where a read is held back for an admin to look at before anything is applied, the file Keyva fetched is kept in private storage, so that what is applied is what the admin saw and not a feed that changed in between.

That stored file is kept. Resolving the hold does not remove it — applying a held read reads the file and leaves it where it is — and Keyva has built nothing that deletes it, so we do not promise you a date. How long it should be kept is the same open question section 6 leaves about your agents' details, and it is answered the same way: the Privacy Policy governs it, and you can ask us in writing to remove the file, which we consider under the Privacy Policy and tell you what we have done. It is part of what the last paragraph of this section calls the stored feed, and it carries whatever that read of your feed carried — every advert in it, your titles and descriptions, and your agents' details as you filed them.

(b) To keep each advert's record and the history of its asking price, for as long as section 7 describes — including after the advert is withdrawn, and after this Agreement ends, unpublished.

(c) To show, on the building page or the project page an advert matches, only what section 4 lists, and of that only the part your feed files: the bedrooms, the property type, whether the home is ready or off-plan, and whether it is for sale or to rent, as you filed them; the size as you filed it, in the unit you filed it in; your asking price, with its period where it is a rent; every asking price Keyva has read for that advert, oldest first, each one dated; and the advertising permit number as you filed it. The rest of what that card carries is Keyva's own — its record of when it read your feed, its reading of the Land Department's public offices file, the registered figures and its own footnote — and needs no licence from you.

Your titles and descriptions, in English and in Arabic, are stored under (a) and (b) as your feed files them. They are kept for two reasons only: so that Keyva's record of an advert is the advert you filed, and so that Keyva can tell on a later read whether anything about the advert has changed — your wording is part of the fingerprint Keyva compares one read against the next, so an advert whose title you edit is written again rather than passed over as unchanged.

They are not used to work out which building or project an advert belongs to. That is done from the location fields your feed files — the community, the sub-community, the building name and the project name — and nothing in Keyva reads a title or a description for it. The licence in (c) does not extend to them, and they are not shown to a reader, in whole or in part. Photographs, videos and floor plans are not fetched, so there is nothing of them to licence.

The licence is revocable. Ask us under section 7 to hide an advert or to stop reading the feed, or end this Agreement under section 10, and the licence in (c) ends with it. What survives is (a) and (b): the stored feed and the advert history, unpublished, as the record of what was advertised and when.

Your feed carries your agents' names, phone numbers and email addresses and, where Keyva's reader of a Property Finder feed finds one, their broker registration numbers. Keyva stores those in a separate table that only an admin can read.

They are never published. Keyva does not show them to a reader, does not put them in any page, and never writes to or calls an agent using them — not to sell anything, not to invite them to Keyva, not at all. They enter no figure on the site and reach no other system.

There is one intended use, and it is not offered in this version. Keyva does not offer a reader an introduction to the agent advertising your property: the route for it is not built, and where an advert is shown at all, its card says Keyva cannot introduce a reader to that advert's agent. Where Keyva offers such an introduction in a later version, the request would go to the agent advertising that property and to nobody else — routed by the broker registration number your feed files, where it files one, which Keyva's reader of the Bayut/dubizzle format does not take — and through the consent-based introduction flow the reader has agreed to. Where an agent takes part in an introduction, the Agent & Agency Agreement governs their side of it.

Until that is offered, these details are held and used for nothing: they sit in the admin-only table so that the routing above can use them if and when Keyva offers it, and for no other purpose.

You confirm that you may share these details with Keyva for that purpose, that you have a lawful basis for doing so under Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data, and that you have told your agents.

Keyva keeps them while this Agreement is in force, and afterwards for as long as the Privacy Policy allows. Ask us in writing to remove them and we consider that request under the Privacy Policy and tell you what we have done.

An advert that is no longer in the feed is marked withdrawn on the next read, and stops being shown from that moment. Nothing in Keyva shortens the wait for that read: while the scheduled read is switched off, as section 2 says it is, the next read is whenever an admin next runs it, and there is no other clock. Separately, and whatever happens to the feed, an advert Keyva has not read for seven days stops being shown — that is the one automatic limit, and it hides the advert rather than withdrawing it.

A withdrawn advert is not deleted. Its record and its asking-price history stay in Keyva's database, unpublished, as evidence of what was advertised and when. If the same reference comes back into the feed, it goes live again and the history shows both periods.

You can email us at legal@dubaikeyva.com and ask Keyva to hide one advert, or to stop reading the feed, immediately. No reason is needed and there is no notice period. Keyva acts on it promptly, and normally within one working day.

Keyva may pause your feed itself, at once, if an advert looks wrong, if a read looks wrong, or on being told anything about an advert or about you by the Land Department, RERA or any other authority. Keyva tells you why when it does.

Tell us if a figure on a card is wrong and Keyva looks into it. Where we agree it is wrong, Keyva corrects it or stops showing the card while it is sorted out. Where the error is in the feed itself, correct it in your CRM and the next read carries the correction through.

Keyva does not offer an introduction from your advert in this version. There is no route by which a reader can ask to be introduced to the agent advertising it, and where an advert is shown at all, the card on it says so. Section 4's first paragraph is the wider point: no advert from any agency is shown to a reader today.

Where Keyva offers such an introduction in a later version, a request made from your advert would go to the agent advertising that property and to nobody else. Keyva would never answer a request made from your advert by sending that reader to a different agency, or to an agent at another brokerage.

The site service charge in the Agent & Agency Agreement is a charge on an agent for using the site to answer an introduction. It is not a charge under this Agreement, it is not a commission, and it is never a share of anything you earn on a property.

No other money passes between us, in either direction, under this Agreement.

Each of us is liable for our own breach of this Agreement.

You will indemnify and hold harmless Fikra Ventures FZE LLC, a Free Zone Entity incorporated under Amiri Decree No. 15 of 2023 at Ajman NuVentures Centre Free Zone, holding trade license/registration number 2629617609888, with its registered address at Office BC-892072, 26th Floor, Amber Gem Tower, Sheikh Khalifa Street, P.O. Box 4848, Ajman, United Arab Emirates, its officers and employees, against any claim, fine, penalty, loss or reasonable legal cost arising from an advert in your feed that had no Trakheesi permit validly issued to you, or whose permit had expired or been withdrawn, or that infringed a third party's rights. This indemnity survives the ending of this Agreement.

Because no money passes between us, Keyva's total liability to you under this Agreement, however it arises, is capped at AED 1,000. That is a nominal cap, set there because there is no consideration to measure one against rather than because a larger loss is contemplated. It does not apply to fraud or fraudulent misrepresentation by Keyva.

Keyva does not warrant that any advert will be shown, that it will be matched to a building or a project, that it will be seen by anybody, or that it will produce an enquiry, a viewing or a transaction.

This Agreement starts on the date it is signed and runs until one of us ends it.

Either of us may end it on 30 days' written notice, for any reason or for none.

Where the two of us agreed an end date, it is written on the line for it on the copy we both sign, and Keyva's admin records that date against your feed. This Agreement then ends on that date, without either of us giving further notice: from that date Keyva stops reading the feed and stops showing its adverts. Where we agreed none, that line is left blank and this Agreement runs until one of us ends it as above.

Either of us may end it immediately, in writing, on the other's breach of it. Keyva may also end it immediately on being told anything by the Land Department, RERA or any other authority that makes reading or showing your feed inappropriate.

When it ends, Keyva stops reading the feed, marks every advert from it withdrawn, and stops showing them. The records and the asking-price history stay in the database, unpublished, as section 7 describes.

Section 5 (the licence, narrowed as section 5 says on ending), section 6 (personal data), section 9 (liability) and section 11 (governing law) survive the ending of this Agreement.

This Agreement is governed by the laws of the United Arab Emirates as applied in the Emirate of Dubai, consistent with the Terms of Service.

Any dispute arising from this Agreement is subject to the exclusive jurisdiction of the competent courts of the UAE, without prejudice to any other resolution method we may agree in writing.

The copy you sign is at /legal/agency-feed-agreement/print. It carries the same sections as this page and a ruled line for each of: Agreement reference, written on this copy and recorded against the feed; Agency name, as written on the trade licence; Office number (ORN) on the Land Department's offices file; Trade licence number; Name of the person signing; Their title; Date of signature; The feed URL's host only — not the full address; The feed format the CRM produces — Bayut/dubizzle combined XML, or Property Finder legacy XML; End date, if the two of us agreed one (otherwise leave blank). The same page carries a second block for Keyva's signatory — name, title and date — because both of us sign one copy.

Only the host of the feed URL goes on the signed copy — the part before the first slash, such as feeds.your-crm.com, and not the full address. The full URL, which often carries a token, is given to Keyva separately and stored encrypted.

Keyva's admin uploads the signed copy against your feed and records, from that copy, the date you signed, the agreement reference written on it, the feed format you named, and the end date where the copy carries one. No feed is read until that signed copy and that signing date are on the record.