Skip to content
Ushly
Use light theme
  • URL Shortener
  • QR Codes
  • Analytics
  • Features
Log inGet started

Privacy

Privacy Policy

This policy explains the data used by the current Ushly project and the safeguards built into its link and account features.

Project template: review this page and replace its configurable legal identity and contact placeholders before production launch.

Contents
  1. 1Who is responsible
  2. 2Accounts and authentication
  3. 3Short links and redirects
  4. 4Click analytics and minimization
  5. 5Deletion and privacy requests
  6. 6Future tools

Who is responsible

The service operator is [Legal name to be confirmed]. Privacy and deletion requests should be sent to [Contact email to be confirmed]. These configurable placeholders must be replaced with verified operator details before production launch.

Accounts and authentication

Local accounts use an email address and a one-way password hash. Access tokens stay in browser memory. A rotating refresh token is stored in a path-scoped HttpOnly cookie and as a cryptographic hash in the database.

If you choose Google sign-in or explicitly link Google, Ushly receives the Google account subject and email needed to identify the account. Ushly does not automatically merge accounts based only on matching email addresses.

Short links and redirects

Ushly stores the destination URL, generated short code, optional title and expiration, link status, and ownership when a signed-in user creates the link. Anonymous links are not attached to an account.

Destinations are public through their short URLs. Do not place secrets or sensitive query values in a destination you intend to share.

Click analytics and minimization

When a short link redirects, Ushly records a keyed one-way HMAC of the visitor IP address rather than the clear IP address. It may also store a user-agent value limited to 256 characters and the referrer origin, without its path or query, limited to 256 characters. No geolocation provider is currently enabled.

Click analytics are available only to the authenticated owner of the link. The configured click-retention policy defaults to 90 days. Automated scheduled deletion is still pending operational implementation, so the deployment operator must review and enforce retention before production launch.

Deletion and privacy requests

Use the configured contact email to request access, correction, or deletion. The production operator must verify the requester, define applicable response procedures, and document any records that must be retained. Ushly does not currently provide a public self-service privacy-request form.

Future tools

Ushly does not currently load optional third-party audience analytics or advertising tools. If either is introduced later, this policy and the consent controls must be updated before those tools are enabled where consent is required.

Related information

Cookie PolicyTerms of Service

Product

  • URL Shortener
  • QR Codes
  • Analytics
  • Features

Legal

  • Privacy Policy
  • Cookie Policy
  • Terms of Service

Account

  • Log in
  • Get started
Ushly

Short links, QR codes, and owner-only analytics.

© 2026 Ushly. All rights reserved.