THIS WEEK How to Add Links to Instagram Stories Using GoTo.now: A Simple Guide Read this week's article →
← All templates

Privacy-first redirect

Reduce the source information passed to a destination while keeping the short link editable.

Privacy-first redirect workflow preview

What happens when you use it

The setup is saved to your account, then applied to a short link you choose. Its public URL and default destination stay in place while the listed routing and redirect controls are added.

Review all schedules, destinations, limits, and privacy controls before publishing. Shared templates never copy the creator’s password, account ownership, click history, or private reports.

What this starter includes

Referrer policy

Hide referrer

The destination should not receive the source URL through the browser referrer header.

Redirect status

302 temporary

Browsers and intermediaries are less likely to treat the destination as permanently fixed.

Destination

Your existing destination

The template changes redirect behavior, not the page you selected.

Analytics

Aggregate and IP-free

The setting does not disable GoTo.now's privacy-safe click counts.

Privacy-focused analytics controls separating useful measurements from personal data

Example: a sensitive resource shared across communities

A nonprofit shares a counseling directory through partner newsletters and community groups. The destination does not need to know which referring page a visitor came from, so the link uses a no-referrer policy and a temporary 302 redirect.

GoTo.now can still count the redirect and show privacy-safe aggregate performance, while the destination receives less browsing context. The organization keeps one editable short link without claiming that the destination itself is anonymous or encrypted.

What to preserveReduce the source information passed to a destination while keeping the short link editable.

Set it up carefully

  1. 1

    Confirm the privacy objective

    Decide whether the destination needs campaign source data. Hiding the referrer deliberately removes a useful attribution signal.

  2. 2

    Apply the setup to one link

    Start with a single sensitive workflow instead of changing every campaign by default.

  3. 3

    Inspect the destination request

    Use browser developer tools or destination logs to confirm the expected referrer behavior.

  4. 4

    Document the tradeoff

    Tell collaborators that source analytics at the destination will be less complete.

Where this setup fits

Use it when

  • Sensitive resource directories
  • Cross-organization links where the source should not be disclosed
  • Editable campaigns that do not depend on destination-side referrer reports

Choose another approach when

  • Affiliate programs that require referrer attribution
  • Fraud controls that depend on source context
  • Situations where users might mistake referrer hiding for full anonymity

Questions about privacy-first redirect

Does this make a visitor anonymous?
No. It limits referrer information sent by the browser. The destination can still receive ordinary network and request information.
Will UTM parameters still be visible?
Yes. Query parameters in the destination URL are part of the URL itself and are not removed by a referrer policy.
Why use a 302 redirect?
A temporary redirect is appropriate when the destination can change and avoids signaling that one target is permanently canonical.