Privacy Policy

What L@tr.link handles

When you sign in, L@tr.link handles your AT Protocol account identifier and OAuth authorization information. When you save an item, it handles the URL or AT URI you selected, any tags you wrote, and metadata used to create the library preview, such as the page title, description, image, site name, and author.

The browser extensions only access the active page when you invoke L@tr.link. They do not collect or transmit your browsing history in the background.

Why it is used

This information is used to authenticate you, save and organize the item you selected, build its preview, display your library, prevent abuse, and diagnose service failures. L@tr.link does not sell this data, use it for advertising, or use it for unrelated profiling.

Where information goes

Extension requests pass through the L@tr.link web proxy and gateway. Authentication is completed with the AT Protocol authorization server you select. Saved records are written to your account's Personal Data Server. L@tr.link may request the selected page and metadata services to resolve a useful preview.

Storage and retention

Saved URLs, tags, and Open Graph fields are stored on-protocol in your Personal Data Server until you delete the record or your host applies its own retention rules. L@tr.link caches resolved preview metadata for up to seven days. The extensions store the OAuth session and a pending save locally in browser storage; pending saves expire after five minutes and are cleared after a successful save or sign-out.

Infrastructure providers may retain limited operational logs, such as request route, status, timing, IP address, and error details, for security and reliability.

Your controls

You can archive or delete saved items in your library, sign out to revoke the extension session, clear extension data in browser settings, or remove the extension. Your Personal Data Server remains the authoritative home for saved records.

Chrome Limited Use

L@tr.link's use and transfer of information received from Google APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Questions and changes

Use the support page for privacy questions or requests. Material policy changes will be reflected here with a new effective date.