SafeSlugSafeSlug
Encrypted Link Storage

Private URL Shortenerfor destinations worth protecting

SafeSlug encrypts destination URLs and slugs with AES-256-GCM before storage, keeps redirect analytics lean, and lets anyone shorten without first creating an account.

Cryptographic Storage PipelineCiphertext At Rest
1. Plaintext In

https://corp/doc

Validated for SSRF

2. AES-256-GCM

PBKDF2 SHA-256

+ HMAC-SHA256 index

3. At Rest

8f4b...9a12

URL & slug encrypted

4. Redirect

no-referrer

0 raw IPs stored

Custom
Length:7 chars

Security Architecture

Destinations and slugs stay encrypted at rest.

SafeSlug is built for users and organizations who need short links without turning their link database into a readable map of every asset they share.

Encrypted before storage

Destination URLs and slugs are encrypted with AES-256-GCM before they are saved, and indexed via keyed HMAC-SHA256 hashes so plaintext URLs never touch disk.

Decrypted only for redirect

The server decrypts the destination URL in volatile memory only when a short link is requested and needs to redirect the visitor.

Analytics without raw IP retention

SafeSlug stores aggregated redirect signals such as visits, 2-letter country code, referrer hostname, and device class without keeping raw IP addresses.

No-referrer redirects

Redirect responses include Referrer-Policy: no-referrer so destination sites do not receive your short-link URL as the referral source.

What makes a URL shortener truly private?

Standard shorteners store links and slugs in plain text. That means any internal breach, misconfigured backup, or data export exposes every URL, document path, and token you have ever shortened.

SafeSlug encrypts both destination URLs and custom slugs before writing to the database. Even if storage were dumped, links remain completely unreadable without the server-side environment keys.

Redirect analytics follow the same strict discipline: visit counts, high-level country codes, and device types are aggregated without ever saving raw visitor IP addresses.

Encryption & Privacy FAQ

Private URL shortening questions.

How is an encrypted URL shortener safer than a standard shortener?

Standard URL shorteners store target URLs and slugs in plaintext tables, meaning a database leak or backup exposure reveals every shared document path and query parameter. SafeSlug encrypts destinations and slugs with AES-256-GCM before writing to storage.

How can SafeSlug resolve a short link if slugs are encrypted?

SafeSlug computes a deterministic keyed HMAC-SHA256 lookup hash from the incoming slug using a server-only secret. This allows O(1) database lookup without storing the readable slug in plaintext.

Does clicking a SafeSlug link leak the short URL to the destination site?

No. Redirect responses set `Referrer-Policy: no-referrer`, instructing browsers not to transmit the SafeSlug short URL in the HTTP Referer header when loading the destination.

Can I create encrypted short links without signing up?

Yes. Random and memorable passphrase links can be created immediately with no account, and still receive full AES-256-GCM encryption at rest and no-referrer redirect protection.

Create an encrypted short link now.

Generate random or memorable passphrase slugs without signing in, or create an account to unlock custom slugs, CLI access, and analytics.

Related features