Enterprise-grade controls for Creator content

miilink ships enterprise content security in every short link. Below is the auditable list of controls live in production today.

Transparency commitment

Every security fix lands as a public GitHub commit. During pre-launch, every P0 / P1 issue has a matching PR, roadmap document, and review.

Implemented security controls

As of 2026-05-14

Three-layer access control

Every content view passes through uploadStatus → publishStatus → expiry → view limit → geo → takedown. Any layer failing fails the request.

lib/content/access-check.ts

End-to-end encryption

AES-GCM-256 encrypted in the browser before upload. PBKDF2 with 100k iterations derives the key. The server never sees plaintext, and the password is never stored.

lib/crypto/encrypt.ts

Geographic restrictions

Creators specify an allowed-country whitelist. IP-to-country is resolved via the DB-IP database in real time.

Content.allowedCountries

Distributed rate limiting

Token bucket implemented as a Redis Lua script — consistent across app instances, no race conditions.

lib/rate-limit/limiter-unified.ts

Fail-closed secret validation

JWT_SECRET / FINGERPRINT_SECRET / CRON_SECRET / DATABASE_URL — any missing one throws on production startup. No silent fallback.

lib/config/secrets.ts

Content Security Policy

CSP + HSTS + Referrer-Policy + X-Frame-Options. A Report-Only mirror writes violations to the DB to inform the upcoming nonce migration.

lib/security/csp.js

Secret scanning CI

Gitleaks runs on every PR. Findings get inline review comments and block merge.

.github/workflows/ci.yml

Instant admin takedown

Taking down a short link or content immediately rejects future views and invalidates the viewer cache. No race.

lib/content/access-check.ts → takedownResponse

Questions about any of these controls?

We don't hide from security audits. Email us with what you'd like to see in detail.