rlist Chrome Extension Privacy Policy

1) What extension data we process

The extension reads the active tab URL when you open the popup or use the keyboard shortcut so we can prefill the link you want to save.

The extension processes URLs and optional tags that you submit, and it may request page metadata (title, description, favicon, domain) to show a preview before saving.

During login, the extension processes your email address and password through the authentication flow so you can access your account.

• Personally identifiable information: account email and related account profile data.
• Website content: submitted URL and optional metadata shown in preview.
• Authentication information: credentials provided by you during sign in.

2) Extension permissions and why they are required

The extension requests only the permissions needed for core functionality.

• `activeTab` and `tabs`: read the current tab URL when you intentionally open the extension or use its command.
• `storage`: keep minimal extension-local state such as `pendingUrl` and `hasSession`.
• `commands`: support the keyboard shortcut to open and prefill the save flow.
• Host permissions are limited to configured Convex backend domains used to authenticate and save user data.

3) How we use extension data

Data is used only to sign you in, prefill the URL input, fetch preview metadata, and save links/tags to your own rlist account.

We do not use extension data to build advertising profiles or for purposes unrelated to the extension’s single purpose.

4) Data storage and transfer

A small amount of local state is stored in Chrome extension storage (`pendingUrl`, `hasSession`) to support extension UX.

Submitted content and account-related requests are sent to the rlist backend over network requests to configured service endpoints.

5) Data sharing and sale

We do not sell or transfer extension user data to third parties except service providers needed to run rlist.

We do not use or transfer extension data for creditworthiness or lending decisions.

6) Retention and deletion

Locally stored extension state can be cleared by removing extension storage or uninstalling the extension.

For account-level deletion requests covering saved content associated with your account, contact us using the details below.

7) Contact information

For Chrome Extension privacy questions or deletion requests, contact: support@rlist.app.

8) Policy changes

We may update this policy as extension features evolve. The effective date above indicates the latest version.