SECURITY & PRIVACY

Security & privacy at AirCues

Last updated: 25 October 2026

Your releases are your work. Here, in plain words, is what we store, who can see it and how it's protected. Technical details are at the bottom.

In short

What we store

Who can see what

PageWho can open it
Press kit (EPK)Only people who have the link. Unlisted, never indexed.
Personal (per-recipient) linksLead to the same press kit. You see opens, plays and downloads on that link. Recipients see a short note that the link is personal.
Smart link (fan page)Public, if you turn it on for a release. Off by default.
Artist page (/@handle)Public, if you turn it on. Off by default.

Good to know: anyone who has a press kit link can forward it. If a link spreads further than you wanted, change it from your dashboard.

Inside AirCues: only the founder has admin access, and uses it only for support you ask for, or to handle abuse reports.

Where your data lives

These are our subprocessors. OurPrivacy Policylists them with what each one handles.

Crawlers & AI

Deleting your data

Reporting a security issue

Emailsecurity@aircues.com. During the pilot we aim to reply within 48 hours. If we ever have a security incident affecting your data, we'll tell you without undue delay.

What we're working on

We're a small team in a pilot phase, and we'd rather be honest about what's next:


Technical details

Accounts
Passwords hashed with Argon2id · server-side sessions · session cookie httpOnly, Secure,SameSite=Lax · rate limiting on sign-in and password reset · CSRF protection on all state-changing requests · single-use, time-limited password reset links · Google sign-in via OAuth.
Transport
TLS 1.2 and 1.3 (1.3 preferred) · HSTS with a two-yearmax-age · Content-Security-Policyupgrade-insecure-requests · HTTP automatically upgraded to HTTPS · all assets served over HTTPS.
Access control
EPK slugs and per-recipient tokens are cryptographically random · EPKs carry<meta name="robots" content="noindex"> and are excluded from the sitemap · smart links and artist landing pages are opt-in per release / per artist (default off) · stored URLs are normalised to HTTPS on save.
Analytics
No cookies for visitors · daily-rotating visitor hash (resets every 24 hours, cannot identify a person across days) · referrer domain only, never full URLs · no fingerprinting or cross-site tracking.
Storage
Cloudflare R2, encrypted at rest · deleting a file, release or artist purges the underlying R2 objects, not just the database rows.

← Back to the home page