DONOBLOCK_EN
  • 🔵Litepaper
  • 🟢Whitepaper
  • 2. Introduction
  • 3.Background and Strategy
    • 3-1 World Giving Index
    • 3-2 plan to expand the base of donations
  • 4. DonaBlock Vision
  • 5. DonaBlock Giving Protocol
    • 5-1 DonaBlock.1 Brand mall Connect - DonaBlock Brand Mall
    • 5-2 DonaBlock.2 Bazaar Connect - DonaBlock Bazaar
    • 5-3 DonaBlock.3 - DonaBlock Store
    • 5-4 DonaBlock Ecosystem Participants & Contributors
  • 6. DonaBlock.1 Brand Mall Connect
    • 6-1 Dona Brand ShopBack
    • 6-2 Dona Brand ShopGive
    • 6-3 DonaBlock Browser Extension
    • 6-4 DonaBlock Mobile App
    • 6-5 Service Flow
    • 6-6 Donate Crypto
    • 6-7 Sustainable Development Goals -Impact Index Funds map to the United Nations’ Sustainable Develop
  • 7. DonaBlock.2 Bazaar Connect
    • 7-1 Dona Bazaar ShopBack
    • 7-2 Dona Bazaar ShopGive
    • 7-3 Active consumer participation- volunteer
    • 7-4. BLOCK.2- Architecture
  • 8. DonaBlock.3 Offline Store Connect
    • 8-1 PAYMENT CARD SECURITY Oauth 2.0 Protocol Flow
  • 9. DonaBlock Donation Ecosystem
    • 9-1. How to Donate Crypto to Support Charities
    • 9-2 DonaBlock Giving Fund - Index Fund
    • 9-3. DonaBlock Giving Fund -Impact Fund
    • 9-4 Cryptocurrency Donation Flow
    • 9-5 DonaBlock NFT Fundraising
  • 10. Crypto Fundraising Solution
    • 10-1 DonaBlock Crypto Wallet
    • 10-2 Services for volunteer- Create a Fundraiser
  • 11. DonaBlock Dashboard System
  • 12. DonaBlock Fame Evaluation System
    • 12-1. Volunteer Evaluation System
    • 12-2 Method and the variables that determine
  • 13. DonaBlock Service Flow
  • 14. DonaBlock Technology
    • 14-1 System Architecture
    • 14-2 Core Layer
    • 14-3 Commerce Layer
    • 14-4 Application Layer
    • 14-5 Structure of API and Other Infrastructures
    • 14-6 Quantum cryptography & SECURITY
  • 15. DonaBlock Data Architecture
    • 15-1 Core Data : On-Blockchain Data
    • 15-2 Reference Data :
    • 15-3 Data Ownership : Public / Private
    • 15-4 Configuration and Technical Specifications
  • 16. DonaBlock Token Economy
    • 16-1. Token Flow
    • 16-2. DonaBlock Token and DonaGive Token
    • 16-3 Block-Fame
    • 16-4 Volunteers Charity Campaign Reward
    • 16-5 Consumer Rewards
  • 17. Token Economy Strategy & Risk Management
  • 18. DonaBlock Roadmap
  • 19. Token Allocation
  • 20. Partner with The DonaBlock
  • 21. Audit
Powered by GitBook
On this page
  1. 6. DonaBlock.1 Brand Mall Connect

6-4 DonaBlock Mobile App

Previous6-3 DonaBlock Browser ExtensionNext6-5 Service Flow

Last updated 1 year ago

DonaBlock may make available a mobile app for officially supported mobile operating systems, Android, iOS ("Supported Mobile Operating Systems"), to enhance your shopping experience ("DonaBlock Mobile App")

Affiliate Stores Tracking

The DonaBlock Mobile App will aggregate and present only Affiliate Stores, of which when making a selection the DonaBlock Mobile App will create a tracking ticket and start a "ShopBack" rewards shopping session using an Affiliate Store's native mobile app or on an Affiliate Store's site within the DonaBlock Mobile App.

If you start a shopping session at an Affiliate Store's site within the DonaBlock Mobile App, it may set a cookie on your device, visible within the DonaBlock Mobile App only, for the purpose of tracking your shopping session and crediting your "ShopBack" rewards.

If you start a shopping session at an Affiliate Store's native app via a DonaBlock Mobile App link, the Affiliate Store is responsible for tracking your use of their native mobile app, and this may consist of using cookies or other tracking identifiers that are shared with DonaBlock in order to complete your shopping session and credit your "ShopBack" rewards.

User Referrals

The DonaBlock Mobile App may prompt you to share a referral code ("Referral Code") via link or text. When sharing your Referral Code, your display name ("Display Name"), as selected at signup or while editing your profile, may be shared with future users you refer. As such, both your Referral Code and Display Name should be considered potentially public data.