Privacy Policy

Last updated: October 10, 2026

Data we collect

Account data — name, email address, profile image, and authentication identifiers from the sign-in provider you use.
Workspace and link data — workspaces you create, links, destination URLs, slugs, custom domains, tags, and link-in-bio content.
Click analytics — for each click on a tracked link: timestamp, approximate location derived from IP (country, city, continent), device, browser, operating system, referrer, UTM parameters, and a generated click identifier. We do not store full user-agent strings in the analytics dashboard beyond what is needed for these breakdowns.
Billing data — subscription and payment status. Card details are handled by our payment processor; we do not store them.
Diagnostic data — error reports and performance metrics used to keep the service reliable.

How we use it

Provide the service: shorten links, resolve redirects, count clicks.
Show you analytics for links you own and reports you share.
Enforce plan limits, prevent abuse, and block malicious destinations.
Send transactional email such as verification and invitations.
Diagnose errors and improve performance.

We do not sell personal data. We do not use click analytics to build advertising profiles.

Cookies and local storage

Session cookies — keep you signed in (authentication).
Password-verification cookies — remember that you unlocked a password-protected link.
Attribution cookie — stores a click identifier so lead and sales attribution works across the landing page and the app. It is first-party and only set when you click a link with conversion tracking enabled.
Preferences — layout and theme choices stored locally in your browser.

You can clear cookies in your browser at any time; doing so signs you out and resets remembered link unlocks.

Browser extension

When you open the Slugy extension, it reads the current tab URL to fill the link field. When you choose Shorten & copy, it sends the URL you submit and any custom alias to the Slugy API over HTTPS to create a link in your workspace. Submitted links are processed by the service and its providers for storage, destination safety checks, and link functionality. The extension does not collect your browsing history or the contents of pages you visit.

Connecting your account stores API tokens for your owned workspaces and account details (name, email, profile image URL, and workspace information) in local extension storage, along with your selected workspace. The selected workspace token authenticates link creation; account and workspace details identify your connection. The extension writes created short links to your clipboard and does not read clipboard contents.

Signing out clears the stored extension session. To revoke server access, delete the Slugy Browser Extension key in your workspace settings under API keys. Signing out or uninstalling the extension does not delete links already created; you can manage those in your dashboard. The service provider, retention, and data use practices described in this policy also apply to links created through the extension.

Retention

Link and click data is retained for the analytics retention window of your plan. Deleting your account removes your account and associated workspaces and links, subject to short-lived backups and records we must keep for billing or legal reasons.

Service providers

We share data with processors that operate the service, limited to what each needs:

Cloud hosting and edge delivery
Managed PostgreSQL database and read replica
Redis-compatible cache and scheduled jobs
Analytics event store for click reporting
Object storage for uploaded images
Payment and subscription management
Transactional email delivery
Error monitoring and performance telemetry
Optional AI slug suggestions for links you create

Your choices

Export your links as CSV from the dashboard at any time.
Delete links, workspaces, or your account from settings.
Request a copy of your personal data or its deletion by opening a discussion on GitHub.

Changes

We will update this page when our practices change and revise the date above.