Privacy Policy

This Privacy Policy covers the crxbase website, developer dashboard, project pages, API, SDK-backed account flows, and related services.

It covers how crxbase handles information for its own platform. It does not cover a developer's browser extension, website, support practices, or other business activity outside of crxbase.

We collect the information we need to run the service.

• Developer information: email address, authentication and session information, project names, public project icons, plan names, pricing, descriptions, feature lists, and limited account-connection data related to payouts and payment setup.
• End-user information: email address, project-specific account records, verification code requests, subscription status, trial status, and purchase state.
• Payment information: full card details are handled by payment processors such as Stripe, not stored directly by crxbase. We may receive customer IDs, subscription IDs, payment status, and transaction metadata needed to operate the platform.
• Technical and support information: session cookies, request metadata, browser information, service logs, error reports, and support messages used for security, debugging, customer support, and platform operations.

Some developer-submitted project content, including project names, icons, public plan details, and pricing, may be visible on public project pages.

• Operate, maintain, and improve the platform.
• Authenticate developers and end users.
• Send one-time verification codes and manage sign-in sessions.
• Create and manage subscriptions, checkouts, and payout flows.
• Prevent fraud, abuse, unauthorized access, and misuse.
• Respond to support issues, account requests, and platform problems.
• Comply with legal obligations and enforce our terms.

We may share information in the following cases:

• With service providers that help us run crxbase, including infrastructure, database, authentication, email, payment, error-monitoring, logging, and support providers.
• With the relevant developerwhose project page you are using, to the extent needed to operate that project and show account, payment, or subscription status for that project.
• For legal or safety reasons, including when required by law, legal process, or to protect the rights, safety, and security of the platform and its users.
• As part of a business transfer, such as a merger, acquisition, financing, restructuring, or asset sale.

We do not sell personal information.

crxbase depends on third-party providers to run the service.

• Supabase for database and authentication infrastructure.
• Stripe for payment processing, subscriptions, billing, connected-account onboarding, and payouts.
• Supabase Auth and SMTP providers for developer and end-user one-time-code email delivery.
• Sentry for error monitoring, diagnostic event data, and security-focused debugging.
• Third-party sites or forms we link to from the public website.

Those providers process information under their own terms and privacy policies.

We use cookies and similar technologies that are necessary to run the service, including to keep developers signed in to the dashboard and end users signed in to project pages.

We do not use advertising cookies in the application code.

We keep information for as long as reasonably necessary to operate the service, maintain security, resolve disputes, and comply with legal, tax, accounting, or payment-related obligations.

Verification codes are short-lived. They expire quickly, are deleted after use, and expired records are purged on a rolling basis.

Diagnostic logs, Sentry events, and support messages are kept only as long as needed for security, reliability, support, compliance, and business operations.

Project account, subscription, and payout records may be retained longer where needed for billing, fraud prevention, compliance, dispute handling, or legitimate business records.

You may contact us to request access to, correction of, or deletion of your information. We may need to retain some information for security, billing, chargeback handling, fraud prevention, legal compliance, or legitimate business recordkeeping.

If you are an end user of a specific developer's project, the relevant developer may also hold information about your account or purchase and may need to be involved in certain requests.

We use reasonable technical and organizational measures designed to protect the information handled through crxbase. These measures include access controls, project-scoped access boundaries, and short-lived hashed verification codes.

No system is perfectly secure, and we cannot guarantee absolute security.

We may update this Privacy Policy from time to time. When we do, we will post the updated version here and update the effective date above.

For privacy questions or requests, contact support@crxbase.com.