Privacy Policy

1. Who operates GetLinker

This policy covers the GetLinker website at getlinker.app and the GetLinker Chrome extension published by this project. The service operates under the name GetLinker. For support, privacy questions or deletion requests, email [email protected].

This project does not operate the former publisher’s extension listing or have access to that publisher’s accounts or cloud data.

2. Information we handle

Open tabs and saved libraries

The extension reads eligible tabs in the current Chrome window to display their URLs, titles, active or pinned status, and tab-group names and colors. It uses this information for the Open tabs view and the save, group and restore actions you choose. It does not read Chrome’s browsing-history database, cookies from other websites, full page contents, passwords, typed keystrokes or unsaved form values. Incognito and browser-internal tabs are excluded from its save/list operations.

When you save something, your library can contain collection names, URLs, page titles, notes, favorites, tab order, pin state and group metadata. Preferences include your appearance choice. Saved URLs and notes contain the information you choose to keep; avoid saving secrets you do not want stored.

Accounts and authentication

Google or email sign-in is handled through Supabase Auth. Authentication records include your account ID and email address. Google may provide basic profile information such as your name and profile image. GetLinker does not receive your Google password or request access to Gmail, Google Drive or your contacts. Authentication uses access/refresh tokens and one-time codes or links so your session can work.

Technical requests

Our hosting and service providers process technical information needed to deliver and protect the service, such as IP addresses, request times, device/browser information and operational logs. We do not currently use an analytics or advertising tracking service.

3. Local saving and optional cloud sync

Without signing in, the website keeps its device-only library in browser IndexedDB and the extension keeps its local library in Chrome extension storage. These local libraries are separate and are not automatically uploaded.

When you sign in, GetLinker loads a separate private account library. Changes made in that account library are sent through GetLinker’s API to Supabase so the same account can use them on the website and extension. Copying existing device-only saves into the account is a separate action with a confirmation. Export/import can also transfer a copy.

Account libraries are cached on your device so edits can survive a connection failure. Signing out removes the active session but retains account caches, pending edits and conflict-recovery copies for the next sign-in. This does not expose them as public collections. Use a trusted browser profile; GetLinker does not encrypt these local caches against someone with access to that profile.

Public collection snapshots

From your signed-in website library, you can choose Share collection, review the preview and publish a separate public snapshot. It contains the collection title, description and ordered link URLs/titles. Link notes are excluded unless you select the option to include them. Account email, tab-group details, pinned state and other private metadata are not part of the public page.

Anyone who knows or discovers the public URL can read the snapshot without signing in. Public pages are not currently listed in a directory and ask search engines not to index them; this does not make them confidential. Visitors and third parties can copy or retain published information. Review URLs, titles, descriptions and any included notes for personal information before publishing.

Private edits are not automatically published. Choose Publish updated snapshot to replace the public copy after reviewing it. Take page offline stops public access through GetLinker. Deleting the source collection after successful cloud sync also takes its snapshot offline. These actions cannot erase copies already made by visitors or third parties. Offline snapshots and their reserved addresses remain associated with your account so you can republish them; account deletion removes the associated publication records.

To report a public collection, use its Report this collection link or [email protected].

4. Providers and sharing

Chrome supplies favicons through its extension favicon API. GetLinker does not send your tab list to an external favicon lookup service. Opening a saved link visits its destination website, whose own privacy practices apply.

We share information with these providers to operate the features described here, or when necessary to comply with a valid legal obligation or protect the service. Providers may process data outside your country. We do not sell or rent personal data or use saved browsing data for advertising, unrelated profiling or training AI models.

5. Permissions and security

Chrome permissions support listing and saving tabs, restoring tab groups, local storage, context menus, the side panel, sign-in, favicon display and scheduled sync retries. Network host access is limited to GetLinker and its Supabase project. The extension does not inject content scripts into websites or request all-sites host access.

Cloud requests use HTTPS. Authentication secrets are not included in the extension’s public source. The extension keeps session credentials in trusted extension storage. Saved libraries are not end-to-end encrypted; local storage and exported backups are not encrypted by GetLinker.

GetLinker’s handling of information received through Google APIs complies with the Chrome Web Store User Data Policy and its Limited Use restrictions.

6. Retention, deletion and your choices

Saved account content is retained until you delete it or request account deletion. You can edit collections, remove links, delete collections, and export JSON or Markdown backups. A cloud deletion takes effect after successful sync. Revision numbers and deletion identifiers may be retained to prevent deleted content from reappearing during synchronization.

To request deletion of your account and associated cloud library, email [email protected] from your account’s email address. We may need to verify that you control the account before processing the request. There is currently no self-service account-deletion button.

Cloud deletion does not erase downloads, local caches, conflict-recovery copies, or copies on another device. Clear the relevant website/extension data or uninstall the extension to remove those local copies. Export anything important before clearing data. Service backups and operational records may remain under the relevant providers’ retention practices.

When an existing development extension migrates older local stashes/bookmarks, original storage keys can remain as recovery copies. Deleting a migrated collection does not erase that legacy copy. A different extension ID cannot automatically read the old extension’s storage.

7. Changes and contact

We will update this page when practices change and update the effective date. Material changes to data use will be disclosed through the appropriate product or store notice.

Contact: [email protected]