RNNR CALLS / EDITION 2026-10-19.1
RNNR Calls Privacy Policy
Version 2026-10-19.1. Applies when published with the service. Controller: 1v1me.me, Inc. Contact [email protected] for requests and privacy questions.
Our approach
RNNR Calls is a regenerative community-game experiment, not an advertising audience business. The application contains no behavioral advertising, third-party analytics SDK or sale-of-data feature. Zero platform take rate is an economic choice; it does not mean the service can operate without account and game records. A public wallet is pseudonymous, not necessarily anonymous.
Information this implementation processes
Account and authentication: public Solana wallet address, chosen display name, wallet-signature challenge and signature during verification, a hashed session bearer token, anti-forgery token, session expiry, short-lived nonce, pairing code and pairing approval. Signature bytes are checked by the server; this application does not retain login signatures after verification. It does not ask for personal wallet private keys, seed phrases, payment-card details or account passwords.
Game and token records: room names, descriptions, membership, invitations, member-entered scores and messages; call text, rules, contributions, timestamps, outcome confirmations, referee choices, support tickets, account balances, net standings and ledger entries. In real-token mode it also stores transfer intents, public wallet/transaction references, prepared messages, finalized receipts and signed custody withdrawal transactions required for safe retry and reconciliation.
Acknowledgments: the authenticated account, server time, site origin, policy version, declaration flags and acknowledgment wording reference. Age is a self-declaration. No date of birth, government-ID verification or location eligibility determination is implemented in this release.
Technical information: the server sees request paths, headers, network addresses and timing to operate the service. It maintains short-lived in-memory rate-limit counters and writes startup and limited error messages. A hosting provider or reverse proxy may produce additional security/access logs according to its deployed configuration. We do not promise that network addresses are never processed or that every provider retains identical records.
Device storage and sessions
The essential calls_session cookie is HttpOnly, SameSite=Lax, and Secure when HTTPS is used. Its maximum session life is 30 days, and signing out invalidates that session. Login and withdrawal-signature challenges and browser pairing expire after five minutes. Cleanup periodically removes expired authentication records.
The browser may store deposit-recovery transaction signatures in local storage. These are not private signing keys. Clearing browser data removes local information but does not delete the server balance, unsettled obligations or public blockchain transactions.
The separate downloadable preview stores only synthetic sample state in the browser. It is not connected to live funds. Browser persistence may be unavailable in restrictive viewers; the preview then uses temporary in-memory state.
Why we use these records
Records are used to authenticate requests, maintain accurate balances, prevent duplicate transfers, reserve and settle calls, display rooms and standings, share invitations, reconcile interrupted transactions, handle support and investigate abuse or accounting errors. We also use necessary records to fulfill applicable legal duties and respond to valid rights requests. Acknowledging this notice is not consent to unrelated advertising or a future identity-verification program.
Visibility and third parties
Room members can see room activity and calls. Call participants can see its terms, contributions, proposals and outcomes. People who possess a call invitation may view and join that call without being members of its room. Displayed standings include settled net results, not another player's complete wallet balance. Your account history and transfer controls require your session.
A rich-link image can reveal the claim and amount when you choose that option. Generic previews omit that text, but anyone with the link may still open the underlying call. Messaging providers can fetch a preview; recipients can retain or forward copies. Sharing into iMessage, Telegram or another service involves that service's own practices. External search is only opened when you choose it and may receive the search terms.
In live mode, the configured Solana RPC provider receives blockchain queries, addresses and transaction data. The blockchain publishes its own transfer records. Wallet apps process the signing and connection interactions you initiate. Hosting, network, backup and email providers may process the data required to operate their respective services. The release package does not choose or claim that a particular hosting/RPC/email vendor is already deployed. The operator must update this notice if the installed configuration materially changes the processing described.
Authorized operators can access the server's stored records and custody signer. They are not all public, but this is not an end-to-end-encrypted service against its operator. We may disclose necessary information for lawful requests, security, professional advice, or a service transfer subject to applicable safeguards; those purposes do not authorize unrelated data commercialization.
Retention and requests
Authentication records have the expiry rules above. The room activity feed retains up to 1,200 recent event records across the instance; individual views show a smaller recent window. Core ledger entries, calls, transfers, support tickets and acknowledgment records do not yet have an automatic deletion schedule. They may be needed for balances, pending disputes, reconciliation, abuse prevention and applicable retention duties. Backups can also retain earlier copies.
The account menu provides a scoped JSON export of visible account and gameplay data. This is a convenience export, not a promise that its recent-history window is the entire set of records the operator may hold. Contact [email protected] for access, correction, deletion, portability, objection or other rights that apply in your location. Verification proportionate to a request may be needed. We will explain information that must be retained for outstanding balances, transaction integrity or mandatory duties. We cannot erase a blockchain transaction or another person's independent copy.
The app is not intended for minors. Contact support if an account appears to belong to a minor or if information should not have been collected. The operator should address the account and any outstanding obligations; this notice does not claim automated underage detection or account deletion exists.
Changes and contact
Material changes to data collection, optional tracking or providers should be reflected here before the new processing begins. Applicable privacy rights and statutory thresholds depend on the service's actual operation and the user's location. This notice does not claim certification under every privacy law. Contact [email protected] with the minimum information needed, and never attach a wallet seed phrase.