Operated by Link 2 Link

Optional measurement preferences and withdrawal

Operated by Link 2 Link, a pilot based in San Diego, California. The operator handles support and abuse reports at support@li2.li. This wording identifies the public brand and does not represent a registered company. This is an individually operated pilot.

Support, privacy requests and abuse escalations: support@li2.li.

Daily analytics cleanup is scheduled for 03:10 UTC: expired conversion receipts, conversion-event deduplication records older than 90 days, and daily metrics before the UTC 90-day cutoff. Scheduling and day granularity can extend retention beyond exactly 90 days. Copies outside the verified backup plan, older logs, moderation records and integration receipts have separate, unresolved retention periods. This notice does not claim legal compliance.

Policy version 2026-10-26-operations

Privacy notice

Recovery-copy disclosure revision: October 29, 2026.

Optional first-party acquisition measurement is separate from account registration consent. With explicit permission before a new signup, it records a pseudonymous account identifier, approved first/last source, medium and campaign labels, and signup, email verification, first-link and returning-creator timestamps. Returning means creating another link on a later UTC date, not merely signing in. No referrer, raw URL, advertising ID, email address or link destination is stored in this measurement record, and nothing is sent to advertising services. Unknown attribution is not labeled as direct traffic.

The campaign touch window lasts up to 30 days within the current browser session, which can expire sooner. Milestone collection stops 180 days after signup. Records then become eligible for bounded daily deletion; scheduling and backlogs can extend storage. Signed-in withdrawal or account deletion removes the active measurement record even when collection is disabled. Anonymous withdrawal clears only the current session. New operator-created logical recovery backups exclude measurement records and browser sessions. Our weekly DigitalOcean whole-disk backups may contain those records and scoped error logs and are configured for 28-day retention. Withdrawal removes active measurement records but does not alter those recovery copies or immediately erase data from disk images. Our recovery procedure requires restored servers to remain isolated until all restored measurement records and sessions are cleared, before service reopens; users must sign in again. New Li2.li application and web error logs target seven-day expiry, with up to one extra day for daily cleanup; failures may delay expiry. The seven-day log target applies to active scoped logs, not their whole-disk recovery copies. Retention of older archives and copies outside the verified backup plan has not been established; provider-internal and security copies are separate and are not immediately erased by withdrawal. Collection remains disabled until required backup coverage and safeguards are verified. See the measurement preferences page for the current collection state and your choices.

Account registration and deletion generate private operational emails to the operator. They include your name, email, signup/event time, verification state and, for deletion, account lifetime, alongside aggregate account-count charts. No passwords, authentication tokens, destinations or visitor data are included. The encrypted sending snapshot is removed after successful delivery; undelivered snapshots become ineligible for sending after seven days and are removed by bounded daily cleanup. Minimal delivery records (account ID, event kind, timestamps, state and attempt count) are removed after 90 days. Daily scheduling or a processing backlog can extend storage beyond the cutoff. Uncertain deliveries are not automatically resent. Copies already delivered to the operator's mailbox and backups have separate retention; deleting your account does not retract an email.

We use your name, email address, password hash, verification state and policy acceptance version/time to provide accounts and secure access. Optional two-factor and passkey data support those authentication features. We store link titles, destinations, slugs, status and aggregate redirect counts to operate the service.

Sessions can store IP addresses, browser user agents and session data. Request throttles use short-lived identifiers. Application and server logs may contain request metadata and errors; do not put secrets or personal information in link destinations. The service does not fetch destination pages or send submitted URLs to an external malware scanner. Visitors who follow a short link contact the destination site, which has its own data practices.

Essential session and security cookies support login and protect the service. Interface preferences support the appearance you choose. The Privacy choices button lets you reject optional services, choose categories, or withdraw at any time without losing site access. Optional Google and YouTube resources remain blocked before permission. Google Tag Manager (GTM-56K4M892) is enabled only when both Analytics and Marketing are allowed: this shared container has not yet been audited for independent category enforcement. Allowing either category alone does not load it. Google loading is restricted to anonymous marketing, blog and documentation pages without query strings or fragments, excluding account, login and recovery pages. Unsafe incoming referrers also block Google. We suppress outgoing browser referrers to avoid passing private page URLs to later pages or services. Tags in the container may receive IP address, request headers, page and browsing information and set provider cookies. The exact active tags, recipients and provider retention still need review; this notice does not claim that a particular analytics or advertising tag is active.

Privacy choices are saved locally in this browser under li2li.cookie-consent.v1 with a notice version and choice timestamp. A choice is valid for up to 180 days; expired records are cleared and a new choice requested on the next visit. They are not synced across devices. Global Privacy Control and Do Not Track keep all optional categories off, even if a previous choice allowed them. Rejection does not withdraw separate first-party acquisition measurement permission: use measurement preferences for that. Withdrawing Google or media permission reloads the page to stop previously loaded provider code and removes known accessible first-party Google/advertising cookies where possible. It cannot erase HttpOnly, provider-domain, other-path cookies, already sent data or provider backups; use provider privacy tools or contact support@li2.li for help. Cookies from sites you visit through short links are controlled by those sites.

YouTube privacy-enhanced embeds stay off until External media is allowed and you choose to load a video. YouTube then receives connection information and may use storage during playback. Blocking optional scripts, deleting browser storage, or a failed preference save keeps optional services off. These technical controls are not a certification of compliance with every jurisdiction. Google privacy information.

Email verification and password recovery use the configured mail service. Development mail is logged locally, not delivered. Production password checks may use the Have I Been Pwned password service through Laravel's hashed-prefix lookup; plaintext passwords are not sent by that check.

Optional features and data sharing

Link settings may include tags, expiry times and password hashes. Team workspaces store membership roles and invitation acceptance. Published bio pages and social-preview text are public; do not put confidential information in them. Membership determines access to shared links; a departing member's shared work stays with the workspace owner.

Daily aggregate metrics record link, date and variant totals without raw visitor IPs in the metrics tables. A/B tests use a session assignment so repeat visits in that session use the same variant until settings change. If an owner explicitly enables conversion attribution, a short-lived encrypted receipt is added to the destination query string. The destination can receive and log it; authenticated API submissions record event type and deduplication identifiers. This is not a hidden tracking pixel or proof of a purchase. Session/request logs remain subject to the separate notices above.

Developer token hashes and scopes, domain ownership proof, webhook endpoints and encrypted signing secrets support optional integrations. Explicitly configured webhooks can send link IDs/slugs and event types to their recipients when operator delivery is enabled; no destination URLs or visitor identifiers are included. Delivery records contain status and attempt information. No webhook recipient is configured by default. Customer-domain setup checks DNS ownership proof and submits the requested hostname to Cloudflare for certificate provisioning and routing. Cloudflare processes traffic for active customer hostnames. Customers must configure the displayed DNS records; onboarding is not active until ownership and HTTPS checks pass.

Analytics pruning is configurable and must be run by the operator. Configuration alone does not guarantee deletion from logs, backups or third-party systems. The specific cleanup scope and unresolved retention periods are disclosed below.

Authorized platform administrators can review account and workspace information, link destinations, aggregate activity and abuse reports across workspaces for operation and moderation. Credential fields are excluded from the Admin dashboard. Moderation and role changes record actor and target IDs, action, reason, state change and time. No fixed audit-retention period has been established.

Operational logs and private support

We record email category, recipient count, attempt or transport-acceptance phase and timestamp for operational troubleshooting, retained for 30 days. We do not store email addresses, subjects, bodies or authentication links in this log. Transport acceptance is not proof of inbox delivery. Browser error reports contain only a coarse error category, grouped count and first/last timestamps, not raw errors, stacks, inputs, URLs or user identifiers. Inactive groups are removed after 90 days; counts for active groups can span longer.

For product reporting we record your account ID, UTC date and successful link creation or edit action, retained for 180 days. Reports distinguish observed link activity from login retention and do not provide advertising attribution. Collection is not retroactive.

Private support stores your account ID, request title/type/status, message text, timestamps and retry/read identifiers. Only you and authorized platform administrators may access your conversations. Do not send passwords, authentication links or other secrets. Self-hosted live notifications contain only a change signal; message content is fetched through authenticated access checks. Resolved conversations are removed 90 days after their last update. Unresolved conversations are retained while needed; those inactive for 180 days are flagged for operator review rather than automatically deleted. Account deletion cascades to owned conversations and messages authored by that account.

A bounded daily operations cleanup applies these periods to active tables. Scheduling or a backlog may delay removal beyond the cutoff. Recovery copies follow the backup policy above. Retention of other provider/mailbox copies remains separate and is not changed by this cleanup.

Providers and retention

DigitalOcean hosts the application and database. Cloudflare provides DNS and customer-domain certificate provisioning and tunnel routing, and processes requests to active customer domains. AWS SES in Oregon sends account verification and recovery email. Mailcow receives operator mail. User-configured webhook recipients receive the minimal event data described above. Provider retention and contractual details still require review.

The selected analytics policy is 90 days for daily metrics and conversion-event deduplication records; conversion receipts expire after 24 hours by default. A daily 03:10 UTC cleanup applies these limits to the active analytics tables; it does not erase other records or provider copies. Lifetime link visit counters are separate and are not reset by analytics pruning. Outside the active scoped-log policy and verified 28-day whole-disk backup plan described above, no deletion period has been confirmed for older archives and logs, other provider-held copies, abuse reports, admin audit records, webhook delivery records or legacy migration receipts.

Deleting a link removes its destination and associated reports from the active database. Account deletion removes the account, personal links and bio page, passkeys, API/webhook credentials, database sessions and current-email reset tokens. Shared workspace links remain with their owner. Owned workspaces must be explicitly deleted first, which removes their shared links for every member. Slug-only reservations remain permanently. Legacy migration receipts also retain source record IDs, former numeric owner IDs and content fingerprints to prevent accidental reimport; they contain no separate destination copy. Their retention and deletion-request handling require operator review. Logs, backups and provider-held copies are not erased immediately by account deletion. Their handling must follow the reviewed retention notice above.

Ask the operator for access, correction, an export, deletion assistance or a privacy concern. CSV export of accessible links is available; contact the operator for other account-data requests. The measurement preferences described above control our optional first-party acquisition records only; use Privacy choices to control Google Tag Manager or tags configured in its container. The first-party retention and deletion periods above do not establish retention periods for Google or other tag providers. Contact support@li2.li with questions about marketing and analytics processing. Details of any additional marketing tags, their recipients, retention and applicable consent choices must be reviewed before those tags are enabled.

Operator

Operated by Link 2 Link.

support@li2.li