Company

Privacy Notice

How Glaze Corp handles information when you use the GlazeCorp website: what it collects, who receives it, what stays in your browser and what is public onchain forever.

Updated October 24, 2026

1. Key points

This is a short summary. The full notice below controls.
Anything you do onchain is public and permanent. Your wallet address, your transactions and any fund details, image link or mining message you publish can be seen by anyone. We cannot delete them, and nobody else can either.
You do not give us your name, email address or ID to use the Interface. There are no accounts, profiles or usernames.
Our servers and service providers do receive your IP address and, once you connect a wallet, your wallet address. Some requests carry your wallet address inside the web address (URL).
When you accept our Terms of Use, your wallet signs a message and we keep a record of it: your wallet address, the message, the signature, the Terms version, the network, the website address you signed on and the time. We do not store your IP address with it.
Our host works out an approximate location from your IP address. We do not use it to block or limit access.
On our hosted sites, fund images are checked by AI models from Google or OpenAI through Vercel. Images you upload are then published to IPFS through Pinata, where they are public and may stay forever.
When the wallet window loads, and on every visit while a wallet connection is saved, Reown, the company behind WalletConnect, receives your wallet address, the page you are on and connection events. This happens even though we have turned off its optional analytics.
We do not sell personal information for money, and we do not use advertising trackers. On www.glazecorp.io we use PostHog to count page views and actions, record masked session replays and collect error reports. It never receives your wallet address, what you type or the amounts and balances on the page, and it sets no cookies. Turning on Do Not Track or Global Privacy Control in your browser switches it off (section 8).
We will never ask for your private key or seed phrase. Never send them to anyone.
Questions and privacy requests: admin@glazecorp.io.

2. Who we are and what this notice covers

Glaze Corp LLC, a Delaware limited liability company in the United States, operates the GlazeCorp website at https://www.glazecorp.io. In this notice, “Glaze Corp”, “GlazeCorp”, “we”, “us” or “our” mean Glaze Corp LLC. “You” means anyone who visits or uses the Interface.

“Interface” means our website and everything served from it: its pages, its API routes, the agent tools at /mcp and /api/agents, and any test or preview copy of the site that we run from the same code. “Protocol” means the smart contracts that the Interface shows and helps you use, on Robinhood Chain and, for GLAZE, also on Base. “Onchain” means recorded on a public blockchain, such as Robinhood Chain or Base.

This notice explains what information the Interface collects, how we use it, who receives it, how long we keep it and your choices. It does not cover services run by others, such as your wallet, Reown, block explorers or X. Their own privacy policies apply when you use them.

Where a data protection law uses the term, Glaze Corp is the controller of the personal information described in this notice. You can reach us at admin@glazecorp.io.

3. Onchain data is public and permanent

The Protocol runs on public blockchains. When you use it, your wallet sends transactions that are recorded on Robinhood Chain. GLAZE transfers and the GLAZE bridge also record transactions on Base. Each transaction shows your wallet address, the contract you used, the amounts and the time.

This data is public and permanent. Anyone can read it. Block explorers, indexers and other services copy it and display it, and so does the Interface. Once a transaction is confirmed, no one, including Glaze Corp, can change it, take it down or undo it. It stays on the chain after you disconnect your wallet, clear your browser or send us a privacy request.

Creators and miners publish text and links onchain. This includes a fund’s name, ticker, description, image link, website, X profile, default mining message and fee recipient addresses, and the mining message sent with each mining slot takeover (up to 280 bytes). The creator can later replace the description, image and links, but earlier versions stay in the chain’s history.

A wallet address does not show your name, but it can often be linked to you, for example through an exchange you used, a name service or something you posted. Do not put personal information in anything you publish onchain or upload.

4. Information we collect

We collect only what the Interface needs to work and to stay secure. We do not keep user accounts or profiles. Most information passes through our servers to answer a request and is not stored, apart from the Terms acceptance records described in section 7 and the caches, counters and logs described in section 14.

Wallet address and connection. When you connect a wallet, the Interface saves in a cookie every wallet address your wallet shares with the site, the network and which wallet you used. Your browser sends this cookie to our server with every request, and our server reads it so pages load already connected.
Wallet addresses in requests. To show balances, your portfolio and your activity, the Interface sends requests to our server that include your wallet address. Some put the address inside the web address itself: chain reads (/api/chain/read), indexer queries (/api/indexed), the portfolio card check (/api/portfolio-card), which runs automatically when you open your portfolio, and the Terms check (/api/terms), which runs when you connect a wallet. Addresses you type into a checker, such as the GLAZE check page, are also sent to our server so we can read their balances.
Transactions you prepare. Before you sign, the Interface asks the chain to simulate each transaction and estimate its gas. These requests go through our server and contain your wallet address and the transaction details.
Terms acceptance. When you accept our Terms of Use, your wallet signs a message and the Interface sends the message and the signature to our server, which keeps a record of them (section 7).
IP address, location and device information. Every request to the Interface reaches our host, Vercel. Like any web server, it receives your IP address, your browser and device type, the web address requested, your cookies for this site and the time. Vercel also derives an approximate location (such as country, region and city) from your IP address. Our server uses your IP address to limit how many requests one connection can make.
Images and fund details. When you upload an image while launching a fund, the image and its file name are sent to our server. We check the image (section 6) and pin it to IPFS through Pinata. Still images are cropped and re-encoded in your browser first, which removes embedded photo data such as camera details. GIFs, and images from browsers that cannot re-encode them, are uploaded exactly as you chose them, including any data embedded in the file. The fund details you enter go into your launch transaction and are published onchain (section 3).
Agent tools. Requests to our agent tools include whatever the caller sends, which can include wallet addresses, together with the caller’s IP address.
Messages you send us. If you email admin@glazecorp.io, we receive your email address, what you write and anything you attach.
Public data from other sources. We read public blockchain data through node (RPC) providers and our indexer. We also publish a snapshot of DONUT holder addresses and balances on Base, taken at block 50,924,147 for the move from DONUT to GLAZE. It contains public onchain data about other people’s addresses.

5. Service providers that receive information

We use the service providers below to run the Interface. Each receives what it needs for its task. Some also handle data under their own terms.

Vercel hosts the Interface. It runs our servers, caches some responses on its network and works out an approximate location from each IP address. Its firewall can block or limit traffic by IP address or location. Vercel receives every request, including your IP address, device information, cookies for this site and web addresses that can contain your wallet address, and it may keep logs of these requests. Vercel also runs the AI Gateway we use for image checks.
Blockchain node (RPC) providers. Our server forwards chain reads and transaction simulations to the node providers we use for Robinhood Chain (a main provider and, at times, a separate provider for history reads and a backup). For the GLAZE pages and the GLAZE bridge, it forwards Base reads to Base’s public endpoint (mainnet.base.org) or to a provider we choose, and Robinhood Chain mainnet reads to a provider we choose. To check a Terms acceptance signature (section 7), our server may also send your wallet address, the signed message and the signature to a node provider for Robinhood Chain or Base. These providers see the content of each request, which can include your wallet address, but they see our server’s IP address, not yours. On the testnet version of the site, your browser may also read directly from the public Robinhood Chain testnet endpoint, which then sees your IP address. When the Interface asks your wallet to switch to a network it does not have yet, such as Robinhood Chain or Base, it gives your wallet that network’s public endpoint. Your wallet may then contact that endpoint directly, and it sees your IP address.
Goldsky hosts our indexer, which organizes Protocol data for lists, charts, history and portfolios. Our server, or on some deployments your browser, sends it queries, including your wallet address when you view your portfolio or activity. When your browser queries Goldsky directly, including whenever our server cannot answer, Goldsky also receives your IP address.
Reown runs WalletConnect and the wallet window (AppKit). Its code loads when you open the wallet window, or when you visit with a wallet connection already saved. Reown then receives your IP address, the full web address of the page you are on, your wallet address, the network, which wallet you use, which wallets the window showed you, connection events and error reports from its code. It may also look up a public name or avatar linked to your wallet address. If you connect a mobile wallet, Reown’s relay carries encrypted messages between this site and your wallet app. We have turned off Reown’s optional analytics, but its code still sends the items listed here.
Pinata receives the images you upload, with their file names, and pins them to IPFS. It also serves IPFS content to our server through a dedicated gateway. Filebase’s public IPFS gateway is our backup for reading IPFS content. Your browser never contacts an IPFS gateway: our server fetches the content and passes it on.
Vercel AI Gateway, Google and OpenAI check fund images, as described in section 6.
PostHog (PostHog Inc., United States) provides our product analytics, session replay and error tracking on www.glazecorp.io, as described in section 8. Your browser sends this data to our own site, which passes it to PostHog’s US servers, so PostHog sees our host’s connection and the IP address our host forwards, which we have set PostHog to discard. PostHog does not receive your wallet address.
Neon is the database provider that stores our Terms acceptance records (section 7): your wallet address, the signed message, the signature, the Terms version, the network, the website address you signed on and the time. It hosts our Postgres database, which we use through our host Vercel’s marketplace. Only our server contacts Neon, so Neon does not receive your IP address.
Market data providers. Our server gets token prices, logos and token safety data from services such as CoinGecko, Robinhood, DEX Screener and GoPlus. We do not send them information about you.
Your wallet. Transactions you sign never pass through our server. Your wallet sends them to the network over its own connection, and your wallet provider’s privacy policy applies. Our server accepts only read requests for the chain.
Links to other sites. If you follow a link to a block explorer, X or another site, that site receives your visit under its own policy. The Interface tells your browser not to tell those sites which of our pages you came from.

6. Image checks by AI models

On our hosted sites, fund images are checked for sexual content, nudity, sexualized depictions of minors and gore. The check runs when you upload an image, and again the first time one of our servers shows an image, because anyone can put an image link onchain without using our upload. If the check is switched off or cannot start, an image may be uploaded or shown without it.

For each check, our server makes a small copy of the image, no larger than 512 pixels on its longest side, or a grid of up to four frames for an animation. It sends that copy through Vercel AI Gateway to Google’s Gemini 2.5 Flash-Lite model. If that model does not answer, the copy goes to OpenAI’s GPT-4.1 nano model. We may change the model we use through the same gateway. We do not send your wallet address, your IP address or the file name with the image.

The result decides whether the image is uploaded and shown. Images that fail the check, or that we remove by hand, are not shown in the Interface. They may still exist on IPFS, and links to them stay onchain.

Our server remembers each result in memory, keyed by a fingerprint (hash) of the image, for up to 1,000 images per server instance. Vercel, Google and OpenAI handle these requests under their own terms, including how long they keep them.

7. Accepting the Terms with your wallet

When a wallet is connected, the Interface sends its address to our server to check whether that wallet has accepted the current version of our Terms of Use. If it has not, the Interface asks your wallet to sign a short message that says you accept that version. You need to sign it before you can send transactions through the Interface, but not to browse. When we publish a new version of the Terms, we ask again. Signing costs no gas, sends no transaction and gives no one access to your tokens.

Our server checks that the signature comes from your wallet, and for this it may send your wallet address, the message and the signature to a blockchain node provider (section 5). If the signature is valid, our server stores a record with Neon, our database provider: your wallet address, the signed message, the signature, the Terms version, the network and the website address named in the message, the time you signed and the time we recorded it. We do not store your IP address with it. We keep the first record for each wallet and version. The record is not published onchain. Whether a wallet has accepted the current Terms is not secret: anyone who knows a wallet address can ask our server, and the answer is only yes or no.

We use this record to keep proof that you accepted the Terms and which version you accepted. Your browser also keeps a note that your wallet accepted this version (section 9).

8. Product analytics, session replay and error reports

On www.glazecorp.io only, we use PostHog to understand how the Interface is used and to find what is broken or confusing. It is not used on test or preview copies of the site, and it does not load at all if your browser sends a Do Not Track or Global Privacy Control signal.

What PostHog receives: the pages you open (without the part of the web address after “?”, where wallet addresses travel), the site that linked you here and any campaign tags in the link, your browser, device type and screen size, your approximate country and city where PostHog can work them out from the connection, page speed measurements, the buttons and links you click (with every number removed from their text), and named actions such as opening a trade review, launching a fund, taking over a Mine, allocating, withdrawing, adding liquidity, claiming rewards or sharing, with whether each one succeeded. It also learns whether a wallet is connected and which kind of wallet you used, and, for actions on a fund, that fund’s public contract address.

Session replay: PostHog records how the page changes while you use it, so we can watch a replay of a visit. Before anything leaves your browser, every field you type into is masked, every number on the page is replaced by asterisks, wallet addresses and transaction hashes are removed, and wallet balances, amounts, your portfolio and the wallet window are hidden. The replay also lists which of our pages and services the page loaded and how long each took, without their contents, headers or the part of the web address after “?”. Console messages are not recorded.

Error reports: when something on the page fails, PostHog receives the error’s name, a shortened message with wallet addresses, amounts and other long numbers removed, where in our code it happened, and the page it happened on. For a failed transaction, it receives only the plain-language reason we showed you, such as “Price moved above your maximum”.

PostHog never receives your wallet address, what you type, your balances or amounts, your Terms signature or your private key or seed phrase. We do not tell PostHog who you are and we do not build a profile of you. PostHog identifies your browser by a random ID kept in this site’s local storage (section 9), not by a cookie. We have set PostHog to discard IP addresses instead of storing them.

Separately, the Interface includes a tool that can report errors and page speed to a reporting address of our choosing. It sends nothing unless we set that address, and no reporting address is set on www.glazecorp.io or dev.glazecorp.io as of the date of this notice. If we turn it on, each report would contain: the page path; the release, network and environment; the time; error names, messages and stack traces, with web addresses cut down to their domain; the line number where an error happened; page speed measurements; how you moved to the page (for example a link, a reload or the back button); and a SHA-256 hash of your wallet address. Error messages can also contain wallet addresses, contract addresses and transaction details in plain form, and the reporting provider would receive your IP address. A hash of a public address can be matched back to that address, so these reports would not be anonymous. We will update this notice and name the reporting provider before we turn it on.

9. What the Interface stores in your browser

The Interface stores some information in your browser so it keeps working across reloads. Unless a bullet says otherwise, this information stays on your device and we do not receive it. You can delete all of it by clearing this site’s data in your browser settings.

We do not use advertising cookies or analytics cookies.

Wallet connection cookies, set by our wallet connection library: the wallet addresses your wallet shares with the site, the network, the wallet type and which wallet you used last. They last until your browser session ends, and disconnecting your wallet removes your addresses from them. Your browser sends them to our server with every request.
Explore view cookie (glazecorp-explore-view): whether you prefer the table or card view on Explore. It lasts one year. Your browser sends it to our server, which uses it to draw the page.
Transaction tracking (local storage): pending transactions, until they confirm (entries older than 24 hours are ignored and dropped the next time the list is saved); your last 50 confirmed transactions, until you clear this site’s data; and pending batched wallet requests, until they resolve. Entries hold the transaction hash, a label, your wallet address, the network and related contract and fund addresses.
GLAZE bridge tracking (local storage): your pending transfer and your last 10 transfers, with the sender and recipient address, the amount and the transaction hash.
Launch draft (local storage): what you enter in the Launch form and the result of your launch, kept until the draft is cleared.
Fund records (local storage): public launch records of funds you have viewed, so their pages load faster.
Manage notice (local storage): whether you chose “Don’t show again” on the Manage notice. The name of this entry contains your wallet address.
Terms acceptance (local storage): a note that your wallet accepted a version of the Terms of Use, kept until you clear this site’s data. The name of this entry is glazecorp:terms: followed by the Terms version and your wallet address.
Product analytics (local storage and session storage, www.glazecorp.io only, written by PostHog’s code): a random ID for this browser, the current visit’s session ID and when it was last active, the first page and referring site of your first visit, and which PostHog features are switched on. It contains no wallet address. PostHog receives the random ID with each event (section 8).
Preferences (local storage): theme, interface sounds, advanced fund view, Explore view and which mascot animations you have already seen.
Session state (session storage, cleared when you close the tab): your fund search, and mascot and page animation state.
Wallet window data (local storage and IndexedDB, written by Reown’s code): recently used wallets, a cache of names linked to addresses, and WalletConnect session data and keys.

10. What we do not collect

The Interface does not collect the following.

Accounts, usernames, profiles or passwords. The Interface has none.
Your name, postal address, phone number, date of birth or government ID, unless you choose to send them to us by email.
Private keys or seed phrases. The Interface cannot read them.
Other signed messages. The only message the Interface asks your wallet to sign is the Terms acceptance in section 7. Apart from that, it asks your wallet only to connect, to switch to or add a network, and to approve transactions (including batches of transactions) that you start. If we ever ask you to sign another message in the Interface, we will update this notice first.
Precise location, camera or microphone. The Interface tells your browser to block access to them on every page. The approximate location our host derives from your IP address is described in section 11.
Payment card or bank details.
Advertising trackers. Reown’s code sends the items listed in section 5, and PostHog receives only the masked analytics, replays and error reports described in section 8.

11. How we use information

We use information only for these purposes. We do not use it for advertising, and we do not build profiles of individual users. We do not make decisions about you based only on automated processing that have legal or similarly significant effects. The image check decides only whether an image is shown, and any wallet check decides only whether the Interface is available to you.

To run the Interface: show prices, balances, funds, portfolios and history; prepare and simulate transactions for you to sign; and keep your wallet connected.
To do what you ask: pin your fund image to IPFS and prepare your fund details for your launch transaction.
To keep a record of our agreement: check whether a wallet has accepted the current Terms of Use, ask it to accept before it sends transactions through the Interface, and keep proof of which version it accepted.
To keep the Interface safe and working: limit requests per IP address, block abuse and attacks, find and fix errors, and protect the service keys we pay for.
To improve the Interface: count how often pages and actions are used, see where people get stuck by watching masked session replays, and fix the errors visitors run into (section 8).
To moderate content: check images, and hide images or other content that breaks our Terms of Use.
To answer you: respond to emails, privacy requests and legal notices.
To meet legal duties and enforce our Terms of Use: respond to valid legal requests, comply with sanctions and other laws, and protect our rights and the rights and safety of users and others.
Location: our host, Vercel, works out an approximate location (such as country, region and city) from the IP address of every request. We do not use it to block or limit access, we do not store it ourselves, and we never ask your browser for your precise location.
Wallet screening: if we check wallet addresses against sanctions or other risk lists to enforce our Terms of Use, those addresses will be sent to a screening provider. We will update this notice and name that provider before we start.

12. Legal bases

Some laws, such as the GDPR in the European Economic Area and the UK GDPR, require a legal basis for each use of personal information. Where those laws apply, we rely on the following.

Contract: to provide the Interface you choose to use and the features you ask for, such as connecting a wallet, accepting our Terms of Use, preparing transactions and uploading images.
Legitimate interests: to secure the Interface, limit abuse, moderate content, fix errors, understand and improve how the Interface is used through masked product analytics and session replay, publish public data such as the DONUT holder snapshot, keep proof of which version of our Terms of Use each wallet accepted, and establish or defend legal claims. We weigh these interests against your rights, and you can object (section 17).
Legal obligation: to comply with laws that apply to us, including sanctions laws, and with valid legal requests.
Consent: only where we ask for it. We do not ask for consent for anything today. If we do, you can withdraw it at any time.

14. How long we keep information

We keep information only as long as we need it for the purposes in section 11, or longer if the law requires it or a legal claim needs it. Where we can, we use short, fixed periods.

Request counters by IP address: in server memory only. Each counter covers a one-minute window, or ten minutes for image uploads and Terms acceptances. An expired counter can stay in memory until the same address returns or the server clears old counters, and all counters are lost when a server instance restarts.
Cached answers on our servers and Vercel’s network: chain reads up to five minutes; indexer answers a few seconds; agent tool answers 30 seconds; portfolio card answers up to five minutes, with an older copy served for up to an hour while a new one loads; fund images up to one day.
Image check results: in server memory, up to 1,000 per server instance, until the instance restarts or the entry is replaced.
Terms acceptance records: with Neon, for as long as the Terms of Use apply to you, and then for as long as we need them to bring or defend legal claims. This applies to the record of each version you accepted.
Request and firewall logs: kept by Vercel for the limited period its service provides.
Product analytics events, session replays and error reports: kept by PostHog for the retention period of our PostHog plan, and then deleted.
Uploaded images: pinned until we remove the pin. Copies elsewhere on IPFS, and links onchain, may remain forever.
Emails and requests: as long as we need to deal with them and keep a record of what we did.
Browser storage: on your device, for the periods in section 9, or until you clear it.
Onchain data: permanent and outside our control.

15. Security

We use reasonable measures to protect information. For example, the Interface uses HTTPS, a strict content security policy that limits which services a page can contact, request limits, and service keys that stay on our servers and never reach your browser. Our servers accept only read requests for the chain, so they cannot send transactions.

No system is perfectly secure, and we cannot guarantee the security of information sent over the internet. You are responsible for your wallet, your device and your keys. We will never ask for your private key or seed phrase. Anyone who asks for them is trying to steal from you.

16. International processing

Glaze Corp is based in the United States. Our service providers process information in the United States and in other countries where they operate, and Vercel serves the Interface from data centers around the world. If you use the Interface from outside the United States, your information will be transferred to and processed in countries whose data protection laws may differ from yours. Where the law requires a transfer safeguard, we rely on the safeguards our service providers offer in their own terms, such as standard contractual clauses, where they are available.

17. Your rights and choices

Depending on where you live, you may have the right to know what personal information we hold about you and get a copy; to correct it; to delete it; to object to or restrict how we use it; to receive it in a portable format; and to withdraw consent where we relied on it.

These rights cover information we hold offchain. We cannot change or delete onchain data, and we cannot recall content copied across IPFS. Much of what passes through our servers is never stored, or is kept only for minutes, so we may have nothing to return or delete. If you ask us to delete a Terms acceptance record, we may keep it while we need it to bring or defend legal claims, where the law allows.

To make a request, email admin@glazecorp.io and include the wallet address or other details the request is about. We will verify your request before acting on it. If we need to confirm that you control a wallet address, we will ask you, in our reply from admin@glazecorp.io, to sign a short plain-text message with that wallet. Signing that message does not move tokens or give anyone access to them. To verify a request, we will never ask you to approve a transaction or a token approval, and we will never ask for your private key or seed phrase. We will answer within the time the law that applies to you requires.

If we decline your request, you can ask us to reconsider by replying to our answer. If you are in the European Economic Area, the United Kingdom or Switzerland, you can also complain to your local data protection authority.

You can also limit what we receive yourself:

Turn on Do Not Track or Global Privacy Control in your browser. The Interface then does not load PostHog, so no product analytics, session replay or error reports are sent. Clearing this site’s data resets the random ID PostHog uses for your browser.
Browse without connecting a wallet. Most pages work without one.
Disconnect your wallet. This removes your addresses from the connection cookies.
Clear this site’s data in your browser to delete everything listed in section 9.
Use a separate wallet address if you do not want this activity linked to your other addresses.
Leave personal information out of fund details, mining messages, images and image file names.

18. Notice for US state residents

Some US states, such as California, give residents extra privacy rights. Where those laws apply to us, this section adds to the rest of this notice.

In the past 12 months we have collected these categories of personal information: identifiers (wallet addresses, IP addresses and, if you email us, your email address); internet or other network activity (requests, pages and device type, and on www.glazecorp.io the pages you view, what you click and masked session replays); approximate geolocation (such as the country, region and city our host derives from your IP address); transaction information (the transactions you prepare through the Interface); and content you submit (fund images and their file names, emails, and the Terms acceptance message your wallet signs, with its signature). We collect them from you, from your browser and from public blockchains. We use them for the purposes in section 11, keep them for the periods in section 14, and disclose them for business purposes to the service providers in section 5. Reown also receives identifiers and internet activity directly from your browser through its wallet code (section 5) and uses them under its own terms.

We do not sell personal information for money or share it for cross-context behavioral advertising, and we have not done so in the past 12 months. We do not knowingly sell or share the personal information of anyone under 16. We do not use or disclose sensitive personal information to infer characteristics about you.

You can ask to know, access, correct or delete your personal information, and to opt out of sale, sharing, targeted advertising and profiling. You can use an authorized agent; we may ask the agent for proof that you authorized it and ask you to verify your identity. We will not treat you differently for using these rights. Send requests to admin@glazecorp.io.

19. Children

The Interface is only for adults: people who are at least 18, or the age of majority where they live if that is higher. We do not knowingly collect personal information about people under 18. If you think a minor has sent us personal information, email admin@glazecorp.io and we will delete what we can. We cannot delete onchain data.

20. Changes to this notice

We will update this notice when the Interface changes what it collects, stores or sends, or who receives it. The date at the top of this page shows the latest version, and changes apply from that date. If a change is significant, we will also announce it in the Interface or on our official channels.

21. Contact

Glaze Corp. Email: admin@glazecorp.io. Website: https://www.glazecorp.io.

Use this email address for questions about this notice, privacy requests and legal notices. We do not accept privacy requests through Discord, X or Telegram.

Email admin@glazecorp.io

Company

Privacy Notice

How Glaze Corp handles information when you use the GlazeCorp website: what it collects, who receives it, what stays in your browser and what is public onchain forever.

Updated October 24, 2026

1. Key points

This is a short summary. The full notice below controls.
Anything you do onchain is public and permanent. Your wallet address, your transactions and any fund details, image link or mining message you publish can be seen by anyone. We cannot delete them, and nobody else can either.
You do not give us your name, email address or ID to use the Interface. There are no accounts, profiles or usernames.
Our servers and service providers do receive your IP address and, once you connect a wallet, your wallet address. Some requests carry your wallet address inside the web address (URL).
When you accept our Terms of Use, your wallet signs a message and we keep a record of it: your wallet address, the message, the signature, the Terms version, the network, the website address you signed on and the time. We do not store your IP address with it.
Our host works out an approximate location from your IP address. We do not use it to block or limit access.
On our hosted sites, fund images are checked by AI models from Google or OpenAI through Vercel. Images you upload are then published to IPFS through Pinata, where they are public and may stay forever.
When the wallet window loads, and on every visit while a wallet connection is saved, Reown, the company behind WalletConnect, receives your wallet address, the page you are on and connection events. This happens even though we have turned off its optional analytics.
We do not sell personal information for money, and we do not use advertising trackers. On www.glazecorp.io we use PostHog to count page views and actions, record masked session replays and collect error reports. It never receives your wallet address, what you type or the amounts and balances on the page, and it sets no cookies. Turning on Do Not Track or Global Privacy Control in your browser switches it off (section 8).
We will never ask for your private key or seed phrase. Never send them to anyone.
Questions and privacy requests: admin@glazecorp.io.

2. Who we are and what this notice covers

Where a data protection law uses the term, Glaze Corp is the controller of the personal information described in this notice. You can reach us at admin@glazecorp.io.

3. Onchain data is public and permanent

4. Information we collect

Wallet address and connection. When you connect a wallet, the Interface saves in a cookie every wallet address your wallet shares with the site, the network and which wallet you used. Your browser sends this cookie to our server with every request, and our server reads it so pages load already connected.
Wallet addresses in requests. To show balances, your portfolio and your activity, the Interface sends requests to our server that include your wallet address. Some put the address inside the web address itself: chain reads (/api/chain/read), indexer queries (/api/indexed), the portfolio card check (/api/portfolio-card), which runs automatically when you open your portfolio, and the Terms check (/api/terms), which runs when you connect a wallet. Addresses you type into a checker, such as the GLAZE check page, are also sent to our server so we can read their balances.
Transactions you prepare. Before you sign, the Interface asks the chain to simulate each transaction and estimate its gas. These requests go through our server and contain your wallet address and the transaction details.
Terms acceptance. When you accept our Terms of Use, your wallet signs a message and the Interface sends the message and the signature to our server, which keeps a record of them (section 7).
IP address, location and device information. Every request to the Interface reaches our host, Vercel. Like any web server, it receives your IP address, your browser and device type, the web address requested, your cookies for this site and the time. Vercel also derives an approximate location (such as country, region and city) from your IP address. Our server uses your IP address to limit how many requests one connection can make.
Images and fund details. When you upload an image while launching a fund, the image and its file name are sent to our server. We check the image (section 6) and pin it to IPFS through Pinata. Still images are cropped and re-encoded in your browser first, which removes embedded photo data such as camera details. GIFs, and images from browsers that cannot re-encode them, are uploaded exactly as you chose them, including any data embedded in the file. The fund details you enter go into your launch transaction and are published onchain (section 3).
Agent tools. Requests to our agent tools include whatever the caller sends, which can include wallet addresses, together with the caller’s IP address.
Messages you send us. If you email admin@glazecorp.io, we receive your email address, what you write and anything you attach.
Public data from other sources. We read public blockchain data through node (RPC) providers and our indexer. We also publish a snapshot of DONUT holder addresses and balances on Base, taken at block 50,924,147 for the move from DONUT to GLAZE. It contains public onchain data about other people’s addresses.

5. Service providers that receive information

We use the service providers below to run the Interface. Each receives what it needs for its task. Some also handle data under their own terms.

Vercel hosts the Interface. It runs our servers, caches some responses on its network and works out an approximate location from each IP address. Its firewall can block or limit traffic by IP address or location. Vercel receives every request, including your IP address, device information, cookies for this site and web addresses that can contain your wallet address, and it may keep logs of these requests. Vercel also runs the AI Gateway we use for image checks.
Blockchain node (RPC) providers. Our server forwards chain reads and transaction simulations to the node providers we use for Robinhood Chain (a main provider and, at times, a separate provider for history reads and a backup). For the GLAZE pages and the GLAZE bridge, it forwards Base reads to Base’s public endpoint (mainnet.base.org) or to a provider we choose, and Robinhood Chain mainnet reads to a provider we choose. To check a Terms acceptance signature (section 7), our server may also send your wallet address, the signed message and the signature to a node provider for Robinhood Chain or Base. These providers see the content of each request, which can include your wallet address, but they see our server’s IP address, not yours. On the testnet version of the site, your browser may also read directly from the public Robinhood Chain testnet endpoint, which then sees your IP address. When the Interface asks your wallet to switch to a network it does not have yet, such as Robinhood Chain or Base, it gives your wallet that network’s public endpoint. Your wallet may then contact that endpoint directly, and it sees your IP address.
Goldsky hosts our indexer, which organizes Protocol data for lists, charts, history and portfolios. Our server, or on some deployments your browser, sends it queries, including your wallet address when you view your portfolio or activity. When your browser queries Goldsky directly, including whenever our server cannot answer, Goldsky also receives your IP address.
Reown runs WalletConnect and the wallet window (AppKit). Its code loads when you open the wallet window, or when you visit with a wallet connection already saved. Reown then receives your IP address, the full web address of the page you are on, your wallet address, the network, which wallet you use, which wallets the window showed you, connection events and error reports from its code. It may also look up a public name or avatar linked to your wallet address. If you connect a mobile wallet, Reown’s relay carries encrypted messages between this site and your wallet app. We have turned off Reown’s optional analytics, but its code still sends the items listed here.
Pinata receives the images you upload, with their file names, and pins them to IPFS. It also serves IPFS content to our server through a dedicated gateway. Filebase’s public IPFS gateway is our backup for reading IPFS content. Your browser never contacts an IPFS gateway: our server fetches the content and passes it on.
Vercel AI Gateway, Google and OpenAI check fund images, as described in section 6.
PostHog (PostHog Inc., United States) provides our product analytics, session replay and error tracking on www.glazecorp.io, as described in section 8. Your browser sends this data to our own site, which passes it to PostHog’s US servers, so PostHog sees our host’s connection and the IP address our host forwards, which we have set PostHog to discard. PostHog does not receive your wallet address.
Neon is the database provider that stores our Terms acceptance records (section 7): your wallet address, the signed message, the signature, the Terms version, the network, the website address you signed on and the time. It hosts our Postgres database, which we use through our host Vercel’s marketplace. Only our server contacts Neon, so Neon does not receive your IP address.
Market data providers. Our server gets token prices, logos and token safety data from services such as CoinGecko, Robinhood, DEX Screener and GoPlus. We do not send them information about you.
Your wallet. Transactions you sign never pass through our server. Your wallet sends them to the network over its own connection, and your wallet provider’s privacy policy applies. Our server accepts only read requests for the chain.
Links to other sites. If you follow a link to a block explorer, X or another site, that site receives your visit under its own policy. The Interface tells your browser not to tell those sites which of our pages you came from.

6. Image checks by AI models

7. Accepting the Terms with your wallet

We use this record to keep proof that you accepted the Terms and which version you accepted. Your browser also keeps a note that your wallet accepted this version (section 9).

8. Product analytics, session replay and error reports

9. What the Interface stores in your browser

We do not use advertising cookies or analytics cookies.

Wallet connection cookies, set by our wallet connection library: the wallet addresses your wallet shares with the site, the network, the wallet type and which wallet you used last. They last until your browser session ends, and disconnecting your wallet removes your addresses from them. Your browser sends them to our server with every request.
Explore view cookie (glazecorp-explore-view): whether you prefer the table or card view on Explore. It lasts one year. Your browser sends it to our server, which uses it to draw the page.
Transaction tracking (local storage): pending transactions, until they confirm (entries older than 24 hours are ignored and dropped the next time the list is saved); your last 50 confirmed transactions, until you clear this site’s data; and pending batched wallet requests, until they resolve. Entries hold the transaction hash, a label, your wallet address, the network and related contract and fund addresses.
GLAZE bridge tracking (local storage): your pending transfer and your last 10 transfers, with the sender and recipient address, the amount and the transaction hash.
Launch draft (local storage): what you enter in the Launch form and the result of your launch, kept until the draft is cleared.
Fund records (local storage): public launch records of funds you have viewed, so their pages load faster.
Manage notice (local storage): whether you chose “Don’t show again” on the Manage notice. The name of this entry contains your wallet address.
Terms acceptance (local storage): a note that your wallet accepted a version of the Terms of Use, kept until you clear this site’s data. The name of this entry is glazecorp:terms: followed by the Terms version and your wallet address.
Product analytics (local storage and session storage, www.glazecorp.io only, written by PostHog’s code): a random ID for this browser, the current visit’s session ID and when it was last active, the first page and referring site of your first visit, and which PostHog features are switched on. It contains no wallet address. PostHog receives the random ID with each event (section 8).
Preferences (local storage): theme, interface sounds, advanced fund view, Explore view and which mascot animations you have already seen.
Session state (session storage, cleared when you close the tab): your fund search, and mascot and page animation state.
Wallet window data (local storage and IndexedDB, written by Reown’s code): recently used wallets, a cache of names linked to addresses, and WalletConnect session data and keys.

10. What we do not collect

The Interface does not collect the following.

Accounts, usernames, profiles or passwords. The Interface has none.
Your name, postal address, phone number, date of birth or government ID, unless you choose to send them to us by email.
Private keys or seed phrases. The Interface cannot read them.
Other signed messages. The only message the Interface asks your wallet to sign is the Terms acceptance in section 7. Apart from that, it asks your wallet only to connect, to switch to or add a network, and to approve transactions (including batches of transactions) that you start. If we ever ask you to sign another message in the Interface, we will update this notice first.
Precise location, camera or microphone. The Interface tells your browser to block access to them on every page. The approximate location our host derives from your IP address is described in section 11.
Payment card or bank details.
Advertising trackers. Reown’s code sends the items listed in section 5, and PostHog receives only the masked analytics, replays and error reports described in section 8.

11. How we use information

To run the Interface: show prices, balances, funds, portfolios and history; prepare and simulate transactions for you to sign; and keep your wallet connected.
To do what you ask: pin your fund image to IPFS and prepare your fund details for your launch transaction.
To keep a record of our agreement: check whether a wallet has accepted the current Terms of Use, ask it to accept before it sends transactions through the Interface, and keep proof of which version it accepted.
To keep the Interface safe and working: limit requests per IP address, block abuse and attacks, find and fix errors, and protect the service keys we pay for.
To improve the Interface: count how often pages and actions are used, see where people get stuck by watching masked session replays, and fix the errors visitors run into (section 8).
To moderate content: check images, and hide images or other content that breaks our Terms of Use.
To answer you: respond to emails, privacy requests and legal notices.
To meet legal duties and enforce our Terms of Use: respond to valid legal requests, comply with sanctions and other laws, and protect our rights and the rights and safety of users and others.
Location: our host, Vercel, works out an approximate location (such as country, region and city) from the IP address of every request. We do not use it to block or limit access, we do not store it ourselves, and we never ask your browser for your precise location.
Wallet screening: if we check wallet addresses against sanctions or other risk lists to enforce our Terms of Use, those addresses will be sent to a screening provider. We will update this notice and name that provider before we start.

12. Legal bases

Some laws, such as the GDPR in the European Economic Area and the UK GDPR, require a legal basis for each use of personal information. Where those laws apply, we rely on the following.

Contract: to provide the Interface you choose to use and the features you ask for, such as connecting a wallet, accepting our Terms of Use, preparing transactions and uploading images.
Legitimate interests: to secure the Interface, limit abuse, moderate content, fix errors, understand and improve how the Interface is used through masked product analytics and session replay, publish public data such as the DONUT holder snapshot, keep proof of which version of our Terms of Use each wallet accepted, and establish or defend legal claims. We weigh these interests against your rights, and you can object (section 17).
Legal obligation: to comply with laws that apply to us, including sanctions laws, and with valid legal requests.
Consent: only where we ask for it. We do not ask for consent for anything today. If we do, you can withdraw it at any time.

14. How long we keep information

We keep information only as long as we need it for the purposes in section 11, or longer if the law requires it or a legal claim needs it. Where we can, we use short, fixed periods.

Request counters by IP address: in server memory only. Each counter covers a one-minute window, or ten minutes for image uploads and Terms acceptances. An expired counter can stay in memory until the same address returns or the server clears old counters, and all counters are lost when a server instance restarts.
Cached answers on our servers and Vercel’s network: chain reads up to five minutes; indexer answers a few seconds; agent tool answers 30 seconds; portfolio card answers up to five minutes, with an older copy served for up to an hour while a new one loads; fund images up to one day.
Image check results: in server memory, up to 1,000 per server instance, until the instance restarts or the entry is replaced.
Terms acceptance records: with Neon, for as long as the Terms of Use apply to you, and then for as long as we need them to bring or defend legal claims. This applies to the record of each version you accepted.
Request and firewall logs: kept by Vercel for the limited period its service provides.
Product analytics events, session replays and error reports: kept by PostHog for the retention period of our PostHog plan, and then deleted.
Uploaded images: pinned until we remove the pin. Copies elsewhere on IPFS, and links onchain, may remain forever.
Emails and requests: as long as we need to deal with them and keep a record of what we did.
Browser storage: on your device, for the periods in section 9, or until you clear it.
Onchain data: permanent and outside our control.

15. Security

16. International processing

17. Your rights and choices

You can also limit what we receive yourself:

Turn on Do Not Track or Global Privacy Control in your browser. The Interface then does not load PostHog, so no product analytics, session replay or error reports are sent. Clearing this site’s data resets the random ID PostHog uses for your browser.
Browse without connecting a wallet. Most pages work without one.
Disconnect your wallet. This removes your addresses from the connection cookies.
Clear this site’s data in your browser to delete everything listed in section 9.
Use a separate wallet address if you do not want this activity linked to your other addresses.
Leave personal information out of fund details, mining messages, images and image file names.

18. Notice for US state residents

Some US states, such as California, give residents extra privacy rights. Where those laws apply to us, this section adds to the rest of this notice.

19. Children

20. Changes to this notice

21. Contact

Glaze Corp. Email: admin@glazecorp.io. Website: https://www.glazecorp.io.

Use this email address for questions about this notice, privacy requests and legal notices. We do not accept privacy requests through Discord, X or Telegram.

Email admin@glazecorp.io

Company

Privacy Notice

How Glaze Corp handles information when you use the GlazeCorp website: what it collects, who receives it, what stays in your browser and what is public onchain forever.

Updated October 24, 2026

1. Key points

This is a short summary. The full notice below controls.
Anything you do onchain is public and permanent. Your wallet address, your transactions and any fund details, image link or mining message you publish can be seen by anyone. We cannot delete them, and nobody else can either.
You do not give us your name, email address or ID to use the Interface. There are no accounts, profiles or usernames.
Our servers and service providers do receive your IP address and, once you connect a wallet, your wallet address. Some requests carry your wallet address inside the web address (URL).
When you accept our Terms of Use, your wallet signs a message and we keep a record of it: your wallet address, the message, the signature, the Terms version, the network, the website address you signed on and the time. We do not store your IP address with it.
Our host works out an approximate location from your IP address. We do not use it to block or limit access.
On our hosted sites, fund images are checked by AI models from Google or OpenAI through Vercel. Images you upload are then published to IPFS through Pinata, where they are public and may stay forever.
When the wallet window loads, and on every visit while a wallet connection is saved, Reown, the company behind WalletConnect, receives your wallet address, the page you are on and connection events. This happens even though we have turned off its optional analytics.
We do not sell personal information for money, and we do not use advertising trackers. On www.glazecorp.io we use PostHog to count page views and actions, record masked session replays and collect error reports. It never receives your wallet address, what you type or the amounts and balances on the page, and it sets no cookies. Turning on Do Not Track or Global Privacy Control in your browser switches it off (section 8).
We will never ask for your private key or seed phrase. Never send them to anyone.
Questions and privacy requests: admin@glazecorp.io.

2. Who we are and what this notice covers

Where a data protection law uses the term, Glaze Corp is the controller of the personal information described in this notice. You can reach us at admin@glazecorp.io.

3. Onchain data is public and permanent

4. Information we collect

Wallet address and connection. When you connect a wallet, the Interface saves in a cookie every wallet address your wallet shares with the site, the network and which wallet you used. Your browser sends this cookie to our server with every request, and our server reads it so pages load already connected.
Wallet addresses in requests. To show balances, your portfolio and your activity, the Interface sends requests to our server that include your wallet address. Some put the address inside the web address itself: chain reads (/api/chain/read), indexer queries (/api/indexed), the portfolio card check (/api/portfolio-card), which runs automatically when you open your portfolio, and the Terms check (/api/terms), which runs when you connect a wallet. Addresses you type into a checker, such as the GLAZE check page, are also sent to our server so we can read their balances.
Transactions you prepare. Before you sign, the Interface asks the chain to simulate each transaction and estimate its gas. These requests go through our server and contain your wallet address and the transaction details.
Terms acceptance. When you accept our Terms of Use, your wallet signs a message and the Interface sends the message and the signature to our server, which keeps a record of them (section 7).
IP address, location and device information. Every request to the Interface reaches our host, Vercel. Like any web server, it receives your IP address, your browser and device type, the web address requested, your cookies for this site and the time. Vercel also derives an approximate location (such as country, region and city) from your IP address. Our server uses your IP address to limit how many requests one connection can make.
Images and fund details. When you upload an image while launching a fund, the image and its file name are sent to our server. We check the image (section 6) and pin it to IPFS through Pinata. Still images are cropped and re-encoded in your browser first, which removes embedded photo data such as camera details. GIFs, and images from browsers that cannot re-encode them, are uploaded exactly as you chose them, including any data embedded in the file. The fund details you enter go into your launch transaction and are published onchain (section 3).
Agent tools. Requests to our agent tools include whatever the caller sends, which can include wallet addresses, together with the caller’s IP address.
Messages you send us. If you email admin@glazecorp.io, we receive your email address, what you write and anything you attach.
Public data from other sources. We read public blockchain data through node (RPC) providers and our indexer. We also publish a snapshot of DONUT holder addresses and balances on Base, taken at block 50,924,147 for the move from DONUT to GLAZE. It contains public onchain data about other people’s addresses.

5. Service providers that receive information

We use the service providers below to run the Interface. Each receives what it needs for its task. Some also handle data under their own terms.

Vercel hosts the Interface. It runs our servers, caches some responses on its network and works out an approximate location from each IP address. Its firewall can block or limit traffic by IP address or location. Vercel receives every request, including your IP address, device information, cookies for this site and web addresses that can contain your wallet address, and it may keep logs of these requests. Vercel also runs the AI Gateway we use for image checks.
Blockchain node (RPC) providers. Our server forwards chain reads and transaction simulations to the node providers we use for Robinhood Chain (a main provider and, at times, a separate provider for history reads and a backup). For the GLAZE pages and the GLAZE bridge, it forwards Base reads to Base’s public endpoint (mainnet.base.org) or to a provider we choose, and Robinhood Chain mainnet reads to a provider we choose. To check a Terms acceptance signature (section 7), our server may also send your wallet address, the signed message and the signature to a node provider for Robinhood Chain or Base. These providers see the content of each request, which can include your wallet address, but they see our server’s IP address, not yours. On the testnet version of the site, your browser may also read directly from the public Robinhood Chain testnet endpoint, which then sees your IP address. When the Interface asks your wallet to switch to a network it does not have yet, such as Robinhood Chain or Base, it gives your wallet that network’s public endpoint. Your wallet may then contact that endpoint directly, and it sees your IP address.
Goldsky hosts our indexer, which organizes Protocol data for lists, charts, history and portfolios. Our server, or on some deployments your browser, sends it queries, including your wallet address when you view your portfolio or activity. When your browser queries Goldsky directly, including whenever our server cannot answer, Goldsky also receives your IP address.
Reown runs WalletConnect and the wallet window (AppKit). Its code loads when you open the wallet window, or when you visit with a wallet connection already saved. Reown then receives your IP address, the full web address of the page you are on, your wallet address, the network, which wallet you use, which wallets the window showed you, connection events and error reports from its code. It may also look up a public name or avatar linked to your wallet address. If you connect a mobile wallet, Reown’s relay carries encrypted messages between this site and your wallet app. We have turned off Reown’s optional analytics, but its code still sends the items listed here.
Pinata receives the images you upload, with their file names, and pins them to IPFS. It also serves IPFS content to our server through a dedicated gateway. Filebase’s public IPFS gateway is our backup for reading IPFS content. Your browser never contacts an IPFS gateway: our server fetches the content and passes it on.
Vercel AI Gateway, Google and OpenAI check fund images, as described in section 6.
PostHog (PostHog Inc., United States) provides our product analytics, session replay and error tracking on www.glazecorp.io, as described in section 8. Your browser sends this data to our own site, which passes it to PostHog’s US servers, so PostHog sees our host’s connection and the IP address our host forwards, which we have set PostHog to discard. PostHog does not receive your wallet address.
Neon is the database provider that stores our Terms acceptance records (section 7): your wallet address, the signed message, the signature, the Terms version, the network, the website address you signed on and the time. It hosts our Postgres database, which we use through our host Vercel’s marketplace. Only our server contacts Neon, so Neon does not receive your IP address.
Market data providers. Our server gets token prices, logos and token safety data from services such as CoinGecko, Robinhood, DEX Screener and GoPlus. We do not send them information about you.
Your wallet. Transactions you sign never pass through our server. Your wallet sends them to the network over its own connection, and your wallet provider’s privacy policy applies. Our server accepts only read requests for the chain.
Links to other sites. If you follow a link to a block explorer, X or another site, that site receives your visit under its own policy. The Interface tells your browser not to tell those sites which of our pages you came from.

6. Image checks by AI models

7. Accepting the Terms with your wallet

We use this record to keep proof that you accepted the Terms and which version you accepted. Your browser also keeps a note that your wallet accepted this version (section 9).

8. Product analytics, session replay and error reports

9. What the Interface stores in your browser

We do not use advertising cookies or analytics cookies.

Wallet connection cookies, set by our wallet connection library: the wallet addresses your wallet shares with the site, the network, the wallet type and which wallet you used last. They last until your browser session ends, and disconnecting your wallet removes your addresses from them. Your browser sends them to our server with every request.
Explore view cookie (glazecorp-explore-view): whether you prefer the table or card view on Explore. It lasts one year. Your browser sends it to our server, which uses it to draw the page.
Transaction tracking (local storage): pending transactions, until they confirm (entries older than 24 hours are ignored and dropped the next time the list is saved); your last 50 confirmed transactions, until you clear this site’s data; and pending batched wallet requests, until they resolve. Entries hold the transaction hash, a label, your wallet address, the network and related contract and fund addresses.
GLAZE bridge tracking (local storage): your pending transfer and your last 10 transfers, with the sender and recipient address, the amount and the transaction hash.
Launch draft (local storage): what you enter in the Launch form and the result of your launch, kept until the draft is cleared.
Fund records (local storage): public launch records of funds you have viewed, so their pages load faster.
Manage notice (local storage): whether you chose “Don’t show again” on the Manage notice. The name of this entry contains your wallet address.
Terms acceptance (local storage): a note that your wallet accepted a version of the Terms of Use, kept until you clear this site’s data. The name of this entry is glazecorp:terms: followed by the Terms version and your wallet address.
Product analytics (local storage and session storage, www.glazecorp.io only, written by PostHog’s code): a random ID for this browser, the current visit’s session ID and when it was last active, the first page and referring site of your first visit, and which PostHog features are switched on. It contains no wallet address. PostHog receives the random ID with each event (section 8).
Preferences (local storage): theme, interface sounds, advanced fund view, Explore view and which mascot animations you have already seen.
Session state (session storage, cleared when you close the tab): your fund search, and mascot and page animation state.
Wallet window data (local storage and IndexedDB, written by Reown’s code): recently used wallets, a cache of names linked to addresses, and WalletConnect session data and keys.

10. What we do not collect

The Interface does not collect the following.

Accounts, usernames, profiles or passwords. The Interface has none.
Your name, postal address, phone number, date of birth or government ID, unless you choose to send them to us by email.
Private keys or seed phrases. The Interface cannot read them.
Other signed messages. The only message the Interface asks your wallet to sign is the Terms acceptance in section 7. Apart from that, it asks your wallet only to connect, to switch to or add a network, and to approve transactions (including batches of transactions) that you start. If we ever ask you to sign another message in the Interface, we will update this notice first.
Precise location, camera or microphone. The Interface tells your browser to block access to them on every page. The approximate location our host derives from your IP address is described in section 11.
Payment card or bank details.
Advertising trackers. Reown’s code sends the items listed in section 5, and PostHog receives only the masked analytics, replays and error reports described in section 8.

11. How we use information

To run the Interface: show prices, balances, funds, portfolios and history; prepare and simulate transactions for you to sign; and keep your wallet connected.
To do what you ask: pin your fund image to IPFS and prepare your fund details for your launch transaction.
To keep a record of our agreement: check whether a wallet has accepted the current Terms of Use, ask it to accept before it sends transactions through the Interface, and keep proof of which version it accepted.
To keep the Interface safe and working: limit requests per IP address, block abuse and attacks, find and fix errors, and protect the service keys we pay for.
To improve the Interface: count how often pages and actions are used, see where people get stuck by watching masked session replays, and fix the errors visitors run into (section 8).
To moderate content: check images, and hide images or other content that breaks our Terms of Use.
To answer you: respond to emails, privacy requests and legal notices.
To meet legal duties and enforce our Terms of Use: respond to valid legal requests, comply with sanctions and other laws, and protect our rights and the rights and safety of users and others.
Location: our host, Vercel, works out an approximate location (such as country, region and city) from the IP address of every request. We do not use it to block or limit access, we do not store it ourselves, and we never ask your browser for your precise location.
Wallet screening: if we check wallet addresses against sanctions or other risk lists to enforce our Terms of Use, those addresses will be sent to a screening provider. We will update this notice and name that provider before we start.

12. Legal bases

Some laws, such as the GDPR in the European Economic Area and the UK GDPR, require a legal basis for each use of personal information. Where those laws apply, we rely on the following.

Contract: to provide the Interface you choose to use and the features you ask for, such as connecting a wallet, accepting our Terms of Use, preparing transactions and uploading images.
Legitimate interests: to secure the Interface, limit abuse, moderate content, fix errors, understand and improve how the Interface is used through masked product analytics and session replay, publish public data such as the DONUT holder snapshot, keep proof of which version of our Terms of Use each wallet accepted, and establish or defend legal claims. We weigh these interests against your rights, and you can object (section 17).
Legal obligation: to comply with laws that apply to us, including sanctions laws, and with valid legal requests.
Consent: only where we ask for it. We do not ask for consent for anything today. If we do, you can withdraw it at any time.

14. How long we keep information

We keep information only as long as we need it for the purposes in section 11, or longer if the law requires it or a legal claim needs it. Where we can, we use short, fixed periods.

Request counters by IP address: in server memory only. Each counter covers a one-minute window, or ten minutes for image uploads and Terms acceptances. An expired counter can stay in memory until the same address returns or the server clears old counters, and all counters are lost when a server instance restarts.
Cached answers on our servers and Vercel’s network: chain reads up to five minutes; indexer answers a few seconds; agent tool answers 30 seconds; portfolio card answers up to five minutes, with an older copy served for up to an hour while a new one loads; fund images up to one day.
Image check results: in server memory, up to 1,000 per server instance, until the instance restarts or the entry is replaced.
Terms acceptance records: with Neon, for as long as the Terms of Use apply to you, and then for as long as we need them to bring or defend legal claims. This applies to the record of each version you accepted.
Request and firewall logs: kept by Vercel for the limited period its service provides.
Product analytics events, session replays and error reports: kept by PostHog for the retention period of our PostHog plan, and then deleted.
Uploaded images: pinned until we remove the pin. Copies elsewhere on IPFS, and links onchain, may remain forever.
Emails and requests: as long as we need to deal with them and keep a record of what we did.
Browser storage: on your device, for the periods in section 9, or until you clear it.
Onchain data: permanent and outside our control.

15. Security

16. International processing

17. Your rights and choices

You can also limit what we receive yourself:

Turn on Do Not Track or Global Privacy Control in your browser. The Interface then does not load PostHog, so no product analytics, session replay or error reports are sent. Clearing this site’s data resets the random ID PostHog uses for your browser.
Browse without connecting a wallet. Most pages work without one.
Disconnect your wallet. This removes your addresses from the connection cookies.
Clear this site’s data in your browser to delete everything listed in section 9.
Use a separate wallet address if you do not want this activity linked to your other addresses.
Leave personal information out of fund details, mining messages, images and image file names.

18. Notice for US state residents

Some US states, such as California, give residents extra privacy rights. Where those laws apply to us, this section adds to the rest of this notice.

19. Children

20. Changes to this notice

21. Contact

Glaze Corp. Email: admin@glazecorp.io. Website: https://www.glazecorp.io.

Use this email address for questions about this notice, privacy requests and legal notices. We do not accept privacy requests through Discord, X or Telegram.

Email admin@glazecorp.io

1. Key points

2. Who we are and what this notice covers

3. Onchain data is public and permanent

4. Information we collect

5. Service providers that receive information

6. Image checks by AI models

7. Accepting the Terms with your wallet

8. Product analytics, session replay and error reports

9. What the Interface stores in your browser

10. What we do not collect

11. How we use information

12. Legal bases

13. How we share information

14. How long we keep information

15. Security

16. International processing

17. Your rights and choices

18. Notice for US state residents

19. Children

20. Changes to this notice

21. Contact

1. Key points

2. Who we are and what this notice covers

3. Onchain data is public and permanent

4. Information we collect

5. Service providers that receive information

6. Image checks by AI models

7. Accepting the Terms with your wallet

8. Product analytics, session replay and error reports

9. What the Interface stores in your browser

10. What we do not collect

11. How we use information

12. Legal bases

13. How we share information

14. How long we keep information

15. Security

16. International processing

17. Your rights and choices

18. Notice for US state residents

19. Children

20. Changes to this notice

21. Contact

1. Key points

2. Who we are and what this notice covers

3. Onchain data is public and permanent

4. Information we collect

5. Service providers that receive information

6. Image checks by AI models

7. Accepting the Terms with your wallet

8. Product analytics, session replay and error reports

9. What the Interface stores in your browser

10. What we do not collect

11. How we use information

12. Legal bases

13. How we share information

14. How long we keep information

15. Security

16. International processing

17. Your rights and choices

18. Notice for US state residents

19. Children

20. Changes to this notice

21. Contact