Shrtn v1.1.0
Back to Shrtn Add to Chrome
Shrtn Privacy Policy

Clear data practices

Privacy at Shrtn

This policy explains what information the Shrtn browser extension and URL-shortening service process, why that information is needed, where it is stored, and the choices available to you.

Effective: August 1, 2026 Last updated: August 1, 2026

01

Overview

Shrtn is a URL-shortening service and browser extension. Its primary purpose is to convert a user-selected HTTP or HTTPS URL into a shorter public URL, provide redirect analytics, generate a QR code, and make recent results available inside the browser.

Shrtn does not require an account. It does not collect names, email addresses, payment information, contact lists, passwords, or advertising identifiers as part of its normal shortening workflow.

Important

URLs can contain private information, authentication tokens, document identifiers, or personal data. Do not submit confidential, private, expiring, or access-controlled URLs to Shrtn.

02

Information Shrtn handles

URLs you choose to shorten

When you use the extension or website, Shrtn processes the original URL you submit. The URL is sent to the Shrtn backend so that a public short link can be created.

The backend stores the information required to operate the link:

  • Original destination URL
  • Generated short code and public short URL
  • Link creation timestamp
  • Successful redirect count
  • Most recent successful redirect timestamp

Local browser history

The extension stores up to 20 recent generated results in the browser’s local extension storage. This may include:

  • Original URL
  • Generated short URL and short code
  • Creation and analytics information
  • Whether the result originated from the popup, page menu, or link menu
  • The time the result was saved locally

This recent-result list is not synchronized through a Shrtn account and is not uploaded as a separate browsing-history dataset.

Technical request information

When a browser communicates with the Shrtn service, infrastructure providers may process technical request information needed to deliver, secure, and maintain the service. This can include IP address, request time, browser or user-agent information, and diagnostic information.

Shrtn does not use this technical information to build advertising profiles or track users across unrelated websites.

03

How information is used

Information is used only to provide and maintain Shrtn’s user-facing features, including:

  • Creating and returning public short links
  • Redirecting short links to their original destinations
  • Generating QR codes inside the extension
  • Displaying click counts and timestamps
  • Restoring recent extension results
  • Detecting duplicate URLs in local history
  • Diagnosing failures, preventing abuse, and maintaining service security

Shrtn does not use submitted URLs or extension history for personalized advertising, credit decisions, data brokerage, or marketing profiles.

04

Storage and retention

Browser-local storage

Recent extension results are stored using the browser’s local extension-storage mechanism. They remain until one of the following occurs:

  • You select the extension’s Clear action
  • The browser removes the extension’s stored data
  • You uninstall the extension

The extension limits its recent-result list to 20 entries.

Backend storage

Link records are stored in the Shrtn PostgreSQL database so that public short URLs continue to redirect and analytics remain available.

Because Shrtn does not use accounts, link records are not associated with a user profile. Public short-link records may remain stored while the Shrtn service continues to operate unless removal is required for security, legal, or operational reasons.

05

Sharing and service providers

Shrtn does not sell or rent submitted URLs, local extension history, or analytics data.

Information may be processed by infrastructure providers only as necessary to operate the service:

Railway

Hosts the Shrtn website and backend API and processes network requests sent to the service.

Neon

Hosts the PostgreSQL database containing short-link and redirect-analytics records.

Chrome Web Store

Distributes the extension. Google and the browser may independently process store, installation, and browser information under their own policies.

Information may also be disclosed when reasonably necessary to comply with applicable law, respond to valid legal process, protect users, investigate abuse, or secure the service.

06

Extension permissions

Shrtn requests a limited set of browser permissions directly related to its shortening workflow.

activeTab
Read the current page URL

Used when you open Shrtn and choose to shorten the active HTTP or HTTPS page.

clipboardWrite
Copy a generated short URL

Used only when you select a copy action inside the extension.

contextMenus
Provide right-click actions

Used to shorten the current page or a selected hyperlink and to generate QR results.

storage
Save extension state locally

Used for recent results, last-result restoration, and pending context-menu results.

shrtn.up.railway.app
Communicate with the Shrtn API

Allows the extension to create short links and retrieve redirect analytics through the production API.

07

Your choices

Clear recent history

Use the Clear button in the Recent links section to remove the extension's recent-result list from local browser storage.

Remove extension data

Uninstalling Shrtn removes the extension and normally causes the browser to remove its extension-local storage.

Avoid backend storage

Do not submit a URL through the extension or website when you do not want a persistent public short-link record to be created.

Removal requests

Because links are created without accounts, Shrtn may not be able to verify who created or owns a particular short link. Removal requests will be evaluated individually where ownership, security, legal, or abuse concerns can be reasonably established.

08

Security

Shrtn uses HTTPS for communication between the extension, website, and production API. The backend applies request validation, security headers, rate limiting, request-size restrictions, and trusted-proxy configuration.

No internet service can guarantee absolute security. Do not shorten URLs containing passwords, access tokens, private document keys, financial information, or other confidential material.

09

Chrome Web Store Limited Use

Shrtn’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Information accessed through extension permissions is used only to provide or improve Shrtn’s disclosed URL-shortening, QR-code, local-history, and analytics functionality.

10

Changes to this policy

This policy may be updated when Shrtn adds, removes, or changes functionality, data practices, infrastructure, or legal requirements.

The effective and last-updated dates at the top of this page will be revised when material changes are published.

11

Contact

Privacy questions, security concerns, removal requests, and reports of misuse can be submitted through the Shrtn GitHub support page.

Open support page Return to Shrtn

Do not include private destination URLs, passwords, authentication tokens, or other confidential information in a public GitHub issue.