Privacy & retention
Testnet beta privacy notice · Updated October 25, 2026
About this notice
Dokora is a decentralized application that uses public smart contracts. This website also uses hosted services for account, social and support features. This notice explains how information is handled through those features and describes current beta practices. Wallet, authentication, network and email providers also handle information under their own policies, as explained below.
Support, privacy and legal inquiries: support@dokora.xyz.
Real-USDC services are not enabled in this deployment.
Wallet addresses are public identifiers, not a guarantee of anonymity. An address can be linked to your profile, other addresses, transactions and information available elsewhere. Do not publish personal information about yourself or another person that you do not want to become public.
Information we collect and why
- Account and wallet information. Your login address, verified trading-wallet links, profile fields and images, sign-in challenges, and session records let us authenticate you, maintain your profile and associate activity with the correct wallets.
- Social and service information. Posts, replies, interactions, follows, groups, memberships, invitations, chats, read states, alert preferences and referrals support the features you use and their access and eligibility rules.
- Support information. Requests, reports, their references, attachments, responses and direct email correspondence let us investigate problems, moderate reported content and handle account or privacy requests.
- Agreement records. If active Terms require acceptance, we record the authenticated login address, document version and hash, acceptance time, explicit agreement action and service origin. Draft Terms do not request or record acceptance. These records document the agreement separately from a wallet sign-in.
- Public blockchain information. We read and index wallet addresses, transactions, holdings, proposals, votes, badge ownership and reward activity to display market information, verify activity and reconcile transactions and eligibility.
- Spending limits and reconciliation. For wallets on the legacy app-budget path, Dokora stores spending-cap settings and request/reconciliation records, including linked wallet addresses, call details, amounts, timestamps and outcomes, even when the optional cap is disabled. These support budget continuity and reconciliation and are included in account exports.
- Technical and security information. Requests expose network addresses and other connection metadata to hosting and security services. Server access logs can record network address, request time, method, path, response status and duration. Authentication and rate-limit records help protect the service and prevent abuse.
Information comes from what you submit, your browser and selected wallet services, other users who interact with you or report content, and public blockchain records. Optional profile descriptions and images are your choice; authentication and access checks are needed for the features that require them. Dokora does not ask you to upload a private key or recovery phrase.
Public information and limited-access information
Your profile, username, bio, profile images, public posts and replies, follows, public group information, and verified login/trading-wallet association are public. Blockchain trades, balances, proposals, votes after reveal, badge ownership and rewards are public and cannot be erased by deleting a Dokora profile. Other people, search services and blockchain explorers may retain copies or link them with other information.
Private group information and chats are subject to the service's access rules. People invited to a private group can see its name before accepting; accepted members can see its description and image and read its chat history. Chats are not end-to-end encrypted: eligible conversation participants and people with authorized server access can read them. Participants can copy or share what you send; an access-controlled chat cannot prevent that.
If you enable restricted trading, its paired wallet and executor addresses, permission expiry, daily cap and recorded daily spending are public blockchain information. Changing permissions or deleting your profile does not erase that history.
The optional independent client can interact with a separately reviewed public referral registry. Registering, linking wallets, enrolling a referrer and claiming there publish permanent blockchain associations. These links cannot be reassigned or erased through Dokora account tools. Existing website referral records are not automatically copied to that registry; check the selected deployment before approving a transaction.
Uploaded profile images are cropped and re-encoded to remove embedded image metadata. Approved market images remain public market records. Removing image metadata does not remove personal information visible in the image itself.
Cookies and browser storage
Dokora uses sign-in challenge and session cookies for authentication. Challenges expire after five minutes and profile sessions after seven days; server session identifiers are stored as hashes. Browser storage remembers wallet choices, display and trading preferences, referrals, and pending transaction or vote-reveal recovery state. Protected execution and withdrawal/revocation recovery records can include wallet identities, call details and transaction identifiers and remain across browser reloads. A remembered address is not authorization.
The current permissionless validator deployment uses self-managed reveal. Your decision and secret stay in this browser tab and your downloaded backup; this route does not upload a backup to Dokora or provide automatic reveal. You must reveal the exact vote within its onchain window, including after a manual decision when reveal remains available. The downloaded backup is readable JSON, not an encrypted wallet backup: keep it private until reveal and retain it until the vote is settled. Losing it can prevent reveal and cause validator penalties. An imported backup is parsed locally; a submitted reveal makes its decision and secret public onchain.
Incoming chat previews appear in account notifications for users with conversation access. Optional browser notifications can show validator-request information on your device; manage them in Settings and browser permissions.
Trading-wallet services use their own session storage. Dokora's browser recovery state can include the provider's user identifier, wallet and owner addresses, sign-in method and, for an existing legacy email account, its email address. This does not make the email address a public profile field. Current wallet-only sign-in does not migrate legacy email or Google accounts; check the recovery guide before ending a funded legacy session.
Dokora currently does not change its behavior in response to a browser Do Not Track signal. Wallet and infrastructure providers may recognize activity across services under their own policies. Browser controls can limit cookies or clear storage, but doing so may end access or remove transaction and reveal recovery information. Save what you need and verify wallet access first.
Services involved and disclosures
Hosting and Cloudflare handle traffic and security metadata, including network addresses. Cloudflare R2 stores encrypted operational backups. Coinbase Developer Platform and Base account services handle selected wallet authentication and signing; RPC providers receive blockchain queries and submitted transactions.
If WalletConnect is enabled and selected, Reown and your chosen wallet handle pairing. Opening All wallets sends wallet-name searches and logo requests to Reown's directory, without your account address, session cookies or pairing link. These requests still expose ordinary connection information such as your network address. Wallet services can contact their own security and diagnostic endpoints.
Zoho Mail handles direct support email and received support notifications; Resend handles notification sending when enabled. Providers may process information outside the place where you live. Their policies describe their own collection, processing and retention; a Dokora account request does not automatically delete an independent provider account or its records.
Telegram delivers proposal notifications and operational alerts to the configured private administration chat. Proposal notices can include the proposal name, symbol, category, description, proposer wallet address, source link and review status. Operational alerts include service-health information. These notifications are separate from user-to-user chats and direct support email; Telegram handles delivered messages under its own policies.
Public content is disclosed to visitors, and group or chat content to users allowed by its access rules. People with authorized service access can read nonpublic records to maintain the website, investigate reports, provide support and carry out privacy or recovery requests. Information may also need to be preserved or disclosed in response to an applicable legal obligation or valid legal process.
Support attachments and email
Files attached to in-app support requests are private to your signed-in account and people with authorized support access. They are stored with account data and included in encrypted operational backups. Screenshot images are re-encoded without embedded image metadata; PDF and text contents are retained as submitted. Attach only what support needs. Do not send wallet backups, recovery phrases, private keys, passwords or sign-in codes.
Account exports include your support attachments. Account deletion removes attachments from the live service, including attachments to deletion requests. Backup and separately exported support or operational copies are not erased immediately. Files otherwise follow the support-request retention below.
When support email notifications are enabled, Resend sends a notice to our Zoho support inbox. The only request information included is its request ID and submission time. Your wallet address, request text, attachment names and uploaded files remain in Dokora and are not included in these notifications. Replies remain in Dokora; replying to a notification is not a reply to the user. Deleting a profile cancels notifications that have not begun sending, but does not recall sent email or automatically delete provider-held copies.
Direct support emails also contain whatever contact information, text and files you send. Messages and replies are stored separately from in-app requests. There is no automatic expiry for support emails during the beta; deleting a Dokora profile does not automatically erase this correspondence. Include separately held emails or files in a privacy request if you want them reviewed.
Retention
- Profile, social and chat records remain while your account is active unless removed through an available feature or approved deletion request. Support requests remain until reviewed and explicitly removed by someone with authorized support access; there is no automatic expiry yet.
- Profile sign-in challenges expire after five minutes and sessions after seven days. Expired challenge, session and rate-limit records are cleaned on account-service activity.
- Public blockchain data remains on the network. Transaction, reward, referral, security and deletion records can remain after profile deletion for reconciliation, abuse prevention, recovery or applicable legal obligations. Account deletion does not erase counterparties' records.
- Legacy app spending-budget settings and request/reconciliation records currently remain after profile deletion for budget continuity and reconciliation, including wallet associations in those financial records. This retention is separate from active public profile-wallet links and ordinary account preferences.
- Recorded agreement acceptance and the exact published document remain separately from an active profile for agreement evidence. Privacy-request case metadata can also remain separately from ordinary support content for handling and accountability. Retention periods and necessary legal holds require review by people responsible for the service; these records are not automatically erased with a profile.
- Encrypted operational backups are retained under manually managed policies and protected retention locks. They currently have no automatic age-based deletion schedule. Deletion from the live service does not immediately erase those copies. Approved deletions must be reapplied before a restored backup is made public.
- Infrastructure logs and independent provider records follow the relevant operational or provider settings. This beta notice does not specify a fixed retention period for every infrastructure log or provider record.
These limitations describe current practices; they do not remove any obligation to honor a valid privacy request or delete information when applicable law requires it. They are not a promise of immediate erasure from every provider or backup.
Your account controls
Use account tools to review and download supported account records, edit your profile, or request account deletion. Visit Support to report content or ask for help. An export is not an export of every independent provider's records, every incoming chat message or the entire blockchain.
Automatic deletion requires a fresh, purpose-specific signature from your original login wallet and waits at least 24 hours. You can cancel from account tools until processing begins. Eligible requests are checked every five minutes; unavailable safety checks or a missing recent backup delay processing. Check account tools for status—automatic email confirmations are not sent.
Before scheduling, save your data and confirm independent access to both wallets. Withdraw trading-wallet funds and resolve coin holdings, stewardship badges, escrowed offers, pending proposals and claimable rewards or refunds. Registered validators, referral accounts and group owners need an assisted review. Blocked requests are not automatically resumed: resolve the issue, cancel and submit a fresh request, or contact support. Old support tickets and assisted requests do not start the automatic timer.
Deletion removes your live profile and images, eligible authored social content, sent chat messages, follows, memberships, ordinary server-stored preferences, active public profile-wallet links, sign-in sessions and prior in-app support text. Browser preferences and local recovery records may remain until you clear them. Public-post replies follow the post's deletion rules. A minimal deletion ledger and redacted completion record remain, along with public blockchain/market data, retained transaction/security records, counterparties' records, encrypted backups and separately held support email.
Deleting a profile does not delete its wallets, move funds, cancel transactions or revoke blockchain permissions. Balance hiding affects only your browser display. Profile sign-out and trading-wallet sign-out are separate. Read the recovery guide before clearing browser storage or ending a session you need to recover funds.
Referral invitations
When you visit an invitation, this browser tab remembers the public inviter address for up to seven days, or until removal or sign-out. The address is only a hint: signing in or creating a profile does not enroll a public referral. Review and explicitly confirm enrollment onchain before your first trade. Enrollment in the independent client does not clear the hint in this tab. Coinbase and Phantom app-browser links carry only that public inviter address so the invitation survives switching apps; they do not carry your session, signature or WalletConnect pairing link. Confirmed referral attribution cannot be changed through account tools.
Privacy questions and rights requests
Contact support@dokora.xyz for privacy questions, data requests or help if you cannot sign in. Identify the information and request clearly and share only what is needed. We may ask you to verify control of your original login wallet before acting on an account request. Email alone does not authorize deletion or wallet changes.
Depending on your location and the law that applies, you may have rights to access, correct, delete or obtain a copy of personal information, object to or restrict certain uses, withdraw consent where processing relies on it, appeal a request decision, or complain to a privacy regulator. The account tools do not limit rights available under applicable law. If automatic deletion is blocked, contact support for a separate review of your privacy request; a financial or account dependency does not by itself decide which personal information must be retained.
Children's information
Dokora is intended for people who are at least 18 and of legal age to use the service where they live. If you believe a child has provided personal information to Dokora, contact support so it can be reviewed. Do not include unnecessary information about a child in a public post or support attachment.
Changes to this notice
October 25, 2026: clarified public contracts and hosted website features, self-managed validator reveal and Telegram notifications, and standardized the project contact at support@dokora.xyz. These disclosures describe existing behavior; this update does not change data collection or account controls.
The current notice and its effective date are posted here. Material changes are identified in an updated notice on this page. Where applicable law requires additional notice or consent for a change in processing, that requirement still applies; merely updating this page does not supply that consent.