Web Store Extensions

Privacy

This policy describes how information is collected, used, and protected in connection with the directory and related services.

Scope

It applies to visitors, registered users, and makers who submit extensions to Web Store Extensions. By using the site, you agree to this policy together with the Terms of Service.

Information we collect

Account data: When you register, we process identifiers such as email address, password hash (handled by the authentication provider), and profile fields you choose (for example display name, username, bio, and links).

Listing and content data: Submissions include text, metadata, and URLs you provide for extensions. Community posts and comments are stored with your account association.

Technical data: Standard server and application logs may include IP address, device and browser type, timestamps, and pages requested, used for security and reliability.

How we use information

We use data to operate and improve the directory, authenticate users, moderate content, communicate about your account or listings where appropriate, comply with law, and protect the service and its users.

Storage and processors

Data is stored with infrastructure and database providers (for example Supabase and hosting used for this deployment). Those providers process data under their agreements and security practices. We do not sell your personal information.

Cookies and sessions

Session cookies or similar technologies keep you signed in. You can clear cookies through your browser; doing so may require you to sign in again.

Retention

We retain information for as long as your account exists, as needed to provide the service, or as required for legal, dispute, or safety purposes. Some data may remain in backups for a limited period after deletion.

Your choices

You may update certain profile fields in Account settings. To exercise other rights (such as access or deletion) where applicable, contact us through Contact.

Changes

We may update this policy from time to time. The revised version will be posted on this page with an updated effective date when we adopt that practice.

Effective: March 2026