What GetGuise knows about you.

Who we are, and what this covers

GetGuise is run by an individual sole operator based in the Philippines. In this policy, we means that operator, and the app means GuiseApp, the Windows program you download from this site.

It covers www.getguise.com, the app, and the account, catalogue and entitlement services both of them talk to. It does not cover Twitch, YouTube, OBS, Discord or anything else you point at the avatar once it is running — those are other companies' products with their own policies.

What the website measures

The website runs Google Analytics 4 and the Meta pixel. Between them they record which pages you opened, which site or ad sent you here, roughly where in the world your IP address is, what browser and device you are on, and whether you clicked a Download button.

The Meta pixel is not there to count anything twice. It exists so that a Meta ad campaign can learn which clicks led to a download, because the campaign cannot optimise toward a result it never hears about.

None of this is tied to your name, and none of it is joined to your GetGuise account. The download endpoint also keeps ordinary server logs — request time, IP address, user agent — which is how a download count survives an ad blocker.

What an account holds

An account exists so that avatars you bought follow you to a new machine. Creating one takes an email address and nothing else. There is no password: you ask for a code, we email it, and typing it back proves the address is yours.

What is stored against the account: your email address, an account identifier, the times you signed in, the products you are entitled to, and — if you use AI Create — the balance and history described in section 6. The sign-in codes themselves are minted and verified by Supabase, our authentication provider, and delivered by Resend, our email provider.

Sign in with Google

If you choose Sign in with Google, Google asks your permission and then passes us four things: your name, your email address, your profile picture, and the identifier Google uses for your account.

They are used for one purpose — creating your GetGuise account, recognising you when you come back, and showing you which account you are signed in as. That is the entire use.

• We request no other Google permission. No Gmail, no Drive, no Calendar, no YouTube, no contacts.
• We never receive your Google password. The sign-in happens on Google's own pages.
• Data received from Google is never sold, never used for advertising or ad targeting, and never used to build a profile. It is shared only with the providers in section 8 that store the account itself.
• We do not use Google user data to develop, improve or train any general-purpose model.

You can revoke our access at any time from your Google account permissions page. Revoking stops any further sign-in; to remove the copy we already hold, ask us to delete the account as described in section 11.

What a purchase tells us

Checkout is handled by Gumroad or Lemon Squeezy, and card details go to them. They never reach us and never touch our servers — we could not show you your own card number if you asked.

What each sale sends us is the buyer's email address, what was bought, and the order identifiers, which we store so that the purchase can be granted to an account and reconstructed by hand if something goes wrong. Buying before you have an account is the normal order of events: the purchase parks against that email address until an account with the same address claims it.

What AI Create stores

AI Create stores the descriptions you type, the images generated from them, and your credit balance and its history. Your descriptions are sent to the model provider that draws the image; the finished files come back to your machine and into your account's backup, so a new PC gets its library back.

A creation is a file in a folder you own, and the copy in your account is a safety net rather than the original. Deleting your account deletes that copy and the record of it; the files already on your disk are yours and stay where they are.

What the app sends, and when

The app reaches the network for three things: asking the update feed which version is current, asking the catalogue which avatars exist, and — when you are signed in — asking which of them this account owns. Each request carries what any web request carries, your IP address among it, plus your session token for the third.

Nothing about your webcam, your microphone, your screen or your stream is ever part of that. Every one of those three calls can fail without costing you an avatar you already have.

Who else handles it

These are the companies that see part of the data because they run part of the service:

• Supabase — accounts, sign-in, entitlements, and the cloud copy of your creations.
• Resend — delivering sign-in codes to your inbox.
• Google — Analytics on the website, and Sign in with Google if you use it.
• Meta — the advertising pixel on the website.
• Gumroad and Lemon Squeezy — taking payment and telling us what was bought.
• Our website host and the provider that generates AI Create images.

Their servers are outside the Philippines, and likely outside your own country, so using GetGuise means your data is processed abroad. We do not sell or rent data to anybody, and we hand it over to anyone else only where the law requires it.

Cookies, and turning the measuring off

The only cookies this site sets are the analytics and advertising ones in section 2. Nothing here needs a cookie in order to be read.

You can block them in your browser's settings, install Google's Analytics opt-out add-on, or change what Meta may use from your Meta account's ad settings. Blocking any of it costs you nothing: the app, your account and your purchases work exactly the same.

How long any of it is kept

• Account data — kept while the account exists, and removed when you ask us to delete it.
• Purchase records — kept after deletion where accounting, tax or chargeback rules require it. That record is the order, not a working account.
• Analytics — kept for the retention window configured in Google Analytics, after which only aggregate reporting survives.

Your rights, and how to use them

You can ask for a copy of what we hold, ask for it to be corrected, ask for it to be deleted, object to how it is used, or withdraw consent to the analytics. These rights come from the Philippine Data Privacy Act of 2012, and from the GDPR, UK GDPR or your local equivalent where those apply to you.

Write to support@getguise.com from the address on the account and we will answer within 30 days. Deletion is exactly what it sounds like: the account goes, and with it the list of what you own, which means avatars bought under it stop being restorable. Files already on your PC are unaffected.

Children

GetGuise is not directed at children under 13, and we do not knowingly collect anything from one. Where your country sets a higher age for consenting to data processing on your own, that age applies instead. If you believe a child has an account here, write to us and we will delete it.

Security

Accounts and entitlements sit behind row-level security, so one account cannot read another's rows, and the tables written by payment webhooks are readable by nobody but the service itself. Sign-in codes expire, and requests for them are rate limited. None of that is a promise that nothing can ever go wrong; it is what is in place.

Changes to this policy

When this policy changes, the date at the top changes with it. If a change materially affects what we collect or what we do with it, we will say so on the site, and by email where we have an address for you.

Contact

Questions about this policy, or about anything above, go to support@getguise.com. The companion document is the Terms of Service.