1. What this notice covers

This Cookie Notice applies to:

It works alongside our Privacy Policy — read both together for the full picture.

2. What are cookies?

Cookies are small data files that a website saves to your browser. They let the site remember things between page loads, keep you signed in, count unique visits, or run features like embedded videos.

Cookies we set ourselves are first-party cookies — only Alllinks can read them. Cookies set by another company embedded on a page (a YouTube player, a Spotify embed, a Stripe checkout) are third-party cookies — they belong to that company and follow that company's privacy policy.

Other technologies behave like cookies: localStorage (we use it for things like remembering the last theme you picked in the dashboard), web beacons / tracking pixels in emails, and SDK identifiers in mobile apps. We treat all of these the same way as cookies in this notice.

3. Why Alllinks uses cookies

We use cookies for four specific purposes:

4. The cookies we set

5. Cookies on creator pages

Alllinks creators can choose to add embeds and shop integrations to their pages. When a visitor lands on a profile, the only cookie Alllinks sets is al_visit (counted anonymously for the creator's analytics). Any third-party cookies on the page come from content the creator added — for example, pressing play on a YouTube embed will set YouTube's cookies on the visitor's browser. Creators are responsible for disclosing these in line with their local laws.

6. How to control cookies

If you block strictly necessary cookies, parts of the dashboard — including sign-in, the shop checkout, and analytics — will stop working.

7. Web beacons & email tracking

When we send you a transactional email (welcome, password reset, billing receipt) we may include a tracking pixel to confirm delivery and read state. You can disable image loading in your email client to block these pixels — the emails still work without the images. Marketing emails always include an unsubscribe link.

8. Cookies are not the only tool

We may also use related technologies that don't strictly meet the cookie definition but behave similarly — localStorage and IndexedDB for offline editor state, browser fingerprint hashes for abuse prevention, and SDK identifiers on mobile apps. We treat these as cookies for the purposes of consent and disclosure.

9. Changes to this notice

We update this notice when we add or remove a technology, or when the law requires a clarification. The effective date at the top of the page reflects the latest version. For material changes we'll surface a banner inside the dashboard so account holders see the update.

10. Contact

If you have questions about cookies or want to exercise any of the rights described in our Privacy Policy, email support@alllinks.cc. Billing-specific cookie questions (from Paddle's checkout) can also be raised in your Paddle customer portal.