Privacy Policy

• Email address: to send a 6-digit code that confirms you can read the inbox, and then to send a copy of your lease code
• To limit repeated claims and code submissions: a keyed hash of your email address when you ask for a claim code, a keyed hash of your IP address when you ask for a claim code, and a keyed hash of your IP address when you enter a claim code. The hash is made with a server key, so it can't be reversed without that key. We do not store the raw IP address with the claim. Counting runs in a 15-minute window. When the window ends, the same stored rows are reused and the count starts again. Resetting the window does not remove the stored counters

If you create a referral code or are referred

• Your email address, the referral code we issue you, the date you accepted the referral terms, and whether and when the code was paused
• If you claim with someone's referral code, from a link or typed in: your email address, linked to the referrer's code so the referral is credited once
• For each referred license that earns a reward: the amount credited to the referrer, the rate it was calculated at, when it vests, and the last four characters of the license id
• If you request a payout: the USDC on Base address you give us, the amount you requested, the USDC amount we sent, the request and payment times, the Base transaction hash, the admin who paid or rejected it, and the reason if we reject it
• For a payout email code: your email address, a hash of the six-digit code, its expiry, the number of verification attempts, including a successful check, and when it was used
• To limit repeated payout codes: a keyed hash of your email address when you ask for a payout code and a keyed hash of your IP address when you ask for a payout code, kept as counters that limit repeated attempts
• To limit repeated payout code entries: a keyed hash of your IP address when you enter a payout code, kept as a counter that limits repeated attempts. We do not store the raw IP address

If you sign in to your account

• Your email address, a hash of the six-digit code, its expiry, the number of verification attempts, including a successful check, and when the code was used
• To limit repeated sign-in codes: a keyed hash of your email address when you ask for a sign-in code and a keyed hash of your IP address when you ask for a sign-in code, kept as counters that limit repeated attempts
• To limit repeated sign-in code entries: a keyed hash of your IP address when you enter a sign-in code, kept as a counter that limits repeated attempts. We do not store the raw IP address

If you link a lease to your account

• On the link code: the license id, the lease code, the Unetwork user id, when the lease starts and when it ends, a hash of the link code, its expiry, the number of verification attempts, including a successful check, when the code was used, when it was revoked, and the admin who created it
• On the lease bound to your account: your email address, the license, the lease code, the Unetwork user id, when the lease starts and when it ends, that the link came from a code, when the link was verified, and when it was revoked
• To limit repeated link attempts: a keyed hash of your email address when you enter a link code and a keyed hash of your IP address when you enter a link code, kept as counters that limit repeated attempts. We do not store the raw IP address

• Confirm your email, then show your lease code on screen and email you a copy
• Log the claim against our inventory
• Attribute each referred license to the code that brought it in, and calculate the referrer's earnings from that license
• Verify a payout request, review it, and send USDC on Base
• Prevent self-referral and referral abuse
• Respond to support queries you initiate
• Enforce claim limits so repeated requests cannot take the free inventory
• Send a 6-digit account sign-in code and open the account when it matches
• Bind a lease to the signed-in email when a link code matches
• Limit repeated sign-in and lease-link attempts
• We do not use your data for marketing, profiling, or advertising

Referral and payout records

• A referral code, the email bound to it, and the accruals it earned are kept until you ask us to delete them. No cleanup job removes them.
• A payout request, its address and its transaction hash are kept until you ask us to delete them.
• An expired payout email code is deleted by an hourly cleanup.
• The keyed payout counters are kept until you ask us to delete them. No cleanup job removes them.
• A payout is a public Base transaction. Its address, amount and transaction hash stay on the blockchain, and Ekata Nodes cannot delete them.

Account sign-in and lease links

• An expired account sign-in code is deleted by an hourly cleanup.
• A keyed sign-in counter is kept until you ask us to delete it. No cleanup job removes it.
• A lease-link code is kept until you ask us to delete it, including after it expires, is used, or is revoked. No cleanup job removes it.
• The account email bound to a linked lease is kept until you ask us to delete it, with the license, the lease code, the Unetwork user id, and the lease start and end. No cleanup job removes it.
• A keyed lease-link counter is kept until you ask us to delete it. No cleanup job removes it.

• Request a copy of the data we hold about you
• Request deletion of your data at any time
• Request correction of inaccurate data
• Deleting your referral data stops future referral earnings from that code
• A payout we already sent stays on the Base blockchain, so deleting your data does not remove it