Cookie policy

This Cookie Policy explains the cookies and similar storage Azayemna uses on azayemna.com and on the invitation pages we serve on invite.azayemna.com, and one thing that is not a cookie but that you should know about anyway. It is part of our Privacy Policy.

There is no separate cookie law in the UAE. Cookies are covered by the Personal Data Protection Law, Federal Decree-Law No. 45 of 2021 (PDPL), and only to the extent a cookie carries personal data. Article 4 of that law is what allows a cookie to be set without asking first, and only for the cases it lists. Everything else needs consent under Article 6, which has to be a clear positive action and has to be as easy to withdraw as it was to give.

This policy is published in Arabic and English. If the two versions ever differ, the Arabic version prevails.

The cookies we set

Every cookie below is needed to deliver the service you asked for, which is Article 4(9) of the PDPL. None of them is for advertising, and none of them follows you to another site.

Name	What it does	How long it lasts
azayemna_session	Keeps a signed-in host or operator authenticated. Not readable by any script on the page.	15 minutes
azayemna_renew	Renews the short session cookie without asking you to sign in again. Not readable by any script.	30 days
azayemna_here	Says only that a session exists, so the page can show you as signed in before it asks the server. It holds no identity.	30 days
azayemna_reset	Ties a password reset to the browser that asked for it. It holds a keyed fingerprint of the connection, the moment of the request, and our signature, and no address. Not readable by any script.	15 minutes
azayemna_stepup	Records that an operator has re-authenticated, for the few actions that require it. Admin console only.	15 minutes
azayemna_staff	Set only in an operator's browser, when the admin console opens, so that browser's own visits are left out of the site's page counts. It holds "1" and nothing else, no script can read it, and it is set for azayemna.com and its subdomains so an operator opening an invitation link is left out too. Operators only. Added on 29 September 2026.	12 months
azayemna_admin_clearance	A signed note that an operator signed in recently, so that browser can pass while the site is closed for maintenance. Operators only.	45 minutes
azayemna_visitor	A random identifier for a person who is not signed in, written only when you like, save, or review a design. Nothing about you is in it. Reading a page never sets one.	12 months
azayemna_open	A random number, with our signature beside it, that tells one device from another at a connection. It is how the opens of a shared invitation link are counted, and how a host's own devices are kept out of that count. Set when you open an invitation link or a premium invitation site, or your own workspace while signed in. In production it is set for azayemna.com and its subdomains, so it is the same device on invite.azayemna.com. Nothing about you is in it, nothing is read off your device to make it, and no script can read it.	12 months
azayemna_clear	A signed note that this connection was checked and is not suspended, so we do not repeat the abuse check on every page. It holds no identity, only the moment it runs out, and no script can read it.	2 minutes
azayemna_lang	The language you chose with the language switch, "ar" or "en" and nothing else, so opening azayemna.com again takes you to that language rather than to Arabic. It is written when you press the switch, and at sign in on a device that has never chosen, from the language saved on your account. Nothing about you is in it. Added on 29 September 2026.	12 months
azayemna_cookies	Your answer to the cookie notice: which version of this list you answered and which optional settings you allowed. Nothing about you is in it. The page reads it to know whether to ask.	12 months

The visitor identifier is worth one more sentence, because it is one of the two that are not about signing in. It exists so that a design you liked stays liked, and so that a review you left stays yours to delete. It is written on the server, it is not readable by any script on the page, and it is never joined to your name, your email, or your phone number.

The device number is the other one, and the section below says what it is for.

On invite.azayemna.com

The invitation pages on invite.azayemna.com set one cookie, azayemna_open, and nothing else. It is the only cookie in the table a guest's browser carries to azayemna.com and its subdomains together. The one other cookie set that way, azayemna_staff, is only ever in an operator's own browser. Every other cookie belongs to azayemna.com alone, so a browser never sends the sign-in cookies, the visitor identifier or your cookie answer to an invitation page. Nothing optional is stored there, which is why an invitation page shows no cookie notice.

Storage that is not a cookie

Some things are kept in your browser's own storage rather than in a cookie, which means they stay on your device and never reach us.

• Whether you had the side panel in your workspace wide or narrow. This is the one optional setting, and it is kept only if you allowed "What you set on this device" in the cookie notice. If you did not, the site works the same and forgets the setting each time.
• Whether you pressed "Later" on a note about your account, such as the one asking for your phone number. It lasts only until you close that tab, so the note comes back on your next visit. It holds that one choice and nothing about you.
• Whether you turned an invitation's music off. It lasts only until you close that tab, and it holds that one choice and nothing about you.
• The last few colours you picked in an editor, so they are offered again while you work. They last only until you close that tab, and they hold colour values and nothing about you.
• On a door helper's phone, the offline guest list for one event, a random identifier for that phone so a scan can be traced to the door it came through, and a note that the helper has already seen the tip about adding the scanner to the home screen. None of it says anything about the person holding the phone. The list is deleted the moment the scanner link for that event expires.

Shared invitation links, and what counts their opens

Azayemna's free tier is one shareable invitation link. Each account has a set number of free opens, shared by every link it shares, card links and premium site links together, and after them opens are bought in hundreds. When an account has no opens left of a link's kind, its links of that kind stop opening for new devices. An open is worked out from two things: which connection a request arrived on, and which device at that connection it came from. The first five devices at one connection count as one open between them, and every two devices after that count as one more.

The connection comes from the network address every request carries, on our server, never from anything your browser tells us about itself. We never store the address. We store a keyed one-way fingerprint of it, which cannot be turned back into an address, and we delete it twelve months after that device last opened the link.

The device is the azayemna_open cookie in the table above. That is the one part of the count that is storage on your machine, and it holds a random number with our signature and nothing else. Blocking it or clearing it does not lift the count. It makes your browser look new to us the next time you open the link, which spends the host's opens slightly faster rather than slower. No connection is ever counted for more than forty devices, so this cannot be used to close somebody's invitation.

For a host, the same cookie does one more job. When she uses a device while signed in, we keep a keyed fingerprint of that device's random number against her account, in a scope of its own, so that her own opens of her own links are never counted, even after she signs out on that device. That record cannot be matched to anybody else's opens.

The full explanation, including the legal basis and the rights you have, is in the Privacy Policy.

Payment pages

When you pay, the payment gateway loads its own secure form and may set its own cookies for fraud prevention, under its own policy rather than ours.

Maps and typefaces on a premium invitation site

A premium invitation site fetches its typefaces from Google Fonts, and it may show the venue on a map from OpenStreetMap or Google Maps inside the page. Your browser reaches those providers directly. We set no cookie for them, and anything a map provider stores in its own frame is under its policy rather than ours. The Privacy Policy says what they receive.

Consent, and managing cookies

We do not set an analytics cookie, an advertising cookie, or any cookie that follows you across sites. The cookie notice asks about the one optional setting described above, records your answer, and lets you change it later from the cookie settings link at the foot of every page. If we ever add an optional category, we will ask you again before using it. Under Article 6 of the PDPL consent has to be a clear positive action, so nothing counts as consent because you scrolled past it.

You can clear or block cookies in your browser settings. Blocking the session cookies stops you from staying signed in. Blocking the visitor identifier means a like or a review you leave while signed out will not be recognised as yours afterwards. Blocking the device number changes nothing you can see as a guest: an invitation link still opens exactly as before. As a host, it means a device you use may not be recognised as yours, so opening your own link from it while signed out may be counted. Blocking the language cookie means a bare visit to azayemna.com opens in Arabic, as it did before you chose.

Changes

We may update this policy as the product changes. The date above shows the latest version.