Waitlist privacy notice

This notice explains how we handle your details when you join the Ammora private waitlist or complete a waitlist campaign. Notice version: 2026-09-06.liquidity-v1.

What we collect

We save the email and public wallet address you provide, when you register and give consent, and the version of this notice you agreed to. When you join or verify your wallet again, we also save the GIWA Sepolia chain ID, an identifier for the wallet connection you used, the verification time, and a hash of the message you signed.

If you separately allow optional product analytics, we record a pseudonymous browser identifier, session identifier, page and section views, CTA clicks, wallet-connected and waitlist form milestones, timestamps, device class, and a broad acquisition category such as direct, search, social, referral, or campaign. We do not put your email, wallet address, URL query, signed message, transaction amount, or raw error text in these events.

Your registration signature confirms that you control the wallet. We don’t keep the signature or the full message. We never ask for your private key or recovery phrase.

For the Weekly post mission, we save the public X post ID and link, the author name and current handle returned by X, an X numeric user ID when X makes it available to our verifier, the verified post text, a verification hash, the result, and the points entry. The numeric ID helps an already linked account continue after a username change. We never request your X password.

X account changes are available only after a verified Weekly post (or a historical Daily post) has linked an X account to your wallet. If you choose optional X account verification, you first sign an account-linking message with your wallet and authorize Ammora through X OAuth 2.0. We read your own X numeric user ID and current @handle and link them to your waitlist wallet; the display name is not used to identify your account. Your AP and mission records stay with your wallet. A different X account may replace the linked account once; verified username changes for the same numeric ID do not use that replacement.

For the Daily liquidity supply mission, you choose an amount of at least 0.001 GIWA Sepolia test ETH and deposit it into Ammora’s campaign Vault. Test ETH has no real-world value. Contributors cannot withdraw their deposits; withdrawals can only be sent to the configured Ammora operating wallet. We save the amount, transaction hash, block number, wallet, Vault address, verified call data, result, and points entry.

How we use and store your details

We use your details to manage the waitlist, avoid duplicate entries, and email you about Ammora access and product updates. Joining doesn’t guarantee beta access, rewards, or an allocation. We check the format of your email address, but this form doesn’t verify that you own it.

Your registration is stored in dedicated waitlist tables in Ammora’s database. The landing page sends your details to Ammora’s server over an encrypted connection. It isn’t published onchain, and there’s no public API for listing registrations. Records stay in the database until the operator removes them. Automatic deletion after a set period hasn’t been configured yet.

We use submitted public X data only to validate campaign requirements, prevent duplicate rewards, record points, and review abuse. One X post and one X author can receive the Weekly post reward only once per UTC week, starting Monday at 00:00 UTC. Campaign points and recorded liquidity contributions are internal campaign records. They don’t guarantee tokens, money, beta access, rewards, or an allocation.

How registration works

We use a temporary, essential cookie to link your registration to your browser. You have five minutes to complete a signing request before it expires. To limit repeated attempts, we use salted hashes of IP addresses instead of storing the addresses themselves. Expired requests and records used to limit attempts are cleared as new registrations come in.

Optional X verification uses a separate 10-minute essential browser cookie, a one-use authorization request and PKCE. We do not persist the X access token, request offline access or post on your behalf. The account-linking audit and identity reservations are retained to enforce the one-replacement policy and prevent duplicate rewards. My Page shows wallet-scoped points, mission and linked-account records; visiting it does not award points or send a transaction.

Ammora does not use advertising trackers. Optional product analytics starts only after you select Allow analytics. It uses a signed first-party browser cookie for up to 180 days so return visits can be measured. Do Not Track and Global Privacy Control signals disable it. The landing page queues a small event batch and sends it only to Ammora’s own server; failed batches are bounded and then discarded. Product events remain in Ammora’s database until an operator removes them.

RainbowKit and wagmi connect directly to your installed browser wallet. This app doesn’t use a WalletConnect relay or QR connection. Your browser saves essential connection preferences separately from your registration. Your wallet and the Ethereum Sepolia and GIWA Sepolia RPC providers may handle network requests under their own privacy policies.

Signing the message doesn’t send a transaction or prove activity on GIWA Sepolia. We don’t currently support verification for smart contract wallets.

Weekly post verification sends only the allowlisted public X post URL to X’s official oEmbed endpoint. The temporary campaign code lasts up to 30 minutes, ending no later than the next UTC week and is bound to your waitlist wallet and browser session. We store a keyed hash of the code rather than keeping the code as a permanent credential.

Your choices

Joining is optional. You can ask the Ammora team to update or delete your offchain waitlist details, or withdraw your consent to product updates. Deleting an offchain record cannot reverse a completed onchain deposit.

Product analytics is separate from the waitlist consent. Disabling it stops new collection, clears the local analytics session, and asks Ammora to expire the pseudonymous browser cookie. Because analytics is not linked to your waitlist contact details, disabling it does not automatically identify or delete earlier pseudonymous event rows.