Your data.
Your business.
Privacy information for the PayUp website and early-access registration.
What this preview does
PayUp is a product concept. This preview does not connect to a wallet, accept deposits, issue a payment card or process purchases. The dashboard uses sample data only.
What stays on your device
Card finishes, saved shopping categories, demo transactions and display preferences can be stored in your browser. A local early-access preview stores its example X username, public Solana address and sample code on this device only. Live registration stores an opaque receipt token and whether you have revealed your code, so this browser can recover your entry. Anyone with access to that token may view the entry; do not share browser storage exports. Clearing local storage does not delete a live server-side entry. No advertising analytics are included.
Early access, when enabled
The form labels local preview and live registration separately. Local previews are not sent to PayUp and their codes are not valid registrations. In live mode, your X username is sent when you request the arithmetic question and held temporarily in the session. When you complete registration, your X username and public Solana address are stored together with a unique public code, timestamp, privacy-notice version and a hashed receipt token for early-access administration and duplicate prevention. We do not ask for your email address, country, passwords, seed phrase or private key. The form does not prove that you control the X account or Solana address.
Security and retention
A first-party, HTTP-only session cookie supports the live form, arithmetic check and request protection. It is marked SameSite=Strict and Secure on HTTPS. Rate limiting uses a keyed hash of the network address rather than storing the raw address in the registration file. Rate counters expire after an hour and are removed on later requests. Your hosting provider may keep separate access logs. Entry details are retained for up to 90 days by default and are pruned on later registration requests or the operator’s scheduled cleanup. The configured retention period appears in the live operator details below. A register of previously used codes, without usernames or wallet addresses, is retained to prevent code reuse. Server session cleanup is subject to the hosting configuration.
Sharing on X
Revealing a code does not publish it. A configured comment link opens X with the code in a reply composer; you decide whether to submit it. A public comment may publicly associate your X profile with your code, but PayUp does not publish your wallet address. Like, repost and comment activity is not automatically verified. X has its own privacy practices. A code is not a password, guaranteed reward, token allocation or payment-card approval.
Operator details
Live registration is disabled in the delivered package until the operator configures their real identity and privacy contact. The live form displays those details when enabled. Do not submit real personal data to a local preview.
External websites and fonts
Shopping links open a retailer’s website, which has its own terms and privacy practices. Product searches are sent to Amazon only when you choose to search or open a product category. This site requests fonts from Google Fonts when available; those requests can reveal your IP address to that provider. The site uses system-font fallbacks when external fonts are unavailable.
Updates and requests
Live launch details, providers and operator contact information must be published before this preview becomes a production financial product. You can request access to or deletion of a live early-access entry through the privacy contact displayed in the form and operator details above. The operator must establish an appropriate way to verify such requests; the public registration code alone is not proof of identity.