Skip to main content

Frequently Asked Questions

What is the difference between anonymous login and not being logged in?​

From the perspective of C-end users:

  • There is no difference in initial usage between anonymous login and not being logged in; neither requires registration
  • Anonymous login users have a unique user identifier. During the validity period on the same device, users can generate independent private data
  • Compared to not being logged in, anonymous login can be converted to a formal user. Private data generated during anonymous login will be automatically inherited under the formal username

From the perspective of application developers:

  • The anonymous user generated by CloudBase anonymous login is essentially a valid user with a unique user ID. This allows creating private database and cloud storage data for it, as well as establishing personalized access policies in conjunction with security rules
  • The not being logged in mode is purely access without login status; accesses in this mode will not be included in user tracking statistics
  • Under default permissions, users who are not logged in cannot access any CloudBase services or resources. In contrast, anonymous login allows corresponding resource read and write operations with basic permissions, and can also implement more granular control in conjunction with security rules

Will anonymous users expire?

CloudBase's expiration policy for anonymous users is: only one anonymous user exists per device at the same time, and this user never expires. However, if a user manually clears the device or browser's local data, the anonymous user's data will be cleared accordingly. Calling the CloudBase anonymous login API again will generate a new anonymous user.