url-kit
~/security

Locked down by default.

Security isn’t a setting you turn on in url-kit. It’s how the service is built, from how you sign in to how a single click is recorded.

Last updated November 22, 2026

The short version

Encrypted everywhere

HTTPS on every domain, including yours. Secrets are hashed or encrypted before they’re stored.

Every workspace is walled off

Each request is checked against your workspace and your role, on our servers.

Strong sign-in

Passkeys, email codes and a fresh check before anything sensitive.

Safer links

Destinations are validated, and risky ones get a warning page before anyone lands on them.

01

Infrastructure

  • url-kit runs on Amazon Web Services in the Mumbai region.
  • Databases and caches sit on a private network and aren’t reachable from the internet. Only the web edge is exposed.
  • Releases are built in CI and deployed without anyone signing in to the servers by hand.
02

Encryption

In transit
Every page, API call and short link is served over HTTPS. Plain HTTP is redirected. Certificates for custom domains are issued and renewed automatically.
Passwords
Account passwords and link passwords are stored only as bcrypt hashes. We can’t read them.
Sign-in tokens
Tokens from Google and Microsoft sign-in are encrypted with AES-256-GCM before they’re stored.
Payments
Card and bank details are handled by Dodo Payments and never touch our servers.
03

Account protection

  • Sign in with a password, a passkey, or Google or Microsoft. New devices also confirm a one-time code sent by email.
  • Sensitive actions, such as deleting a workspace, removing an admin or transferring ownership, ask you to verify again first.
  • You can see your active sessions and sign out of any of them. Changing someone’s role ends their sessions so the change applies straight away.
  • Sign-in, password and one-time code endpoints are rate-limited to slow down guessing.
04

Access control

  • Owner, Admin, Member and Analyst roles decide what each person can see and do. Permissions are checked on our servers on every request, never just in the browser.
  • Every query is scoped to the active workspace. A link, domain or report from another workspace is treated as if it doesn’t exist.
  • An audit log records sign-ins and changes so owners and admins can review who did what.
06

Privacy by design

Visitor IP addresses are never stored. They are used once for an approximate location and then discarded, and our access logs drop client IPs and request headers. Unique visitors are counted with a one-way hash that changes every day. See the Privacy Policy for everything we collect.

07

Reporting a vulnerability

If you find a security issue, email [email protected] with the details and steps to reproduce it. We will confirm we received it, keep you updated and credit you if you’d like.

Please act in good faith: don’t access or change other people’s data, don’t run tests that degrade the service, and give us reasonable time to fix the issue before sharing it publicly. We won’t take action against research done this way.