What we see, and what we don’t.

LinxMax is built and operated by Spergs, LLC, a Florida limited liability company. Reach us at privacy@spergs.com for anything privacy-related, or to point out something on this page that isn't accurate.

We don't sell, rent, or trade data, and we don't run ads. That isn't going to change.

If you visit a short URL we increment a counter for that mapping. The hit isn't tied to you. We don't store the visitor's IP at the application layer, we don't set any cookies, and we don't load any third-party scripts.

If you create or manage short URLs (via the web app, CLI, or REST API), the server stores the mapping you created. That's a row in our Postgres database with the slug, target, optional campaign label, and timestamps.

If you join a webring or run one, we store the public-facing membership (site name, URL, status) in the database. There's no email, no password, no private account; ring owners moderate the same shared rows.

URL mappings

• The short slug, the target URL, an optional campaign label, created/updated timestamps, and a hit counter.
• No per-visit data: no IP, no User-Agent, no Referer, no fingerprint.

Webring rosters

• For each ring: its name, description, owner name + URL, and a list of member sites (name, URL, approval status).
• Join requests carry the same fields plus a generated ID and a "pending" status until the ring owner approves.

Reverse-proxy access logs

• The nginx in front of the LNX servers writes its standard access log: timestamp, request line, status code, response size, User-Agent.
• We rotate the logs and don't join them to any account or mapping. They exist for troubleshooting and are kept for at most 14 days.

• No accounts on lnx.mx (today). There's nothing to sign up for; the app is single-tenant.
• No cookies. Neither the marketing site nor the app sets any.
• No analytics, behavioural tracking, Sentry, or third-party advertising pixels. There is no SDK on the page that phones home.
• No visitor IPs at the application layer. The hit counter is just a counter.
• No contact-book or address-book sync. There's no concept of contacts.
• No fonts or scripts from third-party CDNs on the marketing site. Everything is served from lnx.mx.

The only third party in the loop is our hosting vendor. Our servers run on a virtual private server hosted in the United Kingdom. Standard hosting operations involve the vendor having physical access to the underlying hardware. They do not have credentialed access to our service.

When a short URL targets an external site (e.g. you set /gh → https://github.com/...), the visitor's browser follows our 301/302 redirect to that external site, which has its own privacy policy. We have nothing to do with what happens after the redirect.

On our servers (United Kingdom):

• A Postgres database — the mappings table (every short URL and its hit counter, with per-hit timestamps in mapping_hits) and the webrings / webring_sites tables (every webring and its membership roster).
• Nginx access logs, rotated daily, retained at most 14 days.

If you're outside the UK, using lnx.mx means your request metadata transits to and rests on our UK servers. The contents of your short links are public by design; there's no private payload being transferred.

• URL mappings live until you delete them via the app, CLI, or API.
• Webring members stay listed until the ring owner removes them.
• Hit counters are stored alongside the mapping; deleting the mapping zeroes them.
• Nginx access logs are rotated daily and deleted after 14 days.

Because lnx.mx today is a single-tenant deploy without per-user accounts, there isn't a per-user dataset to export. If you've sent us a webring join request and want it removed (whether or not the ring owner has approved it yet), email privacy@spergs.com and we'll remove it within 30 days. You can also ask for a copy of any metadata associated with you (the join request row, basically).

If you're in the UK and aren't happy with how we've handled a data request, you can complain to the Information Commissioner's Office (ICO). EU/EEA users can complain to their national data protection authority.

LinxMax is for adults. Our terms of service require you to be at least 18 years old. We don't knowingly collect data from anyone under 18; if you believe we have, email privacy@spergs.com and we'll delete it.

If something material changes (e.g. we add accounts, or hit counters start carrying per-visit data), we'll update the "Last updated" date at the top and post a notice on the homepage. We won't make changes that surprise existing users.

Spergs, LLC
privacy@spergs.com