Skip to content
How2Earn.AI

Privacy policy

Privacy

How2Earn.AI explains what this site collects when you browse or sign in with Google, and what it does not collect.

Published 17 October 2026.

What this site is

How2Earn.AI is a public guide to practical AI work. You can read the homepage, AI Work guides, platform notes, official-source links, videos, projects, and the shop without an account. Google sign-in is optional. It opens your own Account and Library pages. Admin stays limited to the authorized owner.

Checkout, orders, downloads, and payment collection are not enabled. This site does not run advertising, a mailing list, or a product analytics tracker.

Google account data

If you choose Continue with Google, sign-in goes through Supabase Authentication to Google. The app asks only for the default Google identity used to sign in. It does not request Gmail, Drive, Calendar, Contacts, or offline access.

From that sign-in, How2Earn.AI uses:

  • Your Google account email address, shown to you on Account, Library, and the signed-in sign-in page.
  • Your name, when Google supplies full_name or name. If your profile has no display name, the site stores one trimmed name of 1–80 characters.
  • The Supabase user id created for that Google identity. Your profile row uses that id. The app does not copy a separate Google subject id into the profile table.

Google may include other profile fields in the sign-in metadata. How2Earn.AI does not publish that metadata, does not show a profile photo, and does not store Google access or refresh tokens in its profile table.

How that data is used

  • Confirm that you are signed in and show your own email and display name.
  • Create and update only your own profile row.
  • Keep Account and Library private to the signed-in person.
  • Allow Admin only when your user id is in the owner-authorization table.

A display name is presentation only. It does not grant owner access, a purchase, or a download. Google user data is not sold, used for advertising, or used to train a model. The site does not send marketing email.

Providers

  • Google provides the sign-in identity and receives the sign-in request.
  • Supabase hosts authentication and the database tables profiles and owner_authorizations. Row-level security lets a signed-in person read and update only their own profile, and read only their own owner-authorization row.
  • Vercel hosts the website. Serving a page can involve ordinary connection data such as IP address and browser details in the host's logs.

No payment provider, email-marketing provider, or analytics provider is connected. Links to AI-work platforms leave this site and follow those sites' own policies.

Session cookies

After a successful Google sign-in, this website stores the Supabase session in first-party cookies on its own host. Those cookie names start with sb- and belong to this Supabase project. They keep you signed in and let the server confirm your user id. They are not advertising cookies. Public pages do not require them.

Sign out clears the local session. The cookie lifetime is the one Supabase sets for that session. This page does not add a different expiry.

What else is stored

A profile stores its id, display name, and created and updated timestamps. An owner-authorization row stores a user id and a created timestamp. The database deletes those rows when the matching authentication user is deleted.

Browsing public pages does not create an account. There are no orders, downloads, or saved payment details because checkout is closed. Library text says purchases will appear only after checkout exists.

Retention

The email in Supabase Authentication and the profile display name remain while that account exists. There is no separate marketing list and no purchase archive. How2Earn.AI does not publish a separate retention period for Vercel request logs.

Deletion and contact

Sign out removes the session from the browser you are using. The site has no delete-account button. Deleting or disconnecting the Google account does not, by itself, remove the How2Earn.AI profile through this website.

A deletion request should come from the Google account email and ask for removal of the Supabase authentication user, the profile, and any owner-authorization row. Those database rows are removed with the authentication user. The support page is the place that request would go.

No public email address, form, or phone number is published, so How2Earn.AI cannot receive that request through this website today.

Publisher

How2Earn.AI publishes this website and this policy. The policy does not state a separate legal entity, postal address, public email address, or phone number.

The terms describe how the site may be used. They do not change this privacy policy.