Privacy.

What this site collects, what it sets in your browser, and what the panel on your own server does not send. Specific to this site rather than a template — every cookie and every company named below is one actually involved.

Last updated 1 September 2026

What this covers

This policy covers aurapanel.net — the website where auraPanel is described and bought. Garuda Consulting Ltd is the controller for the personal data described here.

Two related things are covered elsewhere. Customer accounts, subscriptions and licence records live on goaura.one, which is the account surface for every Aura product. The auraPanel software itself runs on a server you control, and what it does and does not send is set out on the security page.

When you visit this site

You can read every page here without an account. There is no sign-in on this site and no profile is created by browsing it.

Cloudflare sits in front of the site to deliver and protect it, and necessarily processes your IP address to do so. Our own web server records requests it serves, including the requesting IP address, as ordinary operational logging.

Cloudflare Web Analytics runs on every page. It is cookieless: it reports page views, the referring site, broad device and browser information, and page-performance measurements. It sets nothing in your browser and does not follow you to other sites, which is why it is not gated behind a choice.

Analytics, and your choice

We would also like to use Google Analytics to understand which pages are useful. Google Analytics sets cookies, so it is not loaded until you have said yes.

Until you choose, no analytics tag is loaded and no analytics cookie exists. If you accept, Google Analytics is loaded and sets its cookies. If you decline, it is never loaded and any of its cookies already present are expired.

Your choice is remembered in your own browser, in local storage, under the name ap-analytics-consent. That value stays in your browser and is never sent to us.

You can change your mind at any time using the Cookies control in the footer of any page. Withdrawing is exactly as easy as agreeing.

When you buy a licence

Payment is handled by Stripe. Stripe collects your email address and payment details directly and processes the payment; card numbers never reach this site and we do not store them.

Prices shown here are fetched by our server from our licensing service. No information about you is involved in that request.

After a successful payment, our licensing service creates or matches a customer record using the email address you gave Stripe, and issues the licence for your server. That record lives on goaura.one, along with your subscription and licence history.

Cookies and local storage

This site sets nothing in your browser unless one of the following applies. It sets no advertising or cross-site tracking cookies at all.

  • _ga and _ga_… — Google Analytics. Set only after you accept analytics, and expired if you later decline.
  • ap-analytics-consent — your analytics choice, held in local storage in your browser so you are not asked again. Never transmitted.
  • Stripe may set cookies of its own during checkout, to run the payment and to detect fraud.

The auraPanel software

auraPanel is self-hosted. The sites, databases, files and users it manages stay on your server, and it sends us no usage information about them.

It does contact our licensing service to check that the licence for that server is valid. That is the connection required to run a paid licence, and it is described in more detail on the security page.

The live demo

The public demo is a shared server that anyone can sign into with the credentials published beside it. Treat everything in it as public, and do not enter real data, real credentials or anything you would not publish.

Who else is involved

We do not sell personal data and we do not share it for advertising. Data reaches the following organisations because they provide part of this site:

  • Cloudflare — delivers and protects the site, and provides the cookieless analytics.
  • Stripe — takes the payment when you buy a licence.
  • Google — provides Google Analytics, and only if you have accepted it.

Your rights

Under UK data protection law you can ask what personal data we hold about you, ask for it to be corrected or deleted, object to how we use it, and withdraw a consent you have given. Withdrawing analytics consent needs no request at all — the Cookies control in the footer does it immediately.

To exercise any of the others, contact us and we will answer. If you are not satisfied with how we handle it, you can complain to the Information Commissioner’s Office, the UK supervisory authority.

Changes to this policy

This policy was last updated on 1 September 2026. If it changes in a way that affects what we collect or who we share it with, the updated date here changes with it.

Try the live demo

A real auraPanel on a real server, shared with everyone. Sign in with the demo account and click around.

Email
demo@goaura.one
Password
demo1234
Open the demo panel ↗

Shared public demo, so please don’t put anything personal in it. More about the demo →

Talk to us

Tell us what you need and how to reach you. A person reads this, not a queue.

We use these details only to reply to you. Privacy

Recent updates

What shipped in the last releases. With automatic updates on, each lands on your server the moment it is published.

  1. v1.21.3
    Framework sites were undetectable, and a restore could silently point the copy at the original's live database.

    DetectApp looked for each application's signature relative to the docroot — but every PHP framework in the registry serves from a subdirectory (DocrootSub: public, webroot, web, pub, docroot) and keeps the file that identifies it one level *above* that. So the Laravel signature searched <project>/public/artisan,…

  2. v1.21.2
    Restarting nginx now blocks the panel and reconnects, instead of showing a notice.

    v1.21.1 stopped the false "HTTP 520" but only put up a toast — and a toast is the wrong affordance when the panel itself is about to go away: the page sat there looking broken while every request failed underneath it.

  3. v1.21.1
    Restarting nginx from Services no longer reports a false failure.

    It showed "Restart failed — HTTP 520". The panel is reverse-proxied *by* nginx, so the request deadlocked against itself: the handler blocked waiting for the restart to finish, while nginx's graceful stop waited for that very request to drain. Neither could proceed until nginx's stop-retry timeout force-killed it,…

  4. v1.21.0
    Per-site X-Frame-Options, fixing page builders that couldn't load their preview.

    Elementor's editor failed with *"Multiple 'X-Frame-Options' headers with conflicting values ('DENY, SAMEORIGIN')"*. The cause is that nginx's add_header appends rather than replaces: when the application also sets the header — a WordPress security plugin, or a CDN transform — the browser received two values,…

  5. v1.20.6
    The multi-database restore refusal now says what is in the backup and what still works.

    It read only "Restoring a multi-database site isn't supported yet", which is a dead end: it named neither the databases involved, nor why one of them is the limit, nor any route forward.

  6. v1.20.5
    Services: cards in a row now match heights.

    Like the settings grid before it, the Services grid pinned each card to its own content height, so a row often showed one card noticeably shorter than the card beside it. Each row now takes the taller card's height and both fill it, and it re-balances as content changes — a runtime installed, a longer service list.

  7. v1.20.4
    Settings: paired cards now match heights.

    Organisation / Panel Domain and auraPanel Updates / Session timeout each sat at their own content height, so a row showed one card visibly shorter than its neighbour. Each row now takes the taller card's height and both fill it — driven by content, not a fixed value, so it still adapts as a card grows (a validation…

  8. v1.20.3
    Settings: Organisation and Panel Domain now share a row too.

    They were full-width blocks stacked above the rest of the page; they now sit side by side in the same two-column grid as the Updates / Session timeout pair, so the top of Settings reads as two tidy rows instead of four stacked bands. Both cards shrink cleanly — the logo drop zone is a fixed 44×44 and the name field…

All releases on GitHub ↗