Kirora is coming. Email and push first. WhatsApp and SMS to follow.Join the waitlist
Legal

Cookie Policy

How Kirora uses cookies, local storage and message tracking, and how to control them.

Last updated 13 October 2026

This policy explains the cookies and similar technologies used by Kirora Technologies Limited (“Kirora”, “we”) on our website kirora.io, in the Kirora app at app.kirora.io, and in emails our customers send through Kirora. “Cookies” here also covers similar technologies such as browser local storage, tracking pixels and tracked links.

We keep this short because we use very little. We use no advertising cookies anywhere, and no analytics on kirora.io today.

kirora.io (our website and documentation)

Our website sets no cookies. We do not run analytics, advertising or social media trackers on it.

The documentation stores one preference in your browser’s local storage:

Name Type Purpose How long
kirora-docs-lang Local storage Remembers which programming language you chose for code samples, so every page shows the same one Until you clear your browser’s site data

This value stays in your browser. It is never sent to us and does not identify you. Because it only remembers a choice you made, it is strictly necessary for the feature you asked for and does not need consent.

app.kirora.io (the Kirora dashboard)

The dashboard uses only what it needs to sign you in and keep your account secure.

Name Type Purpose How long
sid Cookie, first-party, HttpOnly, Secure, SameSite=Lax Keeps you signed in. It holds a random session token; we store only a hash of it. Up to 14 days, or until you sign out
engage:sidebar-collapsed Local storage Remembers whether you collapsed the side menu Until you clear your browser’s site data

These are strictly necessary, or remember a choice you made, so they do not need consent. Signing out deletes the session cookie. When you sign in we also record the IP address and browser your session started from, as explained in our Privacy Policy.

Sign-up forms built with Kirora

Our customers can build sign-up forms with Kirora and show them on a page we host or embed them on their own website.

  • Bot protection. Forms use Cloudflare Turnstile to tell people from bots: by default Kirora’s own Turnstile widget, or one from the business’s own Cloudflare account if it chooses. Cloudflare runs a check in your browser, and we verify the result with Cloudflare when the form is submitted. Cloudflare may set or read its own cookies or similar data to do this; see Cloudflare’s privacy policy.
  • Pop-up forms. If a business shows a form as a pop-up on its website and you close it, your browser’s local storage on that website remembers this for a while (key kirora-signup:<form id>:hidden-until), so the pop-up does not keep reappearing.

The business that runs the website decides whether to use these, and is responsible for any consent its website needs.

Emails sent through Kirora

Emails our customers send through Kirora can contain two tracking technologies:

  • Open tracking pixel. A tiny, invisible image unique to each email. When your mail app loads images, it requests that image from Kirora, which tells the sender the email was opened and when. Some mail apps load images automatically or through a proxy, so an “open” is an estimate.
  • Click tracking. Links in the email first pass through a Kirora address, which records the click and then sends you straight on to the destination. This tells the sender which links were clicked.

These do not place cookies in your browser. Each business can switch open tracking and click tracking off for its whole workspace. How we treat contacts in the EEA and the UK is set out in our Privacy Policy. Links can still carry campaign tags (UTM parameters) that tell the destination website which campaign you came from.

If you have questions about emails you received, contact the business that sent them. Its details are in the email’s footer.

Push notifications

Push notifications from a business using Kirora appear only if you allow them. On the web, your browser asks for permission first. If you agree, the browser gives the business a device token, which Kirora stores so the business can reach you through your browser’s or phone’s push service. You can turn notifications off at any time in your browser or device settings.

How to control cookies and local storage

  • Browser settings. Every major browser lets you see, block and delete cookies and site data. Blocking the sid cookie will stop you from signing in to the dashboard. Clearing site data for kirora.io resets your code-sample language.
  • Email images. Most mail apps let you turn off automatic image loading, which stops open tracking pixels.
  • Push notifications. Change notification permissions in your browser or device settings.
  • Unsubscribe. Every marketing email sent through Kirora has an unsubscribe link.

If we add analytics

We do not run analytics on kirora.io today. If we add analytics or any non-essential cookies in future, we will update this policy first and, where the law requires it, ask for your consent before setting them.

Changes to this policy

We will update this policy when the technologies we use change. The date at the top shows the latest version.

Contact

Questions about this policy: privacy@kirora.io Kirora Technologies Limited, Woodland Court, DPK Estate, Orchid, Lagos, Nigeria