Privacy Policy

1. Information We Collect

We collect the data needed to operate accounts, storefront pages, uploads, and subscription access.

• Account data such as name, email address, username, and login method.
• Account access state such as approval status and related admin review history.
• Storefront content such as page title, bio, avatar, social links, product details, and affiliate URLs.
• Custom-domain records such as hostname, DNS verification state, and related provisioning status.
• Uploaded assets such as product images and profile images.
• Session, device, and request data used for authentication, security, and abuse prevention.
• Subscription and billing records such as plan status, manual adjustments, transaction IDs, and payment state when billing is enabled.
• Operational and admin records such as audit logs, support notes, and subscription override history.

2. How We Use Information

• To create and secure user accounts.
• To review, approve, or restrict dashboard access.
• To render public storefront pages and product detail pages.
• To connect, validate, and maintain optional custom domains.
• To store and serve uploaded media.
• To enforce plan limits, protect the service, and investigate abuse.
• To maintain subscription state and reconcile payment events if paid billing is enabled.
• To provide support, resolve billing issues, and maintain operational logs.

3. What Becomes Public

Storefront content is public by design. If you publish a public page, other people may be able to view your display name, avatar, bio, social links, product catalog, affiliate disclosure text, and product images.

Account email addresses, internal approval records, session records, and internal billing logs are not intended to be public.

4. Third-Party Services

Byzhop currently depends on infrastructure and selected sign-in or payment providers to operate the service.

• Cloudflare is used for application hosting, database, object storage, caching, and edge delivery.
• Google OAuth is used for account sign-in and account creation.
• Cloudflare Turnstile may be used on sensitive auth entry points to reduce automated abuse.
• Midtrans may be used later for payment checkout and payment status notifications if paid upgrades are enabled.

We do not store third-party marketplace credentials in the MVP. Affiliate destinations are stored as links, not as marketplace account passwords or API secrets.

5. Cookies, Sessions, and Security

We use authentication cookies and session storage to keep users signed in, protect dashboard access, and help detect suspicious activity. We may also use request metadata, anti-abuse challenge verification, and internal security logs to protect authentication entry points and maintain service reliability.

6. Retention and Deletion

We retain account and billing data for as long as needed to operate the service, resolve disputes, investigate abuse, and maintain financial and operational records. Public storefront content may remain available until the account owner removes it or the operator deletes the account.

When supported operationally, the operator may delete or anonymize data after account closure, subject to security, billing, fraud-prevention, and legal recordkeeping needs.

7. User Choices

• Users can edit or remove storefront content from the dashboard.
• Users can remove uploaded assets through supported product and page management flows.
• Users can remove a connected custom domain and continue using the fallback Byzhop URL.
• Users may request account closure or data review through the support channel published by the operator.

8. Children and Restricted Use

Byzhop is intended for adult creators and operators. Do not use the platform if you are not permitted to enter into a digital service agreement in your jurisdiction.

9. Policy Updates

The operator may update this Privacy Policy as the platform adds new providers, analytics, support tooling, billing flows, or legal requirements. The date at the top of this page will be updated when material changes are published.