BETA H PIXEL

Privacy Policy

This policy explains what information is processed when you browse the gallery, use an account or community feature, or contact Beta H Pixel. It describes the current site code and does not replace the settings or policies of the services that support it.

Last updated: October 5, 2026

1. Information handled by the site

Depending on the features you use, the site may process:

  • Account information: email address and account identifiers used by Supabase Authentication; if you choose Google sign-in, information returned by Google such as your account identifier, name, email, or profile image may be used to create or access the account.
  • Profile information: username, display name, avatar URL, bio, and profile appearance choices that you provide.
  • Community content: posts, image URLs or uploaded images, titles, descriptions, categories, comments, likes, follows, and related timestamps and counts.
  • Digital-feature records: Points, progress, inventory, and membership state used by the shop and membership features. The current site uses Points and does not process real-money purchases.
  • Contact information: name, email, message category, subject, and message text that you choose to submit through the contact form.
  • Technical data: information necessarily handled by the browser, hosting, Supabase, Formspree, Google, and other service providers to deliver requests, protect their services, authenticate accounts, or diagnose failures. Their exact logs and retention depend on their configurations and policies, which we have not independently verified.

2. How information is used

Information is used to authenticate and manage accounts; display profiles, posts, images, comments, and interactions; support follows, notifications, search, Points, inventory, and memberships; upload and serve user images; answer contact messages; maintain and troubleshoot the site; protect the service against abuse; and meet applicable legal obligations.

3. Public profiles and community content

Community profiles, posts, and comments are presented as public community features and may be visible to other users and visitors. Public image URLs and profile details you choose to provide may be displayed with that content. Likes and follows support public interaction and profile counts. Do not publish personal or sensitive information that you do not want others to see, and do not upload an image unless you have the right to share it. The actual access rules are also controlled by the live Supabase policies, which have not been verified as part of this page review.

The site provides controls to edit or delete your own posts and comments. The actual effect of deletion on service-provider logs, backups, or copies is subject to the relevant provider systems and retention settings; those periods have not been confirmed for the live project.

4. Cookies, local storage, and sessions

The site stores the selected interface language in browser local storage. Supabase Authentication is configured to persist and refresh a sign-in session in browser storage and to detect authentication redirects. These storage mechanisms support language preference and account access. The AdSense code is present on selected public discovery, informational, and content pages; ad requests remain paused until the site checks the current account’s membership entitlement. Your browser also handles ordinary network and security data when loading the site.

When Google AdSense is active for the site, Google and its advertising partners may use cookies or similar technologies subject to the serving settings, region, and consent choices that apply. See the Google AdSense section below for information about consent messaging and CMP configuration.

5. Google AdSense and advertising

Selected public discovery and content pages load Google AdSense using our publisher ID. The site is structured for Auto ads; whether ads are served and where they appear depends on account approval and the Auto ads settings in our AdSense account. Google and other advertising vendors may use cookies, web beacons, IP addresses, or similar identifiers to serve, measure, or personalize ads, depending on configuration, region, and consent choices. When personalized advertising is used, vendors may use cookies to serve ads based on prior visits to this or other sites. Users can review or opt out of personalized advertising through Google Ads Settings. Read Google’s Privacy Policy for how Google handles data. Consent and privacy messages are managed through Google AdSense Privacy & messaging; where required, a Google-certified CMP integrated with the IAB TCF must be configured before personalized ads are served.

6. Supabase and other service providers

Supabase is used for authentication, the application database, image storage, and server functions. The site uses the Supabase JavaScript client distributed through esm.sh. Choosing Google sign-in involves Google’s identity service. The contact form sends the fields you submit to Formspree for delivery. Community image search can send a supported post image to a server-side function that requests an image embedding from Google’s Generative Language service; the resulting vector is used to support image-similarity search. This processing happens when the feature is configured and invoked.

These providers process information under their own terms and privacy notices. We have not verified the live Supabase project’s data-region, logging, backup, or retention configuration, nor the Formspree form’s recipient and retention settings. No secret keys are included in this page.

7. Sharing

Information may pass to the service providers described above as needed to host the site, authenticate users, store and deliver content, process community features, provide image search, and deliver contact messages. Information may also be disclosed where required by law or needed to respond to a valid legal process. We do not claim that every provider retains or processes data in the same way.

8. Security and retention

The site uses provider-managed authentication and database services and sends privileged operations to server-side functions rather than placing secret service keys in the browser. No online system can guarantee absolute security. The project code does not establish a single retention period for all account, content, request, log, or backup data; actual periods depend on Supabase, Formspree, Google, hosting configuration, and applicable requirements.

9. Your choices and requests

You can edit profile details and manage your own posts and comments using available site controls. You may also request access to, correction of, or deletion of personal information, or ask a privacy question, through the contact form. There is no self-service account-deletion feature in the current public interface. We will review requests in light of applicable law, technical capabilities, and records we are required or permitted to retain; the live account-deletion and retention procedures have not been confirmed.

10. Children

The project does not currently display a verified age threshold or a dedicated age-check flow. The service is not intended to override age requirements that apply where you live. A parent or guardian who believes a child’s information was submitted can contact us through the contact form so the request can be reviewed.

11. Changes and contact

We may revise this policy as the site or its providers change. The updated date at the top shows when this page was last revised. For privacy questions or requests, use the contact form. Also see our Terms of Use and About page.