Pular para o conteúdo

Privacy Policy

This Privacy Policy explains what information LinkMagnet collects, why we collect it, the service providers involved, and the choices available to users.

Atualizado em October 30, 2026 · Baseado na Califórnia e operado de forma independente

1. Who we are

LinkMagnet is operated by Dario Rapisardi (Pants AI), an individual based in California, USA. This Privacy Policy applies to our website, short-link tools, analytics features, Open Graph validator, card service, REST API, MCP server, command-line client, and related services.

2. Information you provide

  • URLs, metadata, prompts, and other content you submit for shortening, validation, or preview generation.
  • For the card service: site names, the hostnames you register, the verification token we issue for each hostname, your card template settings (layout, colors, and an optional logo URL), and a daily count of new cards drawn for each site; and, for each page you audit from the console, the latest Open Graph audit report for that page. If we restrict a site under the Terms, we store its status (rate-limited, new cards paused, or suspended), the reason and when it ends, and show them to you in the console.
  • Account information provided at sign-up, such as your name, email address, and password (stored as a secure hash). If you sign in with Google or Facebook, we receive your name, email address, and profile image from that provider instead.
  • For API keys: the key's name (the one you choose, or the client name an approved request reported), its first 11 characters, a one-way hash of the key (never the key itself), how it was created, the user agent of the browser or program that created it, and when it was created, last used, and revoked.
  • For key requests started by an agent or program: the client name and user agent it reports, the short code shown to you, whether you approved or denied it and from which account, and when that happened. We store only a hash of the secret the requester uses to collect the key.
  • When you start checkout for a site: its Stripe customer identifier and, once subscribed, the subscription identifier, plan, status, billing period and whether it is set to cancel, plus which subscription emails we sent. Your card or other payment details go directly to Stripe; we never receive or store them.
  • For short links: the destination URL and the page's title, description, site name, type and language, read when the link is created; on Business, the custom short-link domain you set, with its status and when it was last checked and verified.
  • Messages, feedback, or other information you send to us directly.

3. Information collected automatically

When you use LinkMagnet, we may collect technical and usage information such as browser details, device information, IP address, approximate location, referral information, and interactions with the site. Some of this information comes directly from your browser or from infrastructure and analytics providers we use to run the service.

When a program uses your key through the API, the MCP server, or the command-line client, we update the time the key was last used, at most every five minutes. The command-line client identifies itself in its user agent. It names its key requests "linkmagnet CLI" unless you give another name, and it stores your key in a file on your own computer (or reads it from an environment variable); we keep only a hash. A new key is shown once in your browser, and we exclude it from session replay.

On supported website pages, we may use Microsoft Clarity to better understand how visitors navigate and use the site through behavioral analytics such as page views, clicks, scrolling activity, session replay, and heatmap-style insights. We use this information to improve site content, navigation, usability, and overall product experience. We do not use Microsoft Clarity on LinkMagnet short-link redirect pages under /s/*.

5. Cookies and similar technologies

LinkMagnet uses cookies and similar technologies for authentication, security, analytics, and basic site functionality. This includes a persistent cookie called better-auth.last_used_login_method, set for 30 days, that remembers which sign-in method (Google, Facebook, or email) you last used so we can highlight it on your next visit. We also set a session cookie called NEXT_LOCALE to remember the language you selected during your visit.

Our analytics and site tooling providers may also set or read cookies and similar technologies to help us understand site usage, measure performance, and improve the service.

6. How we use information

  • Provide, maintain, secure, and improve LinkMagnet.
  • Authenticate users and support account access.
  • Create short links, previews, reports, and analytics dashboards.
  • Understand how visitors use supported website pages so we can improve content, navigation, usability, and product experience.
  • Detect abuse, fraud, bugs, and security incidents, for example by reviewing how many new cards each site draws per day, how many sites an account creates, and how many API key requests a program makes.
  • Send transactional and onboarding emails, such as email verification, password reset, and welcome messages.
  • Process subscription payments and send subscription emails.
  • Respond to support requests and communicate about the service.
  • Comply with legal obligations and enforce our Terms.

7. Service providers and third parties

Depending on the feature used, LinkMagnet currently relies on third-party providers for infrastructure and product functionality, including analytics and session replay tooling on supported website pages.

  • Google for account authentication via Google Sign-In.
  • Meta (Facebook) for account authentication via Facebook Login. Meta receives an OAuth request and returns your name, email address, and profile image.
  • Meta (Graph API) and LinkPreview for reading the link-preview metadata of URLs submitted to the Open Graph validator.
  • Resend for transactional email delivery, including email verification, password reset, and subscription emails.
  • Stripe for checkout, subscriptions, invoices and the customer portal. When checkout is started for a site, we create a Stripe customer with your account email, the site name, the site and account identifiers, and your language. Stripe processes subscription payments; we do not send it render counts or other usage data. Stripe collects your payment details and billing address directly and handles them under its own privacy policy.
  • Vercel for hosting, TLS certificates for custom short-link domains, and analytics-related site tooling.
  • Google Tag Manager for deploying analytics-related and site tooling.
  • Microsoft Clarity for behavioral analytics such as session replay and heatmap-style insights on supported website pages.
  • Sentry for error monitoring and debugging.
  • 404found.love, which shows adoptable pets on our page-not-found and missing short-link pages. That page loads in a frame from 404found.love, which receives your IP address, browser details, the LinkMagnet address you came from and a source tag; it may use your approximate location to pick nearby pets.
  • Neon (Postgres) for application data and analytics storage.
  • OpenAI for some AI-assisted preview and summary features, including short captions generated from the title and description of pages on your verified sites when that option is enabled.

8. How we share information

We may share information with service providers that help us operate LinkMagnet. We may also disclose information if required by law, to protect rights and safety, to investigate abuse or security issues, or in connection with a sale, transfer, or restructuring of the service.

We do not sell personal information for money.

9. Retention

We retain information for as long as reasonably necessary to provide the service, maintain security, comply with legal obligations, resolve disputes, and enforce our agreements. We may keep aggregated or de-identified analytics longer.

Key requests expire after 15 minutes and are deleted within two days of being created. If you approve a request, the client name and user agent it reported are kept with the resulting API key. Revoked API keys stay on record, marked revoked, until your account data is deleted, so we can investigate past access; they no longer appear on your API keys page.

Billing records for a site (its Stripe identifiers, plan and subscription status) are kept for as long as the site exists. Records of processed payment notifications are deleted after 90 days. Deleting a site removes our billing records for it; the Stripe customer created for the site (email, site name and identifiers), its invoices and payment records stay with Stripe as required for tax and accounting.

The latest audit report for each page you check from the console is kept until you audit that page again, remove its domain, or delete the site.

When we rate-limit a site, pause its new cards, suspend it or unverify one of its hostnames, we keep a record of the action: the site, account or hostname it applies to, the reason, any note our staff wrote, who took it and when it ends. These records are kept to enforce our Terms and handle appeals, and they stay after the site or account is deleted.

Short-link click statistics are kept for up to 18 months; deleting a link, or the site it belongs to, removes the link and its statistics immediately. Removing a custom short-link domain, or deleting its site, detaches the hostname from Vercel and deletes our record of it. Rendered cards and cached site icons are kept for up to 14 and 30 days respectively and are then purged. Deleting a site removes its hostnames and render counts immediately; cards already cached expire on their own schedule.

10. Your choices and California rights

You can contact us to request access to, correction of, or deletion of certain personal information, subject to applicable law and exceptions. California residents may have additional rights under California privacy law, including the right to know what categories of personal information we collect and the right to request deletion.

To request deletion of your data, email contact@linkmag.net with the subject line "Data Deletion Request". We will acknowledge your request within a few business days and complete the deletion within 30 days, subject to any legal obligations that require us to retain certain records. See our Data Deletion Instructions page for full details.

11. Children's privacy

LinkMagnet is not intended for anyone under 18, and we do not knowingly permit accounts for minors. We also do not knowingly collect personal information from children under 13. If we learn that we collected personal information from a child under 13, we will take reasonable steps to delete it.

12. Security

We use reasonable administrative, technical, and organizational measures to protect information, but no method of transmission or storage is completely secure. As a result, we cannot guarantee absolute security.

13. Changes and contact

We may update this Privacy Policy from time to time. When we do, we will post the revised version here and update the last updated date.

Privacy questions or requests can be sent to contact@linkmag.net.